Entra ID

Microsoft Entra Tenant Governance Finds Shadow Tenants

3 min read

Summary

Microsoft Entra Tenant Governance now helps organizations discover shadow tenants connected through B2B collaboration, multitenant apps, and shared billing signals. The new related tenants capability gives IT teams continuous visibility into hidden tenant sprawl so they can assess risk, quarantine unsanctioned tenants, and tighten identity governance.

Need help with Entra ID?Talk to an Expert

Microsoft Entra Tenant Governance helps uncover shadow tenants

Introduction

As organizations expand through acquisitions, development projects, and partner collaboration, Microsoft tenant sprawl can quickly become a security blind spot. Microsoft Entra Tenant Governance aims to address that problem with a new related tenants discovery capability that helps admins find shadow tenants before they become an incident response issue.

This matters because tenants outside central IT oversight can still have trusted connections, app permissions, or shared billing ties to your environment. That creates risk even if those tenants were forgotten years ago.

What’s new

Microsoft highlighted the Related Tenants pillar in Entra Tenant Governance, now available in public preview. After enabling discovery in the Microsoft Entra admin center, organizations can identify connected tenants using signals such as:

  • B2B collaboration relationships
  • Multitenant application registrations
  • Shared billing accounts

The process is designed to be simple:

  1. Go to Tenant governance > Related tenants in the Entra admin center
  2. Turn on discovery with a single click
  3. Review surfaced tenants and the signals behind each relationship
  4. Investigate unknown or unsanctioned tenants and take action

Microsoft says the inventory is continuously updated, so this is not just a one-time scan. New tenant relationships can surface automatically as your environment changes.

Why it matters for IT admins

For identity and security teams, the biggest benefit is visibility. Hidden tenants from acquisitions, proof-of-concept work, legacy testing, or partner activity may still expose your organization through user sign-ins, app consent, or cross-tenant access.

Microsoft recommends several response options for suspicious tenants:

  • Confirm exposure by reviewing app permissions, admin consent, and affected users or workloads
  • Block inbound and outbound sign-ins using cross-tenant access settings
  • Contain app-based access by revoking permissions or removing service principals
  • Apply tenant restrictions v2 through Global Secure Access and universal tenant restrictions
  • Validate impact through sign-in and audit logs before deciding whether to onboard or isolate the tenant

Organizations can also expand discovery with additional telemetry, including Azure subscription billing data, Entra sign-in logs, Microsoft 365 activity, and audit logs.

Action items and next steps

Admins should consider the following next steps:

  • Enable related tenants discovery in the Entra admin center or via the tenant governance API
  • Review newly discovered tenants and classify them as trusted, unknown, or unsanctioned
  • Use tenant quarantine workflows for risky tenants pending review
  • Update tenant creation practices, since the legacy workforce tenant creation flow retires on August 15, 2026

For organizations focused on reducing identity attack surface, this preview gives a practical way to find hidden tenant relationships and bring them under governance before attackers do.

Need help with Entra ID?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

Microsoft EntraEntra IDtenant governanceshadow tenantsidentity security

Related Posts

Entra ID

macOS Platform SSO with Entra ID Explained

Microsoft has published new guidance that explains how macOS Platform SSO works with Microsoft Entra ID, including registration, token handling, and ownership boundaries between Apple, Microsoft, and MDM. The clarification helps IT admins better plan deployments, troubleshoot sign-in issues, and understand how security is maintained without exposing powerful credentials to apps.

Entra ID

Microsoft Entra Ignite 2026: New AI Access Controls

Microsoft announced a broad set of Microsoft Entra updates at Ignite 2026 focused on securing AI agents, reducing standing access, and improving multitenant governance. The new capabilities matter for IT teams because they extend identity protections, conditional access, and lifecycle controls to both human users and AI-driven identities.

Entra ID

Microsoft Entra at Ignite 2026: AI Access Sessions

Microsoft has published its Microsoft Entra guide for Ignite 2026, highlighting breakout sessions focused on securing access for users and AI agents. The agenda matters for IT and security teams planning identity, access, and agent governance strategies as AI-driven workloads and threats continue to expand.

Entra ID

Microsoft Entra November 2026: Access Security Updates

Microsoft Entra’s November 2026 updates focus on securing access as users, devices, guests, and AI agents change over time. Key additions include agent and guest lifecycle policies, faster Continuous Access Evaluation based on device and user risk, phishing-resistant MFA improvements, and new governance tools for access drift and application groups.

Entra ID

Microsoft Entra at Ignite 2026: Key Sessions to Watch

Microsoft has outlined its Microsoft Entra presence at Ignite 2026, with breakout sessions focused on securing access for users and AI agents, unified policy management, and faster identity threat response. For IT and security teams, the event offers a practical roadmap for adapting identity and access controls to AI-driven environments.

Entra ID

Entra Conditional Access Policy Plans Preview Launches

Microsoft has introduced Microsoft Entra Conditional Access policy plans in public preview, giving identity teams a new way to manage related access controls at scale. The feature reduces policy sprawl by letting admins define shared targeting once, organize enforcement as rules, and gradually migrate existing Conditional Access policies without disrupting production.