When you rollout a Synapse workspace with managed_virtual_network_enabled=true everything seems to roll out correctly:
- Synapse Workspace overview page is showing
- You can create managed private endpoints to other resources via Terraform
But
- Default and newly created integration endpoints are not running in the managed VNET
- The newly create managed private endpoints are not working. The PAAS services still needing public networking enabled to be able support connections from Synapse
- Azure Portal UI and Synapse Studio is not showing or grey out managed private endpoint configuration
- ARM template is showing
“resources”: [
{
“type”: “Microsoft.Synapse/workspaces”,
“apiVersion”: “2021-06-01”,
“name”: “[parameters(’*)]",
“location”: “westeurope”,
“identity”: {
“type”: “SystemAssigned”
},
“properties”: {
“defaultDataLakeStorage”: {
“accountUrl”: "”,
“filesystem”: “synapse”
},
“encryption”: {},
"managedVirtualNetwork": “default”,
So in other words what you rollout now with this option doesn’t work, fixing it will need a full redeploy of synapse
I see Pull Request and I’m convinced that this will fix my problem but this will be released in v3.xxx of the Terraform azurerm provider
Seeing it’s a very small fix for a not common setup (Synapse in a Private Network Environment) used deployment, current deploy is resulting in not working components. Can this pull request not be integrated earlier?