Microsoft Dynamics CRM Cloud: What Does It Mean Today?

Reviewed by Grant Sullivan – Senior Market Structure Analyst

If you search for Microsoft Dynamics CRM cloud, you will quickly encounter several names that sound as though they describe the same product: Dynamics CRM, Dynamics 365 Sales, Dynamics 365 Customer Engagement, Dataverse, Power Apps and Dynamics 365 Customer Engagement on-premises. They are related, but Microsoft no longer uses the old Dynamics CRM naming in the same way it did before Dynamics 365 and Power Platform became the center of its customer-engagement architecture.

For a new cloud CRM implementation, the product most businesses are usually referring to is Dynamics 365 Sales, which runs as an online Dynamics application on Microsoft Dataverse and uses the model-driven Power Apps architecture. Microsoft’s Dynamics 365 Customer Engagement on-premises overview makes the distinction unusually clear: for online customers, applications such as Dynamics 365 Sales and Customer Service run on Dataverse, while the official name for the locally deployed CRM product is Dynamics 365 Customer Engagement (on-premises).

That terminology matters because the cloud and on-premises choices are no longer simply two hosting locations for one identically positioned CRM product. Microsoft’s online sales platform continues developing alongside Dataverse, Power Platform, AI capabilities and the wider Dynamics 365 ecosystem, while Customer Engagement on-premises follows its own product lifecycle and deployment architecture. A buyer comparing them should therefore evaluate the operating model and future application ecosystem rather than asking only where the database will be stored.

If your broader question is whether the rest of the Dynamics family is cloud-based, the guide to Microsoft Dynamics 365 cloud and on-premises deployment covers Finance and Operations, Business Central and the wider deployment landscape. This page stays focused on the CRM side: what “Dynamics CRM cloud” means today and when an on-premises customer-engagement environment still makes sense.

The Short Answer: Dynamics CRM in the Cloud Is Now Dynamics 365 Sales and Related Online Apps

For online customers, Microsoft no longer uses “Dynamics CRM” as the main product identity for its modern sales application. Dynamics 365 Sales is the current sales-focused cloud application, while Dynamics 365 Customer Service and other customer-engagement applications cover adjacent business functions. These applications run within Microsoft’s Dataverse and Power Platform architecture rather than as a cloud-hosted copy of the older standalone CRM server product.

Microsoft’s Dynamics 365 Sales product page positions Dynamics 365 Sales as its current sales automation platform, while the Dynamics 365 Sales developer guide documents how the application uses Dataverse tables and the Dataverse Web API. That combination is a useful way to understand the modern architecture: Sales is the business application, while Dataverse provides the underlying business-data and application platform.

The old terminology still appears because many organizations have used Microsoft CRM products for years. A company may say it is “moving Dynamics CRM to the cloud” even when the actual project involves migrating an older Dynamics CRM or Customer Engagement environment into Dynamics 365 Sales, redesigning customizations around Dataverse and reconsidering integrations that were built for the older deployment.

What Microsoft Calls the Products Now

The terminology is easier to understand when the old and current names are separated.

The main mistake is assuming that “Dynamics 365 Customer Engagement” remains the ordinary cloud product name. Microsoft specifically explains that the former online Customer Engagement SKU terminology was retired, while the on-premises product continues using Dynamics 365 Customer Engagement (on-premises) as its official name. That distinction makes older blog posts and licensing discussions surprisingly easy to misread.

How Does Dynamics 365 Sales Work in the Cloud?

Dynamics 365 Sales is a model-driven business application built around Dataverse data. Microsoft’s model-driven app architecture overview explains that model-driven applications use data housed in Dataverse and organize the experience around tables, relationships, forms, views, charts and dashboards. Sales builds on that platform with sales-specific tables, processes, security roles and application features.

From a buyer’s perspective, this means Microsoft manages the cloud application environment while your organization configures the sales processes, records, security, integrations and business logic that make the system yours. Users work with CRM concepts such as accounts, contacts, leads, opportunities, quotes, orders and activities while the underlying platform handles much of the application infrastructure that a traditional CRM deployment would have required locally.

This architecture also explains why Dynamics 365 Sales is so closely connected with Power Platform. A company can build additional model-driven applications around the same Dataverse environment, use Power Automate for workflows, extend experiences with Power Apps and connect other Microsoft business applications without treating the CRM as an isolated server application.

Dataverse Is a Major Difference Between Modern Cloud CRM and Older Dynamics CRM

