The layers you're actually navigating
Microsoft doesn't hand marketing and sales teams one tool. It hands you a stack, and the names changed again in 2025-2026. Before you automate anything, know which layer does what — because picking the wrong layer for a job is how you end up rebuilding it.
- Copilot Studio — a graphical, low-code tool for building agents and agent flows. It connects to data through prebuilt or custom connectors, and the agents you build can run on their own or extend Microsoft 365 Copilot with your enterprise data and scenarios.
- Power Platform — the low-code foundation underneath: Power Apps (canvas and model-driven apps), Power Automate (cloud flows, RPA and process mining), and Dataverse (the shared data store).
- Microsoft 365 Copilot — combines large language models with your own work data via the Microsoft Graph, grounding responses in emails, chats, files and calendars you're already permitted to see.
- Dynamics 365 — the CRM and marketing applications: Sales for AI-assisted selling and Customer Insights for unified profiles and real-time journeys.
- Microsoft Foundry — the pro-developer Azure platform (formerly Azure AI Studio / Azure AI Foundry) for building, deploying and governing AI models and agents.
- Microsoft Agent 365 plus Purview — the control plane to observe, govern and secure every agent.
Copilot Studio and Power Platform: your build layer
For most marketing and sales teams, the work starts in Copilot Studio. It's a low-code authoring surface where you build agents that answer questions, take actions, or hand off to a human. Its agent flows give you an authoring experience similar to Power Automate but native inside Copilot Studio — a flow can run standalone or be triggered from an agent as a tool, run prompts, call other agents, and include human review steps. That last detail matters: human-in-the-loop is built in, not bolted on.
Underneath sits Power Platform. Power Apps lets you build in two styles — canvas apps (WYSIWYG layout control, connecting to 400+ data sources) and model-driven apps (which start from the Dataverse data model to generate forms and views), well suited to data-dense work like managing a sales process. Power Automate covers automation across cloud flows, robotic process automation and process mining; its desktop flows mimic a human's mouse and keyboard to automate web and desktop tasks, and cloud flows can trigger them remotely.
How it connects to your CRM, ads and revenue data
The connective tissue is Dataverse. It's the default data store for Power Platform, letting you integrate data from multiple sources into a single store usable across Power Apps, Power Automate and Power BI — alongside data already in your Dynamics 365 applications. Critically, Dynamics 365 apps like Sales and Customer Service also run on Dataverse, so you can build Power Apps directly against core Dynamics business data without separate integration work.
On the marketing side, Dynamics 365 Customer Insights brings data and engagement together. Its Data capability unifies disconnected CRM data into customer profiles and builds segments; its Journeys capability delivers personalized, real-time, multichannel journeys, with Copilot generating tailored content, emails and images. For analytics, Microsoft OneLake ships automatically with every Microsoft Fabric tenant as a single unified data lake — built on Azure Data Lake Storage, storing tables in open Delta Parquet or Iceberg formats, and using shortcuts so teams share data across workspaces without duplicating it.
If you need pro-developer muscle, Microsoft Foundry supports multi-agent orchestration via C#/Python SDKs, a tool catalog, memory and Foundry IQ knowledge grounding. Foundry agents publish to Microsoft 365, Teams, BizChat or containers, and preview tools connect them to your data: Fabric IQ for Microsoft Fabric data and Work IQ for Microsoft 365 content.
How to prioritise your first workflow
The stack is broad enough that the real risk is starting everywhere at once. Don't. Pick one workflow using three practical filters, and let the rest wait.
- Where your data already lives — if your CRM is Dynamics 365, it's already on Dataverse, so a Power Apps or Copilot Studio agent against that data needs no integration. Start where the connection is free.
- Where a human review step adds safety, not friction — Copilot Studio agent flows support human review natively. A first automation that drafts (a follow-up email, a segment, a journey) and waits for sign-off earns trust faster than one that sends.
- Where the output is reversible and observable — favour read-and-draft over send-and-act for workflow one. You want to watch it run before you let it run alone.
A strong first candidate for most teams: an agent that grounds in your own work data through Microsoft 365 Copilot — which only accesses data the user is already authorized to see under existing permissions — and drafts the repetitive thing a rep or marketer does daily. Low integration cost, built-in permission boundary, easy to audit.
Governance: keep autonomy bounded
The enemy isn't AI acting — it's AI acting in a black box you can't see into. Microsoft's control plane is built for exactly this. Microsoft Agent 365 (generally available May 1, 2026) lets you observe, govern and secure your agents: through the Agent 365 registry in the Microsoft 365 admin center, plus Microsoft Entra and Microsoft Purview, admins manage agent lifecycle, access control and compliance, while Microsoft Defender adds continuous threat detection. It governs agents from Copilot Studio, Dynamics 365 and partners through one registry.
Purview Data Lifecycle Management lets you define retention and deletion policies for human-to-agent and agent-to-human interactions, scoped by users and groups — extending established data-governance controls to agent activity. Use that surface to make every agent action legible: treat each one as a Trigger / Action / Impact record so you can see what fired, what it did, and what changed. That's the practice behind guardrail-driven automation — autonomy inside limits you set, logged and reversible, read-only first.
Last reviewed June 2026. Microsoft and Google rename and reshape these products frequently — confirm current capabilities and naming on the vendor's own docs.
Not sure which Microsoft workflow to automate first?
Before you open Copilot Studio, find out where your data, permissions and review steps actually line up. The free Readiness Score tells you which workflow is ready to automate first — 4 minutes, no login.
Get your free Readiness Score →Keep reading
- Connecting your marketing stack — the vendor-neutral version of how these data spines and connectors fit together.
- Google for marketing & sales — the parallel guide to Google's stack, for teams comparing ecosystems.
- The bounded-autonomy buyer's guide — what to demand from any agent platform before you let it act.