Merge pull request #113438 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/Microsoft/azure-docs (branch master)

Author: huypub

articles/active-directory/develop/msal-net-system-browser-android-considerations.md

@@ -15,7 +15,6 @@ ms.author: marsma
 ms.reviewer: saeeda
 ms.custom: aaddev
 #Customer intent: As an application developer, I want to learn about considerations for using Xamarin Android and MSAL.NET so I can decide if this platform meets my application development needs.
-ms.collection: M365-identity-device-management
 ---
 
 #  Xamarin Android system browser considerations for using MSAL.NET

articles/active-directory/develop/msal-net-uwp-considerations.md

@@ -15,7 +15,6 @@ ms.author: marsma
 ms.reviewer: saeeda
 ms.custom: aaddev
 #Customer intent: As an application developer, I want to learn about considerations for using Universal Windows Platform and MSAL.NET so that I can decide if this platform meets my application development needs.
-ms.collection: M365-identity-device-management
 ---
 
 # Considerations for using Universal Windows Platform with MSAL.NET

articles/active-directory/develop/msal-net-xamarin-android-considerations.md

@@ -15,7 +15,6 @@ ms.author: marsma
 ms.reviewer: saeeda
 ms.custom: aaddev
 #Customer intent: As an application developer, I want to learn about considerations for using Xamarin Android and MSAL.NET so that I can decide if this platform meets my application development needs.
-ms.collection: M365-identity-device-management
 ---
 
 # Considerations for using Xamarin Android with MSAL.NET

articles/active-directory/develop/msal-net-xamarin-ios-considerations.md

@@ -15,7 +15,6 @@ ms.author: marsma
 ms.reviewer: saeeda
 ms.custom: aaddev
 #Customer intent: As an application developer, I want to learn about considerations for using Xamarin iOS and MSAL.NET so I can decide if this platform meets my application development needs.
-ms.collection: M365-identity-device-management
 ---
 
 # Considerations for using Xamarin iOS with MSAL.NET

articles/active-directory/develop/scenario-mobile-app-registration.md

@@ -15,7 +15,6 @@ ms.author: jmprieur
 ms.reviewer: brandwe
 ms.custom: aaddev 
 #Customer intent: As an application developer, I want to know how to write a mobile app that calls web APIs by using the Microsoft identity platform for developers.
-ms.collection: M365-identity-device-management
 ---
 
 # Register mobile apps that call web APIs

articles/active-directory/hybrid/how-to-connect-fed-group-claims.md

@@ -14,15 +14,15 @@ ms.author: billmath
 author: billmath
 ---
 
-# Configure group claims for applications with Azure Active Directory (Public Preview)
+# Configure group claims for applications with Azure Active Directory
 
 Azure Active Directory can provide a users group membership information in tokens for use within applications.  Two main patterns are supported:
 
-- Groups identified by their Azure Active Directory object identifier (OID) attribute (Generally Available)
-- Groups identified by sAMAccountName or GroupSID attributes for Active Directory (AD) synchronized groups and users (Public Preview)
+- Groups identified by their Azure Active Directory object identifier (OID) attribute 
+- Groups identified by sAMAccountName or GroupSID attributes for Active Directory (AD) synchronized groups and users 
 
 > [!IMPORTANT]
-> There are a number of caveats to note for this preview functionality:
+> There are a number of caveats to note for this functionality:
 >
 >- Support for use of sAMAccountName and security identifier (SID) attributes synced from on-premises is designed to enable moving existing applications from AD FS and other identity providers. Groups managed in Azure AD do not contain the attributes necessary to emit these claims.
 >- In larger organizations the number of groups a user is a member of may exceed the limit that Azure Active Directory will add to a token. 150 groups for a SAML token, and 200 for a JWT. This can lead to unpredictable results. If your users have large numbers of group memberships, we recommend using the option to restrict the groups emitted in claims to the relevant groups for the application.  

articles/active-directory/user-help/index.yml

