Microsoft listed the feature as launched in Roadmap item 501120, with general availability dated April 2026; its Microsoft Tech Community announcement followed on May 5. Current Microsoft Learn documentation, updated September 1, confirms the implementation has expanded into a managed connector framework that includes Copilot Chat, Excel, Researcher, and Cowork. The original roadmap wording names “Agent Mode in Excel,” but Microsoft’s current Excel support documentation now calls the feature Edit with Copilot or editing mode. For admins, the important point is that the underlying Excel capability is still supported even as the product label has changed.
The immediate benefit is fresher information. A user can ask Copilot to retrieve a project status, sales record, support detail, or specialized research from a connected service at prompt time, using the access the user already has in that service. The constraint is equally important: a federated connector is read-only. It is a retrieval path for Copilot, not a general-purpose automation channel that can edit tickets, change CRM records, or run arbitrary actions in a third-party system.
Real-Time Retrieval Replaces Another Copy of the Data
Microsoft 365 has long supported synced connectors, which pull material from a third-party system into Microsoft’s substrate and index it in Microsoft Graph. That model can make externally held content searchable and available for Copilot grounding, but it introduces a second searchable copy, an ingestion schedule, source-administrator setup, and a continuing data-management obligation.
Federated connectors take the other route. According to Microsoft Learn, the connector invokes the source through MCP at runtime; content stays in the external service and is not indexed into Microsoft 365. Authentication is based on the individual user’s identity, with OAuth-based configuration between the external service and Microsoft Entra ID. In practical terms, an employee who cannot open a particular HubSpot record, Box document, Azure DevOps item, or financial-data result should not receive it through Copilot either.
That approach is useful where staleness is the bigger problem than broad enterprise discovery. A regularly indexed knowledge base can be a sound fit for policy documents and durable reference material. A live query is more appropriate for a sales pipeline, engineering backlog, live service status, or an external research source whose contents change throughout the day.
It also changes the failure mode. A synced connector can return an older indexed copy when the source is unavailable or the crawl has not yet caught up. A federated connector depends on the source service, its MCP server, its OAuth configuration, and the user’s current entitlement being available when the question is asked. Copilot can be more current, but it is also directly exposed to outages, API limits, authentication expiry, and poor query behavior in the external system.
The Licensing Boundary Is Narrower Than the UI Suggests
The connector menu may make federated sources look like a simple Copilot setting, but Microsoft’s licensing documentation makes clear that availability is tied to the full commercial Microsoft 365 Copilot entitlement. Every person querying a federated source needs a Microsoft 365 Copilot add-on license or Microsoft 365 E7.
That excludes two licensing arrangements that some organizations may expect to work. Microsoft says federated connectors are not supported for users covered only by a Copilot Studio license, and they are not supported under Microsoft 365 Copilot pay-as-you-go. Those models can support certain agent scenarios or synced-search capabilities, but they do not unlock federated grounding in Microsoft 365 Copilot.
The distinction deserves attention in pilots. An organization can build or license an agent separately from Microsoft 365 Copilot, then discover that the desired live external-data experience is unavailable in Copilot Chat or Excel for the intended users. Before enabling a connector, administrators should verify both the tenant’s licensing model and the licenses assigned to the pilot group rather than treating a successful admin-side configuration as proof of end-user eligibility.
Microsoft says no separate connector charge applies once an organization has the required Microsoft 365 Copilot licenses. That does not mean the integration is cost-free. The third-party service may have its own API, data-access, MCP hosting, or subscription costs, and any internal MCP server still needs to be built, secured, maintained, and monitored.
Microsoft-Published Connectors Can Be On by Default
The most consequential deployment detail is not in the roadmap item: Microsoft-published federated connectors are enabled by default at the tenant level unless an administrator disables them. Partner-published connectors require Microsoft approval and an administrator’s approval before the organization can use them, but the default state for Microsoft-published sources means a tenant should not assume every new option will arrive disabled.
Microsoft’s current connector gallery spans services in finance, customer relationship management, design, developer tooling, project management, files, IT service management, health, legal work, and productivity. Examples listed by Microsoft include HubSpot, Intercom, Linear, Notion, Box, Azure DevOps, Cloudflare, Malwarebytes, Canva, Context7, Microsoft Learn, LSEG, Moody’s, Morningstar, S&P Global, and Wolfram. The presence of a connector in the gallery is not a finding that it is appropriate for every tenant; it means Microsoft has made a governed connection route available.
Admins can manage individual connectors from the Microsoft 365 admin center under Copilot connectors and Your connections. Microsoft documents tenant-wide enablement and disablement, selective rollout to Microsoft Entra ID groups, and user-scope controls for individual connectors. Users still authenticate with their own credentials and can turn a connected source off, but the administrator decides whether the source is offered at all.
Microsoft has also moved this control plane. Its older Set-FederatedConnectorToggle PowerShell mechanism was retired on August 25, 2026. The replacement is the Allowed agent types setting in Agent 365, where admins can disable the connector agent type globally and then selectively re-enable individual connections for approved users or groups. Microsoft says tenants that relied on the old PowerShell state must reapply the policy in the new interface by October 20, 2026, or the old setting will stop being honored.
That deadline creates a concrete housekeeping task. Organizations that disabled federated connectors through PowerShell during preview or early rollout should verify the new Agent 365 setting now. Otherwise, a policy that appeared to be holding the feature off can lapse after October 20.
“No Indexing” Does Not Remove the Governance Work
Microsoft’s central privacy claim is accurate but incomplete if it is read as a blanket security conclusion. Federated connectors do not copy or index external data in Microsoft 365, and Microsoft says source permissions remain enforced. The company also documents encrypted communications, OAuth 2.0 authentication, read-only behavior, and auditing in Microsoft Purview.
Those controls reduce the risk of creating a broad secondary corpus of third-party information inside Microsoft 365. They do not eliminate the need to assess what Copilot is allowed to send to the connected service to answer a query, what the source logs, how its MCP server interprets requests, or whether user permissions in that source are clean. Microsoft’s Excel documentation explicitly says users must consent before data is sent to an external service. That is a useful confirmation step, but it is not a substitute for a data-flow review.
The right security question is therefore narrower and more useful than “Does Microsoft store our external data?” Ask instead: Which users can invoke which connector, what request context reaches the service, what source permissions will Copilot inherit, and what audit trail exists when it does? The answer will vary by connector and by the external vendor’s own identity, retention, and logging policies.
For sensitive sources, start with a limited Entra ID group and a set of real business prompts. Verify that users receive only the records they can open directly in the source system. Test accounts with deliberately different entitlements, revoked access, and expired credentials. Then review Purview events and the third-party service’s logs before expanding access.
What Users Will Actually See
Once IT enables a federated connector, users discover it in the Sources controls for Researcher and in supported Copilot Chat experiences. They connect their own account, authenticate to the external service, and then can ask Copilot to draw on that source for an answer. Microsoft says the source can be disabled by the user later from Researcher or Copilot Chat settings.
In Excel, the change is more than a separate chat convenience. Copilot can retrieve external information and use it in a workflow that produces editable tables, formulas, analysis, charts, or workbook changes. That makes the feature attractive for analysts, but it also makes verification essential: a live external result can feed a workbook that is shared onward, while the result may change after the prompt was run. Teams using this for operational or financial work should preserve source citations, timestamps, and the approved output of the analysis rather than assume a later query will reproduce the same result.
Microsoft’s rollout turns MCP from a developer and agent-building concept into a tenant-managed Microsoft 365 capability. The near-term decision for administrators is not whether live third-party data is useful—it plainly can be—but whether their tenant has selected the sources, licenses, access groups, and review process needed to expose it safely.