Action Required – Microsoft Purview Audit Management Activity API service tag changes [MC1052910]

Action Required – Microsoft Purview Audit Management Activity API service tag changes [MC1052910]

Message ID: MC1052910

Due to ongoing security hardening of Microsoft Purview services, the Microsoft Purview Audit Management Activity API will be hosted on a new set of IP addresses which will have a new service tag.

[When this will happen:]

This change will be in effect on April 21, 2025.

[How this will affect your organization:]

If your organization followed official M365 endpoint guidance (https://aka.ms/m365endpoints), then no action is necessary, and no impact is expected.

If your organization’s network security policies only allow access to Service tag or allowlisting specific IPs, you will need to make changes to add the new Service tag for continued access.

This new service tag will be shared by multiple Microsoft Security Products to offer various capabilities. The service tag M365ManagementActivityApiWebhook will be unaffected and should continue to be allow listed by your organization.

[What you need to do to prepare:]

If you currently allow outbound traffic based on Azure service tags, please add the new Azure service tag AzureFrontDoor.MicrosoftSecurity which will be applicable and available by April 21, 2025.

For updated service tag definition, please refer to Download Azure IP Ranges and Service Tags – Public Cloud from Official Microsoft Download Center

For more information about the Microsoft Purview Audit Management Activity API, please refer to Management Activity API reference | Microsoft Learn.

Note: Refer to Microsoft 365 URLs and IP address ranges which outlines M365 network guidance on the supported way to manage domains for M365.

Source: Microsoft

Show 1 Comment

1 Comment

  1. Mike Rosoft

    The recent announcement regarding the changes to the Microsoft Purview Audit Management Activity API service tag is certainly a significant development for both admins and users alike. Beginning April 21, 2025, these changes will be implemented as part of Microsoft’s ongoing commitment to enhancing security, which is always a positive step in our increasingly digital world.

    For administrators, the impact is quite straightforward. If your organization has been diligently following the official M365 endpoint guidance, you can breathe a sigh of relief—no action is necessary, and your operations should remain unaffected. However, if your network security policies are a bit more restrictive, and you rely on allowlisting specific IPs or service tags, you will need to make the necessary adjustments to include the new service tag, AzureFrontDoor.MicrosoftSecurity. It’s a great reminder that staying proactive in managing network security can prevent future headaches!

    On the user side, the changes should be largely transparent, given that the backend adjustments are primarily for security and compliance. Users can continue to enjoy the reliable functionality of Microsoft Purview, knowing that their data is being protected by the latest security measures. And let’s be honest—who wouldn’t appreciate a little extra peace of mind when it comes to data security?

    In terms of overall impact, these changes reinforce Microsoft’s dedication to robust security practices, which is crucial in today’s environment where data breaches are unfortunately common. It also encourages organizations to review and update their network security policies regularly, fostering a culture of vigilance and adaptability.

    So, what do you think? Are you excited about these changes, or do you feel a bit of apprehension about implementing new service tags? Let’s hear your thoughts! Feel free to share your insights or experiences in the comments below. And for those looking for more information, don’t forget to check out additional posts on mwpro.co.uk. Your input could be invaluable to fellow readers navigating these updates!

Leave a Reply

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