Forum Discussion
Intune URLs - Default Category Seems to Include Non-Applicable URLs
I've run a PowerShell script that returns the URLs and IP ranges required by Intune but it seems to return URLs that should not be required such as Cortana.ai, itunes.apple.com, virtualearth.net, assets-yammer.com, platform.linkedin.com and many others. Those listed are in the default category. Does anyone know of a script I can use that just returns URLs and IP ranges essential for Intune, or what I can do to modify the code I am using to do the same. Below is the code I use to collect the IPs\URLs.
(invoke-restmethod -Uri ("https://endpoints.office.com/endpoints/WorldWide?ServiceAreas=MEM`&`clientrequestid=" + ([GUID]::NewGuid()).Guid)) | ?{$_.ServiceArea -eq "MEM" -and $_.urls}
Regards,
Pete.
True, but in my experience, the URLs rarely change. It is the IPs associated with the URLs that change regularly.
4 Replies
To be honest, the already published list of endpoints and urls should be enough to meet the FW\network requirements. https://learn.microsoft.com/en-us/intune/intune-service/fundamentals/intune-endpoints
My concern here is that the URLs are liable to change. I thought the whole idea behind the script was that you could check for those changes. I have a similar process for Exchange and O365, and things have changed since I started using the script.
True, but in my experience, the URLs rarely change. It is the IPs associated with the URLs that change regularly.