Dataverse is more than a database used by Dynamics Sales. It provides structured business tables, relationships, security, business rules and application services that model-driven applications can use consistently. Microsoft’s guidance for defining model-driven application data explains that model-driven application data models are defined in Dataverse through tables, columns, relationships, business rules, forms and views.

That makes the current cloud platform more extensible than a traditional view of CRM as one application with one fixed set of database tables. An organization can introduce additional business applications into the same broader Power Platform architecture, although good governance is still required so every department does not create competing definitions of the same customer.

The architectural benefit is strongest when Dataverse is treated as an intentional business platform rather than a dumping ground for every enterprise record. Sales data belongs there when it participates in the CRM lifecycle, while detailed ERP transactions can remain in Finance and Operations and be integrated only where the sales process requires them. The guide to Dynamics 365 F&O and Power Platform integration explains the same ownership principle from the ERP side.

What Does Dynamics 365 Sales Manage?

Dynamics 365 Sales is designed around the commercial relationship and sales process. Microsoft’s current Sales application and documentation include capabilities around accounts, contacts, leads, opportunities, activities, quotes, orders, invoices, forecasting, sales sequences and other seller-oriented processes. Different Sales editions provide different feature depths, but the underlying application remains focused on helping sales teams manage customer relationships and progress commercial work.

The distinction between Sales and an ERP is important. A CRM order record can participate in a commercial workflow without becoming the same operational object as a sales order inside Finance and Operations. Inventory valuation, production, fulfillment, financial posting and many other back-office responsibilities still belong elsewhere when an ERP is part of the architecture.

This is one reason businesses integrating CRM and ERP should define a handoff rather than automatically synchronize every record. The article on Salesforce and Dynamics 365 Finance and Operations integration examines that problem using Salesforce as the CRM, but the ownership principle is equally relevant inside Microsoft’s own ecosystem: commercial and operational systems should exchange the information required for the process without pretending they perform the same job.

Does Microsoft Dynamics CRM Still Have an On-Premises Version?

Yes. Microsoft continues supporting Dynamics 365 Customer Engagement (on-premises), version 9.x. Microsoft’s Customer Engagement on-premises documentation describes version 9.1 as the current supported on-premises Customer Engagement product family for organizations operating sales, service and related customer-management functionality on their own infrastructure.

That product should be distinguished from Dynamics 365 Sales online. The cloud application runs within the current Dataverse and Power Platform environment model, while the on-premises product is installed, operated and maintained as a customer-managed deployment. They share many CRM concepts and capabilities, but their lifecycle, infrastructure and connection to Microsoft’s modern cloud services are different.

Microsoft’s deployment guidance for Customer Engagement on-premises makes the operational burden visible because administrators must plan, deploy, update and maintain the Dynamics Server environment themselves. That responsibility is a central part of the deployment decision rather than a minor infrastructure detail.

Cloud Dynamics 365 Sales vs Customer Engagement On-Premises

The table should not be interpreted as saying the on-premises product is unusable. Microsoft still documents, updates and supports version 9.x. The strategic difference is that the online platform sits inside Microsoft’s active Dataverse and Power Platform ecosystem, which makes the cloud version the more natural starting point for most new CRM projects.

How Long Is Dynamics 365 Customer Engagement On-Premises Supported?

Microsoft’s current product lifecycle page for Dynamics 365 Customer Engagement 9.x on-premises lists the product under the Fixed Lifecycle Policy. As of the current lifecycle listing, mainstream support extends to January 12, 2029, while extended support runs to January 9, 2031 for the 9.x on-premises update family.

Those dates matter because an organization already running on-premises has time to operate and plan rather than treating migration as an emergency. They do not mean an organization beginning a new CRM transformation should automatically choose on-premises simply because support remains available.

The more useful question is where Microsoft is investing its broader customer-engagement platform. Current Sales development is tied closely to Dataverse, Power Platform and increasingly AI-assisted sales capabilities. Existing on-premises customers can therefore use the remaining lifecycle strategically to determine how and when they want to modernize rather than waiting until support pressure dictates the decision.

Why Dynamics 365 Sales Online Is Usually the Better Starting Point

The strongest argument for the cloud version is the surrounding platform. Dynamics 365 Sales does not need to operate as an isolated CRM database because Dataverse, Power Apps and Power Automate can participate in related processes. Organizations can build additional experiences, workflows and applications without managing a separate CRM server infrastructure underneath them.

