Merge pull request #219642 from inward-eye/main

prmerger-automator[bot] · web-flow · commit b24e8e9ff491 · 2022-11-28T17:15:35.000Z
change name for Arc-SQL data source
diff --git a/articles/purview/concept-policies-devops.md b/articles/purview/concept-policies-devops.md
@@ -57,7 +57,7 @@ Bob and Alice are DevOps users at their company. Given their role, they need to
 
 ## Next steps
 To get started with DevOps policies, consult the following guides:
-* Doc: [Microsoft Purview DevOps policies on Arc-enabled SQL Server](./how-to-policies-devops-arc-sql-server.md)
+* Doc: [Microsoft Purview DevOps policies on Azure Arc-enabled SQL Server](./how-to-policies-devops-arc-sql-server.md)
 * Doc: [Microsoft Purview DevOps policies on Azure SQL DB](./how-to-policies-devops-azure-sql-db.md)
 * Doc: [Microsoft Purview DevOps policies on resource groups and subscriptions](./how-to-policies-devops-resource-group.md)
 * Blog: [New granular permissions for SQL Server 2022 and Azure SQL to help PoLP](https://techcommunity.microsoft.com/t5/sql-server-blog/new-granular-permissions-for-sql-server-2022-and-azure-sql-to/ba-p/3607507)
diff --git a/articles/purview/how-to-policies-data-owner-arc-sql-server.md b/articles/purview/how-to-policies-data-owner-arc-sql-server.md
@@ -1,6 +1,6 @@
 ---
-title: Provision access by data owner for SQL Server on Azure Arc-enabled servers (preview)
-description: Step-by-step guide on how data owners can configure access to Arc-enabled SQL servers through Microsoft Purview access policies.
+title: Provision access by data owner for Azure Arc-enabled SQL Server (preview)
+description: Step-by-step guide on how data owners can configure access to Azure Arc-enabled SQL Servers through Microsoft Purview access policies.
 author: inward-eye
 ms.author: vlrodrig
 ms.service: purview
@@ -9,13 +9,13 @@ ms.topic: how-to
 ms.date: 11/23/2022
 ms.custom: references_regions, event-tier1-build-2022
 ---
-# Provision access by data owner for SQL Server on Azure Arc-enabled servers (preview)
+# Provision access by data owner for Azure Arc-enabled SQL Server (preview)
 
 [!INCLUDE [feature-in-preview](includes/feature-in-preview.md)]
 
 [Data owner policies](concept-policies-data-owner.md) are a type of Microsoft Purview access policies. They allow you to manage access to user data in sources that have been registered for *Data Use Management* in Microsoft Purview. These policies can be authored directly in the Microsoft Purview governance portal, and after publishing, they get enforced by the data source.
 
-This guide covers how a data owner can delegate authoring policies in Microsoft Purview to enable access to SQL Server on Azure Arc-enabled servers. The following actions are currently enabled: *Read*. This action is only supported for policies at server level. *Modify* is not supported at this point.
+This guide covers how a data owner can delegate authoring policies in Microsoft Purview to enable access to Azure Arc-enabled SQL Server. The following actions are currently enabled: *Read*. This action is only supported for policies at server level. *Modify* is not supported at this point.
 
 ## Prerequisites
 [!INCLUDE [Access policies generic pre-requisites](./includes/access-policies-prerequisites-generic.md)]
@@ -40,14 +40,14 @@ Register each data source with Microsoft Purview to later define access policies
 
 1. Enable Data Use Management. Data Use Management needs certain permissions and can affect the security of your data, as it delegates to certain Microsoft Purview roles to manage access to the data sources. **Go through the secure practices related to Data Use Management in this guide**: [How to enable Data Use Management](./how-to-enable-data-use-management.md)
 
-1. Upon enabling Data Use Management, Microsoft Purview will automatically capture the **Application ID** of the App Registration related to this Arc-enabled SQL server if one has been configured. Come back to this screen and hit the refresh button on the side of it to refresh, in case the association between the Arc-enabled SQL server and the App Registration changes in the future.
+1. Upon enabling Data Use Management, Microsoft Purview will automatically capture the **Application ID** of the App Registration related to this Azure Arc-enabled SQL Server if one has been configured. Come back to this screen and hit the refresh button on the side of it to refresh, in case the association between the Azure Arc-enabled SQL Server and the App Registration changes in the future.
 
 1. Select **Register** or **Apply** at the bottom
 
 Once your data source has the **Data Use Management** toggle *Enabled*, it will look like this picture.
 ![Screenshot shows how to register a data source for policy.](./media/how-to-policies-data-owner-sql/register-data-source-for-policy-arc-sql.png)
 
-## Enable policies in Arc-enabled SQL Server
+## Enable policies in Azure Arc-enabled SQL Server
 [!INCLUDE [Access policies Arc enabled SQL Server configuration](./includes/access-policies-configuration-arc-sql-server.md)]
 
 ## Create and publish a Data owner policy
@@ -116,7 +116,7 @@ SELECT * FROM sys.dm_server_external_policy_principal_assigned_actions
 
 ### Policy action mapping
 
-This section contains a reference of how actions in Microsoft Purview data policies map to specific actions in SQL Server on Azure Arc-enabled servers.
+This section contains a reference of how actions in Microsoft Purview data policies map to specific actions in Azure Arc-enabled SQL Server.
 
 | **Microsoft Purview policy action** | **Data source specific actions**     |
 |-------------------------------------|--------------------------------------|
diff --git a/articles/purview/how-to-policies-data-owner-azure-sql-db.md b/articles/purview/how-to-policies-data-owner-azure-sql-db.md
@@ -111,4 +111,4 @@ This section contains a reference of how actions in Microsoft Purview data polic
 Check blog, demo and related how-to guides
 * [Concepts for Microsoft Purview data owner policies](./concept-policies-data-owner.md)
 * [Enable Microsoft Purview data owner policies on all data sources in a subscription or a resource group](./how-to-policies-data-owner-resource-group.md)
-* [Enable Microsoft Purview data owner policies on an Arc-enabled SQL Server](./how-to-policies-data-owner-arc-sql-server.md)
+* [Enable Microsoft Purview data owner policies on an Azure Arc-enabled SQL Server](./how-to-policies-data-owner-arc-sql-server.md)
diff --git a/articles/purview/how-to-policies-data-owner-resource-group.md b/articles/purview/how-to-policies-data-owner-resource-group.md
@@ -23,7 +23,7 @@ In this guide we cover how to register an entire resource group or subscription
 **Only these data sources are enabled for access policies on resource group or subscription**. Follow the **Prerequisites** section that is specific to the data source(s) in these guides:
 * [Data owner policies on an Azure Storage account](./how-to-policies-data-owner-storage.md#prerequisites)
 * [Data owner policies on an Azure SQL Database](./how-to-policies-data-owner-azure-sql-db.md#prerequisites)(*)
-* [Data owner policies on an Arc-enabled SQL Server](./how-to-policies-data-owner-arc-sql-server.md#prerequisites)(*)
+* [Data owner policies on an Azure Arc-enabled SQL Server](./how-to-policies-data-owner-arc-sql-server.md#prerequisites)(*)
 
 (*) The *Modify* action is not currently supported for SQL-type data sources.
 
@@ -42,7 +42,7 @@ In the end, your resource will have the  **Data Use Management** toggle **Enable
 ![Screenshot shows how to register a resource group or subscription for policy by toggling the enable tab in the resource editor.](./media/how-to-policies-data-owner-resource-group/register-resource-group-for-policy.png)
 
 >[!Important]
-> - If you create a policy on a resource group or subscription and want to have it enforced in Arc-enabled SQL servers, you will need to also register those servers independently and enable *Data use management* which captures their App ID: [See this document](./how-to-policies-devops-arc-sql-server.md#register-data-sources-in-microsoft-purview).
+> - If you create a policy on a resource group or subscription and want to have it enforced in Azure Arc-enabled SQL Servers, you will need to also register those servers independently and enable *Data use management* which captures their App ID: [See this document](./how-to-policies-devops-arc-sql-server.md#register-data-sources-in-microsoft-purview).
 
 
 ## Create and publish a data owner policy
diff --git a/articles/purview/how-to-policies-devops-arc-sql-server.md b/articles/purview/how-to-policies-devops-arc-sql-server.md
@@ -1,6 +1,6 @@
 ---
-title: Provision access to Arc-enabled SQL Server for DevOps actions
-description: Step-by-step guide on provisioning access to Arc-enabled SQL Server through Microsoft Purview DevOps policies
+title: Provision access to Azure Arc-enabled SQL Server for DevOps actions
+description: Step-by-step guide on provisioning access to Azure Arc-enabled SQL Server through Microsoft Purview DevOps policies
 author: inward-eye
 ms.author: vlrodrig
 ms.service: purview
@@ -9,11 +9,11 @@ ms.topic: how-to
 ms.date: 11/16/2022
 ms.custom:
 ---
-# Provision access to system metadata in Arc-enabled SQL Server
+# Provision access to system metadata in Azure Arc-enabled SQL Server
 
 [DevOps policies](concept-policies-devops.md) are a type of Microsoft Purview access policies. They allow you to manage access to system metadata on data sources that have been registered for *Data use management* in Microsoft Purview. These policies are configured directly in the Microsoft Purview governance portal, and after being saved they get automatically published and then get enforced by the data source.
 
-This how-to guide covers how to provision access from Microsoft Purview to Arc-enabled SQL Server system metadata (DMVs and DMFs) *SQL Performance Monitoring* or *SQL Security Auditing* actions. Microsoft Purview access policies apply to Azure AD Accounts only.
+This how-to guide covers how to provision access from Microsoft Purview to Azure Arc-enabled SQL Server system metadata (DMVs and DMFs) *SQL Performance Monitoring* or *SQL Security Auditing* actions. Microsoft Purview access policies apply to Azure AD Accounts only.
 
 ## Prerequisites
 [!INCLUDE [Access policies generic pre-requisites](./includes/access-policies-prerequisites-generic.md)]
@@ -23,7 +23,7 @@ This how-to guide covers how to provision access from Microsoft Purview to Arc-e
 [!INCLUDE [Access policies generic configuration](./includes/access-policies-configuration-generic.md)]
 
 ### Register data sources in Microsoft Purview
-The Arc-enabled SQL Server data source needs to be registered first with Microsoft Purview, before policies can be created.
+The Azure Arc-enabled SQL Server data source needs to be registered first with Microsoft Purview, before policies can be created.
 
 1. Sign in to Microsoft Purview Studio.
 
@@ -38,14 +38,14 @@ The Arc-enabled SQL Server data source needs to be registered first with Microso
 
 1. Enable Data Use Management. Data Use Management needs certain permissions and can affect the security of your data, as it delegates to certain Microsoft Purview roles to manage access to the data sources. **Go through the secure practices related to Data Use Management in this guide**: [How to enable Data Use Management](./how-to-enable-data-use-management.md)
 
-1. Upon enabling Data Use Management, Microsoft Purview will automatically capture the **Application ID** of the App Registration related to this Arc-enabled SQL server if one has been configured. Come back to this screen and hit the refresh button on the side of it to refresh, in case the association between the Arc-enabled SQL server and the App Registration changes in the future.
+1. Upon enabling Data Use Management, Microsoft Purview will automatically capture the **Application ID** of the App Registration related to this Azure Arc-enabled SQL Server if one has been configured. Come back to this screen and hit the refresh button on the side of it to refresh, in case the association between the Azure Arc-enabled SQL Server and the App Registration changes in the future.
 
 1. Select **Register** or **Apply** at the bottom
 
 Once your data source has the **Data Use Management** toggle *Enabled*, it will look like this picture.
 ![Screenshot shows how to register a data source for policy.](./media/how-to-policies-data-owner-sql/register-data-source-for-policy-arc-sql.png)
 
-## Enable policies in Arc-enabled SQL Server
+## Enable policies in Azure Arc-enabled SQL Server
 [!INCLUDE [Access policies Arc enabled SQL Server configuration](./includes/access-policies-configuration-arc-sql-server.md)]
 
 ## Create a new DevOps policy
@@ -103,7 +103,7 @@ SELECT * FROM sys.dm_server_external_policy_principal_assigned_actions
 
 ### Policy action mapping
 
-This section contains a reference of how actions in Microsoft Purview data policies map to specific actions in SQL Server on Azure Arc-enabled servers.
+This section contains a reference of how actions in Microsoft Purview data policies map to specific actions in Azure Arc-enabled SQL Server.
 
 | **Microsoft Purview policy action** | **Data source specific actions**     |
 |-------------------------------------|--------------------------------------|
diff --git a/articles/purview/how-to-policies-devops-authoring-generic.md b/articles/purview/how-to-policies-devops-authoring-generic.md
@@ -85,5 +85,5 @@ Check the blog, related videos and documents
 * Video: [Pre-requisite for policies: The "Data use management" option](https://youtu.be/v_lOzevLW-Q)
 * Video: [Microsoft Purview DevOps policies on data sources and resource groups](https://youtu.be/YCDJagrgEAI)
 * Video: [Reduce the effort with Microsoft Purview DevOps policies on resource groups](https://youtu.be/yMMXCeIFCZ8)
-* Document: [Microsoft Purview DevOps policies on Arc-enabled SQL Server](./how-to-policies-devops-arc-sql-server.md)
+* Document: [Microsoft Purview DevOps policies on Azure Arc-enabled SQL Server](./how-to-policies-devops-arc-sql-server.md)
 * Document: [Microsoft Purview DevOps policies on Azure SQL DB](./how-to-policies-devops-azure-sql-db.md)
diff --git a/articles/purview/how-to-policies-devops-azure-sql-db.md b/articles/purview/how-to-policies-devops-azure-sql-db.md
@@ -112,7 +112,7 @@ Check the blog and related docs
 * Video: [Pre-requisite for policies: The "Data use management" option](https://youtu.be/v_lOzevLW-Q)
 * Video: [Microsoft Purview DevOps policies on data sources and resource groups](https://youtu.be/YCDJagrgEAI)
 * Video: [Reduce the effort with Microsoft Purview DevOps policies on resource groups](https://youtu.be/yMMXCeIFCZ8)
-* Doc: [Microsoft Purview DevOps policies on Arc-enabled SQL Server](./how-to-policies-devops-arc-sql-server.md)
+* Doc: [Microsoft Purview DevOps policies on Azure Arc-enabled SQL Server](./how-to-policies-devops-arc-sql-server.md)
 * Doc: [Microsoft Purview DevOps policies on resource groups and subscriptions](./how-to-policies-devops-resource-group.md)
 
 
diff --git a/articles/purview/how-to-policies-devops-resource-group.md b/articles/purview/how-to-policies-devops-resource-group.md
@@ -20,7 +20,7 @@ In this guide we cover how to register an entire resource group or subscription
 
 **Only these data sources are enabled for access policies on resource group or subscription**. Follow the **Prerequisites** section that is specific to the data source(s) in these guides:
 * [DevOps policies on an Azure SQL Database](./how-to-policies-devops-azure-sql-db.md#prerequisites)
-* [DevOps policies on an Arc-enabled SQL Server](./how-to-policies-devops-arc-sql-server.md#prerequisites)
+* [DevOps policies on an Azure Arc-enabled SQL Server](./how-to-policies-devops-arc-sql-server.md#prerequisites)
 
 ## Microsoft Purview Configuration
 [!INCLUDE [Access policies generic configuration](./includes/access-policies-configuration-generic.md)]
@@ -37,7 +37,7 @@ In the end, your resource will have the  **Data Use Management** toggle **Enable
 ![Screenshot shows how to register a resource group or subscription for policy by toggling the enable tab in the resource editor.](./media/how-to-policies-data-owner-resource-group/register-resource-group-for-policy.png)
 
 >[!Important]
-> - If you create a policy on a resource group or subscription and want to have it enforced in Arc-enabled SQL servers, you will need to also register those servers independently and enable *Data use management* which captures their App ID: [See this document](./how-to-policies-devops-arc-sql-server.md#register-data-sources-in-microsoft-purview).
+> - If you create a policy on a resource group or subscription and want to have it enforced in Azure Arc-enabled SQL Servers, you will need to also register those servers independently and enable *Data use management* which captures their App ID: [See this document](./how-to-policies-devops-arc-sql-server.md#register-data-sources-in-microsoft-purview).
 
 
 ## Create a new DevOps policy
@@ -60,5 +60,5 @@ To test the policy see the DevOps policy guides for the underlying data sources
 Check the blog and related docs
 * Blog: [Microsoft Purview DevOps policies enable at scale access provisioning for IT operations](https://techcommunity.microsoft.com/t5/microsoft-purview-blog/microsoft-purview-devops-policies-enable-at-scale-access/ba-p/3604725)
 * Video: [Reduce the effort with Microsoft Purview DevOps policies on resource groups](https://youtu.be/yMMXCeIFCZ8)
-* Doc: [Microsoft Purview DevOps policies on Arc-enabled SQL Server](./how-to-policies-devops-arc-sql-server.md)
+* Doc: [Microsoft Purview DevOps policies on Azure Arc-enabled SQL Server](./how-to-policies-devops-arc-sql-server.md)
 * Doc: [Microsoft Purview DevOps policies on Azure SQL DB](./how-to-policies-devops-azure-sql-db.md)
diff --git a/articles/purview/includes/access-policies-prerequisites-arc-sql-server.md b/articles/purview/includes/access-policies-prerequisites-arc-sql-server.md
@@ -36,7 +36,7 @@ Policy enforcement is available in only the following regions for Microsoft Purv
 - Japan East
 - Australia East
 
-#### Security considerations for SQL Server on Azure Arc-enabled servers
+#### Security considerations for Azure Arc-enabled SQL Server
 
 - The server admin can turn off the Microsoft Purview policy enforcement.
 - Azure Arc admin and server admin permissions provide the ability to change the Azure Resource Manager path of the server. Because mappings in Microsoft Purview use Resource Manager paths, this can lead to wrong policy enforcements. 
diff --git a/articles/purview/register-scan-azure-arc-enabled-sql-server.md b/articles/purview/register-scan-azure-arc-enabled-sql-server.md
@@ -121,7 +121,7 @@ The account must have access to the master database, because `sys.databases` is
 
 1. Select **Register**.
 
-1. Select **SQL Server on Azure Arc-enabled servers**, and then select **Continue**.
+1. Select **Azure Arc-enabled SQL Server**, and then select **Continue**.
 
    :::image type="content" source="media/register-scan-azure-arc-enabled-sql-server/set-up-azure-arc-enabled-sql-data-source.png" alt-text="Screenshot that shows selecting a SQL data source.":::
 
@@ -196,13 +196,13 @@ Before you can create policies, you must register the Azure Arc-enabled SQL Serv
 
 1. Enable **Data use management**. **Data use management** needs certain permissions and can affect the security of your data, because it delegates to certain Microsoft Purview roles to manage access to the data sources. Go through the secure practices related to **Data use management** in this guide: [Enable Data use management on your Microsoft Purview sources](./how-to-enable-data-use-management.md).
 
-1. Upon enabling Data Use Management, Microsoft Purview will automatically capture the **Application ID** of the App Registration related to this Arc-enabled SQL server if one has been configured. Come back to this screen and hit the refresh button on the side of it to refresh, in case the association between the Arc-enabled SQL server and the App Registration changes in the future.
+1. Upon enabling Data Use Management, Microsoft Purview will automatically capture the **Application ID** of the App Registration related to this Azure Arc-enabled SQL Server if one has been configured. Come back to this screen and hit the refresh button on the side of it to refresh, in case the association between the Azure Arc-enabled SQL Server and the App Registration changes in the future.
 
 1. Select **Register** or **Apply**.
 
 ![Screenshot that shows selections for registering a data source for a policy.](./media/how-to-policies-data-owner-sql/register-data-source-for-policy-arc-sql.png)
 
-### Enable policies in Arc-enabled SQL Server
+### Enable policies in Azure Arc-enabled SQL Server
 [!INCLUDE [Access policies Arc enabled SQL Server configuration](./includes/access-policies-configuration-arc-sql-server.md)]
 
 ### Create a policy
