Skip to content

Commit bce7f67

Browse files
Merge pull request #210268 from gahl-levy/patch-32
Update how-to-configure-capabilities.md
2 parents 0a634cb + b46bf25 commit bce7f67

File tree

1 file changed

+10
-2
lines changed

1 file changed

+10
-2
lines changed

articles/cosmos-db/mongodb/how-to-configure-capabilities.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to configure your API for MongoDB account capabilities
44
author: gahl-levy
55
ms.service: cosmos-db
66
ms.topic: how-to
7-
ms.date: 07/01/2022
7+
ms.date: 09/06/2022
88
ms.author: gahllevy
99
---
1010

@@ -32,6 +32,10 @@ Copy each of these capabilities. In this example, we have EnableMongo and Disabl
3232
```powershell
3333
az cosmosdb update -n <account_name> -g <azure_resource_group> --capabilities EnableMongo, DisableRateLimitingResponses
3434
```
35+
If you are using PowerShell and receive an error using the command above, try using a PowerShell array instead to list the capabilities:
36+
```powershell
37+
az cosmosdb update -n <account_name> -g <azure_resource_group> --capabilities @("EnableMongo","DisableRateLimitingResponses")
38+
```
3539

3640
## Disable a capability
3741
1. Retrieve your existing account capabilities:
@@ -55,6 +59,10 @@ Copy each of these capabilities. In this example, we have EnableMongo and Disabl
5559
```powershell
5660
az cosmosdb update -n <account_name> -g <azure_resource_group> --capabilities EnableMongo
5761
```
62+
If you are using PowerShell and receive an error using the command above, try using a PowerShell array instead to list the capabilities:
63+
```powershell
64+
az cosmosdb update -n <account_name> -g <azure_resource_group> --capabilities @("EnableMongo")
65+
```
5866

5967
## Next steps
6068

@@ -63,4 +71,4 @@ az cosmosdb update -n <account_name> -g <azure_resource_group> --capabilities En
6371
- Explore MongoDB [samples](nodejs-console-app.md) with Azure Cosmos DB API for MongoDB.
6472
- Trying to do capacity planning for a migration to Azure Cosmos DB? You can use information about your existing database cluster for capacity planning.
6573
- If all you know is the number of vCores and servers in your existing database cluster, read about [estimating request units using vCores or vCPUs](../convert-vcore-to-request-unit.md).
66-
- If you know typical request rates for your current database workload, read about [estimating request units using Azure Cosmos DB capacity planner](estimate-ru-capacity-planner.md).
74+
- If you know typical request rates for your current database workload, read about [estimating request units using Azure Cosmos DB capacity planner](estimate-ru-capacity-planner.md).

0 commit comments

Comments
 (0)