Merge pull request #195371 from whhender/7-azure-purview-to-microsoft-purview

AnnaMHuff · web-flow · commit 4c26da29d152 · 2022-04-18T17:02:52.000-07:00
Purview Includes - Azure Purview to Microsoft Purview
diff --git a/articles/purview/includes/access-policies-configuration-generic.md b/articles/purview/includes/access-policies-configuration-generic.md
@@ -8,51 +8,51 @@ ms.date: 04/18/2022
 ms.custom:
 ---
 
-### Register Azure Purview as a resource provider in other subscriptions
-Execute this step only if the data sources and the Azure Purview account are in different subscriptions. Register Azure Purview as a resource provider in each subscription where data sources reside by following this guide: [Register resource provider](../../azure-resource-manager/management/resource-providers-and-types.md#register-resource-provider).
+### Register Microsoft Purview as a resource provider in other subscriptions
+Execute this step only if the data sources and the Microsoft Purview account are in different subscriptions. Register Microsoft Purview as a resource provider in each subscription where data sources reside by following this guide: [Register resource provider](../../azure-resource-manager/management/resource-providers-and-types.md#register-resource-provider).
 
-The Azure Purview resource provider is:
+The Microsoft Purview resource provider is:
 ```
 Microsoft.Purview
 ```
 
 ### Configure permissions for policy management actions
 This section discusses the permissions needed to:
-- Make a data resource available for *data use governance*. This step is needed before a policy can be created in Azure Purview for that resource.
-- Author and publish policies in Azure Purview.
+- Make a data resource available for *data use governance*. This step is needed before a policy can be created in Microsoft Purview for that resource.
+- Author and publish policies in Microsoft Purview.
 
 >[!IMPORTANT]
-> Currently, Azure Purview roles related to policy operations must be configured at **root collection level** and not child collection level.
+> Currently, Microsoft Purview roles related to policy operations must be configured at **root collection level** and not child collection level.
 
 #### Permissions to make a data resource available for *Data use governance*
-To enable the *data use governance* (DUG) toggle for a data source, resource group, or subscription, the same user needs to have both certain IAM privileges on the resource and certain Azure Purview privileges. 
+To enable the *data use governance* (DUG) toggle for a data source, resource group, or subscription, the same user needs to have both certain IAM privileges on the resource and certain Microsoft Purview privileges. 
 
 1) User needs to have **either one of the following** IAM role combinations on the resource:
    - IAM *Owner*
    - Both IAM *Contributor* + IAM *User Access Administrator*
 
    Follow this [guide to configure Azure RBAC role permissions](../../role-based-access-control/check-access.md).
 
-2) In addition, the same user needs to have Azure Purview Data source administrator (DSA) role at the **root collection level**. See the guide on [managing Azure Purview role assignments](../catalog-permissions.md#assign-permissions-to-your-users).
+2) In addition, the same user needs to have Microsoft Purview Data source administrator (DSA) role at the **root collection level**. See the guide on [managing Microsoft Purview role assignments](../catalog-permissions.md#assign-permissions-to-your-users).
 
 #### Permissions for policy authoring and publishing
-The following permissions are needed in Azure Purview at the **root collection level**:
+The following permissions are needed in Microsoft Purview at the **root collection level**:
 - *Policy authors* role can create or edit policies.
 - *Data source administrator* role can publish a policy.
 
-Check the section on managing Azure Purview role assignments in this [guide](../how-to-create-and-manage-collections.md#add-roles-and-restrict-access-through-collections).
+Check the section on managing Microsoft Purview role assignments in this [guide](../how-to-create-and-manage-collections.md#add-roles-and-restrict-access-through-collections).
 
 >[!WARNING]
 > **Known issues** related to permissions
-> - In addition to Azure Purview *Policy authors* role, user requires *Directory Reader* permission in Azure Active Directory to create data owner policy. Learn more about permissions for [Azure AD Directory Reader](../../active-directory/roles/permissions-reference.md#directory-readers)
+> - In addition to Microsoft Purview *Policy authors* role, user requires *Directory Reader* permission in Azure Active Directory to create data owner policy. Learn more about permissions for [Azure AD Directory Reader](../../active-directory/roles/permissions-reference.md#directory-readers)
 
-#### Delegation of access control responsibility to Azure Purview
+#### Delegation of access control responsibility to Microsoft Purview
 
 >[!WARNING]
 > - IAM Owner role for a data source can be inherited from parent resource group, subscription or subscription Management Group. 
-> - Once a resource has been enabled for *Data use Governance*, **any** Azure Purview root-collection *policy author* will be able to create access policies against it, and **any** Azure Purview root-collection *Data source admin* will be able to publish those policies at **any point afterwards**.
-> - **Any** Azure Purview root *Collection admin* can assign **new** root-collection *Data Source Admin* and *Policy author* roles.
+> - Once a resource has been enabled for *Data use Governance*, **any** Microsoft Purview root-collection *policy author* will be able to create access policies against it, and **any** Microsoft Purview root-collection *Data source admin* will be able to publish those policies at **any point afterwards**.
+> - **Any** Microsoft Purview root *Collection admin* can assign **new** root-collection *Data Source Admin* and *Policy author* roles.
 
 With these warnings in mind, here are some **suggested best practices for permissions:**
-- Minimize the number of people that hold Azure Purview root *Collection admin*, root *Data Source Admin* or root *Policy author* roles.
-- To ensure check and balances, assign the Azure Purview *Policy author* and *Data source admin* roles to different people in the organization. With this, before a data policy takes effect, a second person (the *Data source admin*) must review it and explicitly approve it by publishing it.
+- Minimize the number of people that hold Microsoft Purview root *Collection admin*, root *Data Source Admin* or root *Policy author* roles.
+- To ensure check and balances, assign the Microsoft Purview *Policy author* and *Data source admin* roles to different people in the organization. With this, before a data policy takes effect, a second person (the *Data source admin*) must review it and explicitly approve it by publishing it.
diff --git a/articles/purview/includes/access-policies-prerequisites-generic.md b/articles/purview/includes/access-policies-prerequisites-generic.md
@@ -8,5 +8,5 @@ ms.date: 01/28/2022
 ms.custom:
 ---
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
-- Create a new, or use an existing Azure Purview account. You can [follow our quick-start guide to create one](../create-catalog-portal.md).
+- Create a new, or use an existing Microsoft Purview account. You can [follow our quick-start guide to create one](../create-catalog-portal.md).
 - Create a new, or use an existing resource group, and place new data sources under it. [Follow this guide to create a new resource group](../../azure-resource-manager/management/manage-resource-groups-portal.md).
diff --git a/articles/purview/includes/access-policies-prerequisites-storage.md b/articles/purview/includes/access-policies-prerequisites-storage.md
@@ -9,7 +9,7 @@ ms.custom:
 ---
 
 ### Enable access policy enforcement for the Azure Storage account
-To enable Azure Purview to manage policies for one or more Azure Storage accounts, execute the following PowerShell commands in the subscription where you'll deploy your Azure Storage account. These PowerShell commands will enable Azure Purview to manage policies on all **newly created** Azure Storage accounts in that subscription.
+To enable Microsoft Purview to manage policies for one or more Azure Storage accounts, execute the following PowerShell commands in the subscription where you'll deploy your Azure Storage account. These PowerShell commands will enable Microsoft Purview to manage policies on all **newly created** Azure Storage accounts in that subscription.
 
 If you’re executing these commands locally, be sure to run PowerShell as an administrator.
 Alternatively, you can use the [Azure Cloud Shell](../../cloud-shell/overview.md) in the Azure portal: [https://shell.azure.com](https://shell.azure.com).
@@ -27,14 +27,14 @@ If the output of the last command shows *RegistrationState* as *Registered*, the
 If the output is *Registering*, wait at least 10 minutes, and then retry the command. **Do not continue unless the RegistrationState shows as *Registered***.
 
 >[!IMPORTANT]
-> The access policy feature is only available on **new** Azure Storage accounts. Storage accounts must meet the following requirements to enforce access policies published from Azure Purview.
+> The access policy feature is only available on **new** Azure Storage accounts. Storage accounts must meet the following requirements to enforce access policies published from Microsoft Purview.
 > - Storage account versions >= 81.x.x.
 > - Created in the subscription **after** the feature *AllowPurviewPolicyEnforcement* is *Registered*.
 
 ### Create a new Azure Storage account
 After you’ve enabled the access policy above, create new Azure Storage account(s) in one of the regions listed below. You can [follow this guide to create one](../../storage/common/storage-account-create.md).
 
-Currently, Azure Purview access policies can only be enforced in the following Azure Storage regions:
+Currently, Microsoft Purview access policies can only be enforced in the following Azure Storage regions:
 -   France Central
 -   Canada Central
 -   East US
diff --git a/articles/purview/includes/authentication-to-enumerate-resources.md b/articles/purview/includes/authentication-to-enumerate-resources.md
@@ -9,5 +9,5 @@ ms.date: 02/04/2022
 1. Go to the subscription or the resource group in the Azure portal. 
 1. Select **Access Control (IAM)** from the left menu.
 1. Select **+Add**.
-1. In the **Select input** box, select the **Reader** role and enter your Azure Purview account name (which represents its MSI file name).
-1. Select **Save** to finish the role assignment. This will allow Azure Purview to list resources under a subscription or resource group.
+1. In the **Select input** box, select the **Reader** role and enter your Microsoft Purview account name (which represents its MSI file name).
+1. Select **Save** to finish the role assignment. This will allow Microsoft Purview to list resources under a subscription or resource group.
diff --git a/articles/purview/includes/data-factory-common-supported-capabilities.md b/articles/purview/includes/data-factory-common-supported-capabilities.md
@@ -34,7 +34,7 @@ ms.date: 11/01/2021
 | SQL Server \* | Yes | 
 | Teradata \* | Yes |
 
-*\* Azure Purview currently doesn't support query or stored procedure for lineage or scanning. Lineage is limited to table and view sources only.*
+*\* Microsoft Purview currently doesn't support query or stored procedure for lineage or scanning. Lineage is limited to table and view sources only.*
 
 If you use Self-hosted Integration Runtime, note the minimal version with lineage support for:
 
@@ -71,8 +71,8 @@ In additional to lineage, the data asset schema (shown in Asset -> Schema tab) i
 | Azure Synapse Analytics \* | Yes |
 | Azure Dedicated SQL pool (formerly SQL DW) \* | Yes | 
 
-*\* Azure Purview currently doesn't support query or stored procedure for lineage or scanning. Lineage is limited to table and view sources only.*
+*\* Microsoft Purview currently doesn't support query or stored procedure for lineage or scanning. Lineage is limited to table and view sources only.*
 
 #### Limitations on data flow lineage
 
-Currently, data flow lineage doesn't integrate with Azure Purview [resource set](../concept-resource-sets.md).
+Currently, data flow lineage doesn't integrate with Microsoft Purview [resource set](../concept-resource-sets.md).
diff --git a/articles/purview/includes/manage-scans.md b/articles/purview/includes/manage-scans.md
@@ -13,7 +13,7 @@ ms.date: 1/20/2021
 
 To create and run a new scan, do the following:
 
-1. Select the **Data Map** tab on the left pane in the [Azure Purview Studio](https://web.purview.azure.com/resource/).
+1. Select the **Data Map** tab on the left pane in the [Microsoft Purview Studio](https://web.purview.azure.com/resource/).
 
 1. Select the data source that you registered.
 
diff --git a/articles/purview/includes/purview-quickstart-prerequisites.md b/articles/purview/includes/purview-quickstart-prerequisites.md
@@ -23,7 +23,7 @@ ms.date: 04/05/2022
   1. Then select **My permissions**. 
   1. If you have access to multiple subscriptions, select the appropriate subscription.
 
-* No [Azure Policies](../../governance/policy/overview.md) preventing creation of **Storage accounts** or **Event Hub namespaces**. Azure Purview will deploy a managed Storage account and Event Hub when it is created. If a blocking policy exists and needs to remain in place, please follow our [Azure Purview exception tag guide](../create-azure-purview-portal-faq.md) and follow the steps to create an exception for Azure Purview accounts.
+* No [Azure Policies](../../governance/policy/overview.md) preventing creation of **Storage accounts** or **Event Hub namespaces**. Microsoft Purview will deploy a managed Storage account and Event Hubs when it is created. If a blocking policy exists and needs to remain in place, please follow our [Microsoft Purview exception tag guide](../create-azure-purview-portal-faq.md) and follow the steps to create an exception for Microsoft Purview accounts.
 
 ## Sign in to Azure
 
diff --git a/articles/purview/includes/view-and-manage-scans.md b/articles/purview/includes/view-and-manage-scans.md
@@ -12,7 +12,7 @@ ms.custom: ignite-fall-2021
 
 To view existing scans, do the following:
 
-1. Go to the [Azure Purview Studio](https://web.purview.azure.com/resource/). Select the **Data Map** tab under the left pane.
+1. Go to the [Microsoft Purview Studio](https://web.purview.azure.com/resource/). Select the **Data Map** tab under the left pane.
 
 1. Select the desired data source. You will see a list of existing scans on that data source under **Recent scans**, or can view all scans under the **Scans** tab.
 
@@ -24,7 +24,7 @@ To view existing scans, do the following:
 
 To manage or delete a scan, do the following:
 
-1. Go to the [Azure Purview Studio](https://web.purview.azure.com/resource/). Select the **Data Map** tab under the left pane.
+1. Go to the [Microsoft Purview Studio](https://web.purview.azure.com/resource/). Select the **Data Map** tab under the left pane.
 
 1. Select the desired data source. You will see a list of existing scans on that data source under **Recent scans**, or can view all scans under the **Scans** tab.
 
@@ -36,4 +36,4 @@ To manage or delete a scan, do the following:
 
 > [!NOTE]
 > * Deleting your scan does not delete catalog assets created from previous scans.
-> * The asset will no longer be updated with schema changes if your source table has changed and you re-scan the source table after editing the description in the schema tab of Azure Purview.
+> * The asset will no longer be updated with schema changes if your source table has changed and you re-scan the source table after editing the description in the schema tab of Microsoft Purview.
