![Power Platform – Tenant Isolation will be enabled by default across your tenant [MC942823]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-steve-1418595-1024x683.webp)
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
![Microsoft 365 admin center: Business Chat usage in Microsoft 365 Copilot usage report [MC942832]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-jeswin-700971-150x150.webp)
![Dynamics 365 Field Service – Summarize records with Copilot in the mobile app [MC946934]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-jplenio-1114897-150x150.webp)
The upcoming update regarding tenant isolation in the Power Platform is certainly a significant shift, and it’s bound to have a ripple effect on both admins and users alike. Starting March 2025, the default enabling of tenant isolation will mean that connections between different tenants will be blocked unless specific policies are configured.
For admins, this change will necessitate a proactive approach. They will need to assess their current configurations and potentially establish allow lists for any cross-tenant interactions that are crucial for their operations. While this might sound like a daunting task, think of it as a spring cleaning for your tenant—refreshing and safeguarding your digital space!
Users, on the other hand, may experience a more seamless environment within their own tenant, but they could find themselves facing hurdles when trying to collaborate with external partners unless those connections are pre-approved. It’s like throwing a party and realizing you forgot to send out the invites!
Overall, the impact of this change is poised to be quite substantial. While it enhances security and aligns with the Secure by Default initiative, it also places the onus on admins to ensure that their configurations are in line with their operational needs. It’s a balancing act of security and collaboration that will require some thoughtful planning.
I encourage everyone to share their thoughts and experiences regarding this change. How do you foresee it affecting your workflows? Have you begun preparing for the update? Let’s keep the conversation going! For more insights, don’t forget to check out additional posts on mwpro.co.uk.