Added Docs about adding Purview Root Collection Admins (#193)

* Update EnterpriseScaleAnalytics-GitHubActionsDeployment.md * Update EnterpriseScaleAnalytics-AzureDevOpsDeployment.md * Update docs/EnterpriseScaleAnalytics-AzureDevOpsDeployment.md Co-authored-by: Marvin Buss <[email protected]> * Update docs/EnterpriseScaleAnalytics-GitHubActionsDeployment.md Co-authored-by: Marvin Buss <[email protected]> Co-authored-by: Marvin Buss <[email protected]>
Azure · Oct 15, 2021 · ef2881c · ef2881c
1 parent 6254bb7
commit ef2881c
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 0 deletions.
diff --git a/docs/EnterpriseScaleAnalytics-AzureDevOpsDeployment.md b/docs/EnterpriseScaleAnalytics-AzureDevOpsDeployment.md
@@ -137,5 +137,9 @@ After following the instructions and updating the parameters and variables in yo
 
 Now, you can navigate to the pipeline that you have created as part of step 5 and monitor it as each service is deployed. If you run into any issues, please check the [Known Issues](/docs/EnterpriseScaleAnalytics-KnownIssues.md) first and open an [issue](https://github.com/Azure/data-management-zone/issues) if you come accross a potential bug in the repository.
 
+## Add Root Collection Administrator role to Purview account
+
+Since the Purview account is being deployed using a Service Principal, at this point, the only identity that has access to the Purview data plane, is the Service Principal. Use the [instructions in this guide](https://docs.microsoft.com/azure/purview/tutorial-metadata-policy-collections-apis#add-the-root-collection-administrator-role) to assign additional user accounts to the Purview Root Collection as Collection Admin.
+
 >[Previous](/docs/EnterpriseScaleAnalytics-ServicePrincipal.md)
 >[Next](/docs/EnterpriseScaleAnalytics-KnownIssues.md)
diff --git a/docs/EnterpriseScaleAnalytics-GitHubActionsDeployment.md b/docs/EnterpriseScaleAnalytics-GitHubActionsDeployment.md
@@ -90,5 +90,9 @@ After following the instructions and updating the parameters and variables in yo
 
 Now, you can navigate to the **Actions** tab of the main page of the repository, where you will see a workflow with the name `Data Management Zone Deployment` running. Click on it to see how it deploys the environment. If you run into any issues, please check the [Known Issues](/docs/EnterpriseScaleAnalytics-KnownIssues.md) first and open an [issue](https://github.com/Azure/data-management-zone/issues) if you come accross a potential bug in the repository.
 
+## Add Root Collection Administrator role to Purview account
+
+Since the Purview account is being deployed using a Service Principal, at this point, the only identity that has access to the Purview data plane, is the Service Principal. Use the [instructions in this guide](https://docs.microsoft.com/azure/purview/tutorial-metadata-policy-collections-apis#add-the-root-collection-administrator-role) to assign additional user accounts to the Purview Root Collection as Collection Admin.
+
 >[Previous](/docs/EnterpriseScaleAnalytics-ServicePrincipal.md)
 >[Next](/docs/EnterpriseScaleAnalytics-KnownIssues.md)