M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions m365con.net

Power Platform tenant isolation

Concept

A Power Platform admin setting that blocks cross-tenant connections through Microsoft Entra ID-based connectors unless the external tenant is on an explicit allow list. The episode describes it as enforced by default, breaking undocumented cross-tenant flows.

✦ CONCEPTPower Platform tenantisolationM365.FM
Title graphic: Power Platform tenant isolation (Concept)

Relationships

Power Platform tenant isolation falls under the broader topic Power Platform.

Description

Power Platform tenant isolation is a Power Platform administration setting that controls cross-tenant connections made through connectors. It lets administrators decide which Microsoft Entra tenants may be reached from the tenant (outbound) and which external tenants may connect into it (inbound). The stated aim is to keep connector use secure within the tenant and to reduce the risk of data exfiltration. It is a feature of Power Platform and is configured as part of that platform's tenant-level security settings.

The setting applies only to connectors that authenticate with Microsoft Entra ID, such as Office 365 Outlook or SharePoint. It is separate from the Entra-wide tenant restrictions feature, so access outside Power Platform is not affected by it. According to the documentation notes, only canvas apps and flows are affected, and the Azure DevOps connector is not covered because it uses its own OAuth flow. These boundaries matter when judging what tenant isolation does and does not protect.

The behavior depends on whether the setting is switched on. According to the Microsoft Learn documentation, by default the setting is off, and cross-tenant connections work as long as valid Entra credentials are supplied. When isolation is switched on, all tenants are blocked in both directions except those on an allow list. Each allow-list entry can apply to inbound traffic, outbound traffic or both, and can be specified as a domain or as a tenant ID. A wildcard entry allows every tenant in a given direction. The short description of this topic states that the episode context describes the isolation as enforced by default, which can break cross-tenant flows that were never documented. That wording differs from the documentation notes, so the effective default in a given tenant is worth verifying in the admin center.

Administrators configure tenant isolation in the Power Platform admin center under the security and identity settings. The documentation mentions that a Power Platform administrator role is relevant for viewing and setting it. Because the effect is tenant-wide, a typical preparation step is to inventory which apps and flows rely on connections to partner or other tenants, then add those tenants to the allow list in the correct direction before enabling the restriction.

The consequences of a block differ between design time and runtime. At design time, canvas apps cannot add a connection that violates the policy, and flows can still be saved but are suspended. At runtime, apps and flows that violate the policy fail. This is why undocumented cross-tenant dependencies are a common source of surprises: a flow built years earlier that quietly reads a SharePoint site or sends mail through a connection in another tenant can stop working once isolation is enforced, even though nothing in the flow itself changed.

In practice, decisions around tenant isolation come down to balancing collaboration with data-exfiltration risk. Organizations that work with partners or subsidiaries in separate tenants need deliberate allow-list entries, while organizations without such needs can leave the allow list empty and block every external tenant. Using specific domains or tenant IDs is narrower than the wildcard, which opens a whole direction. Since the topic sits under the broader Power Platform area, it is usually reviewed together with other governance and data-protection settings for environments, connectors and flows.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeConcept
DocumentationPower Platform tenant isolation – Microsoft Learn learn.microsoft.com

Frequently asked questions

Questions marked with AI were written with AI from the facts on this page.

What does Power Platform tenant isolation block? (AI)

When switched on, it blocks cross-tenant connections made through Microsoft Entra ID-based connectors in both directions, except for tenants on an allow list. It affects only canvas apps and flows.

How are exceptions to tenant isolation defined? (AI)

Exceptions are allow-list entries given as a domain or tenant ID, applied to inbound, outbound or both directions. A wildcard entry allows every tenant in a direction.

What happens to existing apps and flows that use cross-tenant connections? (AI)

At runtime, apps and flows that violate the policy fail. At design time, canvas apps cannot add the connection and flows are saved but suspended.

Related topics in brief

Topics linked to Power Platform tenant isolation, each briefly explained:

All relationships of Power Platform tenant isolation, grouped by type of relationship:

Broader topic

Broader topics of Power Platform tenant isolation:

Glossary

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

Nobody has listed this topic yet. Add it to your profile.

Experts on related topics

Experts on topics related to Power Platform tenant isolation, each with the topic that connects them:

Sources

Maintained by Mirko Peters (Microsoft MVP) · Last updated: