Where you will run into Microsoft Dynamics 365 (5)
- Microsoft 365 E3 or E5 shop where IT owns the CRM decision and an enterprise agreement renewal is near.
- Company running Business Central or Dynamics 365 Finance as its ERP, where the CFO wants one vendor for ERP and CRM.
- Buyer rolling out Microsoft 365 Copilot who assumes the CRM must be Dynamics for Copilot to use customer data.
- Internal Power Platform team that wants to extend its Power Apps and Power Automate skills to sales and service.
- Price-driven evaluation where procurement puts Sales Professional at $65 next to Sales Cloud Core.
Competitor snapshot (9) Verified facts
| Dynamics 365 Sales list prices (as of October 2026) | Sales Professional $65, Sales Enterprise $105, Sales Premium $150 per user/month, paid yearly. Microsoft Relationship Sales (Sales Enterprise plus LinkedIn Sales Navigator) has variable pricing and a 10-seat minimum. Source |
|---|---|
| Dynamics 365 Customer Service and Contact Center list prices (as of October 2026) | Customer Service Professional $50, Enterprise $105, Premium $195 per user/month, paid yearly. Contact Center $110, discounted when bought with Customer Service Enterprise. Azure Communication Services is priced separately. Source |
| Dynamics 365 Field Service list prices (as of October 2026) | Field Service $105 and Field Service Contractor $50 per user/month, paid yearly. Resource Scheduling Optimization is $30 per resource/month. Prebuilt agents need Copilot Credits. Source |
| Licensing model | Each user's first Dynamics 365 app must be a base license, always the highest-priced option. Cheaper attach licenses only go to users with a qualifying base license. Team Members licenses are read-only. Source |
| Copilot and agents in Dynamics 365 | Sales Enterprise includes Copilot in Dynamics 365 and agentic capabilities; Sales Premium adds 1,000 Copilot Credits. Agents run on Copilot Credits and, per Microsoft, need an Azure subscription. Source |
| Copilot Studio and Microsoft 365 Copilot pricing (as of October 2026) | Copilot Studio is $200 per month for a 25,000-credit pack, or pay-as-you-go, with up to 20% off for pre-purchase. Microsoft 365 Copilot is $30 per user/month paid yearly on top of a qualifying Microsoft 365 plan. Source |
| Microsoft's Sales agent also works with Salesforce | Microsoft documents deploying its Sales agent for Salesforce CRM customers. Each user needs a Microsoft 365 Copilot license and Salesforce API access; the agent applies existing CRM permissions and provisions a Dataverse environment for its data. Source |
| Power Platform add-ons | Microsoft marks Power Apps custom apps and Power Automate customization as needing additional licenses. Power Apps Premium is $20 per user/month paid yearly. Source |
| Salesforce list prices for comparison (as of October 2026) | Sales Cloud Pro Suite $100, Core $195, Advanced $395, Max $550 per user/month billed annually. Agentforce for Sales from $125 per user/month. Flex Credits are $500 per 100,000; a standard action uses 20. Source |
As of October 27, 2026. Vendors change packaging and prices often; confirm before quoting a number to a customer.
Who decides, and how to talk to them (5) Approach
CIO / IT director
Cares about: Fewer vendors, Entra ID sign-on, one admin stack, and bargaining power in the Microsoft agreement.
Your angle: Do not fight the Microsoft estate. Show Salesforce inside it: Outlook and Teams integrations, single sign-on, and Microsoft's own Sales agent connecting to Salesforce. Then ask who will own CRM change requests each quarter.
CRO / VP Sales
Cares about: Forecast accuracy, rep adoption, and how fast process changes show up in the system.
Your angle: Run the demo on their stages, forecast categories and service handoff. Ask how many reps live in the CRM today and what they skip. Adoption is the metric this persona owns.
CFO / procurement
Cares about: Per-seat price, multi-year cost, and riding the existing Microsoft agreement.
Your angle: Agree list price matters, then build a three-year model with equal scope: base and attach licenses, Copilot Credits, Power Apps seats, capacity, Azure, implementation and admin staff.
VP Customer Service
Cares about: Handle time, channel coverage, self-service deflection and agent quality.
Your angle: Show Service Cloud with Agentforce for Service on their two or three highest-volume case types. Ask what share of cases needs sales or billing data, then show it on the case.
Power Platform or CRM admin team
Cares about: Reusing their skills and keeping control of change.
Your angle: Treat them as future Salesforce admins. Map their skills to Flow and low-code app building, and ask what they would build first.
Where Salesforce wins (6) Approach
The CRM is the product, not an add-on to the suite
Position Salesforce as the system revenue and service teams change every quarter. Sales Cloud, Service Cloud, Field Service, Revenue Cloud and Marketing Cloud share one customer record and one permission model. Ask the buyer to list last year's CRM changes and how long each took. If the answer is many and slow, the decision is about speed of change, and a CRM-first platform with a large admin talent pool is the safer bet.
See the proof →Agentforce acts on CRM records under CRM permissions
Agentforce agents run inside Salesforce and use the same records, Flows and sharing rules the business already governs. Recommend the buyer compare agent pricing on the same scenario: Salesforce offers Flex Credits ($500 per 100,000, 20 credits per standard action) or per-user Agentforce add-ons, while Microsoft agents need Copilot Credits plus an Azure subscription. Ask them to price 10,000 customer conversations on both.
See the proof →Microsoft 365 Copilot is not a reason to pick Dynamics
Microsoft's own Learn documentation covers deploying the Sales agent for Salesforce CRM customers, and Salesforce supports both an Outlook integration and a Microsoft Teams integration. When the buyer says Copilot needs Dynamics, share Microsoft's guide. Then reframe: the real choice is which CRM the reps and service teams should live in all day. Copilot can sit on top of either, so it should not decide the platform.
Data 360 and MuleSoft for mixed stacks
Most mid-market buyers run more than Microsoft: an ERP, billing, a support tool, a data warehouse. Data 360 unifies customer data for segments, analytics and agents, and MuleSoft connects systems with reusable APIs. Lead with this when discovery finds three or more systems holding customer data. Ask which of them will still exist in three years, and who reconciles the numbers today.
See the proof →AgentExchange and industry depth
AgentExchange gives buyers prebuilt apps and agents for CPQ, e-signature, telephony and industry needs, and Salesforce sells industry clouds for regulated verticals. Use this when the buyer has a specialist process such as dealer management, financial services compliance or healthcare intake. Ask which process they would otherwise build from scratch in Power Apps, and who would maintain it. Then show one AgentExchange app on that process.
One platform from lead to field visit
Sales Cloud, Service Cloud and Field Service share data, so a sales commitment, a case and a work order sit on the same account. For service-heavy buyers, show a case turning into a scheduled field visit, with the technician seeing the sales history and open quotes. Ask the buyer how many systems that path touches today and where the handoffs break.
See the proof →Where Microsoft Dynamics 365 is strong, and how to respond (4)
Acknowledging these builds credibility. Buyers already know them.
Lower list price per seat
Dynamics 365 Sales Professional lists at $65 and Sales Enterprise at $105 per user/month, paid yearly, against Sales Cloud Core at $195. Customer Service Professional lists at $50. On a seat-price spreadsheet Dynamics usually looks cheaper, and procurement will lead with that.
How to respond: Do not argue the list price. Agree, then expand the model: attach licenses, Copilot Credits, Power Apps Premium seats, capacity, implementation and admin cost over three years for the same scope. Offer Pro Suite where the scope fits.
Native fit with Microsoft 365 and Entra ID
Copilot in Dynamics 365 Sales works in Outlook and Teams, draws on SharePoint documents, and respects the signed-in user's record access. Contact Center integrates with Teams Phone. For an all-Microsoft IT team, one identity and admin model is a real operational advantage.
How to respond: Acknowledge it plainly. Show Salesforce's Outlook and Teams integrations and Entra ID SSO, then ask how often reps work in the CRM itself versus in Outlook. If the answer is rarely, the CRM fit matters more than the inbox fit.
One vendor for ERP and CRM
Microsoft licensing allows Business Central Premium users to add certain Dynamics 365 apps at the attach price, and Dataverse capacity is shared across Dynamics products in the tenant. A CFO who already runs Microsoft ERP sees one contract and one data platform.
How to respond: Ask which CRM processes truly need ERP data in real time and which need it nightly. Most need a few objects: orders, invoices, inventory. Show the integration scope and our NetSuite adoption story as a parallel.
Power Platform skills already in house
Power Apps and Power Automate run on the same Dataverse as Dynamics 365, so an internal Power Platform team can extend the CRM without learning a new toolset. That lowers the staffing risk buyers worry about most and keeps change in house.
How to respond: Respect the team. Map Power Automate to Flow and Power Apps to Lightning App Builder, and point to Trailhead. Ask whether that team has capacity for a CRM backlog on top of current work.
Discovery questions that change the deal (12) Approach
Business
- What changed in your sales or service process in the last 12 months, and how long did it take the CRM to catch up?
- If this project works, what number on your board deck moves first?
- Which teams outside sales will need to work on the customer record in the next two years?
Technical
- Besides Microsoft 365, which systems hold customer data today, and which of them will still be here in three years?
- Who would own CRM configuration day to day: a Power Platform team, a CRM admin, or a partner?
- Are you planning Microsoft 365 Copilot for sellers, and have you looked at how it connects to a non-Dynamics CRM?
- How do your ERP and CRM need to share orders, invoices or inventory, and how fresh does that data need to be?
AI and service
- Which two or three customer requests would you want an AI agent to resolve without a person first?
- How do you plan to budget for AI usage: per user, per conversation, or per action?
Decision
- Is CRM part of a broader Microsoft agreement negotiation, and when does that agreement renew?
- Who besides IT has a vote, and what would make the sales or service leader push back on the choice?
- What would a three-year cost comparison need to include for your CFO to trust it?
Objections, and what to say (6) Approach
"We're a Microsoft shop. Dynamics just fits."
Agree the Microsoft estate is a real asset, then separate the inbox from the CRM. Salesforce runs inside Microsoft environments every day with Outlook and Teams integrations and single sign-on. The question is which platform sellers and service teams should spend the day in, and which will keep up with process change. Suggest a scripted demo of their three most-changed processes on both platforms, scored by business owners.
"Dynamics is half the price per user."
Confirm the list prices honestly: Sales Enterprise is $105 and Sales Cloud Core is $195 per user/month. Then ask to price the same scope over three years: base and attach licenses, Copilot Credits, Azure, Power Apps Premium seats, capacity, implementation and the people who run it. Offer to fill in the Salesforce side line by line with our TCO guide. If scope is simple, put Pro Suite on the table.
Proof to send →"We need Copilot to work with our CRM, so it has to be Dynamics."
Share Microsoft's own deployment guide for the Sales agent with Salesforce CRM. It runs in Outlook and Teams for Salesforce users with a Microsoft 365 Copilot license. So the Copilot plan does not decide the CRM. Then show Agentforce acting on Salesforce records under Salesforce permissions, and ask which job belongs to which tool: internal productivity in Copilot, customer-facing work in Agentforce.
Proof to send →"Our ERP is Business Central, so CRM should be Microsoft too."
Ask which ERP data the CRM truly needs and how fresh it must be. Usually it is accounts, orders, invoices and inventory status. Show how that sync works with Salesforce through standard connectors or MuleSoft, and share a story where Salesforce runs next to a non-Salesforce ERP. Then ask what the sales team gives up if CRM choice is driven by ERP convenience.
Proof to send →"Switching from Dynamics would be too disruptive."
Agree that a move is a re-implementation, not a copy. Lay out the work plainly: data model mapping, rebuilding automation, integrations and security. Share our Dynamics migration guide and a migration story with a short timeline. Then ask what the current system costs them in workarounds each quarter. Disruption is a one-time cost; a poor fit is a recurring one.
Proof to send →"Microsoft is giving us a big discount in the EA."
Do not race to match. Ask how long the discount lasts, what renews at list price, and whether Copilot Credits, capacity and Power Apps seats are inside it. Then bring the business owner back in: a discount on a system the reps avoid still produces bad forecasts and slow change. Ask the CFO to weigh three-year cost alongside adoption and time-to-change.
Traps that lose these deals (5)
- Attacking Microsoft 365 or Teams. The buyer chose them; position Salesforce as working inside that estate.
- Letting IT run the evaluation alone. Get the CRO or VP Service to own and score the scenarios.
- Quoting Salesforce list prices without the full three-year comparison, which hands procurement an easy seat-price win.
- Claiming Copilot cannot work with Salesforce. Microsoft documents that it does, and the buyer's IT team will know.
- Running a generic demo. Both platforms look good in a canned tour; only the buyer's own scenarios separate them.
Qualify honestly
Strong fit for Salesforce
- Sales or service processes change often and the business owner feels slow CRM change.
- Customer data sits in several non-Microsoft systems that must come together.
- The buyer wants customer-facing AI agents, not only seller productivity in Outlook.
- Several clouds in scope: sales plus service, field service, CPQ or marketing.
- A regulated or specialist industry with a matching industry cloud or AgentExchange app.
Risky fit
- Small team with simple CRM needs where the lowest seat price decides.
- Microsoft ERP is the system of record and the CFO controls CRM budget with no business sponsor.
- A mature Power Platform team with spare capacity and no appetite for a new platform.
- CRM is a line item in a Microsoft agreement that closes before a real evaluation.
Salesforce products to lead with (6)
Moving the customer off Microsoft Dynamics 365
Moving from Dynamics 365 to Salesforce is a re-implementation, not a lift and shift. Map Dataverse tables, including custom tables and option sets, to Salesforce objects and picklists. Business process flows, plugins and Power Automate flows must be rebuilt, usually in Flow, with Apex where needed. Inventory every integration, especially ERP, Outlook and Teams, and plan single sign-on with Entra ID. Security roles and business units map to profiles, permission sets and the role hierarchy, so design that model early. Clean and deduplicate accounts and contacts before loading. Run parallel reporting so leaders can compare numbers before cutover, and train reps on their real records.
Questions AEs and buyers ask (5)
Is Dynamics 365 cheaper than Salesforce?
On list price per seat, usually yes: Sales Enterprise is $105 per user/month and Sales Cloud Core $195 as of October 2026. A fair comparison prices the same scope over three years, including attach licenses, AI usage, Power Apps seats, implementation and administration.
Can Microsoft 365 Copilot work with Salesforce?
Yes. Microsoft documents deploying its Sales agent with Salesforce CRM. Each user needs a Microsoft 365 Copilot license and Salesforce API access.
How are Dynamics 365 AI agents priced?
Agents run on Copilot Credits from Copilot Studio, at $200 per month for 25,000 credits or pay-as-you-go, and Microsoft requires an Azure subscription. Sales Premium includes 1,000 credits.
What is base and attach licensing in Dynamics 365?
Each user's first Dynamics 365 app must be the highest-priced license, the base. Further apps for that user come at lower attach prices, which matters when the same people need sales, service and field service.
When should an AE walk away from a Dynamics deal?
When scope is simple, the decision is purely seat price, and no sales or service leader is engaged. Also when CRM is bundled into a Microsoft agreement that closes before an evaluation can happen.
Sources (14)
- Microsoft: Dynamics 365 Sales pricing
- Microsoft: Dynamics 365 Customer Service pricing
- Microsoft: Dynamics 365 Field Service pricing
- Microsoft: Dynamics 365 Contact Center
- Microsoft: Dynamics 365 licensing guidance
- Microsoft: Copilot Studio pricing
- Microsoft: Microsoft 365 Copilot for enterprise
- Microsoft: Power Apps pricing
- Microsoft Learn: Copilot in Dynamics 365 Sales overview
- Microsoft Learn: Sales agent deployment guide for Salesforce CRM customers
- Salesforce Help: Turn on the Outlook integration
- Salesforce Help: Enable Salesforce Microsoft Teams integration
- Salesforce: Sales Cloud pricing
- Salesforce: Agentforce pricing