Microsoft IP ranges and FQDN-s in outgoing rules

Announcements

ATTENTION Customers, All Partners and Employees: The Customer Support Portal (CSP) will be undergoing maintenance and unavailable on Saturday, November 7, 2020, from 11 am to 11 pm PST. Please read our blog for more information.

Reply
Highlighted
L0 Member

Microsoft IP ranges and FQDN-s in outgoing rules

Hi all,

must be someone had similar thoughts too,

we have a customer who'd like to secure outgoing traffic, by specifying not only applications, but also restrict destination FQDN-s and/or IP ranges.

Issue with Microsoft is that their FQDN-s, and moreover IP public ranges, change monthly.

I was just wandering if there is a smart way to address this issue?

Is there any feature in roadmap, possibly getting a pre-defined range for Microsoft, that gets dynamically updated, just like country IP ranges?

 

Thanks,

Alex

Tags (3)
Highlighted
L4 Transporter

Is the goal to allow access to only specific tenants within MS? There are some things you can do with header insertion in URL profiles to provide access only to sanctioned Microsoft resources that match your policy.

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000POJACA4

 

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!