Azure DocumentDB (with MongoDB compatibility) Networking problem

Question

Azure DocumentDB (with MongoDB compatibility) Networking problem

Tengku Aiman 120

Hello, currently I am trying to troubleshoot my DocumentDB in Azure of Networking from yesterday. I have left it untouched for one day, but it still returning this error when I try to troubleshoot it again

User's image

I checked the allow public access. Do you have any idea why it behaving like this?

0 comments

2 answers

Your answer

Answer 1

The error message in the screenshot indicates a conflict because a networking/public access update operation on the Azure DocumentDB cluster is already in progress. While that operation is still running or stuck, any new attempt to change public access or networking settings will fail with this conflict error.

To move forward, use these steps:

Verify whether any previous networking change is still being applied:
- In the Azure portal, open the DocumentDB cluster.
- Check the Overview blade for any ongoing operation or provisioning state (for example, Updating or In progress).
- If the cluster is still updating, wait until the state returns to Succeeded/Running and then retry the networking change.
If the cluster looks healthy but the error persists for a long time:
- Try refreshing the Networking blade and the entire resource in the portal.
- Avoid making multiple networking changes at once (for example, editing firewall rules and private endpoints simultaneously). Apply one change, wait for it to complete, then apply the next.
Confirm public access and firewall configuration once the conflict clears:
- On the cluster page, go to Networking.
- Under Public access, ensure the desired option is selected:
  - To allow access from specific IPs, add firewall rules with the correct start and end IPv4 addresses.
  - Optionally, enable Allow Azure services and resources to access this cluster if access from other Azure services is required.
- Select Save and wait for the update to complete successfully.
If the cluster remains stuck in an updating state or the conflict error continues even after waiting and refreshing, open a support ticket so the backend operation on the resource can be checked and cleared.

Once the networking update succeeds, connectivity to the cluster should follow the configured rules (public access, firewall IPs, or private endpoints) as described in the networking and connectivity guidance.

References:

Answer 2

Hi Tengku Aiman,
it looks like you’re hitting this error because Azure thinks a previous networking change is still “in-progress” on your Mongo cluster, so any new update (like toggling public access) gets blocked with that conflict message. Here’s how you can troubleshoot and clear that state:

Check the cluster’s provisioning state
- Go to your Cosmos DB account Overview and confirm it’s in “Succeeded” (not “Updating” or “Failed”).
- If it’s still “Updating,” give it another 5–10 minutes—sometimes network or private-endpoint operations can take a while to finish.
Inspect the Activity log and Resource deployments
- In the portal, open the Activity log for your resource group and filter for your cluster name.
- Look for any failed or long-running “Microsoft.DocumentDB/” operations (for example, adding/removing a private endpoint or modifying firewall settings).
- In Deployments under your resource group, see if there’s a stuck deployment you can cancel or retry.
Review Private Endpoint requests (if you’re using Private Link)
- In the Networking blade of your cluster, expand Private access and hit Refresh.
- If you see any private-endpoint connections in “Pending” or “Approving,” either approve or remove them so the service can finish that change.
Retry the public-access toggle
- Once you confirm no operation is stuck, uncheck/re-check Allow public access… and hit Save again.
- If it still errors out after 10–15 minutes of waiting, you might need to open a support ticket to clear the lock.

If you’re not using Private Link but only firewall/IP rules, double-check that no other teammate or automation is modifying the same setting at the same time.

Hope this helps unblock you—let me know if the cluster stays locked after you’ve waited out the in-progress operation!

Follow-up questions if you hit more trouble:

• Do you see your Cosmos account’s provisioning state as “Updating” anywhere in the portal?

• Can you share any recent entries from the Activity log around when you hit the error?

• Are there any private-endpoint connections listed in “Pending” on the Networking pane?

• Which region and API (vCore vs. standard) is your cluster running?

Reference documentation

• Manage public access to Azure Cosmos DB (firewall & IP rules)

https://learn.microsoft.com/azure/cosmos-db/mongodb/how-to-public-access

• Data Explorer fails to connect (allow-access-from-portal setting)

https://learn.microsoft.com/troubleshoot/azure/cosmos-db/account-admin/data-explorer#solution-for-the-api-for-mongodb-ru-or-apache-cassandra

• Private Link implementation for Cosmos DB MongoDB vCore

https://supportability.visualstudio.com/AzureCosmosDB/_wiki/wikis/AzureCosmosDB.wiki/1263358/AzureCosmosDB/TSGs/MongoDB%20(vCore)/Create,%20update%20and%20drop%20resources/TSG:%20Private%20Link%20Implementation%20with%20Azure%20Cosmos%20DB%20Mongo%20DB%20VCore

• Troubleshoot common issues in Azure DocumentDB (including provisioning/deployment locks)

https://learn.microsoft.com/azure/documentdb/troubleshoot-common-issues

Pilladi Padma Sai Manisha 11,715 Reputation points Microsoft External Staff Moderator

2026-05-27T10:41:32.2233333+00:00

Hi

Following up to see if the below answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.