Deployment to create a Vm with SQL server standard 2022 failed

Question

Deployment to create a Vm with SQL server standard 2022 failed

David Domínguez 20

I tried to create a VM with sql server standard 2022 on windows server 2022 using Azure Portal but failed with error:

{
  "code": "Ext_SqlIaasExtensionError",
  "message": "Error: 'Healthy;DatabaseMonitorArcPlugin: {State:NotRunning};ExtendedSecurityUpdates: ESU service is disabled'"
}

I don't want to pay for ESU plans.

Configuration

Basics

Subscription : xxxx-subscription
Resource group: Clients
Virtual machine name: mxc-prod-db
Region: Mexico Central
Availability options: No infrastructure redundancy required
Zone options: Self-selected zone
Security type: Trusted launch virtual machines
Enable secure boot: Yes
Enable vTPM: Yes
Integrity monitoring: No
Image: SQL Server 2022 Standard on Windows Server 2022 - Gen2
VM architecture: x64
Size: Standard D2ds v4 (2 vcpus, 8 GiB memory)
Enable Hibernation: No
Username: theuser
Public inbound ports: RDP
Already have a Windows license? No
Azure Spot: No

Disks

OS disk size: Image default
OS disk type: Premium SSD LRS
Use managed disks: Yes
Delete OS disk with VM: Enabled
Ephemeral OS disk: No

Networking

Virtual network: the-name-of-vnet

Subnet: the-subnet-vnet (10.15.10.0/24)

Public IP: None

Accelerated networking: On

Place this virtual machine behind anexisting load balancing solution?: No

Delete NIC when VM is deleted: Disabled

Management

Microsoft Defender for Cloud: Basic (free)
System assigned managed identity: Off
Login with Microsoft Entra ID: Off
Auto-shutdown: Off
Site Recovery: Disabled
Enable periodic assessment: Off
Enable hotpatch: Off
Patch orchestration options: Manual patching: Install patches yourself or through a different patching solution.

Monitoring

Alerts: Off
Boot diagnostics: On
Enable OS guest diagnostics: Off
Enable application health monitoring: Off

Advanced

Extensions: None
VM applications: None
Cloud init: No
User data: No
Disk controller type: SCSI
Proximity placement group: None
Capacity reservation group: None

SQL Server settings

Warning: Per hour VM price shown abovedoes not include SQL Server License

SQL Server License: Pay As You Go

SQL connectivity level: Private

SQL port: 1433

SQL Authentication: Disabled

SQL Server Machine Learning Services(In-Database): Disabled

Storage optimization type: Transactional processing

SQL Data file path: F:\data

SQL Data storage: 256 GiB, 1100 IOPS, 125 MB/s, Premium SSD

SQL Log file path: G:\log

SQL Log storage: 1024 GiB, 5000 IOPS, 200 MB/s, Premium SSD

SQL tempdb file path: D:\tempDb

SQL tempdb storage: Use local SSD drive

SQL tempdb data file count: 2

SQL tempdb data file size: 8

SQL tempdb data file growth size: 64

SQL tempdb log file size: 8

SQL tempdb log file growth size: 64

Move system DB to data pool disk: false

Automated patching: Disabled

Automated backup: Disabled

Azure Key Vault integration: Disabled

MAXDOP: 0

Optimize for ad-hoc workload: Disabled

Server Collation: SQL_Latin1_General_CP1_CI_AS

What can I do

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

The deployment is failing because the selected VM size uses an uninitialized ephemeral (local SSD) disk, and tempdb is configured to be placed on that local SSD. On these NVMe-based ephemeral disks, SQL Server setup and the SQL IaaS extension can fail, which surfaces as extension errors during deployment.

From the configuration:

VM size: Standard D2ds v4 (a d-series size with ephemeral storage)
SQL tempdb storage: Use local SSD drive

For affected VM sizes, placing tempdb on the local temp disk is unsupported and causes SQL Server deployment failures.

To resolve the issue without paying for ESU plans:

Use a non-ephemeral VM SKU
- Choose a VM size that does not have the lowercase d in its name (no ephemeral local SSD), for example use a size like D2s v4 instead of D2ds v4, or another size from the recommended VM size list.
- These sizes place tempdb on the same storage as the SQL data files and avoid the RAW NVMe temp disk issue.
Or keep the current VM family but avoid local SSD for tempdb
- In the Azure portal, on the SQL Server settings page while deploying the SQL Server VM image:
  - Under Storage configuration, select Change configuration.
  - Expand tempdb storage.
  - Select any option other than Use local SSD drive (for example, place tempdb on the C: drive or on one of the remote data/log disks).
- Redeploy the VM after changing this setting.
If deploying Windows-only and installing SQL Server manually (alternative approach)
- Deploy a Windows Server-only image on the same VM size.
- Format and initialize the temporary NVMe disk following the documented steps.
- Install SQL Server manually and configure tempdb on non-ephemeral storage.
- If tempdb is placed on the local SSD, the disk must be reinitialized before starting SQL Server every time the VM is restarted or deallocated.

Also note:

When this failure occurs, the VM itself may succeed, but the SQL Server installation fails. The VM should be deleted to avoid charges and then redeployed using one of the methods above.

References: