Transition your Azure Synapse Analytics workspaces to private links before 1 August 2026

Question

Transition your Azure Synapse Analytics workspaces to private links before 1 August 2026

Mohd Anas 20

Is there a way to enable a managed private network in an existing Azure Synapse workspace where it hasn’t been enabled? We recently received an email about transitioning to private links before August next year, otherwise Synapse will lose its ability to connect to Azure Storage and Key Vault. From what I’ve read, the managed private network setting can’t be modified after a workspace is created. This seems to leave creating a new workspace with a managed VNet and migrating artifacts as the only option. Is anyone else running into the same issue? How are you handling it?

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

Anonymous

2025-09-23T07:29:20.5166667+00:00

Hi Mohd Anas,

I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.
Anonymous

2025-09-24T06:54:29.76+00:00

Hi Mohd Anas,

We haven't heard back from you. Please reply if you have any questions in this matter and we will gladly continue the discussion.

Answer accepted by question author

0 additional answers

Anonymous

2025-09-23T07:29:20.5166667+00:00

Hi Mohd Anas,

I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.
Anonymous

2025-09-24T06:54:29.76+00:00

Hi Mohd Anas,

We haven't heard back from you. Please reply if you have any questions in this matter and we will gladly continue the discussion.

Answer 1

Anonymous

Hi Mohd Anas,

Thank you for reaching out on Q&A.

I dug into the docs and here’s what I found.

If your workspace was created without a managed VNet, you cannot retroactively add one or convert the workspace to use the managed VNet. It cannot be enabled or changed after the Synapse workspace is created. Here's a Microsoft Learn link for further information: Synapse Workspace Managed Vnet

Please let us know if you need any additional information on this.

Mohd Anas 20 Reputation points

2025-09-29T19:09:38.78+00:00

So I can't transition to private links and I have to create a copied workspace and then do the migration from managed identities to private links?
Anonymous

2025-09-30T04:34:15.5933333+00:00
Hi Mohd Anas,

You're correct, you can't transition an existing Azure Synapse workspace from using public network access to using Private Link with a managed virtual network if the workspace wasn't created with that setting.

So yes, the only viable path is to create a new Synapse workspace with a managed virtual network enabled, and then:

Migrate your artifacts (pipelines, notebooks, SQL scripts, etc.).

Reconfigure your linked services (like to Azure Data Lake, Key Vault, SQL DBs, etc.) to use Managed Private Endpoints (Private Links).

Switch authentication and access models, such as from public-access-based Managed Identity connections to private endpoint-secured connections.

I'd also recommend applying an Azure Policy to block the creation of new workspaces without Managed VNet to avoid this issue going forward.

If this answers your query, please click Accept Answer and Upvote for was this answer helpful.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Share via

Transition your Azure Synapse Analytics workspaces to private links before 1 August 2026

0 additional answers