Skip to content

Commit 5105f63

Browse files
Merge pull request #229185 from TimShererWithAquent/us2036619a
Freshness Pass User Story: 2036619 Work with data using Azure Cosmos DB Explorer
2 parents 815f02c + adb7a4e commit 5105f63

File tree

3 files changed

+21
-23
lines changed

3 files changed

+21
-23
lines changed

articles/cosmos-db/data-explorer.md

Lines changed: 21 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -1,55 +1,53 @@
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
7-
ms.date: 09/23/2020
7+
ms.date: 03/02/2023
88
ms.author: esarroyo
99
author: StefArroyo
1010
---
1111

12-
# Work with data using Azure Cosmos DB Explorer
12+
# Work with data using Azure Cosmos DB Explorer
1313
[!INCLUDE[NoSQL, MongoDB, Cassandra, Gremlin, Table](includes/appliesto-nosql-mongodb-cassandra-gremlin-table.md)]
1414

1515
Azure Cosmos DB Explorer is a standalone web-based interface that allows you to view and manage the data stored in Azure Cosmos DB. Azure Cosmos DB Explorer is equivalent to the existing **Data Explorer** tab that is available in Azure portal when you create an Azure Cosmos DB account. The key advantages of Azure Cosmos DB Explorer over the existing Data explorer are:
1616

17-
* You have a full screen real-estate to view your data, run queries, stored procedures, triggers, and view their results.
18-
19-
* You can provide temporary or permanent read or read-write access to your database account and its collections to other users who do not have access to Azure portal or subscription.
20-
21-
* You can share the query results with other users who do not have access to Azure portal or subscription.
17+
- You have a full screen real-estate to view your data, run queries, stored procedures, triggers, and view their results.
18+
- You can provide read or read-write access to your database account and its collections to other users who don't have access to Azure portal or subscription.
19+
- You can share the query results with other users who don't have access to Azure portal or subscription.
2220

2321
## Access Azure Cosmos DB Explorer
2422

25-
1. Sign in to [Azure portal](https://portal.azure.com/).
23+
1. Sign in to [Azure portal](https://portal.azure.com/).
2624

27-
2. From **All resources**, find and navigate to your Azure Cosmos DB account, select Keys, and copy the **Primary Connection String**.
25+
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:
2826

29-
3. Go to https://cosmos.azure.com/, paste the connection string and select **Connect**. By using the connection string, you can access the Azure Cosmos DB Explorer without any time limits.
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.
3029

31-
If you want to provide other users temporary access to your Azure Cosmos DB account, you can do so by using the read-write and read access URLs.
30+
1. Go to [https://cosmos.azure.com/](https://cosmos.azure.com/).
3231

33-
4. Open the **Data Explorer** blade, select **Open Full Screen**. From the pop-up dialog, you can view two access URLs – **Read-Write** and **Read**. These URLs allow you to share your Azure Cosmos DB account temporarily with other users. Access to the account expires in 24 hours after which you can reconnect by using a new access URL or the connection string.
32+
1. Select **Connect to your account with connection string**, paste the connection string, and select **Connect**.
3433

35-
**Read-Write** – When you share the Read-Write URL with other users, they can view and modify the databases, collections, queries, and other resources associated with that specific account.
34+
To open Azure Cosmos DB Explorer from the Azure portal:
3635

37-
**Read** - When you share the read-only URL 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 URL.
36+
1. Select the **Data Explorer** in the left menu, then select **Open Full Screen**.
3837

39-
Choose the type of access you'd like to open the account with and click **Open**. After you open the explorer, the experience is same as you had with the Data Explorer tab in Azure portal.
38+
:::image type="content" source="./media/data-explorer/open-data-explorer.png" alt-text="Screenshot shows Data Explorer page with Open Full Screen highlighted." lightbox="./media/data-explorer/open-data-explorer.png":::
4039

41-
:::image type="content" source="./media/data-explorer/open-data-explorer-with-access-url.png" alt-text="Open Azure Cosmos DB Explorer":::
40+
1. In the **Open Full Screen** dialog, select **Open**.
4241

4342
## Known issues
4443

45-
Currently the **Open Full Screen** experience that allows you to share temporary read-write or read access is not yet supported for Azure Cosmos DB API for Gremlin and Table accounts. You can still view your Gremlin and API for Table accounts by passing the connection string to Azure Cosmos DB Explorer.
46-
47-
Currently, viewing documents that contain a UUID is not supported in Data Explorer. This does not 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.
44+
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.
4845

49-
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.
5047

5148
## Next steps
5249

53-
Now that you have learned how to get started with Azure Cosmos DB Explorer to manage your data, next you can:
50+
Now that you've learned how to get started with Azure Cosmos DB Explorer to manage your data, next you can:
5451

55-
* Start defining [queries](nosql/query/getting-started.md) using SQL syntax and perform [server side programming](stored-procedures-triggers-udfs.md) by using stored procedures, UDFs, triggers.
52+
- [Getting started with queries](nosql/query/getting-started.md)
53+
- [Stored procedures, triggers, and user-defined functions](stored-procedures-triggers-udfs.md)
Binary file not shown.
50.3 KB
Loading

0 commit comments

Comments
 (0)