Azure Arc-Enabled SQL Server Now Available in Italy North: Setup and Regional Requirements

This is a regional expansion only. Microsoft hasn't announced a new engine feature, a performance gain or a price change with it. Region choice still matters, especially if you've been waiting for this exact option.

What Microsoft announced​

The Azure Updates item is short. Microsoft's Azure SQL blog gives a little more context in its roundup from SQLCon/FabCon Europe 2026 in Barcelona. Anna Hoffman, Principal Group Product Manager, wrote there 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.

That tells us two things:

• Italy North isn't the only new region. Germany West Central was announced at the same time. The Azure Updates item covered here deals only with Italy North.
• Microsoft says the reason is data residency. It's the company's own explanation, but it fits: many European customers want their management metadata in a specific country as well as their workloads.

The same roundup included other hybrid SQL news. SQL Server on Azure Local is generally available in both connected mode and disconnected mode, and SQL Server on Azure Virtual Machines in Azure Bleu (France Sovereign Cloud) is generally available. Taken together, Microsoft is filling in European and sovereignty-focused options for SQL Server.

Summary: Italy North is now a production-ready region for Arc-enabled SQL Server. Microsoft announced it alongside Germany West Central and says the main benefit is data residency.

A quick refresher: what Arc-enabled SQL Server does​

If Arc has so far just been one more blade in the portal for you, here's the short version. According to Microsoft Learn, SQL Server enabled by Azure Arc extends Azure services to SQL Server instances hosted outside of Azure. That covers SQL Server in your datacenter, at edge sites such as retail stores, and on other public clouds or hosting providers.

Microsoft says Azure Arc enables you to manage all of your SQL Server instances from a single point of control: Azure. As you connect your SQL Server instances to Azure, you get a single place to view the detailed inventory of your SQL Server instances and databases. Microsoft Learn also lists these capabilities, depending on license type, OS and SQL Server version:

• Inventory queries through Azure Resource Graph, such as "how many SQL Server 2014 instances do we still have?"
• Best practices assessment and migration assessment
• Microsoft Entra authentication (SQL Server 2022 or later)
• Microsoft Defender for Cloud vulnerability assessment and threat protection
• Microsoft Purview governance
• Pay-as-you-go licensing: Microsoft says pay-as-you-go, billed through Azure, is now available for all versions of SQL Server from 2012 to 2022
• Extended Security Updates for SQL Server versions past end of support

Some of these cost extra. Microsoft's Azure Arc pricing page says additional services including, Microsoft Defender for Cloud, Microsoft Purview and Azure Log Analytics are available for additional costs. It also notes that customers can benefit from discounted pricing for Microsoft Defender when consumed through Azure Arc.

Summary: Arc lets you manage SQL Servers outside Azure from the Azure portal. Italy North is a new place to register those resources.

Documentation hasn't caught up yet​

When this was checked, the supported-regions tables on Microsoft Learn's overview and prerequisites pages didn't list Italy North. The European list included France Central, North Europe, Norway East, Sweden Central, Switzerland North, UK South, UK West and West Europe, among others. The prerequisites page was last updated July 7, 2026, and the overview page on June 23, 2026. Both were updated before the September 29 announcement.

Read this as documentation lag, not a sign that the launch didn't happen. It does matter in practice, though. The onboarding script checks whether Arc-enabled SQL Server is supported in the region you choose. If Italy North doesn't appear in the portal or gets rejected when you first try, the rollout may not have reached every part of the service yet. Wait, or raise it with Microsoft, before assuming you've misconfigured something.

Deploying in Italy North: what to check first​

Nothing in the setup process is specific to Italy North. The standard prerequisites still apply, and several are easy to get wrong.

1. Keep both resources in the same region​

Microsoft Learn says that for successful onboarding and operation, the Arc-enabled server and its Arc-enabled SQL Server instance should be assigned the same region. If you want the SQL resource in Italy North, put the Arc-enabled server resource there too. A server already registered in West Europe paired with a SQL instance in Italy North goes against that guidance.

