From 6d4202da8479bf86590dfbc24f6b234c209dc0e6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A9ment=20Notin?= Date: Tue, 10 Dec 2024 12:40:46 +0100 Subject: [PATCH] Use more precise page in link Looks like the content was split into this 2nd page whereas the current one is about "number matching" but not these additional location and app name context --- .../authentication/concept-authentication-default-enablement.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/identity/authentication/concept-authentication-default-enablement.md b/docs/identity/authentication/concept-authentication-default-enablement.md index 9fd07cd14ee..2b3837d9c46 100644 --- a/docs/identity/authentication/concept-authentication-default-enablement.md +++ b/docs/identity/authentication/concept-authentication-default-enablement.md @@ -44,7 +44,7 @@ In addition to configuring Authentication methods policy settings to be either * The option to let Microsoft Entra ID manage the setting is a convenient way for an organization to allow Microsoft to enable or disable a feature by default. Organizations can more easily improve their security posture by trusting Microsoft to manage when a feature should be enabled by default. By configuring a setting as **Microsoft managed** (named *default* in Graph APIs), IT admins can trust Microsoft to enable a security feature they haven't explicitly disabled. -For example, an admin can enable [location and application name](how-to-mfa-number-match.md) in push notifications to give users more context when they approve MFA requests with Microsoft Authenticator. The additional context can also be explicitly disabled, or set as **Microsoft managed**. Today, the **Microsoft managed** configuration for location and application name is **Disabled**, which effectively disables the option for any environment where an admin chooses to let Microsoft Entra ID manage the setting. +For example, an admin can enable [location and application name](how-to-mfa-additional-context.md) in push notifications to give users more context when they approve MFA requests with Microsoft Authenticator. The additional context can also be explicitly disabled, or set as **Microsoft managed**. Today, the **Microsoft managed** configuration for location and application name is **Disabled**, which effectively disables the option for any environment where an admin chooses to let Microsoft Entra ID manage the setting. As the security threat landscape changes over time, Microsoft can change the **Microsoft managed** configuration for location and application name to **Enabled**. For customers who want to rely upon Microsoft to improve their security posture, setting security features to **Microsoft managed** is an easy way stay ahead of security threats. They can trust Microsoft to determine the best way to configure security settings based on the current threat landscape.