Skip to content

Cross-tenant Access & B2B Trust

The question it answers: Which external tenants can collaborate with this one, and whose MFA and device-compliance claims does Conditional Access trust?

Which external tenants can collaborate with yours, whose MFA and device-compliance claims your Conditional Access accepts, and where shared channels (B2B direct connect) are open. Trusting another tenant’s device compliance means their Intune decides who is ‘compliant’ in yours.

Where in the appEntra ID › Identity Hygiene › Cross-tenant Access & B2B Trust
WorkloadEntra ID
KindTable
DataBuilt from the tenant data IntensiveReports keeps in memory and refreshes in the background, so it opens at once.
LicenceNo extra licence needed.
Report id (API and MCP)entra.security.cross-tenant-access
ColumnKeyType
TenantNameText
AssessmentSeverityStatus
FindingsFindingsText
B2B inB2BCollaborationInboundText
B2B outB2BCollaborationOutboundText
Direct connect inDirectConnectInboundText
Trust MFATrustMfaText
Trust compliantTrustCompliantDeviceText
Trust hybridTrustHybridJoinedDeviceText
Auto-redeemAutoRedeemInboundText

Licence: No extra licence needed.

Application permissions on the IntensiveReports app registration (all permissions):

PermissionAPIWhat it allowsNote
Policy.Read.AllMicrosoft GraphRead your organization’s policies
CrossTenantInformation.ReadBasic.AllMicrosoft GraphRead cross-tenant basic information
Data sources it reads
  • GET /v1.0/policies/crossTenantAccessPolicy/default
  • GET /v1.0/policies/crossTenantAccessPolicy/partners
  • GET /v1.0/tenantRelationships/findTenantInformationByTenantId (names)
GET /ir-api/v1/reports/entra.security.cross-tenant-access?size=100

An AI assistant reads it with the MCP tool get_report and the id entra.security.cross-tenant-access. The client needs the Read grant for Entra ID. See Using the API.