Skip to content

Commit e9d24e6

Browse files
Merge pull request #287299 from KrishnakumarRukmangathan/patch-38
Update connector-azure-cosmos-db.md
2 parents 1fb78c0 + 8295ee3 commit e9d24e6

File tree

1 file changed

+9
-3
lines changed

1 file changed

+9
-3
lines changed

articles/data-factory/connector-azure-cosmos-db.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: jianleishen
77
ms.subservice: data-movement
88
ms.topic: conceptual
99
ms.custom: synapse
10-
ms.date: 08/13/2024
10+
ms.date: 09/04/2024
1111
---
1212

1313
# Copy and transform data in Azure Cosmos DB for NoSQL by using Azure Data Factory
@@ -222,7 +222,7 @@ You can also store service principal key in Azure Key Vault.
222222
### <a name="managed-identity"></a> System-assigned managed identity authentication
223223

224224
>[!NOTE]
225-
>Currently, the system-assigned managed identity authentication is not supported in data flow.
225+
>Currently, the system-assigned managed identity authentication is supported in data flows through the use of advanced properties in JSON format.
226226
227227
A data factory or Synapse pipeline can be associated with a [system-assigned managed identity for Azure resources](data-factory-service-identity.md#system-assigned-managed-identity), which represents this specific service instance. You can directly use this managed identity for Azure Cosmos DB authentication, similar to using your own service principal. It allows this designated resource to access and copy data to or from your Azure Cosmos DB instance.
228228

@@ -240,6 +240,9 @@ These properties are supported for the linked service:
240240
| accountEndpoint | Specify the account endpoint URL for the Azure Cosmos DB instance. | Yes |
241241
| database | Specify the name of the database. | Yes |
242242
| connectVia | The [integration runtime](concepts-integration-runtime.md) to be used to connect to the data store. You can use the Azure integration runtime or a self-hosted integration runtime if your data store is in a private network. If not specified, the default Azure integration runtime is used. |No |
243+
| subscriptionId | Specify the subscription id for the Azure Cosmos DB instance | No for Copy Activity, Yes for Mapping Data Flow |
244+
| tenantId | Specify the tenant id for the Azure Cosmos DB instance | No for Copy Activity, Yes for Mapping Data Flow |
245+
| resourceGroup | Specify the resource group name for the Azure Cosmos DB instance | No for Copy Activity, Yes for Mapping Data Flow |
243246

244247
**Example:**
245248

@@ -250,7 +253,10 @@ These properties are supported for the linked service:
250253
"type": "CosmosDb",
251254
"typeProperties": {
252255
"accountEndpoint": "<account endpoint>",
253-
"database": "<database name>"
256+
"database": "<database name>",
257+
"subscriptionId": "<subscription id>",
258+
"tenantId": "<tenant id>",
259+
"resourceGroup": "<resource group>"
254260
},
255261
"connectVia": {
256262
"referenceName": "<name of Integration Runtime>",

0 commit comments

Comments
 (0)