Skip to content

Commit 47afe6d

Browse files
Edits.
1 parent f2d1c25 commit 47afe6d

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

articles/cosmos-db/data-explorer.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Use Azure Cosmos DB Explorer to manage your data
3-
description: Azure Cosmos DB Explorer is a standalone web-based interface that allows you to view and manage the data stored in Azure Cosmos DB.
3+
description: Learn about Azure Cosmos DB Explorer, a standalone web-based interface that allows you to view and manage the data stored in Azure Cosmos DB.
44
ms.service: cosmos-db
55
ms.custom: ignite-2022
66
ms.topic: how-to
@@ -24,26 +24,26 @@ Azure Cosmos DB Explorer is a standalone web-based interface that allows you to
2424

2525
1. From **All resources**, find and navigate to your Azure Cosmos DB account, select **Keys**, and copy the **Primary Connection String**. You can select either:
2626

27-
- **Read-write keys**. When you share the Read-write primary connection string other users, they can view and modify the databases, collections, queries, and other resources associated with that specific account.
28-
- **Read-only** - When you share the read-only primary connection string with other users, they can view the databases, collections, queries, and other resources associated with that specific account. For example, if you want to share results of a query with your teammates who don't have access to Azure portal or your Azure Cosmos DB account, you can provide them with this value.
27+
- **Read-write Keys**. When you share the Read-write primary connection string other users, they can view and modify the databases, collections, queries, and other resources associated with that specific account.
28+
- **Read-only Keys**. When you share the read-only primary connection string with other users, they can view the databases, collections, queries, and other resources associated with that specific account. For example, if you want to share results of a query with your teammates who don't have access to Azure portal or your Azure Cosmos DB account, you can provide them with this value.
2929

30-
1. Go to [https://cosmos.azure.com/](https://cosmos.azure.com/).
30+
1. Go to [https://cosmos.azure.com/](https://cosmos.azure.com/).
3131

3232
1. Select **Connect to your account with connection string**, paste the connection string, and select **Connect**.
3333

3434
To open Azure Cosmos DB Explorer from the Azure portal:
3535

36-
1. Select the **Data Explorer** in the left menu, then select **Open Full Screen**.
37-
38-
1. In the Open Full Screen dialog, select **Open**.
36+
1. Select the **Data Explorer** in the left menu, then select **Open Full Screen**.
3937

4038
:::image type="content" source="./media/data-explorer/open-data-explorer.png" alt-text="Screenshot shows Data Explorer page with Open Full Screen highlighted.":::
4139

40+
1. In the **Open Full Screen** dialog, select **Open**.
41+
4242
## Known issues
4343

4444
Currently, viewing documents that contain a UUID isn't supported in Data Explorer. This limitation doesn't affect loading collections, only viewing individual documents or queries that include these documents. To view and manage these documents, users should continue to use the tool that was originally used to create these documents.
4545

46-
Customers receiving HTTP-401 errors may be due to insufficient Azure RBAC permissions for the customer's Azure account, particularly if the account has a custom role. Any custom roles must have `Microsoft.DocumentDB/databaseAccounts/listKeys/*` action to use Data Explorer if signing in using their Azure Active Directory credentials.
46+
Customers receiving HTTP-401 errors may be due to insufficient Azure RBAC permissions for your Azure account, particularly if the account has a custom role. Any custom roles must have `Microsoft.DocumentDB/databaseAccounts/listKeys/*` action to use Data Explorer if signing in using their Azure Active Directory credentials.
4747

4848
## Next steps
4949

0 commit comments

Comments
 (0)