Microsoft also develops its newest Sales features in the cloud product. The current Dynamics 365 Sales product offering emphasizes modern sales automation, contextual insights, AI-assisted capabilities and integration with the wider Microsoft environment. These capabilities are part of the strategic direction of the online product rather than a secondary cloud copy of an on-premises release.

Infrastructure burden is another consideration. A cloud CRM still needs application administration, security, data governance and integration support, but the customer does not need to operate the entire Dynamics Server and database infrastructure used by an on-premises deployment. That difference can allow internal teams to spend more attention on sales-process design and adoption rather than server maintenance.

When On-Premises CRM Can Still Make Sense

A local Customer Engagement deployment can remain reasonable when an organization has a specific infrastructure or regulatory requirement that the cloud service cannot satisfy. Some organizations have governance rules around data location, network architecture or systems that must remain within controlled environments. Those constraints should be validated precisely because general discomfort with cloud services is weaker evidence than a documented operational requirement.

Existing investment also matters. A mature on-premises Dynamics environment may contain extensive integrations, reports, customizations and trained support teams that cannot be economically replaced overnight. In that situation, continuing to operate the supported platform while developing a staged modernization strategy can be more responsible than treating migration as an immediate technology fashion exercise.

The key distinction is between remaining on-premises intentionally and remaining there because no one has evaluated the alternatives. The first is an architecture decision with documented reasons. The second can become technical debt that gets harder to address as more surrounding applications move toward cloud services.

Cloud CRM Does Not Mean Giving Up Customization

Organizations can customize and extend Dynamics 365 Sales even though the application is cloud-based. The extensibility model simply operates through Dataverse, Power Platform and supported Dynamics customization mechanisms rather than through unrestricted control of the application servers.

Microsoft’s Dynamics 365 Sales developer guide documents the Sales tables and actions available through Dataverse and explains that developers can use the Dataverse Web API to interact with them. Model-driven applications can also be configured with forms, views, dashboards, business rules and process logic.

The discipline should be the same as with any cloud enterprise application: customize where the business gains meaningful value and avoid reproducing every historical behavior merely because the old CRM contained it. Cloud lifecycle management becomes much easier when extensions are deliberate and supported rather than accumulated without architectural ownership.

Dynamics 365 Sales Security Still Belongs to the Customer

Microsoft manages the cloud platform, but your organization still determines who should see and change CRM data. Microsoft’s current security roles for Dynamics 365 Sales explains that predefined and custom roles determine access levels and permissions for sales users, managers and application functions. Those roles are part of the application design rather than something Microsoft can infer automatically from job titles.

This is especially important when the CRM contains customer, pricing and opportunity information that crosses teams or geographies. Giving every user broad access because the service is securely hosted in Microsoft’s cloud does not create a secure business application. Infrastructure security and business-data authorization solve different problems.

Custom security roles also need ongoing attention. Microsoft notes that custom roles based on predefined roles do not automatically inherit every new permission Microsoft later adds to the underlying predefined role. Administrators should therefore include security-role review in the application’s lifecycle rather than treating role design as a one-time implementation task.

Where Does Dynamics 365 Sales Data Live?

The online application stores its business data in Dataverse, where tables represent concepts such as accounts, contacts, opportunities and related sales information. Model-driven applications interact with that structured business data through forms, views, relationships and other application components.

This does not mean every enterprise record should be moved into Sales. An ERP can remain the authoritative source for financial and operational data, while Sales stores the customer-facing and commercial information needed for seller workflows. Integrations can bring selected context into CRM without making Dataverse the master for every business object.

That distinction becomes particularly important in companies using Dynamics 365 Finance or Supply Chain Management. The guide to software that integrates with Dynamics 365 Finance and Operations explains the broader integration ecosystem, while the Dynamics 365 Finance and Operations integration methods page covers the technical connection options more deeply.

Is Dynamics 365 Sales Just Power Apps With CRM Tables?

That description is too simplistic. Dynamics 365 Sales does use the model-driven Power Apps and Dataverse architecture, but Microsoft provides a packaged sales application with sales-specific functionality, tables, roles and business processes. A custom model-driven application can use the same underlying platform without automatically becoming Dynamics 365 Sales.

This distinction matters for licensing, functionality and implementation design. A company that needs standard sales automation may benefit from the packaged Sales application rather than reproducing its capabilities in a custom application. Another company may use a custom model-driven app for a specialized relationship-management process that does not require the complete Sales product.

