Merge pull request #177629 from MicrosoftDocs/repo_sync_working_branch

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

Author: huypub

articles/active-directory/external-identities/current-limitations.md

@@ -32,7 +32,7 @@ Azure AD B2B is subject to Azure AD service directory limits. For details about
 [National clouds](../develop/authentication-national-cloud.md) are physically isolated instances of Azure. B2B collaboration is not supported across national cloud boundaries. For example, if your Azure tenant is in the public, global cloud, you can't invite a user whose account is in a national cloud. To collaborate with the user, ask them for another email address or create a member user account for them in your directory.
 
 ## Azure US Government clouds
-Within the Azure US Government cloud, B2B collaboration is supported between tenants that are both within Azure US Government cloud and that both support B2B collaboration. Azure US Government tenants that support B2B collaboration can also collaborate with social users using Microsoft, Google accounts, or email one-time passcode accounts. If you invite a user outside of these groups (for example, if the user is in a tenant that isn't part of the Azure US Government cloud or doesn't yet support B2B collaboration), the invitation will fail or the user won't be able to redeem the invitation. For details about other limitations, see [Azure Active Directory Premium P1 and P2 Variations](../../azure-government/compare-azure-government-global-azure.md#azure-active-directory-premium-p1-and-p2).
+Within the Azure US Government cloud, B2B collaboration is supported between tenants that are both within Azure US Government cloud and that both support B2B collaboration. Azure US Government tenants that support B2B collaboration can also collaborate with social users using Microsoft, Google accounts, or email one-time passcode accounts. If you invite a user outside of these groups (for example, if the user is in a tenant that isn't part of the Azure US Government cloud or doesn't yet support B2B collaboration), the invitation will fail or the user won't be able to redeem the invitation. For Microsoft accounts (MSAs), there are known limitations with accessing the Azure portal: newly invited MSA guests are unable to redeem direct link invitations to the Azure portal, and existing MSA guests are unable to sign in to the Azure portal. For details about other limitations, see [Azure Active Directory Premium P1 and P2 Variations](../../azure-government/compare-azure-government-global-azure.md#azure-active-directory-premium-p1-and-p2).
 
 ### How can I tell if B2B collaboration is available in my Azure US Government tenant?
 To find out if your Azure US Government cloud tenant supports B2B collaboration, do the following:
@@ -51,4 +51,4 @@ To find out if your Azure US Government cloud tenant supports B2B collaboration,
 See the following articles on Azure AD B2B collaboration:
 
 - [What is Azure AD B2B collaboration?](what-is-b2b.md)
-- [Delegate B2B collaboration invitations](delegate-invitations.md)
+- [Delegate B2B collaboration invitations](delegate-invitations.md)

articles/api-management/api-management-howto-setup-delegation.md

@@ -149,7 +149,7 @@ Recommended steps for creating a new delegation endpoint to implement on your si
 
 These code samples show how to:
 
-* Take the *delegation validation key*, which is set in the **Delegation** screen of the publisher portal.
+* Take the *delegation validation key*, which is set in the **Delegation** screen of the Azure portal.
 * Create an HMAC, which validates the signature, proving the validity of the passed returnUrl.
 
 With slight modification, you can use the same code for the **productId** and **userId**.

articles/backup/backup-create-rs-vault.md

@@ -17,7 +17,7 @@ Azure Backup automatically handles storage for the vault. You need to specify ho
 > [!NOTE]
 > Changing **Storage Replication type** (Locally redundant/ Geo-redundant) for a Recovery Services vault has to be done before configuring backups in the vault. Once you configure backup, the option to modify is disabled.
 >
->- If you haven't yet configured the backup, then [follow these steps](#set-storage-redundancy) to review and modify the settings.
+>- If you haven't yet configured the backup, complete the following steps to review and modify the settings.
 >- If you've already configured the backup and must move from GRS to LRS, then [review these workarounds](#how-to-change-from-grs-to-lrs-after-configuring-backup).
 
 1. From the **Recovery Services vaults** pane, select the new vault. Under the **Settings** section, select  **Properties**.
@@ -54,7 +54,7 @@ When restoring a VM, you can restore the VM or its disk. If you're restoring fro
 
 To choose this feature, select **Enable Cross Region Restore** from the **Backup Configuration** pane.
 
-Since this process is at the storage level, there are [pricing implications](https://azure.microsoft.com/pricing/details/backup/).
+Because this process is at the storage level, there are [pricing implications](https://azure.microsoft.com/pricing/details/backup/).
 
 >[!NOTE]
 >Before you begin:
@@ -163,4 +163,4 @@ If you need to keep the current protected data in the GRS vault and continue the
 ## Next steps
 
 [Learn about](backup-azure-recovery-services-vault-overview.md) Recovery Services vaults.
-[Learn about](backup-azure-delete-vault.md) Delete Recovery Services vaults.
+[Learn about](backup-azure-delete-vault.md) Delete Recovery Services vaults.

articles/dms/tutorial-azure-postgresql-to-azure-postgresql-online-portal.md

@@ -44,7 +44,7 @@ To complete this tutorial, you need to:
 * Check [status of migration scenarios supported by Azure Database Migration Service](./resource-scenario-status.md) for supported migration and version combinations. 
 * An existing [Azure Database for PostgreSQL](../postgresql/index.yml) version 10 and later instance with the **DVD Rental** database. 
 
-    Also note that the target Azure Database for PostgreSQL version must be equal to or later than the on-premises PostgreSQL version. For example, PostgreSQL 10 can migrate to Azure Database for PostgreSQL 10, or 11, but not to Azure Database for PostgreSQL 9.6. Migrations to PostgreSQL 13+ are not supported at this time. 
+    Also note that the target Azure Database for PostgreSQL version must be equal to or later than the on-premises PostgreSQL version. For example, PostgreSQL 10 can migrate to Azure Database for PostgreSQL 10, or 11, but not to Azure Database for PostgreSQL 9.6. 
 
 * [Create an Azure Database for PostgreSQL server](../postgresql/quickstart-create-server-database-portal.md) or [Create an Azure Database for PostgreSQL - Hyperscale (Citus) server](../postgresql/quickstart-create-hyperscale-portal.md) as the target database server to migrate data into.
 * Create a Microsoft Azure Virtual Network for Azure Database Migration Service by using the Azure Resource Manager deployment model. For more information about creating a virtual network, see the [Virtual Network Documentation](../virtual-network/index.yml), and especially the quickstart articles with step-by-step details.

articles/purview/supported-classifications.md

@@ -39,13 +39,16 @@ Person bloom filter has been prepared using the below two datasets.
 - [2010 US Census Data for Last Names (162-K entries)](https://www.census.gov/topics/population/genealogy/data/2010_surnames.html)
 - [Popular Baby Names (from SSN), using all years 1880-2019 (98-K entries)](https://www.ssa.gov/oact/babynames/limits.html)
 
+> [!NOTE]
+> Azure Purview classifies columns only when the data contains first/last names. Azure Purview doesn't classify columns that contain full names.
+
 ## RegEx Classifications
 
 ## ABA routing number
 
 ### Format
 
-nine digits that may be in a formatted or unformatted pattern
+Nine digits that can be in a formatted or unformatted pattern.
 
 ### Pattern