Microsoft Copilot Autopilot for Dynamics 365: Follow-Up Automation, Preview Status and Cost Risks

The three stories are separate, but CX Today sees the same problem in each: customer data only matters if a business can turn it into a useful action without the experience feeling intrusive, disjointed or robotic. For people running Microsoft 365, Dynamics 365 and Power Platform, the Microsoft part matters most, so we'll start there.

Microsoft: Copilot gets a follow-up job​

On September 25, 2026, Microsoft announced a redesigned Copilot built around three capabilities: Home (with Office in Copilot), the Code app builder, and Autopilot, a persistent agent. Microsoft pitched it mainly as a workplace productivity release. CX Today argues it could matter more for customer engagement than that framing suggests.

What Autopilot is supposed to do​

Autopilot is the new name for the agent Microsoft previously called Scout. In Microsoft's blog post, Jared Spataro, Chief Marketing Officer for AI at Work, describes it this way:

• You give it a name, a role and a goal.
• It watches channels, follows up on threads, runs recurring work and can pick a project back up days later without being prompted.
• It runs in the cloud, so it keeps working while the user is offline.
• It sits inside the organization's tenant with its own identity, memory, computer and workspace, and is built on Microsoft IQ.

Microsoft's example is a supplier review. Autopilot builds the schedule and workback plan, then handles prep, meetings and follow-ups, including asking stakeholders for updates. The agent shows up where people already work — Teams, Outlook, chats, channels and documents — so you can @mention it like a colleague, with permissions, audit and governance behind it. You set the objective and boundaries; Autopilot handles the rest.

These are Microsoft's descriptions of how the product is designed. They don't prove that any particular deployment will behave well.

The CRM piece: Dynamics 365 and Power Platform grounding​

This is the part that most affects customer engagement. Microsoft says rolling out over the next month in public preview, Copilot is now grounded in data and workflows from Dynamics 365 and Power Platform. So, when a salesperson is working on a proposal, for instance, Copilot can incorporate data like deal history and support tickets right into the document, with no app-switching or distracting lookups required.

Admins should note the exact wording. This is a public preview rolling out over roughly a month. It was not generally available on announcement day. A separate item, Fabric IQ, which brings trusted context from your data, including the 20+ million semantic models in Power BI into Copilot, is generally available in Chat and Cowork.

WindowsForum's earlier coverage adds some detail. It reported that the Work IQ public preview starts September 30. The Microsoft 365 message center summary scopes it more narrowly than the blog: Work IQ now includes Dynamics 365 Sales, Dynamics 365 Customer Service, and Power Platform data, enabling Copilot to ground responses and tasks on business and productivity data. Microsoft's blog lists more, including Finance and Operations, Power Apps and third-party line-of-business apps. According to the same report, Finance and Operations support is planned for late October. If your organization runs something other than Sales or Customer Service, check the message center entry before promising anything to your service teams.

The data plumbing will look familiar to Dynamics shops. Microsoft names Dataverse as the store for Work IQ semantic models and skills, and Dataverse is already the data layer for Dynamics 365, Power Platform and Copilot Studio.

Where it stands today​

For anyone building a business case: Autopilot is a private preview. No general availability date was given.

The billing detail CX leaders shouldn't skip​

Microsoft's blog says Cowork, Code and Autopilot, along with other long-running agentic features, run on usage-based billing (UBB). Everyday Copilot use stays on a per-user subscription license. So an agent that chases every open service ticket also runs up a meter.

To help, Microsoft is adding FinOps controls in Agent 365. Admins get API-driven spending policies, approval workflows for credit requests, and settings that decide which model families each group of users can access. Before letting Autopilot loose on the customer backlog, work out what "persistent" will cost you.

Section summary: Microsoft is moving CRM context into the collaboration tools where follow-up work actually happens. The rollout is staged and in preview, and the persistent-agent part is metered.

Why this matters for customer engagement​

CX Today's main point will sound right to any support lead. Follow-ups rarely get lost because the team lacks data. They get lost because the data sits in one system while the work happens in email, Teams, documents and meetings. Microsoft seems to be trying to close that gap.

