Field Service in Outlook and Teams after the add-in deprecation

What it does

Field Service used to ship a Copilot-assisted Outlook add-in and a Teams app that let frontline managers create and manage work orders from an email or a Teams tab. Microsoft deprecated that whole family in 2025. What's left is Microsoft 365 Copilot answering Field Service questions inside model-driven apps and Microsoft 365 surfaces, plus the separate Teams chat integration on work order records.

Key facts

Deprecation announced 1 September 2025. Support ended after 30 October 2025.
Four integrations went together: the Microsoft Outlook Add-in, the Microsoft Teams app, Microsoft Viva Connections and Microsoft Planner. The old documentation pages for these now redirect to the deprecation notice.
Microsoft did not name a single replacement product. The guidance points at "a simpler, more integrated Field Service experience inside Microsoft 365" and refers readers to the release plans.
The 2025 release wave 2 plan describes Teams and Outlook integration for frontline workers managing bookings, and Copilot spanning web, mobile and Microsoft 365 apps, as investment areas. Treat anything not yet in product documentation as planned rather than shipped.
Microsoft 365 Copilot in model-driven apps is the currently documented path for asking natural-language questions about Field Service data from a Copilot surface. It is read-only over Dataverse and cannot modify records.
That path needs a Dynamics 365 Enterprise or Premium licence for the Dynamics data, and a Microsoft 365 Copilot licence for anything beyond Dataverse. An admin must enable Microsoft 365 Copilot for the app before the button appears.
It is not available on the Power Apps mobile app.
Selecting or @mentioning an agent inside that pane stops the Dataverse queries unless the agent is explicitly configured for them.
The Teams chats and channels integration on work order records is a different thing entirely and was not part of the deprecation. It links Teams chats to a work order so everyone sees the same conversation history, and it needs its own admin setup.
The Outlook calendar integration for bookings — bookable resource bookings syncing to technicians' Outlook calendars — is also separate from the deprecated add-in and remains documented.

When to use / skip

The main job here is corrective. Plenty of solution designs, statements of work and internal wikis written in 2024 and early 2025 still promise the Outlook add-in and the Teams app. If you inherit one of those, the first thing to do is check whether the client was ever actually using them, and if so, plan the exit rather than the rollout.

For new work, the honest position is that the Microsoft 365 story for Field Service is mid-rebuild. What you can safely commit to today is Teams chat linked to work orders, Outlook calendar sync for bookings, and Microsoft 365 Copilot answering read-only questions about Field Service data for licensed users. Anything more — creating a work order from an email, managing bookings inside Teams — is a release-plan promise, not a deliverable, and should not appear in a fixed-price scope.

Skip the Microsoft 365 Copilot path where the client has no Microsoft 365 Copilot licences. Read-only Dataverse answers alone rarely justify a licensing conversation with a CFO, and the same questions can be asked in the Field Service Copilot pane at no extra cost.

Configuration decisions

Whether the client ever adopted the deprecated add-in, Teams app, Viva Connections cards or Planner integration, and what replaces each specific workflow they built on them.
Whether Microsoft 365 Copilot is enabled for the Field Service model-driven app, and for which user groups.
Which licences are actually in place — Dynamics 365 Enterprise or Premium for the Dataverse answers, Microsoft 365 Copilot for the rest — before promising anyone the experience.
Whether Teams chat integration on work orders is turned on, and the governance around linked chats becoming part of the record's history.
Whether Outlook calendar sync for bookings is in scope, and in which direction changes are allowed to flow.
What the client is told about roadmap items versus shipped features, and how that is documented so it doesn't become a change request later.

Gotchas

The deprecation is easy to miss because the old documentation URLs still resolve — they just serve a notice now. Anyone skim-reading a bookmark will think the feature still exists.
Viva Connections and Planner going at the same time surprises people. Clients who built a frontline manager experience on Viva cards lost more than they expected.
The Teams app being deprecated and the Teams chat integration being alive is a genuinely confusing distinction, and both get called "Teams integration" in meetings.
Microsoft 365 Copilot in the app is read-only. Any requirement phrased as "create the work order from the email" is not met by it.
The licensing split has two layers, and proposals routinely price only one of them.
Release plan wording is not a commitment. Features move waves, and Field Service's Microsoft 365 integration has already been rebuilt once.

Consultant notes

Audit the client's tenant for the deprecated add-in and Teams app early. Finding it in the discovery phase is a conversation; finding it at go-live is an escalation.
Be explicit with the client about the difference between what is documented today and what is in the 2025 wave 2 release plan. Put it in the design document in those words.
If the client's real requirement is a manager triaging inbound email into work orders, design it properly with a flow or a Copilot Studio agent rather than waiting for the platform to catch up.
Demo the Teams chat integration on a work order — it's genuinely useful, it's stable, and it satisfies most of what people mean when they ask for "Teams integration".
Before go-live, confirm which users hold Microsoft 365 Copilot licences. The feature appearing for the project team and not for the business is a classic UAT surprise.

Worth another look once the rebuilt Outlook and Teams booking experiences actually ship, rather than sitting in the release plan.