[BULK] - DocuTune - Rebranding of Azure Active Directory to Microsoft Entra

Author: alexbuckgit

articles/active-directory/authentication/concept-system-preferred-multifactor-authentication.md

@@ -12,7 +12,7 @@ ms.reviewer: msft-poulomi
 ms.collection: M365-identity-device-management
 
 
-# Customer intent: As an identity administrator, I want to encourage users to use the Microsoft Authenticator app in Azure AD to improve and secure user sign-in events.
+# Customer intent: As an identity administrator, I want to encourage users to use the Microsoft Authenticator app in Microsoft Entra ID to improve and secure user sign-in events.
 ---
 
 # System-preferred multifactor authentication  - Authentication methods policy
@@ -54,7 +54,7 @@ By default, system-preferred MFA is [Microsoft managed](concept-authentication-d
 |----------|------|-------------|
 | excludeTarget | featureTarget | A single entity that is excluded from this feature. <br>You can only exclude one group from system-preferred MFA, which can be a dynamic or nested group.|
 | includeTarget | featureTarget | A single entity that is included in this feature. <br>You can only include one group for system-preferred MFA, which can be a dynamic or nested group.|
-| State | advancedConfigState | Possible values are:<br>**enabled** explicitly enables the feature for the selected group.<br>**disabled** explicitly disables the feature for the selected group.<br>**default** allows Azure AD to manage whether the feature is enabled or not for the selected group. |
+| State | advancedConfigState | Possible values are:<br>**enabled** explicitly enables the feature for the selected group.<br>**disabled** explicitly disables the feature for the selected group.<br>**default** allows Microsoft Entra ID to manage whether the feature is enabled or not for the selected group. |
 
 ### Feature target properties
 
@@ -134,7 +134,5 @@ The system-preferred MFA also applies for users who are enabled for MFA in the l
 
 ## Next steps
 
-* [Authentication methods in Azure Active Directory](concept-authentication-authenticator-app.md)
+* [Authentication methods in Microsoft Entra ID](concept-authentication-authenticator-app.md)
 * [How to run a registration campaign to set up Microsoft Authenticator](how-to-mfa-registration-campaign.md)
-
-

articles/active-directory/authentication/concepts-azure-multi-factor-authentication-prompts-session-lifetime.md

@@ -1,6 +1,6 @@
 ---
-title: Azure Active Directory (Azure AD) feature availability in Azure Government
-description: Learn which Azure AD features are available in Azure Government. 
+title: Microsoft Entra feature availability in Azure Government
+description: Learn which Microsoft Entra features are available in Azure Government. 
 
 services: multi-factor-authentication
 ms.service: active-directory
@@ -16,13 +16,15 @@ ms.reviewer: mattsmith
 ms.collection: M365-identity-device-management
 ---
 
-# Azure Active Directory feature availability
+# Microsoft Entra feature availability
 
 <!---Jeremy said there are additional features that don't fit nicely in this list that we need to add later--->
 
-This following tables list Azure AD feature availability in Azure Government.
+This following tables list Microsoft Entra feature availability in Azure Government.
 
-## Azure Active Directory
+<a name='azure-active-directory'></a>
+
+## Microsoft Entra ID
 
 |Service     | Feature | Availability |
 |:------|---------|:------------:|
@@ -33,7 +35,7 @@ This following tables list Azure AD feature availability in Azure Government.
 || Passwordless (Windows Hello for Business, Microsoft Authenticator, FIDO2 security key integrations) | &#x2705; | 
 || Certificate-based authentication | &#x2705; | 
 || Service-level agreement | &#x2705; | 
-|**Applications access**|SaaS apps with modern authentication (Azure AD application gallery apps, SAML, and OAUTH 2.0) | &#x2705; | 
+|**Applications access**|SaaS apps with modern authentication (Microsoft Entra application gallery apps, SAML, and OAUTH 2.0) | &#x2705; | 
 || Group assignment to applications | &#x2705; | 
 || Cloud app discovery (Microsoft Defender for Cloud Apps) | &#x2705; | 
 || Application Proxy for on-premises, header-based, and Integrated Windows Authentication | &#x2705; | 
@@ -46,8 +48,8 @@ This following tables list Azure AD feature availability in Azure Government.
 || Identity Protection (risk events investigation, SIEM connectivity) | See [Identity protection](#identity-protection) below. | 
 |**Administration and hybrid identity**|User and group management | &#x2705; | 
 || Advanced group management (Dynamic groups, naming policies, expiration, default classification) | &#x2705; | 
-|| Directory synchronization—Azure AD Connect (sync and cloud sync) | &#x2705; | 
-|| Azure AD Connect Health reporting | &#x2705; | 
+|| Directory synchronization—Microsoft Entra Connect (sync and cloud sync) | &#x2705; | 
+|| Microsoft Entra Connect Health reporting | &#x2705; | 
 || Delegated administration—built-in roles  | &#x2705; | 
 || Global password protection and management – cloud-only users | &#x2705; | 
 || Global password protection and management – custom banned passwords, users synchronized from on-premises Active Directory | &#x2705; | 
@@ -81,7 +83,7 @@ This following tables list Azure AD feature availability in Azure Government.
 | Risk Detection | Availability |
 |----------------|:--------------------:|
 |Leaked credentials (MACE) | &#x2705; |
-|Azure AD threat intelligence | &#10060; |
+|Microsoft Entra threat intelligence | &#10060; |
 |Anonymous IP address | &#x2705; | 
 |Atypical travel | &#x2705; |
 |Anomalous Token | &#x2705; |
@@ -104,13 +106,8 @@ This following tables list Azure AD feature availability in Azure Government.
 
 | HR-provisioning app | Availability |
 |----------------|:--------------------:|
-|Workday to Azure AD User Provisioning | &#x2705; |
+|Workday to Microsoft Entra User Provisioning | &#x2705; |
 |Workday Writeback | &#x2705; |
-|SuccessFactors to Azure AD User Provisioning | &#x2705; | 
+|SuccessFactors to Microsoft Entra User Provisioning | &#x2705; | 
 |SuccessFactors to Writeback | &#x2705; |
 |Provisioning agent configuration and registration with Gov cloud tenant| Works with special undocumented command-line invocation:<br> AADConnectProvisioningAgent.Installer.exe ENVIRONMENTNAME=AzureUSGovernment |
-
-
-
-
-

articles/active-directory/authentication/feature-availability.md

@@ -1,6 +1,6 @@
 ---
-title: Browser support of FIDO2 passwordless authentication | Azure Active Directory
-description: Browsers and operating system combinations support FIDO2 passwordless authentication for apps using Azure Active Directory
+title: Browser support of FIDO2 passwordless authentication | Microsoft Entra ID
+description: Browsers and operating system combinations support FIDO2 passwordless authentication for apps using Microsoft Entra ID
 
 services: active-directory
 ms.service: active-directory
@@ -17,11 +17,11 @@ ms.collection: M365-identity-device-management
 ---
 # Browser support of FIDO2 passwordless authentication
 
-Azure Active Directory allows [FIDO2 security keys](./concept-authentication-passwordless.md#fido2-security-keys) to be used as a passwordless device. The availability of FIDO2 authentication for Microsoft accounts was [announced in 2018](https://techcommunity.microsoft.com/t5/identity-standards-blog/all-about-fido2-ctap2-and-webauthn/ba-p/288910), and it became [generally available](https://techcommunity.microsoft.com/t5/azure-active-directory-identity/passwordless-authentication-is-now-generally-available/ba-p/1994700) in March 2021. The following diagram shows which browsers and operating system combinations support passwordless authentication using FIDO2 authentication keys with Azure Active Directory. Azure AD currently supports only hardware FIDO2 keys and doesn't support passkeys for any platform.
+Microsoft Entra ID allows [FIDO2 security keys](./concept-authentication-passwordless.md#fido2-security-keys) to be used as a passwordless device. The availability of FIDO2 authentication for Microsoft accounts was [announced in 2018](https://techcommunity.microsoft.com/t5/identity-standards-blog/all-about-fido2-ctap2-and-webauthn/ba-p/288910), and it became [generally available](https://techcommunity.microsoft.com/t5/azure-active-directory-identity/passwordless-authentication-is-now-generally-available/ba-p/1994700) in March 2021. The following diagram shows which browsers and operating system combinations support passwordless authentication using FIDO2 authentication keys with Microsoft Entra ID. Microsoft Entra ID currently supports only hardware FIDO2 keys and doesn't support passkeys for any platform.
 
 ## Supported browsers
 
-This table shows support for authenticating Azure Active Directory (Azure AD) and Microsoft Accounts (MSA). Microsoft accounts are created by consumers for services such as Xbox, Skype, or Outlook.com. 
+This table shows support for authenticating Microsoft Entra ID and Microsoft Accounts (MSA). Microsoft accounts are created by consumers for services such as Xbox, Skype, or Outlook.com. 
 
 | OS  | Chrome | Edge | Firefox | Safari |
 |:---:|:------:|:----:|:-------:|:------:|
@@ -98,7 +98,7 @@ The following tables show which transports are supported for each platform. Supp
 | Chrome  | ❌  | ❌ | ❌ |
 | Firefox | ❌  | ❌ | ❌ |
 
-<sup>1</sup>Security key biometrics or PIN for user verficiation isn't currently supported on Android by Google. Azure AD requires user verification for all FIDO2 authentications.
+<sup>1</sup>Security key biometrics or PIN for user verficiation isn't currently supported on Android by Google. Microsoft Entra ID requires user verification for all FIDO2 authentications.
 
 ## Minimum browser version
 

articles/active-directory/authentication/fido2-compatibility.md

@@ -1,6 +1,6 @@
 ---
-title: Find and address gaps in strong authentication coverage for your administrators in Azure Active Directory 
-description: Learn how to find and address gaps in strong authentication coverage for your administrators in Azure Active Directory
+title: Find and address gaps in strong authentication coverage for your administrators in Microsoft Entra ID 
+description: Learn how to find and address gaps in strong authentication coverage for your administrators in Microsoft Entra ID
 
 services: active-directory
 ms.service: active-directory
@@ -19,9 +19,11 @@ ms.collection: M365-identity-device-management
 
 Requiring multifactor authentication (MFA) for the administrators in your tenant is one of the first steps you can take to increase the security of your tenant. In this article, we'll cover how to make sure all of your administrators are covered by multifactor authentication.
 
-## Detect current usage for Azure AD Built-in administrator roles
+<a name='detect-current-usage-for-azure-ad-built-in-administrator-roles'></a>
 
-The [Azure AD Secure Score](../fundamentals/identity-secure-score.md) provides a score for **Require MFA for administrative roles** in your tenant. This improvement action tracks the MFA usage of Global administrator, Security administrator, Exchange administrator, and SharePoint administrator. 
+## Detect current usage for Microsoft Entra Built-in administrator roles
+
+The [Microsoft Entra ID Secure Score](../fundamentals/identity-secure-score.md) provides a score for **Require MFA for administrative roles** in your tenant. This improvement action tracks the MFA usage of Global administrator, Security administrator, Exchange administrator, and SharePoint administrator. 
 
 There are different ways to check if your admins are covered by an MFA policy. 
 
@@ -43,7 +45,7 @@ There are different ways to check if your admins are covered by an MFA policy.
 
 If you find administrators who aren't protected by multifactor authentication, you can protect them in one of the following ways:
 
-- If your administrators are licensed for Azure AD Premium, you can [create a Conditional Access policy](tutorial-enable-azure-mfa.md) to enforce MFA for administrators. You can also update this policy to require MFA from users who are in custom roles.  
+- If your administrators are licensed for Microsoft Entra ID P1 or P2, you can [create a Conditional Access policy](tutorial-enable-azure-mfa.md) to enforce MFA for administrators. You can also update this policy to require MFA from users who are in custom roles.  
 
 - Run the [MFA enablement wizard](https://aka.ms/MFASetupGuide) to choose your MFA policy.
 
@@ -57,7 +59,7 @@ After your admins are enforced for multifactor authentication and have been usin
 - [FIDO2](concept-authentication-passwordless.md#fido2-security-keys)
 - [Windows Hello for Business](/windows/security/identity-protection/hello-for-business/hello-overview)
 
-You can read more about these authentication methods and their security considerations in [Azure AD authentication methods](concept-authentication-methods.md).
+You can read more about these authentication methods and their security considerations in [Microsoft Entra authentication methods](concept-authentication-methods.md).
 
 ## Next steps