1. Microsoft Azure Documentation
"Use the location condition in a Conditional Access policy": This document explicitly states how to configure locations for use in Conditional Access. In the section "Configure IP address ranges location
" it clarifies
"You can mark IP address ranges that represent your organization's on-premises network in Azure AD as a named location... Private IP ranges cannot be specified." This supports using public IP ranges and directly refutes options involving private IPs.
Source: Microsoft Corporation. (2023). Use the location condition in a Conditional Access policy. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/azure/active-directory/conditional-access/location-condition#configure-ip-address-ranges-location
2. Microsoft Azure Documentation
"Configure Azure AD Multi-Factor Authentication settings": This document describes the "Trusted IPs" feature and its limitations. It notes
"If you're using Conditional Access
trusted IPs must be configured as a named location." This confirms that for modern policy-based control
Named Locations is the correct and integrated feature to use
making it superior to the legacy "Trusted IPs" option.
Source: Microsoft Corporation. (2023). Configure Azure AD Multi-Factor Authentication settings. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/azure/active-directory/authentication/howto-mfa-mfasettings#trusted-ips