CRM
Microsoft Dynamics 365 Sales
Rest of world Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Microsoft Corporation · www.microsoft.com
Compare with HubSpot Sales Hub → Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Microsoft Dynamics 365 Sales scores highest on integrations, 6 to 7: a single-endpoint REST API with SDKs, code samples, change notifications combinable with Azure Event Hubs, Teams bots, PowerShell and Microsoft 365 in the base tier carried the bench's top marks. Pricing transparency follows at 4 to 5 — three tiers publish AU$97.30, AU$157.10 and AU$224.50 user/month, paid yearly, GST excluded — but the vendor labels the numbers informational only, only yearly billing is priced, and the Copilot Credits the agents require are sold separately without a public price. Sovereignty is the floor at 0 to 1: the vendor is a Redmond-headquartered, NASDAQ-listed US entity, and we found no public information on data residency, a DPA or a subprocessor list. Data portability is nearly as weak at 1 to 3, with export to Excel the only exit artifact evidenced. Judges' weighted totals run from 2.8 to 4.3, and scores spread on sales pipeline, 2 to 4, and automation, 3 to 5 — some judges credit the autonomous agents while others find no workflow builder, lead routing or forecasting evidenced.
Speaks for it
- Integrations scored 6 to 7 on a single-endpoint REST API with SDKs, code samples, change notifications, Azure Event Hubs streaming, Teams bots and PowerShell
- The Professional, Enterprise and Premium tiers publish per-user yearly prices from AU$97.30 to AU$224.50 with the GST treatment stated
- The object model spans leads, opportunities, accounts and contacts plus quotes, orders, invoices, product and price lists
- Prebuilt autonomous agents for qualification, research and closing — the Sales Close Agent in preview — and custom agents in Copilot Studio are evidenced
- Reporting extends to advanced analytics with Microsoft Power BI and export to Excel
Held against it
- Sovereignty scored 0 to 1: the vendor is a US entity and we found no public information on data residency, a DPA or a subprocessor list
- Prebuilt and custom agents require Copilot Credits available for purchase separately with no public price, so the real invoice is not computable from public pages
- Tier prices are labeled informational only, the actual price appears at checkout, and no monthly billing figures are published
- We found no public information on stage requirements, forecast views, quota tracking or win/loss capture, leaving sales pipeline at 2 to 4
- Export to Excel is the only evidenced exit path, with no public information on import tooling or export covering activity history and attachments
Best for
- You run a Microsoft 365 estate and want a CRM your developers can build against through a documented single-endpoint REST API with SDKs and real-time change notifications
- You want agent-assisted selling and are pricing Sales Premium, which includes Copilot Credits, or budgeting them as a separate purchase
- You need quotes, orders and invoices handled in the same object model as leads, opportunities, accounts and contacts
Avoid if
- You must underwrite EU data residency, a DPA and subprocessor exposure before signing — ask the vendor: the public pages we read do not show it
- You need to compute the full invoice before committing — ask the vendor: the public pages we read do not show it
- Your forecast must survive a finance audit — ask the vendor: the public pages we read do not show it
- You need a documented exit — full export covering activity history, attachments and relations — where only export to Excel and the REST API are evidenced
The scores
Contact & data model
Show reasoningHide reasoning
How this is scored
Depth and hygiene of the core records — contacts, companies, deals, custom fields, deduplication.
0 — A flat address book; no relations between people, companies and deals.
3 — The standard three objects exist but customization is cosmetic: few field types, no required fields, duplicates accumulate unchecked.
5 — Custom fields across objects, basic dedupe on create, activity history on the record; complex models still need workarounds.
8 — Rich field types with validation, merge and dedupe tooling, relationships beyond the standard model, permissioned field access.
10 — A genuinely modelable system: custom objects or equivalent, bulk hygiene tooling, field-level history — the data model bends to the business, not the reverse.
The Solo Seller
Lead, opportunity, account and contact management plus quotes, orders, invoices and product/price lists are confirmed, which is a wider relational model than a flat address book. But we found no public information on custom field types, required fields, duplicate detection or merge tooling, so the hygiene half of the question is unevidenced. 2
The Data Protection Officer
Lead, opportunity, account and contact management alongside product and price lists, bundles, quotes, orders and invoices are confirmed, which is broader than a bare three-object model. But we found no public information on custom field types, required fields, deduplication, merge tooling or field-level permissions — and for a database of other people's personal data, unevidenced consent fields and hygiene tooling is a real gap. 2 4
The Sales Ops Lead
The captured pages list the standard sales objects — leads, opportunities, accounts, contacts — plus quotes, orders, invoices and product and price lists, which is a workable core model. But I found no public information on custom fields, required fields, dedupe or merge tooling, and that hygiene layer is exactly what a 40-seat team lives or dies by. 2
The RevOps Integrator
The captured pages confirm the standard sales objects — leads, opportunities, accounts, contacts — plus products, price lists, bundles, quotes, orders and invoices, which is more than a flat address book. But we found no public information on custom field types, required fields, dedupe or merge tooling, and the hygiene layer a data model lives or dies on is unevidenced here. 2 4
The Migrator
The object model runs wider than contacts-companies-deals — quotes, orders, invoices, bundles, product and price lists are all named — but we found no public information on custom field types, required-field validation, merge or dedupe tooling, so hygiene on the way in stays unproven. 2
The Skeptic
The captured scope statement lists lead, account, contact and opportunity management extended with product and price lists, bundles, quotes, orders and invoices — a real standard model. We found no public information in these captures on custom field types, dedupe or merge tooling, or field-level permissions. 2
Pipeline & forecasting
Show reasoningHide reasoning
How this is scored
Whether the pipeline enforces a process and produces reporting a finance department accepts.
0 — A kanban of deals with amounts; nothing is enforced, nothing rolls up.
3 — Multiple pipelines and stage probabilities exist, but no required fields per stage and only canned reports.
5 — Stage requirements, win/loss capture and standard forecast views; custom reporting is limited or an add-on.
8 — Enforceable process (required fields, stage gates, routing), custom report builder, forecast by team and period with quota tracking.
10 — Forecasting a CFO signs: weighted and commit-based views, historical snapshots, attainment tracking, and reporting composable enough to answer questions the vendor never anticipated.
The Solo Seller
Opportunity management, deal-analysis agents and analytics via Power BI with export to Excel are confirmed, but we found no public information on stage requirements, win/loss capture or any forecast view. Reporting appears to live in a separate analytics product, and the forecast side is entirely unevidenced. 2 4
The Data Protection Officer
Opportunity management and reporting via export to Excel and Power BI analytics are confirmed, with a preview Sales Close Agent describing autonomous deal analysis. We found no public information on stage requirements, win/loss capture, forecast views, quota tracking or historical snapshots, so nothing evidences a process the pipeline enforces or forecasting a finance function could accept. 2 4
The Sales Ops Lead
Opportunity management is evidenced with Excel export and Power BI analytics, so deals roll up into a BI layer rather than dying on a dashboard. But I found no public information on stage requirements, forecast views, quota tracking or forecast snapshots — the machinery a CFO audit demands — and the pipeline content on the captured pages is dominated by preview-stage AI agents. 2 4
The RevOps Integrator
Opportunity management with quotes, orders and invoices is confirmed, and reporting extends to Excel export and Power BI analytics — but no forecast views, quota tracking, stage gates or win/loss capture appear in the captured pages. What a finance department would need to sign a number is simply not evidenced. 2 4
The Migrator
Opportunity management through the full quote-to-invoice chain is named, with reporting via export to Excel and Power BI analytics, but we found no public information on stage requirements, win/loss capture, or any forecasting view a finance department would sign. 2 4
The Skeptic
Opportunity management running through quotes, orders and invoices evidences a sales process, and Power BI 'advanced analytics' with export to Excel is a genuine reporting path, but nothing enforces anything. We found no public information on stage requirements, win/loss capture, forecast views or quota and attainment tracking. 2 4
Automation & workflows
Show reasoningHide reasoning
How this is scored
Triggers, sequences and routing that remove manual work without a consultant.
0 — No automation beyond email templates.
3 — Simple if-this-then-that on records; no multi-step sequences, no branching.
5 — Multi-step workflows with delays and branching, email sequences, basic lead routing — capped by tier or count.
8 — Full workflow builder across objects with webhooks as steps, round-robin routing, sequence analytics.
10 — Automation as infrastructure: versioned workflows, error handling, per-step logs, and limits generous enough that the feature is not its own upsell.
The Solo Seller
Prebuilt agents for qualification, opportunity research and closing are confirmed, plus custom agents built in Copilot Studio — but running them is metered through Copilot Credits that are purchased separately, so the automation is literally its own add-on line on my card. We found no public information on multi-step workflows with delays, branching or lead routing. 4 2 1
The Data Protection Officer
Autonomous agents for lead research, qualification, opportunity analysis and closing are confirmed, plus custom agents via Copilot Studio and PowerShell for tenant provisioning. We found no public information on a record-level workflow builder with triggers, delays, branching or lead routing — and opaque autonomous processing of personal data with no visible logging is precisely the kind of black box a DPO cannot audit. 1 4 5
The Sales Ops Lead
The pages evidence autonomous agents — lead qualification, opportunity research, a Sales Close Agent in preview — plus custom agents in Copilot Studio and PowerShell provisioning, which is real removal of manual work. But I found no public information on multi-step workflows, branching, delays or lead routing, so nothing here evidences the process enforcement I run a forecast on. 1 4 5
The RevOps Integrator
Autonomous prebuilt agents — lead qualification, opportunity research, a closing agent in preview — plus custom agents via Copilot Studio are genuinely evidenced automation beyond simple triggers. But the agent runtime consumes Copilot Credits that are a separate purchase, and we found no public information on a conventional workflow builder with sequences, branching or lead routing. 1 2 4
The Migrator
Autonomous agents — research, qualification, and a Sales Close Agent in preview — plus custom agents built in Copilot Studio do remove manual work, but running them requires Copilot Credits available for purchase separately, which makes automation its own meter, and we found no public information on conventional workflow builders, sequences or lead routing. 4 2 1
The Skeptic
Autonomous agents for lead research, qualification and deal closing are evidenced, including a Sales Close Agent in preview — but prebuilt and custom agents alike run on Copilot Credits that are 'available for purchase separately', so the headline automation is metered before you start. We found no public information on workflow triggers, sequences or lead routing. 2 4 5
Integrations & API
Show reasoningHide reasoning
How this is scored
Two-way email/calendar sync, native connections, and an API that treats external systems as first-class.
0 — No API, no sync; data enters by CSV and leaves never.
3 — One-way email logging (BCC), a handful of Zapier triggers, a read-mostly API.
5 — Two-way email and calendar sync for the major providers, a documented REST API with sane limits, a modest native directory.
8 — Deep native integrations for the revenue stack, webhooks, OAuth apps, API parity with the UI for core objects.
10 — An ecosystem: public API covering everything the UI does, event streams, a marketplace, and sync so reliable the CRM can be the system of record without being the only system.
The Solo Seller
A single-endpoint REST API with SDKs, code samples, a browser API explorer, change notifications and mail API access is confirmed, which is a genuinely first-class API story. But the pages describe people-centric cloud data, and we found no public information on native two-way email and calendar sync, a third-party app marketplace, or API parity for the sales records themselves. 5 1
The Data Protection Officer
A single-endpoint REST API with SDKs, a browser API explorer, code samples, change notifications combinable with Azure Event Hubs, Teams bots and Graph Toolkit controls is confirmed, alongside Microsoft 365 integration and Power BI analytics. We found no public information on rate limits, a native connector directory or OAuth app publishing, so this stops short of an evidenced ecosystem despite strong developer tooling. 2 4 5
The Sales Ops Lead
A single-endpoint REST API with SDKs, code samples, a browser API explorer, and change notifications combined with Azure Event Hubs for real-time events is a genuinely first-class API story, alongside Microsoft 365 integration and a partner app ecosystem. I found no public information on two-way email and calendar sync inside the product or on API limits, so it stops short of the deep revenue-stack tier. 4 5
The RevOps Integrator
A single-endpoint REST API with SDKs, change notifications, Event Hubs streaming, Teams bots, PowerShell and Bicep templates is exactly the first-class external surface I look for. The gap: the captured pages show no OAuth app model, no spelled-out two-way email and calendar sync, and no confirmation that the API covers the sales objects at parity with the UI. 4 5
The Migrator
The developer surface is genuinely first-class: a single REST endpoint with SDKs, code samples, change notifications, Azure Event Hubs for real-time streams, Teams bots, PowerShell, and Microsoft 365 in the family. We found no public information on whether that API reaches the CRM's core objects at parity with the UI, or on the specifics of two-way email and calendar sync. 5 4
The Skeptic
A documented single-endpoint REST API with SDKs, change notifications combinable with Azure Event Hubs, Teams bots, Bicep templates and an in-browser Graph Explorer is a strong developer story, and Microsoft 365 integration is named in the base tier. The API evidence is all people-centric Microsoft Cloud data though, and we found no public information on native two-way sync for non-Microsoft providers or on any connector catalogue beyond a page that yielded no usable content. 4 5 6
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where other people's personal data actually lives and under whose law — entity, hosting, subprocessors, DPA.
0 — US entity, US-default hosting, no public DPA or subprocessor list.
3 — A DPA exists and an EU region is available on request or on top tiers; subprocessor exposure to US CLOUD Act reach is broad and undocumented.
5 — EU hosting selectable at signup, published DPA and subprocessor list; core processing still touches US entities.
8 — EU entity or EU-default hosting with published subprocessors, consent-friendly fields, retention and deletion controls; residual US exposure named and narrow.
10 — European entity, EU-only processing including subprocessors, deletion that provably deletes — sovereignty a DPO can sign off without a caveat file.
The Solo Seller
The vendor is a publicly listed company headquartered in Redmond, and we found no public information on EU hosting options, a data processing agreement, or a subprocessor list. Nothing on these pages says where other people's personal data actually lives or under whose law. 3
The Data Protection Officer
The vendor is a Redmond-headquartered, NASDAQ-listed US entity, and across the captured pages, including the privacy policy, we found no public information on a DPA, subprocessor list, EU data residency option, or retention and deletion controls that provably delete. Autonomous research on incoming leads operates on contact data with no consent or provenance story anywhere on these pages — US-default processing with undocumented subprocessor exposure is exactly the posture I reject. 1 2 3
The Sales Ops Lead
The vendor is identified as a US-headquartered, publicly listed corporation, and I found no public information on data residency options, a subprocessor list or a DPA in the captured privacy and product pages. For a European buyer there is nothing here to underwrite where personal data lives or under whose law, which sits at the bottom of the scale. 1 3
The RevOps Integrator
The vendor is Microsoft Corporation of Redmond — a US entity — and we found no public information on selectable EU hosting, a published DPA, or a subprocessor list in the captured pages. I cannot place where European personal data lands or under whose law from this material. 1 3
The Migrator
The vendor is Microsoft Corporation of Redmond, publicly listed on NASDAQ — a US entity — and the captured privacy page gave no information on data residency, a DPA, or subprocessors, so a European buyer cannot establish from these pages where personal data will actually live or under whose law. 3 1
The Skeptic
Microsoft is a Redmond-headquartered, NASDAQ-listed US entity, and every sovereignty attribute — jurisdiction, data residency, subprocessor exposure — came back unknown on the vendor's own captured pages. The privacy policy page was captured but produced no DPA, no subprocessor list and no EU processing terms, so we found no public information on where this CRM's personal data actually lives. 3 4
Import, export & exit
Show reasoningHide reasoning
How this is scored
Getting in with history intact, and out with everything — the anti-lock-in criterion.
0 — Import is a support ticket; export is contacts-only CSV missing notes, activities and files.
3 — Self-serve CSV import with mapping; export covers main objects but drops activity history, attachments or relations.
5 — Guided migration from major competitors, full-object CSV export, API access sufficient to rebuild the database elsewhere with effort.
8 — Complete export (all objects, history, files) self-serve in open formats, import with dedupe and dry-run, no API metering that prices exit out of reach.
10 — Exit as a feature: documented full-fidelity export, migration tooling both directions, and contractual data-return terms — leaving is a weekend, which is exactly why you can stay.
The Solo Seller
Export to Excel from reporting is the only portability evidence, and we found no public information on import, guided migration, or a full export covering activities, attachments and history. Power BI analytics is not an exit path. 2
The Data Protection Officer
Export to Excel is the only egress evidenced, and while a documented REST API exists for Microsoft Cloud data, we found no public information on import tooling, guided migration, or full export covering activity history, attachments and relations. Where a lawful data-return obligation depends on complete exit, an unevidenced export path is a compliance exposure in itself. 2 5
The Sales Ops Lead
Self-serve export is evidenced only as export to Excel, with a REST API available to pull data out with effort. I found no public information on guided import, migration from competitors, or full-object export covering history and attachments, so any exit plan rests entirely on the API and my own engineering. 2 5
The RevOps Integrator
Export to Excel and Power BI analytics are the only exit paths evidenced, and we found no public information on migration tooling, full-object export including history and attachments, or contractual data-return terms. For a system of record this size, that is not an exit story I can verify. 2
The Migrator
The only export wording anywhere is "Includes export to Excel" in a sentence about dashboards; we found no public information on import tooling, dedupe, full-object export including notes and activity history, or contractual data-return terms — and in my experience that silence means the exit becomes a project. 2 4
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real invoice — per seat, per month, at renewal — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — An entry price exists, but the tiers most buyers need are unpriced, or per-seat maths is obscured by bundles, minimums or mandatory onboarding fees.
5 — Most tiers carry real numbers with billing period and VAT treatment stated, but at least one commonly needed capability hides in an unpriced tier or usage-metered add-on.
8 — Every tier priced publicly including annual/monthly split; limits, seat minimums and overage rules stated; only genuine enterprise contracts are custom.
10 — Complete price computability: every tier, add-on, usage meter and renewal rule public, with a calculator or table that makes the invoice at 3 and 30 seats a two-minute exercise.
The Solo Seller
All three tiers show per-user yearly prices with GST treatment stated, but the vendor labels them informational only with the actual price appearing at checkout, monthly figures are absent, and the Copilot Credits needed to run agents are sold separately with no public price. Those are numbers I can read, not an invoice I can compute before I commit my card. 4 2
The Data Protection Officer
Three Sales tiers carry stated per-user, paid-yearly prices with GST exclusion disclosed, but Copilot Credits — stated as required to run prebuilt and custom agents — have no public price, and the vendor itself says prices shown are for informational purposes only and may not be reflective of actual list price. A buyer cannot compute the real invoice from these pages, and the metered add-on the flagship agents depend on is unpriced. 2 4
The Sales Ops Lead
Three sales tiers carry public numbers — AU$97.30, AU$157.10 and AU$224.50 per user per month paid yearly — with the GST treatment stated as excluded. But the Copilot Credits required to run the agents are a separately purchasable, unpriced meter, the pricing page itself warns figures are informational only and the actual price appears at checkout, and I found no public information on monthly billing rates — a buyer can estimate but cannot compute the invoice. 2 4
The RevOps Integrator
Three tiers carry real per-user prices with billing period and GST treatment stated — but only on yearly terms, and the vendor's own disclaimer says the numbers may not be reflective of actual list price. The headline agent capability consumes Copilot Credits whose price the captured pages never state, so the real invoice is not computable from public pages alone. 2 4
The Migrator
Three tiers carry real numbers — AU$97.30, AU$157.10 and AU$224.50 user/month, paid yearly, with GST excluded and shown before purchase — but the pricing pages themselves warn the prices "may not be reflective of actual list price," only yearly billing is priced, and the Copilot Credits agents depend on are purchasable separately with no public price. 4 2
The Skeptic
Three tiers carry published figures — AU$97.30, AU$157.10 and AU$224.50 user/month, paid yearly, with GST treatment stated — which is more than many show. But the same pages warn prices 'are for informational purposes only and may not be reflective of actual list price', the AI agents depend on Copilot Credits whose rate we found no public information on, and no month-to-month figure or FastTrack onboarding cost appears anywhere captured. 2 4
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 15 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Subprocessors. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- We found no public information on compliance on the pages we read (microsoft.com/en-us/dynamics-365/products/sales, microsoft.com/en-us/dynamics-365/products/sales/pricing, microsoft.com/en-us/privacy, microsoft.com/en-au/dynamics-365/products/sales, developer.microsoft.com/en-us/graph/rest-api, microsoft.com/de-at/power-platform/connectors). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 10 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (6)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor product page www.microsoft.com Checked 15 Sep 2026 Details →
- 2 Vendor pricing page www.microsoft.com Checked 15 Sep 2026 Details →
- 3 Privacy policy www.microsoft.com Checked 30 Sep 2026 Details →
- 4 Pipeline & forecasting — found from sitemap www.microsoft.com Checked 1 Oct 2026 Details →
- 5 Integrations & API — found from sitemap developer.microsoft.com Checked 1 Oct 2026 Details →
- 6 Integrations & API — found from sitemap www.microsoft.com Checked 1 Oct 2026 Details →