The underlying shared platform is valuable precisely because the applications do not need to be identical. Dataverse provides common architectural services while different applications can serve different business roles.

Can Dynamics CRM Cloud Integrate With Other Software?

Yes. Dynamics 365 Sales can integrate with other Microsoft and third-party applications through Dataverse APIs, Power Platform connectors, Azure integration services and other supported patterns. The correct approach depends on whether the other system needs synchronous data access, asynchronous synchronization, workflow automation or event-driven behavior.

The Dataverse Web API is particularly relevant for application-to-application integrations. Microsoft documents it as the interface developers can use to interact with Dynamics 365 Sales tables and actions. Power Automate can be useful for smaller workflow-oriented processes, while larger enterprise integrations may require more structured orchestration and monitoring.

Integration architecture should still start with ownership. Customer identity, product information, pricing, order status and financial information may be shared across systems, but each field should have a clear authoritative source. Cloud connectivity makes integration technically easier without solving data-governance disagreements automatically.

Can Dynamics 365 Sales Integrate With Finance and Operations?

Yes, but the architecture deserves careful design because CRM and ERP applications own different parts of the customer lifecycle. Sales may manage leads, opportunities and commercial interactions while Finance and Operations manages credit, inventory, fulfillment, invoicing and accounting.

Microsoft’s broader Dataverse and finance-and-operations architecture provides several ways for those applications to participate in connected business processes. The Dynamics 365 F&O and Power Platform integration guide explains why dual-write, virtual tables, Power Apps and events solve different problems rather than acting as interchangeable connection methods.

A good CRM-to-ERP architecture normally focuses on business handoffs. A qualified customer or accepted deal becomes an operational customer or order at a defined point, and status information flows back where sellers need it. That process produces clearer ownership than trying to make both applications maintain the same complete dataset continuously.

What Happens to Existing Dynamics CRM Customizations When Moving to the Cloud?

They need to be assessed rather than assumed to transfer unchanged. Older Dynamics CRM environments can contain plugins, workflows, integrations, reports, JavaScript and server-side customizations created around assumptions that differ from the modern Dataverse and Power Platform environment.

Some customizations may translate naturally into supported cloud extensions. Others may be replaced by standard Dynamics Sales features or redesigned through Power Platform. A few may no longer be necessary because the business process that originally justified them has changed.

The assessment should therefore classify customization by business value. Preserve the capability when employees genuinely depend on it, redesign it when the old technical approach no longer fits, and retire it when it exists mainly because nobody ever removed it. Migration is usually cleaner when the organization treats cloud adoption as an opportunity to simplify CRM rather than reproducing every historical artifact.

Do You Need to Move Every CRM Record to the Cloud?

Usually not. Historical CRM databases can contain years of activities, obsolete leads, duplicate contacts and old custom records that few employees use. Migrating all of that information into a new Dynamics 365 Sales environment increases migration effort and can make the new system harder to navigate.

Organizations should separate information that is operationally necessary from data that only needs to remain available for historical reference or regulatory retention. Active accounts, contacts, open opportunities and relevant service or sales history may need full migration, while older records can sometimes be archived or exposed through another reporting approach.

The decision should be made deliberately because deleting useful history can harm sales context just as easily as migrating everything can clutter the new environment. Data quality work is part of CRM modernization, not merely a technical migration task.

Cloud Migration Is Also a Sales-Process Redesign

One of the easiest ways to waste a CRM migration is to reproduce an unpopular old system exactly. Dynamics 365 Sales provides an opportunity to examine how leads are qualified, how opportunities advance, what information sellers are required to enter and which approvals or handoffs genuinely help the business.

This is where user adoption and architecture meet. A technically excellent cloud environment will still fail if sellers experience it as a long sequence of unnecessary fields and administrative tasks. The CRM should capture enough structured data to support the business without turning every interaction into data-entry work.

The best migration teams therefore include sales leadership and frontline users alongside technical specialists. They evaluate which information improves forecasting, customer continuity and operational handoff, then remove process steps that survive only because the old CRM was designed that way.

Does Dynamics 365 Sales Work With Microsoft 365 and Power Platform?

Yes, and this ecosystem connection is one of the strongest arguments for the online application. Dynamics 365 Sales participates in Microsoft’s broader business environment, while Dataverse provides the data platform that Power Apps and related Dynamics applications can use.

