She wrote CRM service code in Germany in 2000. Now she runs the product line at Microsoft that defines how 228,000-person organizations talk to their customers. The distance between those two points is a story about staying close to the problem while the titles got bigger.
Corporate Vice President - Dynamics 365 CX Applications
In 2000, Devasena Rajamohan was writing CRM service code at SAP's offices in Germany. Not architecting. Writing. The kind of work where you know exactly what breaks at 2am and why. That ground-floor fluency - in the code, the customer, the edge case - is the thread running through a career that eventually landed her as Corporate Vice President at Microsoft, overseeing the full product surface of Dynamics 365 Customer Experience Applications.
The portfolio she leads now is substantial: Customer Insights, Sales, Customer Service, Field Service, and an expanding layer of Copilot-driven AI capabilities woven through all of it. Her team is global - product managers, engineers, data scientists - and the mandate is to make enterprise customer engagement feel less like enterprise software.
That's not an easy assignment. Enterprise CRM is a category defined by complexity, integration debt, and users who wanted something better but accepted something that worked. Rajamohan came up through exactly that world. Six years at SAP Germany. Then chief architect for cloud CRM service. Then running customer service and industries for SAP CX. Then to Microsoft.
"Organizations are evolving toward frontier service models powered by agentic AI."
Devasena Rajamohan, Microsoft Ignite 2025The phrase "agentic CX" is one she's been using publicly since at least Ignite 2025. The premise: customer service doesn't just get assisted by AI - it gets restructured by it. Agents that can act, not just respond. Resolution loops that close without a human in the chain. She's building toward a world where calling customer service feels less like holding music and more like a solved problem.
Rajamohan studied Electrical and Electronics Engineering at Government College of Technology in Coimbatore, graduating in 1997. It's a familiar path for Indian engineers of her generation - rigorous technical fundamentals, then software, then the world. What's less typical is the specific arc: not to the Valley immediately, not to a startup, but to enterprise software in Germany, then two decades of patient ascent through the hardest problems in B2B software.
The EE background matters. People who start with circuits think differently about systems. Latency is physical. Failures cascade. You can't hide bugs behind a refresh button. That engineering instinct shows up later when she's co-innovating at AppHouse in Palo Alto with US utilities and European companies - trying to build customer service software that works for industries with real operational stakes.
Three days of intensive co-innovation sessions. The kind of thing you do when you believe the product should fit the customer, not the other way around.
Individual contributor - deep code
Architecture to engineering leadership
Executive - product strategy + global team
Rajamohan holds patents in enterprise software - a distinction that separates her from most executives who've fully migrated into leadership. Her filings cover business object models that enable consistent interfaces across industries and departments, and issue tracking systems with predictive severity scoring for support tickets. The rare combination: she has the IP and the org chart.
Gartner and Forrester don't hand out Leader designations for roadmaps. They're backward-looking. These are the products her teams actually delivered.
"Frontier service models" is the phrase Rajamohan uses for where she's pointing. It's a specific idea: customer service organizations don't just add AI as a layer - they reorganize around it. The agent becomes the first responder. The human escalates into specialist territory. Resolution rates go up; hold times go down; the entire economics of a contact center shift.
Dynamics 365 Customer Service is the product carrying that bet. The voice channel launch was one signal. Copilot integration across the full CX suite was another. The 2025 Gartner and 2026 Forrester recognition suggests the market agrees the platform is moving in the right direction.
What's unusual about Rajamohan's position is the span. Most CVPs own a product. She owns a product category - and the AI thesis that cuts across it. Customer Insights feeds Sales feeds Customer Service feeds Field Service. When AI works well, those connections become intelligent. When it doesn't, the failure is spectacular. She's responsible for making sure it's the former.
The patents she holds in predictive issue tracking suggest she's been thinking about this specific problem - how do you score a customer service ticket before the damage is done - since before "agentic AI" was a thing people said at conferences.
Unified customer data platform - the foundation of personalization at scale. Brings together behavioral, transactional, and observational signals.
Native voice channel, conversational AI, Copilot-assisted resolution. The first-party approach means no middleware between the AI and the customer.
AI-assisted selling tools built into the workflow - not bolted on. Copilot surfaces context where reps already work.
Scheduling intelligence, technician dispatch, and IoT-connected service - the physical-world layer of CX that most CRM platforms ignore.
From 2000 to 2006, Rajamohan was writing CRM service code at SAP in Germany. Most CVPs have management as their first job. She had commits. That's not a minor distinction - it's the difference between understanding enterprise software and having an opinion about it.
She started at SAP writing CRM service code. She's at Microsoft running the CRM platform that competes with SAP. The product she built at the bottom of her career is now the market she leads from the top. The circle is unusually tight.
Her LinkedIn profile URL ends in "28191217" - a relic of early professional network registration. A small timestamp buried in a hyperlink, a reminder that even the most senior executives were once early adopters figuring out their digital presence.
Three intensive days. US utilities. European companies. Co-innovation on customer service models. This was the kind of session where the product team shows up to watch customers work, not the other way around. The methodology matters as much as the title.
Electrical and Electronics Engineering at Government College of Technology, Coimbatore, 1993-1997. The discipline that trains people to think about systems, fault tolerance, and cascading failure. Then applied to enterprise software for the next 25 years.
Active patents in enterprise software are rare at the CVP level - most executives have drifted fully into leadership by the time they reach this altitude. Rajamohan has the filings and the org chart simultaneously. The intellectual property and the people to ship it.
The Dynamics 365 platform under Rajamohan's leadership spans a remarkable breadth of cloud infrastructure, AI services, and enterprise tooling.
"Bringing voice capability natively into Customer Service - along with conversational virtual agents and AI-infused capabilities throughout the call - represents a major step forward."
DEVASENA RAJAMOHAN - ON THE DYNAMICS 365 VOICE CHANNEL LAUNCH