SQL Server on Azure VMs Reaches GA in Azure Bleu, France’s Sovereign Cloud

What Microsoft announced​

Anna Hoffman, a Principal Group Product Manager on Microsoft's SQL engineering team, posted a roundup from SQLCon/FabCon Europe in Barcelona on September 29, 2026. In its "Hybrid and migration" section, she says that SQL Server on Azure Virtual Machines in Azure Bleu is generally available. I am not quoting that line directly. Her post describes it as bringing the SQL VM experience to France's sovereign cloud.

The Azure Updates entry is labeled "Launched". In Microsoft's taxonomy, that means a fully released, production-ready product. Treat the October 5 timestamp on that record as when the entry was published, not the date the feature shipped. The blog post appeared about a week earlier.

The roundup sits among several other announcements, and they are separate events. SQL Server on Azure Local reached GA in connected and disconnected modes. Azure Arc-enabled SQL Server also expanded to Germany West Central and Italy North. Don't conflate either of those with the Bleu item.

What is Azure Bleu?​

Bleu is a French company set up by Orange and Capgemini. It offers Microsoft Azure and 365 cloud services, with Capgemini and Orange controlling data centers that are separate from the wider Azure infrastructure. The design target is the French government's ANSSI SecNumCloud requirements. Microsoft's sovereign-cloud blog says Bleu is designed to meet the French government's (ANSSI) SecNumCloud requirements.

Bleu's own site says its data centers are located exclusively in France, in two regions more than 300 kilometers apart. Its service catalog lists Virtual Machines among the compute offerings.

Bleu also has critics. Light Reading's coverage notes that Bleu's offering is entirely built on Microsoft technology. Orange told the outlet that Bleu's infrastructure is entirely independent of Microsoft and Microsoft does not have access to the service platform or customer data. Analysts quoted by CIO have called Microsoft's wider sovereignty pitch a smokescreen. Whether Bleu meets your own sovereignty bar is a legal and risk question. A GA badge on a VM product doesn't answer it.

Why a SQL VM matters in a sovereign cloud​

A SQL Server VM is the option for teams that want a conventional SQL Server with control of the operating system. Microsoft's migration documentation says the target suits you when you want to use the familiar SQL Server environment with OS control, along with cloud-provided features such as built-in VM high availability, automated backups, and automated patching. These are general properties of the product. Microsoft hasn't said they are new in Bleu.

This fits workloads that don't suit a fully managed service. Typical examples are:

• Lift-and-shift of existing SQL Server estates that depend on specific versions or editions
• Applications that need OS-level access or third-party agents on the database host
• Estates that still run SSIS, SSRS or SSAS next to the database engine, which Microsoft's migration guide says can move to a SQL Server VM

For regulated French organizations, the practical point is that the VM-based route no longer has to be assembled outside Bleu's platform.

What Microsoft hasn't said​

The announcement leaves a lot out. I could not find published details on any of the following for Bleu:

• Supported SQL Server versions, editions and Marketplace images
• Eligible VM sizes and disk types
• Pricing, and whether Azure Hybrid Benefit applies the same way
• Which Bleu regions offer the service
• Whether features such as automated patching and automated backup behave as they do in public Azure
• Onboarding eligibility, or any compliance certification outcome

Don't assume feature parity with public Azure. Microsoft's general Azure SQL VM documentation describes behavior in public regions, and it doesn't confirm Bleu specifics.

Public Azure workflow for reference​

In public Azure, Microsoft's portal guide describes this flow. Bleu's portal may differ, so confirm each step there:

1. Open the Azure SQL hub, choose SQL Server on Azure VMs, then select Create.
2. Pick a Marketplace image. Microsoft's example uses SQL Server 2025 Enterprise Developer on Windows Server 2025.
3. Choose a VM size. Microsoft's walkthrough uses E4ds_v5 as one of the minimum recommended sizes. Its docs warn that the size picker's cost estimate doesn't include SQL Server licensing costs for paid editions.
4. On the SQL Server settings tab, set connectivity, authentication, storage and tempdb. The docs advise picking the most restrictive connectivity your scenario allows.
5. Decide on automated patching and automated backup. Both are disabled by default in the portal flow.

One caution from the same guide: self-installed SQL Server instances can fail to start when tempdb sits on the local temp disk of VM images with uninitialized ephemeral disks, such as FXmdsv2. Microsoft's advice is to deploy a Marketplace SQL image, use a different VM series, or initialize the drives first.

The roundup also mentions provisioning improvements for VMs generally. You can now configure ephemeral storage during provisioning on v6+ VMs, which removes the post-deployment disk resizing used to place tempdb. That is listed as a general VM change, not a Bleu-specific one.

Bottom line​

For French public-sector and critical-infrastructure organizations that run SQL Server and need a sovereign Azure option, this removes one blocker. Before you plan a migration, confirm in Bleu's own documentation and portal which images, VM sizes, licensing options and management features are actually available. Then work with your compliance team on whether the platform satisfies your obligations. Microsoft's announcement doesn't make that determination.