-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Cosmos DB --network-acl-bypass AzureServices doesn't work #28184
Copy link
Copy link
Open
Labels
Auto-AssignAuto assign by botAuto assign by botCosmosDBaz cosmosdbaz cosmosdbService AttentionThis issue is responsible by Azure service team.This issue is responsible by Azure service team.act-codegen-extensibility-squadbugThis issue requires a change to an existing behavior in the product in order to be resolved.This issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.
Description
Metadata
Metadata
Assignees
Labels
Auto-AssignAuto assign by botAuto assign by botCosmosDBaz cosmosdbaz cosmosdbService AttentionThis issue is responsible by Azure service team.This issue is responsible by Azure service team.act-codegen-extensibility-squadbugThis issue requires a change to an existing behavior in the product in order to be resolved.This issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.
Describe the bug
Running az cosmosdb update --network-acl-bypass AzureServices does not turn the Cosmos DB network settings flag on that accepts connections from within public Azure datacenters. If the flag is already set, it is removed after the command.
Related command
az cosmosdb update
Errors
No error, just didn't produce the expected outcome in Cosmos DB.
Issue script & Debug output
Not available for now. Will submit later if needed.
Expected behavior
The Cosmos DB network setting "Accept connections from within public Azure datacenters" is enabled.
Environment Summary
azure-cli 2.56.0.
Cosmos DB has public network access enabled for selected networks. The selected networks include both a VNET subnet and IP addresses.
Additional context
No response