Microsoft 365 admin center will support Tenant restriction v2 [MC931380]

Microsoft 365 admin center will support Tenant restriction v2 [MC931380]

Message ID: MC931380

Coming soon to the Microsoft 365 admin center: Tenant restrictions v2 enables tenants to enhance security by limiting what users can access when they use an external account to sign in from your networks or devices. The Tenant restrictions v2 settings, included with cross-tenant access settings, are designed to address the security of cross-company exchange.

Authentication plane protection is supported by Microsoft Entra ID. This rollout enables data plane protection for the Microsoft 365 admin center. Learn more: Configure tenant restrictions – Microsoft Entra ID – Microsoft Entra External ID | Microsoft Learn

[When this will happen:]

General Availability (Worldwide): We will begin rolling out mid-November and expect to complete by late December 2024.

[How this will affect your organization:]

Before this rollout: Admins are not able to limit what users can access when they use the Microsoft 365 admin center with an external account to sign in from their networks or devices.

After this rollout

  • Tenant restriction v2 (TRv2) can be used to prevent data exfiltration using a foreign identity.
  • TRv2 works by sending special signals to Microsoft Entra ID, Microsoft Account, and other Microsoft resources.
  • Tenant restrictions v2 settings will be off by default and available for admins to enable them.

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your admins about this change and update any relevant documentation.

Review your current configuration to determine the impact for your organization.

Learn more: Configure tenant restrictions – Microsoft Entra ID – Microsoft Entra External ID | Microsoft Learn

To take advantage of TRv2 in the Microsoft 365 admin center, create a cross-tenant access setting. Learn more: Configure tenant restrictions – Microsoft Entra ID – Microsoft Entra External ID | Microsoft Learn

Source: Microsoft

Show 1 Comment

1 Comment

  1. Mike Rosoft

    The introduction of Tenant Restrictions v2 in the Microsoft 365 admin center is set to create a ripple effect, significantly impacting both admins and users. This update is like adding an extra layer of security to your home—imagine having a bouncer at the door who not only checks IDs but also ensures that no one sneaks in with a foreign identity.

    For admins, the ability to limit user access when signing in with external accounts is a game-changer. This means they can now proactively prevent data exfiltration and manage cross-company exchanges with greater control. While the settings will be off by default, the opportunity to tailor these restrictions to fit the specific needs of the organization is invaluable. It’s like having a customizable security system—admins can decide who gets access and under what circumstances.

    On the user side, the impact might be less visible but equally important. Users will find that their access is more secure, minimizing the risk of unauthorized data sharing. However, they might need to adjust to the new restrictions, especially if they’re used to a more open access environment. Think of it as a new dress code at work; it might take a little getting used to, but it ultimately helps maintain professionalism and security.

    Overall, the changes brought by Tenant Restrictions v2 will enhance security and streamline access management in the Microsoft 365 ecosystem. The rollout, expected to begin in mid-November and complete by late December 2024, will provide organizations the time to prepare and adapt.

    I encourage everyone to share their thoughts and experiences with this update. How do you think it will change your day-to-day operations? Let’s keep the conversation going! For more insights, feel free to check out additional posts at mwpro.co.uk.

Leave a Reply

Your email address will not be published. Required fields are marked *