Message ID: MC981567
As part of our Secure by Default initiative, the tenant isolation feature will be enabled by default for all Power Platform tenants as the new default behavior. The enforcement is scheduled to begin the first week of March 24, 2025.
This feature applies only to Power Platform policies and is separate from guest access policies and Azure tenant restriction features.
How does this affect me?
Tenant isolation only applies to connectors running within a tenant. 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. In addition, users logging in as guests (guest user access) will remain unaffected.
What do I need to do to prepare?
To prevent any disruptions, if our traffic monitoring logs indicate cross-tenant connections involving your tenant, we will proactively set up the necessary policies for you before enforcement. This message is for awareness and no action is required.
However, if you prefer to configure policies proactively prior to enforcement, you can do so by following the tenant isolation policy. 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
- AWS IoT Core adds new logs to troubleshoot connectivity and authentication

- (Updated) Use sensitivity labels to block all connected experiences that analyze content in Word, Excel, and PowerPoint [MC1297982]
![(Updated) Use sensitivity labels to block all connected experiences that analyze content in Word, Excel, and PowerPoint [MC1297982] 3 pexels merictuna 29959515](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)
- (Updated) Microsoft Teams: Viva Engage communities in Teams [MC1218423]
![(Updated) Microsoft Teams: Viva Engage communities in Teams [MC1218423] 4 pexels weirdfish 2640604](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)
- Workers – New Workers bulk secrets API endpoint

![Power Platform - Upcoming enforcement of tenant isolation [MC981567] 1 Power Platform – Upcoming enforcement of tenant isolation [MC981567]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-pixabay-45853-1024x683.webp)

![(Updated) Use sensitivity labels to block all connected experiences that analyze content in Word, Excel, and PowerPoint [MC1297982] 3 pexels merictuna 29959515](https://mwpro.co.uk/wp-content/uploads/2025/06/pexels-merictuna-29959515-150x150.webp)
![(Updated) Microsoft Teams: Viva Engage communities in Teams [MC1218423] 4 pexels weirdfish 2640604](https://mwpro.co.uk/wp-content/uploads/2025/06/pexels-weirdfish-2640604-150x150.webp)

![Microsoft Outlook: New user setting to include a comma in recipient's contact name [MC981634] 7 Microsoft Outlook: New user setting to include a comma in recipient’s contact name [MC981634]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-sebastian-411207-150x150.webp)