2. Meet the basic prerequisites​

Microsoft's prerequisites page says that before you Arc-enable an instance you need to create an Azure account with an active subscription, then verify Arc connected machine agent prerequisites. The Arc agent must run in the typical 'full' mode. Verify Arc connected machine agent network requirements. Open firewall to Azure Arc data processing service.

You also need to register two resource providers, Microsoft.AzureArcData and Microsoft.HybridCompute. Microsoft documents three ways to do it:

1. Azure portal: Subscriptions → select your subscription → Settings → Resource providers → search for each provider and select Register.
2. PowerShell: Register-AzResourceProvider -ProviderNamespace Microsoft.HybridCompute, then the same command for Microsoft.AzureArcData.
3. Azure CLI: az provider register --namespace 'Microsoft.HybridCompute', then the same command for 'Microsoft.AzureArcData'.

3. Open the right outbound connections​

Each server needs outbound HTTPS on TCP 443 to the Azure Arc Data Processing Service, authenticated through Microsoft Entra ID. The endpoint format is *.<region>.arcdataservices.com, and the region segment is the Azure region name with the spaces removed. Microsoft's own example is *.eastus2.arcdataservices.com for East US 2. Italy North isn't in the docs yet, so check the exact hostname against updated guidance before you change firewall rules.

Also note that Microsoft says Azure Private Link connections to the Arc data processing service aren't supported. That limitation applies to the service in every region, not just Italy North. Network teams planning a private-only design need to know it before architecture reviews.

4. Check SQL Server permissions​

The extension deployer runs as NT AUTHORITY\SYSTEM and connects to each instance using Windows integrated authentication. If your security hardening has disabled that login or denied CONNECT SQL, the extension won't provision. Microsoft's prerequisites page includes a query to check this, and suggests testing it in a non-production environment first. The SQL Server service account also needs to be a member of sysadmin. Only databases that are online and updatable are included when the extension sets permissions.

5. Confirm your configuration is supported​

According to Microsoft Learn:

On Windows, .NET Framework 4.7.2 or later is required. Features also differ by OS. On Linux, for example, best practices assessment and Defender for Cloud aren't available through Arc.

Summary: Keep both resources in the same region, register the providers, allow outbound 443 to the regional endpoint, check the SYSTEM login, and confirm your SQL Server and OS versions are supported.

Analysis: what this means in practice​

It's a small change, but it's a useful one if you're in Italy.

Why it matters: Arc sends inventory and usage metadata to Azure. For Italian public-sector bodies, banks and healthcare providers, the region where that metadata lives can come up with auditors and in procurement. Before this launch, Italian customers had to pick another European region, and some compliance officers accept that less readily than others.

What to be careful about: The announcement doesn't say whether every Arc-connected capability works in Italy North from day one. That includes Defender for Cloud, Purview, monitoring, best practices assessment, and the Log Analytics workspaces some of these rely on. Microsoft's overview notes that Defender and best practices assessment need the Azure Monitoring Agent connected to a Log Analytics workspace. Check that each service you plan to use is available where you need it. The Microsoft blog also frames this as supporting "data residency commitments," but that's a goal, not a legal guarantee. Read the relevant Microsoft data residency terms before you tell your DPO the job is done.

Should you move existing resources? Probably not straight away, unless compliance requires it. If your Arc resources already run fine in West Europe or elsewhere, re-registering them in Italy North means redoing onboarding while keeping the server and SQL instance in the same region. That's a project in its own right. For new onboarding in Italy, though, Italy North now looks like the natural default, once the portal and onboarding script accept it for your subscription.

This also fits a wider trend. With Germany West Central added at the same time, and a sovereign-cloud SQL VM launch in France announced alongside it, Microsoft is clearly making region choice a bigger part of its hybrid SQL offer in Europe.

Bottom line: Italy North is now a production-ready Azure region for Arc-enabled SQL Server. If you're onboarding SQL Server in Italy, you have a local option. The prerequisites haven't changed, so check the region pairing, firewall rules and SYSTEM login before you run the onboarding script.