Connectivity issues with synapse using private endpoints

[mrflinstone]

I have got a synapse workspace which uses git as the back end repo, what I have now done is scripted out the synapse workspace in order to create a parallel synapse analytics workspace, called it a different name but points to thesame repo.

The first synapse workspace has all its connections working (workspaceA), including the private endpoints etc. However the second synapse workspace, let us call it workspaceB has got private endpoints created on thesame vnet/subnet as workspaceA, IP addresses obviously different but from within thesame subnet. 

The first is that on workspaceB, my private endpoints do not work when I open synapse studio, all I see is the private endpoint being stuck in a refreshing state with little to no information as to what is actually going on.

Thesame connections work perfectly fine on workspaceA and all have a succeeded status.

The first connection connection below was manually created and I suspect thats why it has a succeeded status, the rest are being read from the json file somewhere in the repo, this is from workspaceB.

[mrflinstone · Accepted solution]

Its Azure synapse. The issue was resolved as the private endpoints were not approved within Azure.

[v-cboorla-msft]

Hi @mrflinstone 

Thanks for using Microsoft Fabric Community.

Could you please confirm whether you are facing connectivity issue in Azure Synapse Workspace or in Microsoft Fabric?

Thanks.

[v-cboorla-msft]

Hi @mrflinstone 

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.
In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help.

Thanks.