Skip to content

Commit 66aad74

Browse files
authored
Merge pull request #178789 from whhender/update-powershell-quickstart
Adding CLI Command to Documentation
2 parents fb6a7db + 9a028fb commit 66aad74

File tree

2 files changed

+19
-2
lines changed

2 files changed

+19
-2
lines changed

articles/purview/catalog-permissions.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -60,6 +60,15 @@ Users can only be added to a collection by a collection admin, or through permis
6060

6161
After creating an Azure Purview account, the first thing to do is create collections and assign users to roles within those collections.
6262

63+
> [!NOTE]
64+
> If you created your Azure Purview account using a service principal, to be able to access the Purview Studio and assign permissions to users, you will need to grant a user collection admin permissions on the root collection.
65+
> You can use [this Azure CLI command](/cli/azure/purview/account#az_purview_account_add_root_collection_admin):
66+
>
67+
> ```azurecli
68+
> az purview account add-root-collection-admin --account-name --resource-group [--object-id]
69+
> ```
70+
>
71+
6372
### Create collections
6473
6574
Collections can be customized for structure of the sources in your Purview account, and can act like organized storage bins for these resources. When you're thinking about the collections you might need, consider how your users will access or discover information. Are your sources broken up by departments? Are there specialized groups within those departments that will only need to discover some assets? Are there some sources that should be discoverable by all your users?

articles/purview/create-catalog-powershell.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -128,13 +128,21 @@ For more information about Purview, [see our overview page](overview.md). For mo
128128
---
129129
130130
1. The deployment command returns results. Look for `ProvisioningState` to see whether the deployment succeeded.
131-
131+
132+
1. If you deployed the Azure Purview account using a service principal, instead of a user account, you will also need to run the below command in the Azure CLI:
133+
134+
```azurecli
135+
az purview account add-root-collection-admin --account-name --resource-group [--object-id]
136+
```
137+
138+
This command will grant the user account [collection admin](catalog-permissions.md#roles) permissions on the root collection in your Azure Purview account. This allows the user to access the Purview Studio and add permission for other users. For more information about permissions in Azure Purview, see our [permissions guide](catalog-permissions.md). For more information about collections, see our [manage collections article](how-to-create-and-manage-collections.md).
139+
132140
## Next steps
133141
134142
In this quickstart, you learned how to create an Azure Purview account.
135143
136144
Follow these next articles to learn how to navigate the Purview Studio, create a collection, and grant access to Purview.
137145
138146
* [How to use the Purview Studio](use-purview-studio.md)
139-
* [Create a collection](quickstart-create-collection.md)
140147
* [Add users to your Azure Purview account](catalog-permissions.md)
148+
* [Create a collection](quickstart-create-collection.md)

0 commit comments

Comments
 (0)