Power Automate can coordinate workflows around sales information, Power Apps can extend user experiences, and other Microsoft services can participate according to licensing and supported application capabilities. This creates an environment in which CRM processes can reach beyond one application without forcing every requirement into the Sales interface itself.

The benefit depends on governance. A company that creates dozens of disconnected flows and applications without ownership can recreate the same fragmentation it hoped the cloud would solve. The platform should make connections easier to govern, not encourage every department to build an independent customer system.

Is the Cloud Version Easier to Maintain?

From an infrastructure perspective, usually yes. The organization avoids the burden of running the complete on-premises Dynamics Server environment and can rely on Microsoft’s managed cloud service for much of the underlying platform operation.

Application maintenance still remains. Administrators need to manage security, environments, data, solutions, integrations and changes. Business teams need to maintain sales processes and data quality. Developers need to test important customizations against platform evolution.

This is the distinction worth carrying into the business case: cloud CRM reduces infrastructure maintenance, while successful CRM still requires application ownership. Companies sometimes underestimate the second category because SaaS purchasing makes the first category disappear from the project plan.

Does Cloud CRM Automatically Improve Sales Performance?

No. CRM software gives the business a structured environment for managing customer information and sales processes, but it cannot compensate for poor sales methodology, weak data discipline or confusing ownership.

Dynamics 365 Sales can provide automation, process support, visibility and increasingly sophisticated sales intelligence. Those capabilities become useful when the organization has defined how opportunities should be managed and when sellers understand what the CRM contributes to their work.

Implementation success should therefore be measured by business behavior rather than login counts alone. Reliable pipeline data, faster handoffs, less duplicate work and better customer continuity are more meaningful indicators than simply having every salesperson open the application.

Should a New Company Choose Dynamics 365 Sales Online or Customer Engagement On-Premises?

For a new implementation without a documented requirement for local deployment, I would start with Dynamics 365 Sales online. That aligns with Microsoft’s current application platform, gives the organization access to Dataverse and Power Platform and avoids creating a new customer-managed CRM server environment that will need its own infrastructure and lifecycle strategy.

I would investigate Customer Engagement on-premises when the organization has a genuine requirement that outweighs those cloud benefits. That could involve an existing supported deployment, a specific infrastructure constraint or another business reason strong enough to justify maintaining the local environment.

The decision becomes much clearer when “control” is translated into responsibilities. On-premises gives the organization direct infrastructure control, while also giving it infrastructure maintenance, patching, resilience and lifecycle responsibility. Cloud gives Microsoft more of that platform responsibility while leaving customer data governance, security roles, sales processes and integration ownership with the business.

A Better Decision Framework Than “Cloud or Server?”

Start by asking whether this is a new CRM implementation or an existing on-premises modernization project. New deployments should evaluate the online Sales platform first, while existing environments need a migration assessment that considers customization, integrations, data and business-process change.

Next, identify any verified requirement that prevents cloud adoption. Separate documented regulatory or infrastructure constraints from habits inherited from the previous CRM deployment. A local data center should not become the default architecture simply because it already exists.

Finally, evaluate the ecosystem the CRM needs over the next several years. If the business expects deeper Power Platform use, modern Dataverse development, connected Dynamics applications and Microsoft’s latest Sales capabilities, the strategic weight moves strongly toward the online application.

Which Microsoft Dynamics CRM Deployment Would I Choose?

For most organizations beginning a CRM project today, I would choose the Dynamics 365 Sales online route unless a concrete requirement makes it unsuitable. The cloud application is where Microsoft’s current Sales, Dataverse and Power Platform architecture comes together, and that ecosystem is increasingly important for organizations that want CRM to participate in broader automation and customer-data processes.

For an organization already running Dynamics 365 Customer Engagement on-premises, the answer can be more measured. Microsoft still supports the 9.x on-premises family under its published lifecycle, so there is time to plan a modernization based on business value rather than panic. The migration should examine customizations, integrations and user processes carefully instead of assuming that the old CRM can simply be lifted into a browser-hosted version of itself.

The terminology therefore becomes straightforward once the architecture is understood. “Microsoft Dynamics CRM cloud” today usually means using Microsoft’s current online Dynamics customer-engagement applications, especially Dynamics 365 Sales, on the Dataverse and Power Platform architecture. Customer Engagement on-premises still exists, but it is a separate supported deployment path rather than the default expression of Microsoft’s modern CRM direction.

Frequently Asked Questions