Share via

Unable to create Network Connectivity Config resource for Databricks in West Europe

Pádraic Slattery 20 Reputation points
2026-05-04T10:54:10.4433333+00:00

We want to use Lakeflow for ingestion (primarily from a MySQL instance). All our resources are deployed with private endpoints in a vnet. We want to use serverless compute to connect to the MySQL instance. We are currently encountering this error when deploying a ``databricks_mws_network_connectivity_config` resource via Terraform:

Error: cannot create mws network connectivity config: Region West Europe doesn't support this serverless function yet.

Serverless capability is fully available in West Europe according to the docs. We are using  version 1.113.0 of the provider package.

Can you please help us with this issue?

Azure Databricks
Azure Databricks

An Apache Spark-based analytics platform optimized for Azure.

Answer accepted by question author

SAI JAGADEESH KUDIPUDI 3,215 Reputation points Microsoft External Staff Moderator
2026-05-05T20:07:05.5066667+00:00

Hi Pádraic Slattery,
it looks like you’ve run into the “Region West Europe doesn’t support this serverless function yet” error because the Terraform resource is expecting the region slug (and in some cases the feature isn’t yet GA in that region) rather than the friendly name. A few things to check:

  1. Use the correct region identifier
    • Terraform for Azure Databricks expects region = "westeurope" (all lower-case, no spaces), not "West Europe" or any other alias.
  2. Confirm serverless networking is actually available in West Europe for your account
    • The Databricks public feature-availability table shows serverless compute is available, but network connectivity configurations (NCCs) for private-endpoint-backed serverless workloads may still be in preview or rolling out in West Europe.
    • You need a Premium-tier account and to have the NCC feature enabled in that region.
  3. Sample Terraform snippet 
 resource "databricks_mws_network_connectivity_config" "ncc" {
     account_id = var.databricks_account_id
     name       = "my-serverless-ncc"
     region     = "westeurope"
   
     // egress rules, private endpoint rules, etc.
   }
  1. If you still get the “doesn’t support…” error after using the slug and confirming your plan, it likely means the service hasn’t been turned on in West Europe yet. In that case your options are:
    • Open an Azure support ticket to get the feature enabled in your tenant/region (preview customers can sometimes get early access)
    • Deploy your NCC in a region where serverless‐networking is fully GA (for example East US or North Europe) until West Europe catches up
      Hope that gets you unblocked! If you’re still seeing the error, could you please share:
  2. The exact Terraform snippet you’re running (especially what you’ve got under region).
  3. Whether your Databricks account is on Premium or Trial tier.
  4. Which workspace(s) you attached this NCC to and whether those workspaces have been updated/restarted since you created the NCC.
    References:

Was this answer helpful?

1 person found this answer helpful.

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Senthil kumar 565 Reputation points
    2026-05-04T11:55:11.9533333+00:00

    Hi Pádraic Slattery,

    • If possible to test without terraform with any other resources.
    • As per my understanding still not established connectivity in west Europe. due to the reason its failed.

    Thanks.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-05-04T10:54:31.57+00:00

    Lakeflow ingestion from MySQL over serverless compute requires two things to be available in a region:

    1. Serverless compute itself.
    2. Lakeflow Connect for MySQL in that region.

    From the provided information:

    • Lakeflow Connect for MySQL is listed as available in all major regions, including westeurope.
    • Network connectivity configurations (NCCs) are the mechanism used to manage serverless network connectivity (private endpoints and firewall rules) and are regional constructs that must match the workspace region.

    However, the error message returned by the Terraform provider:

    Region West Europe doesn't support this serverless function yet.

    indicates that, for the specific serverless networking feature being invoked by databricks_mws_network_connectivity_config, the backend is rejecting creation in West Europe. The context does not provide a per-region matrix for NCC/serverless networking support beyond general statements and therefore does not contradict this error.

    Given the constraints of the available documentation, the only supported guidance is:

    • Network connectivity configurations (NCCs) are required for serverless private connectivity and firewall enablement, and they are regional. The NCC region must match the workspace region.
    • NCCs are used to manage private endpoints and firewall rules for serverless compute, including connections to data sources such as MySQL, and they can be shared across up to 50 workspaces per region.
    • If an NCC cannot be created in a specific region due to backend limitations (as indicated by the error), this is a platform-side limitation rather than a Terraform configuration issue, and must be resolved by the service team.

    Actionable steps based on the documented behavior:

    1. Confirm that the workspace and the intended NCC are in the same region (West Europe). NCCs are region-specific and must match the workspace region.
    2. Since the error explicitly states that the serverless function is not supported in West Europe for this operation, open a support case with Azure Databricks/Microsoft to:
      • Verify whether NCC-based serverless networking is fully enabled in West Europe for the account.
      • Confirm if there are account-level or region rollout constraints affecting NCC creation in West Europe.
    3. As an interim measure, if ingestion and serverless networking are critical and if organizational policies allow, consider using a region where both Lakeflow Connect and NCC/serverless networking are confirmed available and where NCC creation succeeds, then align workspaces and NCCs to that region.

    Because the context does not include any workaround for forcing NCC creation in a region where the backend reports it as unsupported, further resolution requires direct engagement with support.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.