Message ID: MC942823
As part of our Secure by Default initiative, tenant isolation will be enabled by default on your tenant starting March 2025. This change will only affect your tenant if you do not currently have a tenant isolation policy configured.
Tenant isolation only applies to Power Platform policies and is separate from guest access policy and Azure tenant restriction features.
How does this affect me?
The default tenant isolation behavior will block all connection attempts from one tenant to another; inbound (connections to the tenant from external tenants), outbound (connections from the tenant to external tenants), or both (inbound – outbound) will be blocked by Power Platform. Communications within the same tenant will not be affected.
What do I need to do to prepare?
You can enable a tenant isolation policy prior to enforcement by following the tenant isolation policy guide. Additionally, please ensure you identify scenarios currently using cross-tenant connections or anticipate calls to or from other tenants by establishing an allow list of the relevant tenant IDs by following the recommended guidelines.
Source: Microsoft
Latest Posts
- Amazon ECS adds Amazon VPC Lattice support for blue/green, linear, and canary deployments

- MC1166852: Microsoft Viva Copilot Analytics Adds Agent Dashboard for Adoption and Credit Insights

- Access, Cloudflare One – New strict service token authentication setting for Access

- Rules – hash_in_range() is globally available for HTTP products







