Before you pilot it, confirm three things: that the preview actually shows up in your tenant, that your licensing covers it, and exactly who in a connected Teams channel will see customer data. Microsoft announced on October 8, 2026 that the "Dynamics 365 CRM in the flow of Teams experience is now available in public preview." For a business already running Dynamics 365 and Teams, that makes one question worth answering now: can a small native pilot handle one customer-account handoff well enough that you don't need to build, or keep paying for, a custom integration for it? It's a preview, so treat it as an evaluation, not a replacement.
What Microsoft announced, and when
The announcement is dated Oct 8, 2026. Microsoft describes the core behavior like this: "Once a Teams channel is connected to a customer account, agents can deliver real-time updates such as pre-meeting briefs, case notifications, and account developments before engaging with a customer." In plain terms, a sales or service channel gets tied to a CRM account, and account context is pushed into the place the team already talks.
No general-availability date or tenant rollout schedule is given for the CRM-in-Teams experience. So public preview is the status, full stop. Plan around that.
Don't flatten the availability labels
The same announcement covers several things at different maturity levels. Microsoft says: "These skills are generally available in Cowork, with Autopilot in private preview and Code available through the Frontier Program." That sentence is about other skills and surfaces, not the Teams CRM connection. If someone in a planning meeting says "it's GA now," ask which piece they mean.
A bounded pilot, step by step
Prerequisites: an existing Dynamics 365 CRM deployment, Microsoft Teams already in use, an admin who can confirm preview availability, and one named business owner for the pilot. We suggest keeping the pilot inside a single tenant where both products already run. That's a proposed pilot boundary, not a Microsoft eligibility rule: the announcement doesn't state tenant or eligibility requirements, so have your admin or Microsoft contact confirm them. Microsoft hasn't published a CRM-specific setup procedure in the sources we reviewed either, so these are evaluation steps, not configuration instructions.
- Pick one handoff you already run today. A good candidate is the pre-meeting account brief for a single team, or case notifications for one service queue. Write down how it works now and who relies on it.
- Confirm the preview is actually available in your tenant. The announcement says public preview; it doesn't promise every tenant sees it on the same day.
- Confirm licensing with your Microsoft contact or partner before anyone builds expectations. The announcement doesn't spell out entitlements for this experience.
- List who belongs to the Teams channel you plan to connect, and compare that list to who should see that account's CRM data. Guests and broad channels deserve a second look.
- Recheck the sharing caveat Microsoft documents for Channel Agent (details below) and decide whether sensitive accounts stay out of the pilot.
- Run the pilot alongside the existing process, not instead of it. Assign a human owner who reviews what the agent posts.
- Define a plain acceptance check up front, for example: briefs are accurate against the CRM record and arrive before the meeting. Only retire the old process after it passes for a stretch you agreed on in advance.
The governance questions to carry over
Microsoft's Channel Agent admin documentation is older (it shows "Last updated on 11/17/2025") and predates this CRM announcement, so it isn't proof of how the new CRM connection is set up. But two points in it are worth asking about for the new experience.
- Preview status: Microsoft says preview features are "provided for evaluation and exploration purposes only." That's a reason to keep a pilot small and to avoid wiring a critical customer process to it.
- Sensitivity labels: the documentation notes that "the output doesn't inherit the controls of the sensitivity label itself and doesn't prevent the information from being further shared." If your CRM data or source documents rely on labels to limit sharing, test what happens to agent-posted summaries before connecting regulated or confidential accounts.
Neither point is confirmed as CRM-specific behavior yet. Ask your admin or Microsoft contact to verify both for the CRM connection before production use.
Native preview or custom integration?
If you already have a Power Automate flow or a custom bot that posts Dynamics updates into Teams, this preview isn't an automatic reason to rip it out. It's a reason to compare. Run the native version on one handoff, measure it against the same acceptance check your current integration meets, and decide with evidence. Where the native experience covers the job, you carry less custom code. Where it falls short on permissions, timing or format, the custom path still earns its keep.
What the announcement doesn't establish matters too. It says nothing about guaranteed real-time delivery, cost savings, or the safety of letting agents act on their own. Those are things your pilot has to show you, not things to assume.