Official documentation checked October 14, 2026.
You cannot assume that allowing two Microsoft Entra tenants to collaborate makes Microsoft 365 Copilot search both tenants’ documents, email and chats as one combined collection. Microsoft’s documented B2B access controls and its Copilot connector features solve different problems. There is no documented universal “Cross-tenant data access” switch matching that promise.
Before changing permissions, decide whether users need access to a particular shared document, separate Copilot use in each organization, or a deliberately designed assistant that queries selected sources.
Separate collaboration from Copilot search federation
Microsoft Entra cross-tenant access settings govern inbound and outbound B2B collaboration and B2B direct connect, including which users, groups and applications participate. Trusting an external organization’s authentication claims does not, by itself, grant access to all its content.
A user being able to open a shared document proves access to that item. It does not prove that general Copilot chat can discover every document, mailbox and conversation in its tenant. Similarly, a successful cross-tenant sign-in is an identity result, not an acceptance test for a search integration.
Ask both organizations’ administrators to define the intended use case and its supported product path. Do not turn on broad external access merely to test whether an undocumented search feature appears.
Choose a supported route for the actual task
- Working on a specific file: check the app’s supported sharing and Copilot behavior. Microsoft’s multiple-account access documentation permits some open-document scenarios using another account’s Copilot entitlement when policy allows. That does not give the user general access to the organization’s Microsoft Graph.
- Working separately in two organizations: use the appropriate account and approved Copilot entry point for each organization. Check entitlement and policies in each context, rather than assuming one session covers both.
- Searching selected external business sources: evaluate a supported connector or a purpose-built agent with explicit authentication and source permissions. Confirm that the chosen connector actually supports the repository and scenario.
Microsoft’s connector overview uses “federated” for live retrieval through MCP, distinct from synced indexing. The term does not mean that enabling B2B direct connect merges two Microsoft 365 tenants’ indexes.
For a custom solution, budget for permission mapping, source updates, auditing and revocation tests. Treat any transfer or new indexed copy as a data-governance decision. Do not promise that every integration preserves the original storage geography or applies every source policy unchanged.
Avoid unsupported consent links and search headers
Do not follow a hand-built administrator-consent URL using Microsoft Graph’s application ID as though it were your own cross-tenant search application. Consent must belong to a verified application with a documented purpose, publisher and permission set. Repeating an inappropriate consent flow will not create Copilot federation.
The documented Microsoft Graph search/query API does not define a Cross-Tenant-Data-Access header. Adding that header to Graph Explorer is not a supported method of granting external search access. A successful HTTP response is also not proof that the results came from the other tenant.
Do not interpret the absence of results as a reason to grant more permissions automatically. First check the application, signed-in identity, data source and documented search support. A service’s licensing prerequisites must also be verified separately; qualifying Copilot base subscriptions are not limited to E3 and E5.
Validate a pilot before approving wider access
Use a small, explicitly approved dataset with known source URLs. Test an allowed user, an excluded user and a user whose source permission has just been revoked. Check both the cited content and the account that accessed it. A response that merely mentions the other organization is not evidence of authenticated retrieval.
Record where information is fetched, stored and retained, who can inspect interaction records, and how access is removed. If the required combination is not documented, take the specific scenario to Microsoft or the connector provider before deployment. The safe outcome may be separate tenant workflows until an approved integration is available—not an improvised federation setting.