I had opened a service request for this because the download of the Intune Management Extension (imeswdb-afd-secondary.manage.microsoft.com) was not working despite the correct allowlisting of the specified IP networks. At that time, IP addresses from the subnets 13.107. from AzureFrontDoor.FrontEnd were being resolved. The response was that I needed to allow the subnet 13.107.0.0/16.
Now, however, name resolution returns an IP address from the subnet 150.171.109.0/24. These all belong to the AzureFrontDoor.FrontEnd group. I doubt that these ranges are used exclusively for Intune, and without an explicit statement to that effect, I cannot implement the required firewall exception.
Could you please either:
a) update your documentation accordingly, or
b) restrict usage to documented IP ranges?
In this state, I cannot use Intune.
EDIT:
After further testing, this appears to be an inconsistent approach from microsoft. Based on my observations, the domain zone .manage.microsoft.com only partially resolves to the IP ranges documented in ID163.
This does not (or no more?) apply to any other entries that are also refer to specific subdomains of .manage.microsoft.com.
This means that for instance ID170 (Win32Apps) or "Network requirements for PowerShell scripts and Win32 apps" cannot be reached by Intune IP whitelisting alone. You would also have to include the IPs from AzureFrontDoor.Frontend. At least currently, these subdomains resolve to the IP ranges that are documented under this service tag.