Microsoft Dynamics 365
Dynamics 365 is Microsoft's family of CRM and ERP applications, including Sales, Customer Service, Contact Center, Field Service, Customer Insights, Finance, Supply Chain Management and Business Central, with Copilot features and prebuilt agents. CRM apps run on Dataverse. Guides and Remote Assist end on 31 Dec 2026.12
Also known as Dynamics 365
- Intended for
- Sales, service and marketing leaders, Finance and supply chain teams, Contact center and field service managers, Business application administrators and partners
- Runs on
- SaaS (Microsoft cloud), Customer Engagement (on-premises) release, documented separately
At a glance
- What is it?
- Dynamics 365 is a set of business applications that Microsoft sells as separate apps. Microsoft's documentation hub lists Business Central, Commerce, Sales in Microsoft 365 Copilot, Service in Microsoft 365 Copilot, Customer Insights, Customer Service, Customer Voice, Contact Center, Field Service, Finance, Finance Agent, Guides, Human Resources, Intelligent Order Management, Project Operations, Remote Assist, Sales (Premium, Enterprise, Professional), Supply Chain Management and Sustainability. Microsoft's product page calls the family agentic CRM and ERP. Apps such as Sales, Customer Service and Customer Insights are model-driven apps built in Power Apps on Microsoft Dataverse.34
- What does it do?
- The CRM apps manage leads, opportunities, cases, work orders and customer journeys; the ERP apps run finance, supply chain, projects and HR. Copilot features summarize records, suggest form values, draft emails and answer questions over app data. Prebuilt agents include the Sales Qualification Agent, Case Management Agent, Customer Knowledge Management Agent, Scheduling Operations Agent, and the Sales Order Agent and Payables Agent in Business Central; the Account Reconciliation Agent in Finance is a production ready preview. The Dynamics 365 ERP MCP server lets developers build agents that use finance and operations data and business logic.4
- Who needs it?
- Organizations replacing or consolidating CRM or ERP systems, and those already on Microsoft 365 that want sales and service data close to Outlook, Teams and Copilot. Contact center teams use Contact Center and Customer Service, field organizations use Field Service, and finance and operations teams use Finance, Supply Chain Management or Business Central. Partners extend the apps for specific industries.1
- What does it need?5
- A license or trial for each Dynamics 365 app you deploy
- A Power Platform environment with a Dataverse database for the CRM apps
- Access to the Power Platform admin center to install and manage apps
- Data Integrator configuration to make finance and operations data available in Dataverse
- Admin enablement for Copilot features and preview agents where required
- What it is not
- Dynamics 365 is not one product with one license: each app is chosen and licensed separately, with its own trial. Not all apps share Dataverse in the same way; finance and operations apps need the Data Integrator to make their data available in Dataverse. Several AI features are previews, including Microsoft Copilot in model-driven apps, the agent feed and the Power Apps MCP Server. Guides and Remote Assist are not an option for new projects: they reach end of support on 31 Dec 2026.45
Availability and licensing. Checked 26 Oct 2026. Each app has its own plans and free trial or guided tour; prices were not checked for this profile. Dynamics 365 Guides and Remote Assist reach end of support on 31 Dec 2026: purchases and renewals were possible until 1 Nov 2025, the apps stop working after end of support, and their data stays in Dataverse. Several agents and Copilot features are in preview.12
The problem it solves
Customer, sales, service and finance data often sits in separate systems, so staff re-enter data and work from stale records, and AI added on top of fragmented systems has little reliable context.
Dynamics 365 puts its CRM apps on the shared Dataverse platform and adds Copilot features and agents inside the apps, such as qualifying leads, managing cases or reconciling accounts, so automation runs where the business data and security roles already are.
How it works
Dynamics 365 apps share Microsoft's business applications platform:
- Dataverse stores data for apps such as Sales, Customer Service and Human Resources, with tables, business rules, and role-, row- and column-based security.
- Model-driven apps built in Power Apps provide the CRM interface, so Power Apps AI features (form fill assistance, row summaries, timeline highlights, natural language view filters) also appear in those apps.
- Finance and operations apps have their own Copilot features, such as generative help and chat with finance and operations data, and the Dynamics 365 ERP MCP server for agents.
- Agents run inside apps and are supervised through features such as the agent feed (preview) and, in Contact Center, rollout plans and an agent insights dashboard.
- Extension: custom agents are built with Copilot Studio; Power Apps and Power Automate extend screens and processes.145
Diagram as a list
Copilot & business apps
- Sellers, service reps, field technicians and finance staffWork in the apps and supervise agents
- Sales and Service in Microsoft 365 CopilotBring CRM data into Microsoft 365 appsConnects to CRM apps: Sales, Customer Service, Contact Center, Field Service, Customer Insights
- CRM apps: Sales, Customer Service, Contact Center, Field Service, Customer InsightsModel-driven apps for customer processes
- ERP apps: Finance, Supply Chain Management, Business Central, Project OperationsFinance and operations processesConnects to Prebuilt agents and Copilot features
Agents & automation
- Prebuilt agents and Copilot featuresAutomate steps such as lead qualification, case handling and reconciliationConnects to Microsoft Dataverse
- Copilot Studio custom agentsCustom agents for processes not covered by prebuilt onesConnects to Microsoft Dataverse
Data & analytics
- Microsoft DataverseStores CRM data with business rules and security
Developer tools
- Dynamics 365 ERP MCP serverExposes finance and operations data and logic to agentsConnects to ERP apps: Finance, Supply Chain Management, Business Central, Project Operations
Capabilities
CRM applications3
Sales (Premium, Enterprise, Professional), Customer Service, Contact Center, Field Service, Customer Insights and Customer Voice.
Why it matters: Covers the customer lifecycle from marketing to service on one data platform.
Limits: Each app is licensed separately; features differ between Sales editions.
ERP applications3
Finance, Supply Chain Management, Business Central, Project Operations, Human Resources, Commerce and Intelligent Order Management.
Why it matters: Runs core finance and operations processes with AI help built in.
Limits: Finance and operations data needs the Data Integrator to appear in Dataverse.
Copilot features in model-driven apps4
Form fill assistance, find and visualize data in a view, row summaries and timeline highlights, inherited from Power Apps.
Why it matters: Reduces manual data entry and record review in CRM apps.
Limits: Microsoft Copilot in apps and the agent feed are in preview; some features must be enabled and may not appear in every app.
Prebuilt agents14
Sales Qualification, Sales Opportunity, Sales Research, Case Management, Customer Knowledge Management, Quality Evaluation, Scheduling Operations, Sales Order and Payables agents, among others.
Why it matters: Automates defined process steps inside the apps where the data lives.
Limits: Microsoft marks several agents as preview, including Sales Close, Scheduling Operations, Procurement, Account Reconciliation and Time, Expense, and Approvals.
Dynamics 365 ERP MCP server4
An MCP server that lets agents perform data operations and use the business logic of finance and operations apps.
Why it matters: Developers can build their own agents on ERP data without custom integration code for each operation.
Limits: Aimed at developers; each agent built on it still needs its own design, testing and permission review.
Shared Dataverse platform5
Dynamics 365 CRM apps store data in Dataverse, so Power Apps, Power Automate and Power BI can use it without separate integration.
Why it matters: Extensions and reports work directly against core business data.
Limits: Finance and operations apps currently need the Data Integrator for Dataverse access.
Practical use cases
Service representatives spend time filling in case details by hand.
- Approach
- Use the Case Management Agent in Customer Service or Contact Center to create, update, resolve and close cases, alongside Copilot case summaries.
- Role of Microsoft Dynamics 365
- The agent handles routine case fields; representatives handle the customer.
- Data, infrastructure and skills
- Customer Service or Contact Center licenses and a Dataverse environment.
- Type of benefit
- Representative time saved
- Caveats
- Roll agents out in phases with rollout plans and monitor them on the agent insights dashboard.
- First step
- Pilot the agent on one queue under a rollout plan.
Sellers cannot follow up every inbound lead in time.
- Approach
- Use the Sales Qualification Agent to research leads, judge fit, send outreach emails and engage leads.
- Role of Microsoft Dynamics 365
- The agent qualifies and warms up leads; sellers take over qualified ones.
- Data, infrastructure and skills
- Dynamics 365 Sales and a lead process with clear fit criteria.
- Type of benefit
- Pipeline coverage
- Caveats
- Outreach content needs brand and compliance review before it reaches customers.
- First step
- Define qualification criteria and run the agent on one lead source.
A small business keys in vendor invoices from email by hand.
- Approach
- Turn on the Payables Agent in Business Central, which monitors mailboxes for incoming vendor invoices and helps register them.
- Role of Microsoft Dynamics 365
- The agent prepares invoice registration; accounting staff review.
- Data, infrastructure and skills
- Dynamics 365 Business Central and a mailbox for vendor invoices.
- Type of benefit
- Fewer manual entries
- Caveats
- Check the agent output against your posting rules during the pilot.
- First step
- Connect one invoice mailbox and compare agent results with manual postings for a month.
Who uses it
EY
ScalingEY: Dynamics 365 Sales with agents, and Copilot across the firm
85,000 in 18 months; goal 100,000 (measured)
Professional services, Global
Works with
Optional integration
- Microsoft Power PlatformCRM apps are model-driven Power Apps on Dataverse and inherit Power Apps AI features.
- Microsoft Copilot StudioCustom agents for Dynamics 365 are built with Copilot Studio.
- Microsoft 365 CopilotSales in Microsoft 365 Copilot and Service in Microsoft 365 Copilot bring CRM data into Microsoft 365.
Same family
- Microsoft Industry Solutions and Dynamics 365 SustainabilityDynamics 365 Sustainability is listed among the Dynamics 365 apps.
Optional integration for
- Microsoft Industry Solutions and Dynamics 365 SustainabilityHealthcare solutions depend on Dynamics 365 Customer Service and Field Service; Sustainability is a Dynamics 365 app.
- Microsoft Power PlatformDynamics 365 apps store data in Dataverse, so Power Apps can build on it without integration.
Relationship labels follow Microsoft's documentation. "Alternative approaches" does not mean one is better: each profile says when it fits.
Getting started
Map processes to apps
List the processes in scope (sales, service, field work, finance, supply chain) and pick the matching Dynamics 365 apps.
Check: Each in-scope process maps to a named app.
Start a trial
Microsoft offers trials or guided tours from each app product page.
Check: A trial environment opens with sample data.
Prepare the environment
Create a Power Platform environment with a Dataverse database and install the apps from the Power Platform admin center.
Check: The apps show as installed for the environment in the admin center.
Enable Copilot and agents
Turn on the Copilot features and agents you plan to test, starting with one team.
Check: Pilot users see Copilot and agent activity in their app.
Plan any Guides or Remote Assist exit
If you use them, export Guides data and move scenarios before 31 Dec 2026; data remains in Dataverse afterwards.
Check: No production process depends on Guides or Remote Assist.
Official resources
Deciding whether you need it?
Three free tools apply Microsoft's own published guidance to your situation, and say when Microsoft Dynamics 365 or any new technology is not needed.
Sources
Each statement above links to the source it comes from. Labels say who reported it.
- Microsoft Dynamics 365 product page (opens in a new tab)
- Dynamics 365 Guides and Remote Assist reaching end of support on December 31, 2026 (opens in a new tab)
- Microsoft Dynamics 365 documentation hub (opens in a new tab)
- Agents, Copilot, and AI capabilities in Dynamics 365 apps (opens in a new tab)
- What is Microsoft Dataverse? (opens in a new tab)
Thank you. Your correction was sent.
The editors check it against the sources. If you left an email address, they may reply about it.