Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into frontdoortitlelengthseo

Author: KumudD

articles/active-directory/authentication/concept-password-ban-bad.md

@@ -165,7 +165,7 @@ Since this password is at least five (5) points, it is accepted.
 | Users synchronized from on-premises Windows Server Active Directory | Azure AD Premium P1 or P2 | Azure AD Premium P1 or P2 |
 
 > [!NOTE]
-> On-premises Windows Server Active Directory users that not synchronized to Azure Active Directory also avail the benefits of Azure AD password protection based on existing licensing for synchronized users.
+> On-premises Windows Server Active Directory users that are not synchronized to Azure Active Directory also benefits from Azure AD password protection based on existing licensing for synchronized users.
 
 Additional licensing information, including costs, can be found on the [Azure Active Directory pricing site](https://azure.microsoft.com/pricing/details/active-directory/).
 

articles/active-directory/devices/faq.md

@@ -117,7 +117,7 @@ See below on how these actions can be rectified.
 
 ### Q: Does Windows 10 device registration in Azure AD support TPMs in FIPS mode?
 
-**A:** No, currently device registration on Windows 10 for all device states - Hybrid Azure AD join, Azure AD join, and Azure AD registered - does not support TPMs in FIPS mode. To successfully join or register to Azure AD, FIPS mode needs to be turned off for the TPMs on those devices
+**A:** Windows 10 device registration only supported for FIPS-compliant TPM 2.0 and not supported for TPM 1.2. If your devices have FIPS-compliant TPM 1.2, you must disable them before proceeding with Azure AD join or Hybrid Azure AD join. Note that Microsoft does not provide any tools for disabling FIPS mode for TPMs as it is dependent on the TPM manufacturer. Please contact your hardware OEM for support. 
 
 ---
 

articles/active-directory/devices/hybrid-azuread-join-plan.md

@@ -90,7 +90,8 @@ If your Windows 10 domain joined devices are [Azure AD registered](overview.md#g
 - You can prevent your domain joined device from being Azure AD registered by adding this registry key - HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin, "BlockAADWorkplaceJoin"=dword:00000001.
 - In Windows 10 1803, if you have Windows Hello for Business configured, the user needs to re-setup Windows Hello for Business after the dual state clean up.This issue has been addressed with KB4512509
 
-
+> [!NOTE]
+> The Azure AD registered device will not be automatically removed if it is managed by Intune.
 
 ## Review controlled validation of hybrid Azure AD join
 

articles/active-directory/managed-identities-azure-resources/how-to-use-vm-sdk.md

@@ -1,5 +1,5 @@
 ---
-title: How to use managed identities for Azure resources on an Azure VM with Azure SDKs
+title: Use managed identities on an Azure VM with Azure SDKs - Azure AD
 description: Code samples for using Azure SDKs with an Azure VM that has managed identities for Azure resources.
 services: active-directory
 documentationcenter: 

articles/active-directory/managed-identities-azure-resources/how-to-use-vm-sign-in.md

@@ -1,5 +1,5 @@
 ---
-title: How to use managed identities for Azure resources on an Azure VM for sign in
+title: Use managed identities on an Azure VM for sign in - Azure AD
 description: Step by step instructions and examples for using an Azure VM managed identities for Azure resources service principal for script client sign in and resource access.
 services: active-directory
 documentationcenter: 

articles/active-directory/managed-identities-azure-resources/how-to-view-managed-identity-service-principal-powershell.md

@@ -1,5 +1,5 @@
 ---
-title: How to view the service principal of a managed identity using PowerShell
+title: View the service principal of a managed identity using PowerShell - Azure AD
 description: Step-by-step instructions for viewing the service principal of a managed identity using PowerShell.
 services: active-directory
 documentationcenter: ''

articles/active-directory/managed-identities-azure-resources/howto-assign-access-cli.md

@@ -1,5 +1,5 @@
 ---
-title: How to assign a managed identity access to an Azure resource using Azure CLI
+title: Assign a managed identity access to a resource using Azure CLI - Azure AD
 description: Step by step instructions for assigning a managed identity on one resource, access to another resource, using Azure CLI.
 services: active-directory
 documentationcenter: 

articles/active-directory/managed-identities-azure-resources/howto-assign-access-powershell.md

@@ -1,5 +1,5 @@
 ---
-title: How to assign a managed identity access to an Azure resource using PowerShell
+title: Assign a managed identity access to a resource using PowerShell - Azure AD
 description: Step by step instructions for assigning a managed identity on one resource, access to another resource, using PowerShell.
 services: active-directory
 documentationcenter: 

articles/active-directory/managed-identities-azure-resources/howto-migrate-vm-extension.md

@@ -1,5 +1,5 @@
 ---
-title: Stop using the managed identity VM extension and start using the Azure Instance Metadata Service endpoint
+title: Stop using managed identity VM extension - Azure AD
 description: Step by step instructions to stop using the VM extension and start using the Azure Instance Metadata Service (IMDS) for authentication.
 services: active-directory
 documentationcenter: 

articles/active-directory/managed-identities-azure-resources/known-issues.md

@@ -1,5 +1,5 @@
 ---
-title: FAQs and known issues with managed identities for Azure resources
+title: FAQs and known issues with managed identities - Azure AD
 description: Known issues with managed identities for Azure resources.
 services: active-directory
 documentationcenter: