Dynamics 365 and the Power Platform

The Power Platform is the low-code, AI-first extensibility layer for everything Microsoft does in business applications. For Dynamics 365 customers it's not really optional — every non-trivial implementation involves at least one Power Platform component, and most involve all of them. Understanding where Dynamics 365 ends and the Power Platform begins is the single most useful piece of architecture knowledge a project sponsor can carry, because it decides how customisations get built, who can build them, and what they cost.

Dataverse: the foundation

Start at the bottom. Dataverse is the shared data platform underneath: tables, relationships, role-based security, business rules, auditing, and a Web API. Dynamics 365's CRM-side apps (Sales, Customer Service, Field Service, Project Operations) run on Dataverse — their entire data model lives there. The ERP-side apps (Business Central, Finance and Operations) run on their own platforms and integrate with Dataverse via Dual-write, virtual tables, or APIs. This split explains most of the "why doesn't X just work with Y" questions in the ecosystem; the details are in what is Microsoft Dataverse.

Power Apps

Used to build custom business apps in two flavours: model-driven, which is the same framework the CRM apps are themselves built on (forms, views, business process flows over Dataverse), and canvas, a free-form drag-and-drop builder for purpose-built mobile and tablet front ends. Dynamics 365 CRM-side apps are model-driven Power Apps with a pre-built schema and licensing — which is why a Dynamics customisation and a custom Power App are built with the same tools by the same people. When to configure the bought app versus build your own is its own decision — see Power Apps vs Dynamics 365 CRM.

Power Automate

Workflow and robotic process automation. Cloud flows run on triggers and schedules across hundreds of connectors; desktop flows automate legacy applications via UI. The most common Dynamics 365 uses: replacing custom plug-ins with low-code flows, automating approvals, and bridging Dynamics 365 to non-Microsoft systems. The discipline that matters: flows are real software. They need error handling, ownership, and ALM like everything else — the graveyard of failed automation is full of flows built in a personal environment by someone who left.

Power BI

Self-service analytics and dashboards. Dynamics 365 ships pre-built Power BI apps for Sales, Customer Service, Finance, Business Central, Supply Chain, and Field Service — genuinely useful starting points, though every serious deployment ends up building its own semantic model. For deeper analytics, Microsoft Fabric integration streams Dataverse and F&O data into a lakehouse where it can be combined with non-Microsoft data without hand-built ETL.

Copilot Studio

Used to build AI agents — chatbots and agentic assistants — that read and write Dynamics 365 via standard connectors and Dataverse. Increasingly the way customers deflect call-centre volume, build self-service, and embed generative AI into internal apps. Treat agent projects like software projects with testing and guardrails, not like configuration switches; building agents with Copilot Studio covers the reality.

Power Pages

External-facing portals built on Dataverse, used for customer self-service, B2B partner extranets, public-sector citizen services, and event sites. Anywhere someone outside your Entra ID tenant needs to see or submit CRM data, Power Pages is the Microsoft answer.

Licensing

Most Power Platform usage is included with a Dynamics 365 license for the apps that user is licensed for — a Sales user can run flows and model-driven apps within the Sales context. Standalone Power Apps and Power Automate licenses cover use beyond that bundled scope, and this boundary is where surprise costs live: a "small" custom app for non-Dynamics users, a flow using premium connectors run by unlicensed staff, or Dataverse capacity consumed by attachments. Have someone own the licensing question per solution, before it ships.

Governance: the part that decides success

The Power Platform's superpower — anyone can build — is also its failure mode. The platform ships with the controls: Managed Environments, DLP policies, environment strategies, solution-based ALM, and the Center of Excellence toolkit. Companies that treat these as day-one infrastructure get a healthy maker ecosystem on top of their Dynamics investment; companies that skip them get four hundred orphaned apps and a compliance headache. Start with Power Platform environments and DLP policies, and put governance in place while the app count is still small — retrofitting it later is an archaeology project.