@@ -10,7 +10,6 @@ metadata:
   ms.service: active-directory
   ms.subservice: user-help
   ms.topic: landing-page
-  ms.collection: M365-identity-device-management
   author: curtand
   ms.author: curtand
   ms.date: 08/26/2019

articles/advisor/advisor-high-availability-recommendations.md

@@ -80,7 +80,7 @@ Azure Advisor will identify Azure Cosmos DB accounts that are using old versions
 
 ## Upgrade your Azure Cosmos DB Java SDK to the latest version from Maven
 
-Azure Advisor will identify Azure Cosmos DB accounts that are using old versions of the Java SDK and recommend upgrading to the latest version from Maven for the latest fixes, performance improvements, and new feature capabilities. [Learn more about Cosmos DB Java SDK](https://aka.ms/cosmosdb/sql-api-sdk-dotnet)
+Azure Advisor will identify Azure Cosmos DB accounts that are using old versions of the Java SDK and recommend upgrading to the latest version from Maven for the latest fixes, performance improvements, and new feature capabilities. [Learn more about Cosmos DB Java SDK](https://aka.ms/cosmosdb/sql-api-sdk-async-java)
 
 ## Upgrade your Azure Cosmos DB Spark Connector to the latest version from Maven
 

articles/azure-monitor/app/asp-net-core.md

@@ -24,7 +24,7 @@ The [Application Insights SDK for ASP.NET Core](https://nuget.org/packages/Micro
 * **IDE**: Visual Studio, VS Code, or command line.
 
 > [!NOTE]
-> If you are using ASP.NET Core 3.X along with Application Insights, please use the [2.8.0](https://www.nuget.org/packages/Microsoft.ApplicationInsights.AspNetCore/2.8.0) version or higher. This is the only version that supports ASP.NET Core 3.X.
+> ASP.NET Core 3.X requires [Application Insights 2.8.0](https://www.nuget.org/packages/Microsoft.ApplicationInsights.AspNetCore/2.8.0) or later.
 
 ## Prerequisites
 

articles/key-vault/general/best-practices.md

@@ -17,13 +17,13 @@ ms.author: mbaldwin
 
 ## Control Access to your vault
 
-Azure Key Vault is a cloud service that safeguards encryption keys and secrets like certificates, connection strings, and passwords. Because this data is sensitive and business critical, you need to secure access to your key vaults by allowing only authorized applications and users. This [article](secure-your-key-vault.md)) provides an overview of the Key Vault access model. It explains authentication and authorization, and describes how to secure access to your key vaults.
+Azure Key Vault is a cloud service that safeguards encryption keys and secrets like certificates, connection strings, and passwords. Because this data is sensitive and business critical, you need to secure access to your key vaults by allowing only authorized applications and users. This [article](secure-your-key-vault.md) provides an overview of the Key Vault access model. It explains authentication and authorization, and describes how to secure access to your key vaults.
 
 Suggestions while controlling access to your vault are as follows:
 1. Lock down access to your subscription, resource group and Key Vaults (RBAC)
 2. Create Access policies for every vault
 3. Use least privilege access principal to grant access
-4. Turn on Firewall and [VNET Service Endpoints](overview-vnet-service-endpoints.md))
+4. Turn on Firewall and [VNET Service Endpoints](overview-vnet-service-endpoints.md)
 
 ## Use separate Key Vault
 
@@ -35,9 +35,9 @@ Make sure you take regular back ups of your [vault](https://blogs.technet.micros
 
 ## Turn on Logging
 
-[Turn on logging](logging.md)) for your Vault. Also set up alerts.
+[Turn on logging](logging.md) for your Vault. Also set up alerts.
 
 ## Turn on recovery options
 
-1. Turn on [Soft Delete](overview-soft-delete.md)).
+1. Turn on [Soft Delete](overview-soft-delete.md).
 2. Turn on purge protection if you want to guard against force deletion of the secret / vault even after soft-delete is turned on.