Tenant isolation enforcement has been postponed [MC1074710]
Posted inPower Platform

Tenant isolation enforcement has been postponed [MC1074710]

1Posted inPower Platform

Message ID: MC1074710

Update: Tenant isolation enforcement was previously scheduled to begin in May 2025. However, enforcement has been postponed. We will send another Message Center communication when additional details or an updated timeline for enforcement become available.

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. 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.

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 the enforcement.

What do I need to do to prepare?
This message is for awareness and no action is required.

Source: Microsoft

Latest Posts

Tags:
Show 1 Comment

1 Comment

  1. Mike Rosoft
    15 May 2025,

    The recent update regarding the postponement of tenant isolation enforcement presents a fascinating shift for both administrators and users within the Power Platform ecosystem. While the original timeline set for May 2025 has been pushed back, the implications of the Secure by Default initiative are worth discussing.

    For administrators, this change means a bit of breathing room. With the enforcement being delayed, there’s additional time to assess and adapt their policies and practices to ensure a seamless transition when the time comes. The focus on tenant isolation is a positive step towards enhancing security, but it also requires careful planning and consideration. The proactive measures mentioned—like setting up necessary policies based on traffic monitoring logs—will be a relief for many admins who are already juggling multiple responsibilities.

    On the user side, the impact might be less noticeable at first. The good news is that communications within the same tenant will remain unaffected, which means users can continue their work without interruption. However, the block on cross-tenant connections may lead to some adjustments in how users collaborate across different organizations. It’s a classic case of “good news, bad news,” but ultimately, the enhanced security measures should lead to a safer working environment.

    Overall, while the changes may seem daunting at first glance, they promise to fortify the security framework of the Power Platform. The humor in this situation? It’s like being told to prepare for a storm that keeps getting postponed—plenty of time to grab that extra umbrella!

    I encourage everyone to share their thoughts on this update. How do you think these changes will impact your workflow? Let’s get the conversation going! For more insights and discussions, don’t forget to check out other posts on mwpro.co.uk.

Comments are closed