Azure Arc-Enabled SQL Server Is Now GA in Germany West Central: Requirements and Regional Caveats

The news came out during SQLCon/FabCon Europe in Barcelona. In Microsoft's Azure SQL Dev Corner recap, Principal Group Product Manager Anna Hoffman wrote that Azure Arc-enabled SQL Server expands to Germany West Central and Italy North, continuing the regional buildout so you can keep data residency commitments while running Arc management. Italy North is a separate regional launch. This article covers Germany West Central only.

What actually changed​

This is a regional availability change. It isn't a new SQL Server release, and it isn't a new Azure-hosted database service. SQL Server enabled by Azure Arc connects SQL Server instances on physical or virtual machines, running Windows or Linux, to Azure so you can manage them there. As Microsoft's Tech Community overview puts it, whether your SQL Server is running on-premises in your datacenter, on AWS EC2, Google Cloud, or at an edge location Azure Arc brings it under Azure management.

The practical change is simple. Germany West Central can now be selected as a production region for Arc-enabled SQL Server resources. The announcement doesn't mention:

• new features specific to this region
• pricing changes
• region-specific SLA terms or technical limits

Don't assume any of those changed.

Summary: German organizations can now anchor Arc-managed SQL Server estates in a German Azure region with full production support.

Why German admins should care​

Until now, German customers had to choose a region elsewhere. In a region-planning guide, German Microsoft community writer Andreas Hartig noted that Germany lacks important functionality at the end of June 2025 i.e. Azure Arc enabled System Center Virtual Machine Manager, Azure Arc SQL, Azure Arc enabled VMware vSphere but you can consider the Azure Region Sweden Central a strong option. Those workarounds were fine technically. They were harder to explain to a compliance officer who wanted "Germany" written on the diagram.

A caution on data residency: Microsoft says the expansion helps customers keep their residency commitments. It doesn't list which Arc metadata, inventory or usage data is stored where. It also doesn't mean your databases move anywhere. They stay on the servers where they already run. Picking Germany West Central sets where the Azure management resources live. If you have formal sovereignty obligations, check the data-handling details with Microsoft before you tell auditors anything.

The documentation hasn't caught up yet​

When the Microsoft Learn prerequisites page for SQL Server enabled by Azure Arc was checked, it was last updated July 7, 2026. Its supported-region list did not include Germany West Central. For Europe, the Middle East and Africa it listed France Central, North Europe, Norway East, South Africa North, Sweden Central, Switzerland North, UAE North, UK South, UK West and West Europe.

Two newer Microsoft sources, the Azure Updates entry and the SQLCon recap, both say the region is now available. The most likely explanation is that the documentation is behind, though Microsoft hasn't said so. That matters because the onboarding script checks whether your region is supported. Confirm that Germany West Central is offered in the portal or CLI for your subscription before you schedule a rollout.

Prerequisites (unchanged by this launch)​

None of the following is new with this launch. These are the general product requirements from Microsoft Learn, and they apply in any region:

Configurations that aren't supported include SQL Server running in Azure Virtual Machines (those have their own SQL VM experience), SQL Server in containers, the Business Intelligence edition, and Windows Server versions earlier than 2016.

Pre-flight checklist for Germany West Central​

1. Register the providers. You can use the portal (Subscriptions → Resource providers), PowerShell's Register-AzResourceProvider, or az provider register for both namespaces.
2. Use the same region for both resources. Microsoft Learn says successful onboarding requires the Arc-enabled server and the Arc-enabled SQL Server instance to be in the same region.
3. Open outbound HTTPS. Arc-enabled SQL Server needs outbound TCP 443 to *.<region>.arcdataservices.com, authenticated with Microsoft Entra ID. Microsoft's rule is to take the region name without spaces, so East US 2 becomes eastus2. By that rule Germany West Central would be germanywestcentral, but confirm it against current regional guidance before you write firewall rules.
4. Don't plan on Private Link here. Microsoft states that Private Link isn't supported for the Arc data processing service endpoint used for inventory and usage upload.
5. Check hardened servers. The extension deployer connects as NT AUTHORITY\SYSTEM. If your hardening baseline disabled that login or removed its CONNECT SQL permission, provisioning will fail.
6. Check the permissions. You need read access on the subscription, local admin (root on Linux), and the Azure Connected Machine Onboarding role or equivalent on the resource group.

Moving existing Arc resources​

What if you already onboarded servers to West Europe or Sweden Central? Microsoft hasn't published a migration path specific to this region. One Microsoft Q&A thread describes an admin whose server was first onboarded in Poland Central, where the SQL extension failed. The fix was that after removing the Arc resource and re-onboarding the server into Germany West Central, the Azure Arc SQL Extension installed successfully and the SQL Server instance became healthy. That's one admin's troubleshooting story, not official guidance. Still, it suggests that changing regions means re-onboarding, not flipping a setting. Plan for tags, policies, and your monitoring history to need attention.

The bottom line​

This is a small announcement with a clear use. For German enterprises that manage on-premises or multi-cloud SQL Server from Azure, it removes a reason to register those resources outside Germany. The things to watch are the stale region list on Microsoft Learn and the unanswered questions about exactly which data stays in the region. Confirm the region shows up for your subscription, check your firewall and hardening baselines against the checklist, and if you're coming from another region, plan for a full re-onboard.