What Arctera actually announced
Arctera says Microsoft 365 Copilot connects through a custom federated connector to Arctera's MCP server. Through that server, Copilot can interact with enterprise information governed on Arctera's platform. The capability is part of Arctera AI Converge, which uses MCP to connect AI models with information Arctera governs.
Arctera says the work builds on its Unified Platform's communications governance, compliance, and eDiscovery capabilities. The company was created in 2024 from Veritas Technologies. It says the platform captures data from more than 130 content sources and offers more than 280 AI policies.
Arctera's own executives frame the use case as speeding up regulatory inquiries and legal investigations. Product manager Irfan Shuttari said organizations can "dramatically accelerate" those workflows "while maintaining full compliance." That is a vendor claim. The announcement offers no benchmark, customer example, or measured time savings.
What the announcement leaves out
The announcement does not say several things admins would want to know:
- Which content repositories or data types the connector exposes.
- Which Copilot experiences it supports. Arctera says only "supported Copilot workflows."
- Which MCP tools the server offers, and whether any can write or delete data.
- Which authentication method it uses.
- Pricing and licensing.
- Whether retention, legal hold, audit, or access policies are enforced at query time, and what gets logged.
Treat "governance controls in place" as positioning until Arctera publishes technical documentation. Don't read it as a guarantee of compliance outcomes.
How federated connectors work in Microsoft 365 Copilot
Microsoft's documentation explains the model Arctera is using, though it can't confirm Arctera's own implementation. Microsoft says federated connectors:
- Retrieve content in real time through MCP, without indexing data into Microsoft Graph.
- Access data using the user's identity and permissions, and don't index external data into Microsoft 365.
- Are managed and governed by admins in the Microsoft 365 admin center.
- Can read data and, where the connector provides the tools, create, update, or delete data with the user's approval. Admins can audit that activity in Microsoft Purview.
Microsoft also notes that federated connectors fetch content live rather than indexing it. For a governance product, that distinction matters. The source system stays the system of record, and Microsoft says it enforces the permissions. Whatever Arctera's platform decides about who sees what is therefore the relevant control, not a copy sitting in Microsoft 365. Exactly how Arctera maps its policies to each Copilot request is the part still to be documented.
Microsoft says the MCP server determines which tools are available. A connector can therefore be read-only or action-capable. Where tools create, update, or delete data, users must approve them. By default, write tools show a "Needs approval" setting. Researcher stays read-only for federated connectors.
Microsoft lists the supported experiences as Microsoft 365 Copilot Chat, agents, Cowork, Copilot in Word, Excel, PowerPoint and Outlook, and the Researcher agent. Which of those Arctera's connector covers is not stated.
Admin checklist for a custom federated connector
The announcement says a custom federated connector is the route. Microsoft's setup guidance for custom connectors lists these prerequisites:
- An MCP server URL that exposes the tools you want available in Copilot.
- The Global Administrator or AI Administrator role in the Microsoft 365 admin center.
- An appropriate Microsoft Entra admin role if you use single sign-on.
- Access to the Teams Developer Portal.
- Developer and legal details: developer name, website URL, privacy policy URL, and terms of use URL.
Microsoft says custom connectors support three authentication methods: Microsoft Entra SSO, OAuth 2.0, and no authentication. For OAuth 2.0, Microsoft says to include a specific Teams redirect URI in the provider's app registration. It then has you register the OAuth client in the Teams Developer Portal and copy the registration ID. Arctera hasn't said which method it uses, so check with the vendor.
To create the connector:
- Sign in to the Microsoft 365 admin center.
- Select Copilot, then Connectors, then the Gallery tab.
- Under Created by your org, add the Create a new connector tile, then choose Connect to MCP server.
- Enter a display name, a description, and the MCP server base URL.
- Enter the registration ID that matches your authentication method, then save.
If your MCP server restricts incoming traffic by source IP, allow the static egress addresses Microsoft 365 Copilot uses. Microsoft says static egress is on by default.
It's unclear whether Arctera ships a ready-made connector package or expects customers to follow this custom route. Confirm with Arctera before planning a rollout.
Controls that decide who sees it
Microsoft describes layered controls, and all of them must allow a user:
- Agent and plugin access (Agents > Settings) decides whether connectors built by your organization are available.
- User access sets the maximum population.
- Staged rollout, per connector, narrows access within that population.
- Users also need a Microsoft 365 Copilot license, and must connect to the source in Settings > Sources if it requires sign-in.
Microsoft recommends staging first. Select the connector, choose Staged rollout, add pilot users or groups, then use Deploy to all users when ready. Changes can take up to 10 minutes to take effect.
When something doesn't show up, Microsoft's troubleshooting order starts with these checks:
- The publisher type is allowed in Agent and plugin access, or the connector is turned on individually.
- The connector is enabled and not blocked under Agents > Tools.
- The user is in User access and in the staged rollout.
- The user has a Copilot license and has refreshed Copilot.
- The user has signed in to the connector in Settings > Sources.
Context and caveats
Arctera already sells a different Copilot integration. Arctera's existing Copilot connector captures, preserves, and enables surveillance across Copilot interactions, including prompts, responses, and metadata, for regulatory compliance. That integration records what Copilot does. The new MCP connectivity feeds Arctera-governed content into Copilot. They are different directions of the same relationship, and compliance teams may want both.
A fair caution: bringing archived communications into an AI assistant raises its own questions. These include who is allowed to query it, how prompts and results are logged, and whether sensitive content can surface in a response. Microsoft's permission model says the source system enforces access. Whether Arctera's controls behave as hoped is something to test in a pilot, not assume from a press release.
Bottom line
Arctera's MCP connector is a vendor-reported release, and the announcement is light on detail. Microsoft's federated connector documentation gives admins a clear framework for evaluating it:
- Data stays in the source system and is fetched live.
- Access follows the user's identity and permissions.
- Admins control availability, staging, and auditing.
Before a rollout, ask Arctera which tools the connector exposes, which authentication method it uses, and which governance policies apply per query. Then pilot it with a small Entra group.