Merge pull request #223196 from MicrosoftDocs/ShawnJackson-patch-1

edit pass: Revert recent changes to access-policies-prerequisites-azure-sql-db.md

Author: itechedit

articles/purview/includes/access-policies-prerequisites-azure-sql-db.md

@@ -8,7 +8,7 @@ ms.date: 12/01/2022
 ms.custom: references_regions
 ---
 
-Create a new SQL database, or use an existing one, in one of the currently available regions for this preview feature. You can follow [this guide to create a SQL database](/azure/azure-sql/database/single-database-create-quickstart).
+Create a new Azure SQL Database instance, or use an existing one, in one of the currently available regions for this preview feature. You can follow [this guide to create an Azure SQL Database instance](/azure/azure-sql/database/single-database-create-quickstart).
 
 #### Region support
 All [Microsoft Purview regions](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=purview) are supported.
@@ -31,21 +31,16 @@ Enforcement of Microsoft Purview policies is available only in the following reg
 - East Asia
 - Australia East
 
-#### Configure the SQL database for policies from Microsoft Purview
-For the logical server to honor policies from Microsoft Purview, you need to configure an Azure Active Directory admin: 
+#### Configure the Azure SQL Database instance for policies from Microsoft Purview
+For the logical server associated with Azure SQL Database to honor policies from Microsoft Purview, you need to configure an Azure Active Directory admin. In the Azure portal, go to the logical server that hosts the Azure SQL Database instance. On the side menu, select **Azure Active Directory**. Set an admin name to any Azure Active Directory user or group that you prefer, and then select **Save**.
 
-1. In the Azure portal, go to the logical server that hosts the SQL database.
+![Screenshot that shows the assignment of an Active Directory admin to a logical server associated with Azure SQL Database.](../media/how-to-policies-data-owner-sql/assign-active-directory-admin-azure-sql-db.png)
 
-1. On the side menu, select **Azure Active Directory**. Set an admin name to any Azure Active Directory user or group that you prefer, and then select **Save**.
+Then, on the side menu, select **Identity**. Under **System assigned managed identity**, turn the status to **On**, and then select **Save**.
 
-   ![Screenshot shows the assignment of an Active Directory admin to a logical server.](../media/how-to-policies-data-owner-sql/assign-active-directory-admin-azure-sql-db.png)
+![Screenshot that shows the assignment of a system-assigned managed identity to a logical server associated with Azure SQL Database.](../media/how-to-policies-data-owner-sql/assign-identity-azure-sql-db.png)
 
-1. On the side menu, select **Identity**. Under **System assigned managed identity**, turn the status to **On**. Then select **Save**.
-
-   ![Screenshot that shows the assignment of a system-assigned managed identity to a logical server.](../media/how-to-policies-data-owner-sql/assign-identity-azure-sql-db.png)
-
-
-You also need to enable (and verify) external policy-based authorization on the logical server. You can do this in PowerShell:
+You also need to enable (and verify) external policy-based authorization on the logical server associated with Azure SQL Database. You can do this in PowerShell:
 
 ```powershell
 Connect-AzAccount -UseDeviceAuthentication -TenantId xxxx-xxxx-xxxx-xxxx-xxxx -SubscriptionId xxxx-xxxx-xxxx-xxxx