Microsoft IP ranges and FQDN-s in outgoing rules

[Goran_A]

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

[rmfalconer]

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