CX Today asks the obvious question: will Autopilot be a useful safety net for forgotten tasks, or one more agent that needs constant supervision? A proactive agent could prepare a customer briefing, chase an internal update or keep a service task moving. It could also cause confusion if its permissions, memory and escalation paths are poorly defined.

A few cautions, based on general industry experience rather than anything Microsoft has shown:

• Nothing announced shows Autopilot contacting customers directly. Microsoft's examples are internal: stakeholders, schedules, supplier reviews. The customer-facing scenarios above are possibilities, not shipped features.
• "Before employees remember to" is CX Today's phrase, not Microsoft's promise. The agent follows up within the objectives and boundaries a user sets.
• Memory is also a governance question. An agent with its own identity and memory is a new principal in your tenant. Once CRM data is involved, it's worth checking how it's scoped, audited and retired.
• No outcome data exists yet. Microsoft has published no measured results on follow-up completion or customer satisfaction.

For CX leaders, the bigger change may be where customer journeys get managed. CX Today suggests more of that work will happen in everyday collaboration tools, not only in a dedicated CRM or orchestration platform. If that's right, the Teams admin and the Dynamics admin need to start talking.

Section summary: The idea is strong and the problem is real. Execution will depend on permissions design, escalation paths and cost controls.

Adobe and the NHL: personalization at league scale​

The second story has no Microsoft connection, and nothing announced suggests the NHL uses the new Copilot features. It's a useful comparison anyway. On September 28, 2026, the NHL announced that Adobe is its Official Creative, Marketing and AI Partner, ahead of the 2026–27 regular season. The league says it has more than 200 million fans across 147 countries. That is the league's own figure, not an independent count.

The NHL and its 32 clubs get access to Adobe's CX Enterprise tools:

• Adobe GenStudio for AI-assisted content production for NHL.com, the NHL app, social media and digital ads, adapted to individual markets and languages.
• Adobe Experience Platform for a real-time view of fan needs and preferences.
• Adobe Journey Optimizer to act on those insights across app, web, email and in-arena channels.
• Adobe Express and Firefly for a possible future in which fans create shareable NHL-themed content. The league frames this as something that could happen, not a launched feature.

The NHL says the aim is to run personalization as one league-wide program instead of market-by-market experiments that are hard to scale. CX Today notes this is one of the first partnerships announced since Adobe named its new CEO. Adobe CMO Lara Balazs said the League will be able to "scale relevant, engaging content across every channel where fans spend their time." No financial terms or timeline for the fan-creation tools were disclosed.

CX Today's test is a fair one: can the NHL make millions of interactions feel more relevant without turning every touchpoint into another generic marketing message?

The contrast with Microsoft is useful. Microsoft's approach faces employees: it brings CRM context into the tools where staff work. Adobe's faces the audience: it uses fan data to shape what fans see. Both are sold as "proactive engagement," but an agent chasing an internal thread and a system choosing what a hockey fan sees are very different things.

In other news: Forrester's Journey Orchestration Wave​

CX Today also flagged Forrester's latest Customer Journey Orchestration Wave:

• Leaders: Adobe, Alterian, CSG
• Strong Performers: Salesforce, Genesys, Engage Hub, inQuba
• Contenders: Medallia, Quantum Metric

The list shows how broad the category has become. It now includes specialists alongside CRM, contact center, analytics and CX platforms. Microsoft doesn't appear in the placements CX Today reported. That's notable given the argument above that orchestration may drift toward collaboration tools. Microsoft is coming at the problem through Copilot and Dynamics 365 rather than as a standalone journey-orchestration product.

What Microsoft shops should do now​

1. Check the message center for the Work IQ / Dynamics 365 grounding preview, and confirm which Dynamics apps are covered in your tenant.
2. Decide whether to join Frontier or the Autopilot private preview based on a specific, low-risk follow-up scenario. Internal case updates are a better first test than anything customer-facing.
3. Set spending policies in Agent 365 before piloting, since Autopilot runs on usage-based billing.
4. Write down agent boundaries. Decide what records it can see, whom it can contact, and when it must hand off to a person.

CX Today ends with a line worth remembering: the technology is getting closer to the customer moment, and the businesses that succeed will keep "context, consent, and human judgment close behind it."