You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: powerquery-docs/connectors/azure-cosmos-db-for-mongodb-vcore.md
+24-24Lines changed: 24 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,13 @@
1
1
---
2
-
title: Azure DocumentDB Data Connector
3
-
description: Includes basic information and prerequisites, instructions on how to connect to your Azure DocumentDB database, and information about advanced connection options.
2
+
title: Azure Cosmos DB for MongoDB vCore Data Connector
3
+
description: Includes basic information and prerequisites, instructions on how to connect to your Azure Cosmos for Mongo vCore database, and information about advanced connection options.
4
4
author: KazimMir
5
5
ms.topic: concept-article
6
-
ms.date: 12/09/2025
6
+
ms.date: 11/10/2025
7
7
ms.author: dougklo
8
8
---
9
9
10
-
# Azure DocumentDB
10
+
# Azure Cosmos DB for MongoDB vCore
11
11
12
12
## Summary
13
13
@@ -27,39 +27,39 @@ ms.author: dougklo
27
27
-[Supported Power Query Functions](#direct-query-support)
28
28
-[Native Mongo Queries](#native-mongo-queries)
29
29
30
-
## Connect to Azure DocumentDB database from Power Query Desktop
30
+
## Connect to Azure Cosmos DB for MongoDB vCore database from Power Query Desktop
31
31
32
-
To connect to an Azure DocumentDB from Power Query Desktop, take the following steps:
32
+
To connect to an Azure Cosmos DB for MongoDB vCore from Power Query Desktop, take the following steps:
33
33
34
-
1. Select **Azure DocumentDB** in the **Get Data** experience. The **Get Data** experience in Power Query Desktop varies between apps. For more information about the Power Query Desktop **Get Data** experience for your app, go to [Where to get data](../where-to-get-data.md).
34
+
1. Select **Azure Cosmos DB for MongoDB vCore** in the **Get Data** experience. The **Get Data** experience in Power Query Desktop varies between apps. For more information about the Power Query Desktop **Get Data** experience for your app, go to [Where to get data](../where-to-get-data.md).
35
35
36
-
1. In **Azure DocumentDB**, provide the Azure DocumentDB endpoint. Optionally provide a **Database Name** and a **Collection Name**. If a database name isn't provided, the upcoming **Navigator** screen shows all databases and their respective collections. Specifying both database and collection names only shows that collection. Specifying a collection name without a database name results in a connection error.
36
+
1. In **Azure Cosmos DB for MongoDB vCore**, provide the Cosmos DB endpoint. Optionally provide a **Database Name** and a **Collection Name**. If a database name isn't provided, the upcoming **Navigator** screen shows all databases and their respective collections. Specifying both database and collection names only shows that collection. Specifying a collection name without a database name results in a connection error.
:::image type="content" source="./media/azure-cosmos-db-for-mongodb-vcore/enter-credentials.png" alt-text="Screenshot showing Azure Cosmos DB for MongoDB vCore database authentication.":::
47
47
48
48
1. In **Navigator**, select the database information you want. A list of collections appear under each database. Select one or more collections and then either select **Load** to load the data or **Transform Data** to continue transforming the data in Power Query Editor. The list of databases and collections are affected if the optional **Database Name** and **Collection Name** were previously supplied.
:::image type="content" source="./media/azure-cosmos-db-for-mongodb-vcore/navigator-desktop.png" alt-text="Screenshot showing Azure Cosmos DB for MongoDB vCore load or transform." lightbox="./media/azure-cosmos-db-for-mongodb-vcore/navigator-desktop.png":::
51
51
52
-
## Connect to Azure DocumentDB database from Power Query Online
52
+
## Connect to Azure Cosmos DB for MongoDB vCore database from Power Query Online
53
53
54
-
To connect to Azure DocumentDB database from Power Query Online:
54
+
To connect to Azure Cosmos DB for MongoDB vCore database from Power Query Online:
55
55
56
-
1. Select the **Azure DocumentDB** option in the **Get Data** experience. Different apps have different ways of getting to the Power Query Online **Get Data** experience. For more information about how to get to the Power Query Online **Get Data** experience from your app, go to [Where to get data](../where-to-get-data.md).
56
+
1. Select the **Azure Cosmos DB for MongoDB vCore** option in the get data experience. Different apps have different ways of getting to the Power Query Online get data experience. For more information about how to get to the Power Query Online get data experience from your app, go to [Where to get data](../where-to-get-data.md).
57
57
58
-
:::image type="content" source="./media/azure-documentdb/online-select-mongodb-vcore.png" alt-text="Screenshot showing Azure DocumentDB icon in Power Query online.":::
58
+
:::image type="content" source="./media/azure-cosmos-db-for-mongodb-vcore/online-select-mongodb-vcore.png" alt-text="Screenshot showing Azure Cosmos DB for MongoDB vCore icon in Power Query online.":::
59
59
60
-
1. In the **Azure DocumentDB** dialog that appears, enter the Azure DocumentDB endpoint. Optionally provide a **Database Name** and a **Collection Name**. If a database name isn't provided, the upcoming **Navigator** screen shows all databases and their respective collections. Specifying both database and collection names only shows that collection. Specifying a collection name without a database name results in a connection error.
60
+
1. In the **Azure Cosmos DB for MongoDB vCore** dialog that appears, enter the Cosmos DB endpoint. Optionally provide a **Database Name** and a **Collection Name**. If a database name isn't provided, the upcoming **Navigator** screen shows all databases and their respective collections. Specifying both database and collection names only shows that collection. Specifying a collection name without a database name results in a connection error.
61
61
62
-
:::image type="content" source="./media/azure-documentdb/online-connect-endpoint-sign-in.png" alt-text="Screenshot showing Azure DocumentDB Connection dialog in Power Query online." lightbox="./media/azure-documentdb/online-connect-endpoint-sign-in.png":::
62
+
:::image type="content" source="./media/azure-cosmos-db-for-mongodb-vcore/online-connect-endpoint-sign-in.png" alt-text="Screenshot showing Azure Cosmos DB for MongoDB vCore Connection dialog in Power Query online." lightbox="./media/azure-cosmos-db-for-mongodb-vcore/online-connect-endpoint-sign-in.png":::
63
63
64
64
1. You can select an existing a connection or a data gateway. You can connect by specifying the basic authentication kind specifying the username and password associated with the endpoint in the **connection credentials** section and select **Next**.
65
65
@@ -73,27 +73,27 @@ The custom `Value.NativeQuery` function allows native MongoDB queries to be sent
73
73
74
74
1. Using the Navigator, select at least one collection and choosing **Transform Data**.
75
75
76
-
:::image type="content" source="./media/azure-documentdb/transform-data-on-load.png" alt-text="Screenshot showing Native Mongo Query navigator with Transform data emphasized." lightbox="./media/azure-documentdb/transform-data-on-load.png":::
76
+
:::image type="content" source="./media/azure-cosmos-db-for-mongodb-vcore/transform-data-on-load.png" alt-text="Screenshot showing Native Mongo Query navigator with Transform data emphasized." lightbox="./media/azure-cosmos-db-for-mongodb-vcore/transform-data-on-load.png":::
77
77
78
78
1. Choose **Advanced Editor**. The **Advanced Editor** dialog appears to show the initial query that would be used to fetch all the data in the selected collection.
1. The [Value.NativeQuery](/powerquery-m/value-nativequery) function takes two arguments: a source, and the query itself. The `source` variable is populated with all the information needed to connect to the database. If desired, update the name of the collection that the query runs against. The collection doesn't have to be the same as the one selected in the **Navigator**.
1. The second argument is a valid MongoDB query, enclosed in double-quotation marks. Quotation marks within the query are escaped with another quotation mark, for example, `"num1"` to `""$num1""`
87
87
88
88
1. Choose **Done** to transform the data.
89
89
90
-
1. As no schema information is returned from Azure DocumentDB after the query is executed, the resultant table identifies all column types as _any_. Either transform the columns using **Detect Data Type** or manually change the data type for columns of interest. Update the name of the resultant table if desired.
90
+
1. As no schema information is returned from Cosmos DB after the query is executed, the resultant table identifies all column types as _any_. Either transform the columns using **Detect Data Type** or manually change the data type for columns of interest. Update the name of the resultant table if desired.
1. Once the **Power Query Editor** is closed and the changes applied, the resultant table appears in the **Data** pane.
95
95
96
-
:::image type="content" source="./media/azure-documentdb/native-query-final-result.png" alt-text="Screenshot showing Native Mongo Query transform data type final result.":::
96
+
:::image type="content" source="./media/azure-cosmos-db-for-mongodb-vcore/native-query-final-result.png" alt-text="Screenshot showing Native Mongo Query transform data type final result.":::
97
97
98
98
Refer to [Troubleshooting & Limitations](#troubleshooting--limitations) for limitations of the `Value.NativeQuery` function.
99
99
@@ -128,7 +128,7 @@ Refer to [Troubleshooting & Limitations](#troubleshooting--limitations) for limi
128
128
129
129
- Negative OLE times (Dates from before 1899, December 30) for `Date.From`, `DateTime.From`, and `DateTimeZone.From` don't work.
130
130
131
-
- Using the Power BI `DateTimeZone.From` function results in a _(400): Bad Request_ error from the Azure DocumentDB server as the `dateFromString` functionality isn't added to Azure DocumentDB.
131
+
- Using the Power BI `DateTimeZone.From` function results in a _(400): Bad Request_ error from the Cosmos DB server as the `dateFromString` functionality isn't added to Cosmos DB for MongoDB.
132
132
133
133
- Field names that contain special characters aren't supported (for example, `$`, `.`, `@`, etc.).
0 commit comments