π Microsoft Entra ID Named Locations are not defined π’
- Contextual name: π Named Locations are not defined π’
- ID:
/ce/ca/azure/microsoft-entra-id/named-locations
- Located in: π Microsoft Entra ID
Flagsβ
- π’ Impossible policy
- π’ Policy with categories
- π’ Policy with type
Our Metadataβ
- Policy Type:
COMPLIANCE_POLICY
- Policy Category:
SECURITY
Descriptionβ
Descriptionβ
Microsoft Entra ID Conditional Access allows an organization to configure
Named locations
and configure whether those locations are trusted or untrusted. These settings provide organizations the means to specify Geographical locations for use in conditional access policies, or define actual IP addresses and IP ranges and whether or not those IP addresses and/or ranges are trusted by the organization.Rationaleβ
Defining trusted source IP addresses or ranges helps organizations create and enforce Conditional Access policies around those trusted or untrusted IP addresses and ranges. Users authenticating from trusted IP addresses and/or ranges may have less access restrictions or access requirements when compared to users that try to authenticate to Microsoft Entra ID from untrusted locations or untrusted source IP addresses/ranges.
Impactβ
When configuring
Named locations
, the organization can create locations using Geographical location data or by defining source IP addresses or ranges. ConfiguringNamed locations
using a Country location does not provide the organization the ability to mark those locations as trusted, and any Conditional Access policy relying on thoseCountries location
setting will not be able to use theAll trusted locations
setting within the Conditional Access policy. They instead will have to rely on theSelect locations
setting. This may add additional resource requirements when configuring, and will require thorough organizational testing.... see more
Remediationβ
Remediationβ
From Azure Portalβ
- In the Azure Portal, navigate to
Microsoft Entra ID
.- Under
Manage
, clickSecurity
.- Under
Protect
, clickConditional Access
.- Under
Manage
, clickNamed locations
.- Within the
Named locations
blade, click onIP ranges location
.- Enter a name for this location setting in the
Name
text box.- Click on the
+
sign.- Add an IP Address Range in CIDR notation inside the text box that appears.
- Click on the
Add
button.- Repeat steps 7 through 9 for each IP Range that needs to be added.
- If the information entered are trusted ranges, select the
Mark as trusted location
check box.- Once finished, click on
Create
.From PowerShellβ
Create a new trusted IP-based Named location policy:
[System.Collections.Generic.List`1[Microsoft.Open.MSGraph.Model.IpRange]]$ipRanges = @() $ipRanges.Add("<first IP range in CIDR notation>") $ipRanges.Add("<second IP range in CIDR notation>") $ipRanges.Add("<third IP range in CIDR notation>") New-MgIdentityConditionalAccessNamedLocation -dataType "#microsoft.graph.ipNamedLocation" -DisplayName "<name of IP Named location policy>" -IsTrusted $true -IpRanges $ipRanges
... [see more](remediation.md)
policy.yamlβ
Linked Framework Sectionsβ
Section | Sub Sections | Internal Rules | Policies | Flags |
---|---|---|---|---|
πΌ CIS Azure v2.1.0 β πΌ 1.2.1 Ensure Trusted Locations Are Defined - Level 1 (Manual) | 1 | |||
πΌ CIS Azure v3.0.0 β πΌ 2.2.1 Ensure Trusted Locations Are Defined (Manual) | 1 | |||
πΌ Cloudaware Framework β πΌ General Access Controls | 10 |