MongoDB Atlas Private Endpoint - Dedicated clusters on Azure created before 10/16/2020

We have dedicated M10 cluster created before 10/16/2020 using Azure provider. Just tried setting up private endpoint and status shows Available but not able to connect through Azure Private Link.
As per documentation there is an important note

Some Atlas clusters on Azure created before 10/16/2020 use Azure networking hardware that is incompatible with Azure Private Link. You can still configure Azure Private Link for Atlas projects with these clusters to use with supported clusters in the project, but you will not be able to connect to the incompatible ones through Azure Private Link.

All new Atlas clusters are compatible with Azure Private Link. If you must connect to your cluster using only Azure Private Link, you can create a new cluster in the same Atlas project and migrate your data.

I confirmed this is the issue by creating a new cluster and able to connect using Azure private link.

Documentation suggests we create a new cluster and do a live migration of data. This will setup a mirror cluster which we can later switch following cutover plan.
However for us this is not easy as we have lots of live apps which will suffer from downtime as we will have to stop the apps, update the connection string and start again.

Is there any other way to deal with this. Some other trick which can force changing azure network interface hardware compatible with private link. How about scaling M10 to higher tier?

1 Like

We tried upgrading the cluster from M10 to M20 which brought one node out of three to new azure hardware but for rest of the nodes we had to take Support team’s help who fixed it from backend. Now the cluster is compatible with private endpoints. We then downgraded back to M10 to avoid costs.
Connection string stays same for standard connection and no downtime or data loss observed. For you it may be that just upgrading and downgrading will bring cluster on supported hardware and you don’t have to take support team’s help. Anyways better than creating a new cluster and run live data migration

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.