Deprecated images FAQ

This article answers common questions about what happens when Azure Marketplace images are deprecated.

Important

Image deprecation doesn't affect all images the same way. The impact depends on whether the image requires a Marketplace purchase plan.

• Microsoft first-party images (for example, Windows Server, Canonical Ubuntu, Red Hat, SUSE) don't require a purchase plan and continue to support backup, restore, and disaster recovery scenarios after deprecation.
• Third-party Marketplace images that require a purchase plan (for example, CIS, F5, Cisco) are affected by additional Marketplace enforcement checks after deprecation.

Purchase plan information refers to Marketplace billing terms that you must accept for certain third-party images. Only images that require a purchase plan are subject to enforcement checks after deprecation. To check whether your image has a purchase plan, see How do I check if my image has a purchase plan?. For more information, see Marketplace purchase plan.

Overview

When an Azure Marketplace image is deprecated, its availability for new deployments changes—but existing virtual machines (VMs) and virtual machine scale set (VMSS) instances continue running normally. This article explains platform behavior during image deprecation, which operations are impacted, and what actions (if any) you must take.

What image deprecation means

Deprecation removes the image from the Azure Marketplace catalog but doesn't remove OS disks of existing VMs.

Each deprecated image has an enforcement date, which is the specific date when restrictions take effect. The enforcement date is listed in your deprecation notification email, Azure Advisor recommendations, and the Azure CLI or PowerShell output when you query the image. You typically receive at least 90 days' notice before the enforcement date.

• You can't use a deprecated image for new VM or VMSS instance creation after the enforcement date.
• Existing VMs and VMSS instances that were created before the enforcement date continue operating normally.
• VMSS scale-out operations are blocked after the enforcement date because scaling out requires creating new instances from the deprecated image.

Key points

• No action required for existing VMs: Once created, VMs boot from their OS disk—not from the original image. Deprecation doesn't affect running VMs.
• Most operations continue working: Start, stop, restart, deallocate, and redeploy all work normally.
• Backup and restore continue working for images without a purchase plan: VM backup and restore operations, including restoring a backup to create a new VM, continue to work for Microsoft first-party and endorsed Linux images after deprecation.
• Reimage is blocked: This is the only VM operation affected because it requires recreating the OS disk from the source image.
• VMSS instances continue running: Existing instances aren't affected, but scale-out is blocked after enforcement.

What does it mean when I receive an image deprecation notice?

You receive an email notification when your virtual machine (VM) or virtual machine scale set runs on an image that's scheduled for deprecation. Publishers deprecate images for various reasons, including security concerns or when images reach end of life.

Deprecation levels

Deprecation occurs at three levels:

• Image version deprecation: A specific VM image version.
• Plan/SKU deprecation: An entire plan or SKU and all image versions within it.
• Offer deprecation: The entire VM offer, including all plans and image versions.

What is the deprecation timeline and how does it affect my workloads?

Notice period (90 days before enforcement)

The publisher sets an enforcement date when deprecating an image. You typically have at least 90 days between the deprecation announcement and the enforcement date. The exact enforcement date is included in your email notification and Azure Advisor recommendation.

During the notice period:

• You receive email notifications and Azure Advisor recommendations about the upcoming deprecation.
• Existing VMs and virtual machine scale set instances continue to run normally.
• You can deploy new instances by using Azure CLI, PowerShell, or APIs.
• Deprecation warnings appear in the Azure portal, Azure CLI, and APIs.
• You can migrate or update your deployments until the enforcement date.

After enforcement date (soft delete)

After the enforcement date, the image enters a "soft delete" state. The image is no longer available for new deployments, but existing resources aren't deleted or modified.

Images without a purchase plan (for example, Windows Server, Canonical Ubuntu, Red Hat, SUSE):

• Existing VMs and virtual machine scale set instances continue to run without disruption.
• Start, stop, restart, deallocate, and redeploy continue to work.
• VM backup and restore operations continue to work, including restoring a backup to create a new VM.
• Azure Site Recovery and disaster recovery operations continue to work.
• New VM creation from the deprecated image is blocked.
• Reimage is blocked because it requires recreating the OS disk from the source image.
• Virtual machine scale set scale-out is blocked if new instances must be created from the deprecated version. Scale-out with automatic OS upgrade or "latest" version continues to work.

Images with a purchase plan (third-party Marketplace images such as CIS, F5, Cisco):

• Existing VMs and virtual machine scale set instances continue to run without disruption.
• Start, stop, restart, deallocate, and redeploy continue to work.
• New VM creation from the deprecated image is blocked.
• Backup restore operations that require Marketplace purchase validation might fail.
• Reimage is blocked because purchase plan eligibility checks fail after deprecation.
• Virtual machine scale set scale-out is blocked because it requires creating new instances from the deprecated image.

For more details, see Which operations are affected by image deprecation?.

Required actions

The actions you need to take depend on whether your image requires a purchase plan. For help determining this, see How do I check if my image has a purchase plan?. For detailed migration guidance, see When should I migrate?.

Images without a purchase plan:

• If you use automatic OS upgrades, no action is needed. Automatic OS upgrade handles migration across publisher, offer, SKU, and version changes automatically.
• If you need your virtual machine scale set to scale out after deprecation, migrate to a supported image before the enforcement date.
• To avoid future dependency on Marketplace image availability, consider capturing your workload as a custom image in Azure Compute Gallery. Custom images aren't subject to Marketplace deprecation.

Images with a purchase plan:

• Automatic OS upgrade handles only individual version deprecation. For plan, SKU, or offer deprecation, you must migrate manually.
• Migrate your virtual machine scale set to a supported image before the enforcement date to avoid disruption to scale-out, reimage, and backup restore operations.

Which operations are affected by image deprecation?

The impact of deprecation depends on whether the image requires a Marketplace purchase plan.

Operations that continue to work after deprecation (no migration required)

These behaviors apply to images that don't require a purchase plan (for example, Windows Server, Canonical Ubuntu, Red Hat, SUSE):

Operation	Status after enforcement	Explanation
Running VMs	Continue operating normally	After creation, VMs boot from their OS disk—not from the Marketplace image—and no purchase plan validation is required.
Start / Stop / Restart / Redeploy	Continue working	These operations don't require the source image.
VM backup and restore	Continue working	Restoring a backup, including restoring to create a new VM, continues to work.
Azure Site Recovery and disaster recovery	Continue working	Recovery operations continue to work for Microsoft-endorsed images.
VMSS existing instances	Continue running	Existing instances aren't affected by deprecation.
VMSS scale-out	Blocked only if new instances must be created from the deprecated version	Scale-out with automatic OS upgrade or "latest" version continues to work.

Operations that are blocked after deprecation

Operation	Applies to	Status after enforcement	Explanation
Creating new VMs	All images	Blocked	New VM creation from the deprecated image is blocked regardless of purchase plan status.
Reimage	All images	Blocked	Reimage fails because it requires recreating the OS disk from the deprecated source image.
Restoring backups	Images with a purchase plan	Might fail	Backup restore operations that require Marketplace purchase validation might fail. Restore continues to work for images without a purchase plan.
VMSS scale-out	Images with a purchase plan	Blocked	Scale-out is blocked for images with a purchase plan. For images without a purchase plan, scale-out with automatic OS upgrade or "latest" version continues to work.

Note

The VM's image reference property might disappear from the Azure portal, but this doesn't affect VM operation. The OS disk is authoritative for boot.

How do I check if my image has a purchase plan?

The deprecation impact depends on whether your image requires a Marketplace purchase plan. Use one of the following methods to check.

Option 1: Use Azure CLI

Check the Marketplace image directly:

az vm image show --location eastus --urn <publisher>:<offer>:<sku>:<version> --query plan

Or check an existing VM:

az vm show --resource-group <resource-group> --name <vm-name> --query plan

Option 2: Use PowerShell

Check from an existing VM:

(Get-AzVM -ResourceGroupName <resource-group> -Name <vm-name>).Plan

Check from a Marketplace image:

Get-AzVMImage -Location "eastus" -PublisherName <publisher> -Offer <offer> -Skus <sku> -Version <version> | Select-Object -ExpandProperty PurchasePlan

Interpreting the results

• If the command returns null or empty output, the image doesn't have a purchase plan. Deprecation has minimal impact on your workloads.
• If the command returns name, publisher, and product values, the image has a purchase plan. You should migrate to a supported image before the enforcement date.

For more information, see Supply Azure Marketplace purchase plan information when creating images.

Can I restore a VM from backup after my image is deprecated?

Yes—if your image doesn't require a purchase plan.

• For Microsoft first-party and endorsed Linux images (for example, Windows Server, Canonical Ubuntu, Red Hat, SUSE), restoring a backup—even to create a new VM—is supported after deprecation. This is expected behavior.
• For third-party images that require a purchase plan, restore behavior might be blocked after deprecation because of Marketplace enforcement checks.

If you're using an image that requires a purchase plan, migrate to a supported image before the enforcement date. For more information, see purchase plan information.

When should I migrate my VMs or virtual machine scale sets to a different image?

Migration isn't always required. Review the following scenarios to determine whether you need to take action.

Migration is not required if:

• Your image doesn't require a purchase plan, even if it's deprecated.
• You're using automatic OS image upgrades for VMSS and only the image version is deprecated.
• You aren't performing reimage or scale-out operations that require the original Marketplace image.

Migration is required if:

• Your image requires a purchase plan.
• You need to scale out, reimage, or create new workloads after the enforcement date.
• The entire offer or SKU is deprecated, your image requires a purchase plan, and automatic OS image upgrade can't handle the migration.

Recommended actions

Images without a purchase plan:

• Don't panic when you receive a deprecation notice. Deprecation doesn't imply immediate disruption for first-party images.
• Existing workloads, backup restore, and disaster recovery scenarios continue to work after deprecation. No migration is required for these operations.
• To avoid future dependency on Marketplace image availability, consider capturing your workload as a custom image in Azure Compute Gallery. Custom images aren't subject to Marketplace deprecation.

Images with a purchase plan:

• Coordinate migration with the publisher before the enforcement date. Backup restore, reimage, and scale-out operations might fail after deprecation.
• Custom images that include purchase plan information are still subject to Marketplace enforcement checks. Migrate to a newer, non-deprecated image to avoid disruption.

All images:

• Review which VMs and virtual machine scale sets use the deprecated image. See How do I find VMs using deprecated images? and How do I find virtual machine scale sets using deprecated images?.

How do I find VMs using deprecated images?

Option 1: Use automated script (recommended)

Run Get-AzVMImageDeprecationStatus.ps1 to list all VMs in a subscription that were created from deprecated or soon-to-be-deprecated images.

Option 2: Use Azure Resource Graph

Run the following query in Azure Resource Graph to list all VMs and their image details:

resources 
| where type == "microsoft.compute/virtualmachines" 
//| where properties.storageProfile.imageReference.publisher =~ 'MicrosoftWindowsServer' //Optional: Filter by publisher
//| where properties.storageProfile.imageReference.sku =~ '2016-Datacenter' //Optional: Filter by SKU (Plan)
//| where properties.storageProfile.imageReference.version == '14393.4467.2106061537' //Optional: Filter by version
| project name, subscriptionId, resourceGroup, ImagePublisher=properties.storageProfile.imageReference.publisher, ImageOffer=properties.storageProfile.imageReference.offer, imageSku=properties.storageProfile.imageReference.sku, imageVersion=properties.storageProfile.imageReference.exactVersion

Option 3: Use Azure CLI

To list all VMs using a specific SKU (replace 2016-Datacenter with your deprecated SKU):

az vm list --query "[?storageProfile.imageReference.sku=='2016-Datacenter'].{VM:id, imageOffer:storageProfile.imageReference.offer, imagePublisher:StorageProfile.imageReference.publisher, imageSku: storageProfile.imageReference.sku, imageVersion:storageProfile.imageReference.version}"

To list all VMs using a specific image version (replace with your deprecated version):

az vm list --query "[?storageProfile.imageReference.version=='14393.4402.2105052108'].{VM:id, imageOffer:storageProfile.imageReference.offer, imagePublisher:StorageProfile.imageReference.publisher, imageSku: storageProfile.imageReference.sku, imageVersion:storageProfile.imageReference.version}"

Option 4: Use PowerShell

To list all VMs using a specific SKU (replace 2016-Datacenter with your deprecated SKU):

Get-AzVM | Where-Object {$_.StorageProfile.ImageReference.Sku -eq '2016-Datacenter'} | Select-Object -Property ResourceGroupName, Name, @{label='imageOffer'; expression={$_.StorageProfile.ImageReference.Offer}}, @{label='imagePublisher'; expression={$_.StorageProfile.ImageReference.Publisher}}, @{label='imageSKU'; expression={$_.StorageProfile.ImageReference.Sku}}, @{label='imageVersion'; expression={$_.StorageProfile.ImageReference.ExactVersion}}

To list all VMs using a specific image version (replace with your deprecated version):

Get-AzVM | Where-Object {$_.StorageProfile.ImageReference.ExactVersion -eq '14393.4402.2105052108'} | Select-Object -Property ResourceGroupName, Name, @{label='imageOffer'; expression={$_.StorageProfile.ImageReference.Offer}}, @{label='imagePublisher'; expression={$_.StorageProfile.ImageReference.Publisher}}, @{label='imageSKU'; expression={$_.StorageProfile.ImageReference.Sku}}, @{label='imageVersion'; expression={$_.StorageProfile.ImageReference.ExactVersion}}

How do I find virtual machine scale sets using deprecated images?

Option 1: Use automated script (recommended)

Run Get-AzVMImageDeprecationStatus.ps1 to list all virtual machine scale sets in a subscription that were created from deprecated or soon-to-be-deprecated images.

Option 2: Use Azure Resource Graph

Run the following query in Azure Resource Graph to list all virtual machine scale sets and their image details:

resources 
| where type == "microsoft.compute/virtualmachinescalesets" 
//| where properties.virtualMachineProfile.storageProfile.imageReference.publisher =~ 'MicrosoftWindowsServer' //Optional: Filter by publisher
//| where properties.virtualMachineProfile.storageProfile.imageReference.sku =~ '2016-Datacenter' //Optional: Filter by SKU (Plan)
//| where properties.virtualMachineProfile.storageProfile.imageReference.version == '14393.4467.2106061537' //Optional: Filter by version
//| where properties.virtualMachineProfile.storageProfile.imageReference.version != "latest" //Optional: Exclude scale sets using "latest"
| project name, subscriptionId, resourceGroup, ImagePublisher=properties.virtualMachineProfile.storageProfile.imageReference.publisher, ImageOffer=properties.virtualMachineProfile.storageProfile.imageReference.offer, imageSku=properties.virtualMachineProfile.storageProfile.imageReference.sku, imageVersion=properties.virtualMachineProfile.storageProfile.imageReference.version

Option 3: Use Azure CLI

To list all virtual machine scale sets using a specific SKU (replace 2016-Datacenter with your deprecated SKU):

az vmss list --query "[?virtualMachineProfile.storageProfile.imageReference.sku=='2016-Datacenter'].{VMSS:id, imageOffer:virtualMachineProfile.storageProfile.imageReference.offer, imagePublisher:virtualMachineProfile.storageProfile.imageReference.publisher, imageSku:virtualMachineProfile.storageProfile.imageReference.sku, imageVersion:virtualMachineProfile.storageProfile.imageReference.version}"

To list all virtual machine scale sets using a specific image version (replace with your deprecated version):

az vmss list --query "[?virtualMachineProfile.storageProfile.imageReference.version=='14393.4402.2105052108'].{VMSS:id, imageOffer:virtualMachineProfile.storageProfile.imageReference.offer, imagePublisher:virtualMachineProfile.storageProfile.imageReference.publisher, imageSku:virtualMachineProfile.storageProfile.imageReference.sku, imageVersion:virtualMachineProfile.storageProfile.imageReference.version}"

Option 4: Use PowerShell

To find virtual machine scale sets using a specific SKU (replace 2016-Datacenter with your deprecated SKU):

$vmsslist = Get-AzVmss
$vmsslist | Where-Object {$_.virtualMachineProfile.storageProfile.imageReference.Sku -eq '2016-Datacenter'} | Select-Object -Property ResourceGroupName, Name, @{label='imageOffer'; expression={$_.virtualMachineProfile.storageProfile.imageReference.Offer}}, @{label='imagePublisher'; expression={$_.virtualMachineProfile.storageProfile.imageReference.Publisher}}, @{label='imageSKU'; expression={$_.virtualMachineProfile.storageProfile.imageReference.Sku}}, @{label='imageVersion'; expression={$_.virtualMachineProfile.storageProfile.imageReference.Version}}

To find virtual machine scale sets using a specific image version (replace with your deprecated version):

$vmsslist = Get-AzVmss
$vmsslist | Where-Object {$_.virtualMachineProfile.storageProfile.imageReference.Version -eq '14393.4402.2105052108'} | Select-Object -Property ResourceGroupName, Name, @{label='imageOffer'; expression={$_.virtualMachineProfile.storageProfile.imageReference.Offer}}, @{label='imagePublisher'; expression={$_.virtualMachineProfile.storageProfile.imageReference.Publisher}}, @{label='imageSKU'; expression={$_.virtualMachineProfile.storageProfile.imageReference.Sku}}, @{label='imageVersion'; expression={$_.virtualMachineProfile.storageProfile.imageReference.Version}}

How do I migrate a VM to a different image?

Azure VMs don't support in-place OS upgrades. Create a new VM with a supported image, migrate your data, and decommission the old VM.

Important

For deprecated images that require a Marketplace purchase plan, you can't create new VMs or perform backup restore operations after the enforcement date. Migrate before the enforcement date.

Part 1: Create a new VM

1. Identify the replacement image: Check your deprecation email for the recommended replacement. For more information, see Find and use images using the Azure CLI or Find and use images using Azure PowerShell.

2. Configure the new VM: Match the region and networking settings of your existing VM for the simplest migration. You can change VM size or region if needed.

3. Deploy and test: Confirm the VM starts correctly and your application dependencies are present.

Part 2: Migrate data

Method A: Detach and attach data disks (recommended)

If your workload data is stored on data disks (not the OS disk):

1. Stop and deallocate the old VM.
2. Detach the data disks from the old VM. For more information, see Detach a data disk from a Linux VM or Detach a data disk from a Windows VM.
3. Attach the data disks to the new VM. For more information, see Attach a data disk to a Linux VM or Attach a data disk to a Windows VM.
4. Start the new VM and verify data accessibility.

Note

Data on the OS disk isn't preserved with this method. Only data on attached data disks is migrated.

Method B: Use snapshots (for OS disk data or backup requirements)

If you need to preserve OS disk data or create a backup before migration:

1. Create a snapshot of the data disks.
2. Create managed disks from the snapshots.
3. Attach the disks to the new VM. For more information, see Attach a data disk to a Linux VM or Attach a data disk to a Windows VM.

Method C: Use file-based transfer

Use OS transfer tools for selective data migration:

• Windows: Robocopy or SMB share
• Linux: rsync, scp, or sftp
• Cross-OS: AzCopy with Azure Storage as an intermediate location

Part 3: Switch over

1. Validate: Verify network connectivity, application functionality, firewall rules, and extensions.
2. Update references: Point DNS names, load balancers, or API endpoints to the new VM.
3. Decommission: Keep the old VM briefly for rollback, then deallocate and delete it.

How do I migrate a virtual machine scale set to a different image?

The migration approach depends on whether an image version, plan/SKU, or entire offer is deprecated.

Note

If your image doesn't have a purchase plan and you have automatic OS image upgrade enabled, automatic OS upgrade handles migration automatically for all deprecation levels (version, plan/SKU, and offer), including changes to publisher, offer, SKU, and version. The manual steps in each section below apply only to images with a purchase plan or scale sets without automatic OS upgrade enabled.

Version deprecation

If only a specific image version is deprecated:

• Using "latest" version: No action required for new instances. Azure resolves to the newest available version at deployment time. Existing instances remain on their original version.
• Using automatic OS upgrades: No action required. Azure upgrades existing instances to the latest version automatically, regardless of whether your image reference uses "latest" or a pinned version. This applies to all images, including those with a purchase plan.
• Using a pinned version without automatic OS upgrades: Update the image reference to a supported version. See Modify an Azure virtual machine scale set. After updating the model, upgrade existing instances using one of these methods:
  • Manual upgrade: Use az vmss update-instances (CLI) or Update-AzVmssInstance (PowerShell) to upgrade specific instances.
  • Rolling upgrade policy: Configure the upgrade policy to "Rolling" so instances automatically upgrade when the model changes.

Tip

Enable automatic OS image upgrade to avoid manual intervention for future deprecations.

Plan/SKU deprecation

If an entire plan or SKU is deprecated:

• Images without a purchase plan and automatic OS upgrade enabled: No action required. Automatic OS upgrade migrates your scale set to the replacement SKU automatically.
• Images with a purchase plan, or automatic OS upgrade not enabled: Update to a different SKU from the same offer using a scale-out/scale-in approach:

1. Find an alternative SKU from your deprecation email. For more information, see Find and use images using the Azure CLI or Find and use images using Azure PowerShell.

2. Update the VMSS model to use the new SKU:

   az vmss update --resource-group <resource-group> --name <vmss-name> \
     --set virtualMachineProfile.storageProfile.imageReference.sku=<new-sku> \
     --set virtualMachineProfile.storageProfile.imageReference.version=latest
   

3. Scale out to create new instances using the updated image, then scale in to remove old instances. Or delete specific old instances and let the scale set replace them with new ones.

Important

Upgrading or reimaging existing instances replaces their OS disks. Use scale-out/scale-in to avoid data loss on OS disks.

Offer deprecation

If an entire offer is deprecated:

• Images without a purchase plan and automatic OS upgrade enabled: No action required. Automatic OS upgrade migrates your scale set to the replacement offer automatically, even if the publisher, offer, or SKU changes.
• Images with a purchase plan, or automatic OS upgrade not enabled: Create a new virtual machine scale set with a supported image:

1. Find a replacement offer from your deprecation email or search in the Azure Marketplace.

2. Create a new virtual machine scale set using the replacement image. Match your existing configuration (networking, extensions, scaling rules).

3. Test application compatibility thoroughly. A different publisher or offer may have significant OS or configuration differences.

4. Migrate traffic to the new scale set, then delete the old one.

Note

We recommend that you create a new VMSS instead of doing in-place updates when you change publishers or offers, because the differences between images are typically significant.

How do I receive email notifications about image deprecation?

Azure notifies you about image deprecation through two channels:

• Email notifications: Sent directly to subscription administrators with the Owner or Account Admin role on the subscription.
• Azure Advisor recommendations: Deprecation recommendations appear in Azure Advisor.

Notify additional recipients

To notify team members who don't have Owner or Account Admin roles on the subscription, create an Advisor alert with an action group. Use action groups to specify email addresses, SMS numbers, or webhooks that receive notifications when new deprecation recommendations are published.

How do I check if a specific image is deprecated or scheduled for deprecation?

Option 1: Use Azure CLI

az vm image show --location eastus --urn MicrosoftWindowsServer:WindowsServer:2016-Datacenter:14393.4169.2101090332 --query [imageDeprecationStatus]

Option 2: Use PowerShell

To check a single image version:

Get-AzVMImage -Location "eastus" -PublisherName "MicrosoftWindowsServer" -Offer "WindowsServer" -Skus "2016-Datacenter" -Version "14393.4169.2101090332" | Select-Object -ExpandProperty "ImageDeprecationStatus"

To check all versions of a SKU with deprecation details:

Get-AzVMImage -Location "westus" `
  -PublisherName "center-for-internet-security-inc" `
  -Offer "cis-rocky" `
  -Skus "cis-rockylinux-9-l1-gen2-azure-observability" `
  -Expand "properties/imageDeprecationStatus" |
  Select-Object Version, @{
    Name = "DeprecationDetails"
    Expression = { $_.ImageDeprecationStatus | Out-String }
  } | Format-Table -Wrap -AutoSize

Option 3: Use REST API

Use the Virtual Machine Images - Get API. If the image is deprecated, you receive a response like:

{
  "error": {
    "code": "ImageVersionDeprecated",
    "message": "VM Image from publisher: MicrosoftWindowsServer with - Offer: WindowsServer, Sku: 2016-Datacenter, Version: 14393.4169.2101090332 is deprecated."
  }
}

Option 4: Use automated script

Run Get-AzVMImageDeprecationStatus.ps1 in Cloud Shell or locally to check all VMs and virtual machine scale sets in a subscription for deprecated images.

How do I list active (non-deprecated) image versions for a specific SKU?

Active images are images that aren't scheduled for deprecation or already deprecated.

Option 1: Use Azure CLI

az vm image list --location eastus --publisher "MicrosoftWindowsServer" --offer "WindowsServer" --sku "2022-Datacenter" --all --query "[?imageDeprecationStatus.imageState=='Active']"

Option 2: Use PowerShell

Get-AzVMImage -Location "westus" `
  -PublisherName "center-for-internet-security-inc" `
  -Offer "cis-rocky" `
  -Skus "cis-rockylinux-9-l1-gen2-azure-observability" `
  -Expand "properties/imageDeprecationStatus" |
  Where-Object { $_.ImageDeprecationStatus.ImageState -eq "Active" } |
  Select-Object Version

What happens to SQL Server if a SQL Server Azure Marketplace image is deprecated?

Your SQL Server remains unaffected when a SQL Server Azure Marketplace image is deprecated:

• Your Azure VM continues to run without interruption.
• Your SQL Server instance continues to function normally.
• You can't deploy new VMs using the deprecated SQL Server image.

Existing deployments require no action.

This article answers common questions about what happens when Azure Marketplace images are deprecated.

Important

Image deprecation doesn't affect all images the same way. The impact depends on whether the image requires a Marketplace purchase plan.

• Microsoft first-party images (for example, Windows Server, Canonical Ubuntu, Red Hat, SUSE) don't require a purchase plan and continue to support backup, restore, and disaster recovery scenarios after deprecation.
• Third-party Marketplace images that require a purchase plan (for example, CIS, F5, Cisco) are affected by additional Marketplace enforcement checks after deprecation.

Purchase plan information refers to Marketplace billing terms that you must accept for certain third-party images. Only images that require a purchase plan are subject to enforcement checks after deprecation. To check whether your image has a purchase plan, see How do I check if my image has a purchase plan?. For more information, see Marketplace purchase plan.

Overview

When an Azure Marketplace image is deprecated, its availability for new deployments changes—but existing virtual machines (VMs) and virtual machine scale set (VMSS) instances continue running normally. This article explains platform behavior during image deprecation, which operations are impacted, and what actions (if any) you must take.

What image deprecation means

Deprecation removes the image from the Azure Marketplace catalog but doesn't remove OS disks of existing VMs.

Each deprecated image has an enforcement date, which is the specific date when restrictions take effect. The enforcement date is listed in your deprecation notification email, Azure Advisor recommendations, and the Azure CLI or PowerShell output when you query the image. You typically receive at least 90 days' notice before the enforcement date.

• You can't use a deprecated image for new VM or VMSS instance creation after the enforcement date.
• Existing VMs and VMSS instances that were created before the enforcement date continue operating normally.
• VMSS scale-out operations are blocked after the enforcement date because scaling out requires creating new instances from the deprecated image.

Key points

• No action required for existing VMs: Once created, VMs boot from their OS disk—not from the original image. Deprecation doesn't affect running VMs.
• Most operations continue working: Start, stop, restart, deallocate, and redeploy all work normally.
• Backup and restore continue working for images without a purchase plan: VM backup and restore operations, including restoring a backup to create a new VM, continue to work for Microsoft first-party and endorsed Linux images after deprecation.
• Reimage is blocked: This is the only VM operation affected because it requires recreating the OS disk from the source image.
• VMSS instances continue running: Existing instances aren't affected, but scale-out is blocked after enforcement.

You receive an email notification when your virtual machine (VM) or virtual machine scale set runs on an image that's scheduled for deprecation. Publishers deprecate images for various reasons, including security concerns or when images reach end of life.

Deprecation levels

Deprecation occurs at three levels:

• Image version deprecation: A specific VM image version.
• Plan/SKU deprecation: An entire plan or SKU and all image versions within it.
• Offer deprecation: The entire VM offer, including all plans and image versions.

Notice period (90 days before enforcement)

The publisher sets an enforcement date when deprecating an image. You typically have at least 90 days between the deprecation announcement and the enforcement date. The exact enforcement date is included in your email notification and Azure Advisor recommendation.

During the notice period:

• You receive email notifications and Azure Advisor recommendations about the upcoming deprecation.
• Existing VMs and virtual machine scale set instances continue to run normally.
• You can deploy new instances by using Azure CLI, PowerShell, or APIs.
• Deprecation warnings appear in the Azure portal, Azure CLI, and APIs.
• You can migrate or update your deployments until the enforcement date.

After enforcement date (soft delete)

After the enforcement date, the image enters a "soft delete" state. The image is no longer available for new deployments, but existing resources aren't deleted or modified.

Images without a purchase plan (for example, Windows Server, Canonical Ubuntu, Red Hat, SUSE):

• Existing VMs and virtual machine scale set instances continue to run without disruption.
• Start, stop, restart, deallocate, and redeploy continue to work.
• VM backup and restore operations continue to work, including restoring a backup to create a new VM.
• Azure Site Recovery and disaster recovery operations continue to work.
• New VM creation from the deprecated image is blocked.
• Reimage is blocked because it requires recreating the OS disk from the source image.
• Virtual machine scale set scale-out is blocked if new instances must be created from the deprecated version. Scale-out with automatic OS upgrade or "latest" version continues to work.

Images with a purchase plan (third-party Marketplace images such as CIS, F5, Cisco):

• Existing VMs and virtual machine scale set instances continue to run without disruption.
• Start, stop, restart, deallocate, and redeploy continue to work.
• New VM creation from the deprecated image is blocked.
• Backup restore operations that require Marketplace purchase validation might fail.
• Reimage is blocked because purchase plan eligibility checks fail after deprecation.
• Virtual machine scale set scale-out is blocked because it requires creating new instances from the deprecated image.

For more details, see Which operations are affected by image deprecation?.

Required actions

The actions you need to take depend on whether your image requires a purchase plan. For help determining this, see How do I check if my image has a purchase plan?. For detailed migration guidance, see When should I migrate?.

Images without a purchase plan:

• If you use automatic OS upgrades, no action is needed. Automatic OS upgrade handles migration across publisher, offer, SKU, and version changes automatically.
• If you need your virtual machine scale set to scale out after deprecation, migrate to a supported image before the enforcement date.
• To avoid future dependency on Marketplace image availability, consider capturing your workload as a custom image in Azure Compute Gallery. Custom images aren't subject to Marketplace deprecation.

Images with a purchase plan:

• Automatic OS upgrade handles only individual version deprecation. For plan, SKU, or offer deprecation, you must migrate manually.
• Migrate your virtual machine scale set to a supported image before the enforcement date to avoid disruption to scale-out, reimage, and backup restore operations.

The impact of deprecation depends on whether the image requires a Marketplace purchase plan.

Operations that continue to work after deprecation (no migration required)

These behaviors apply to images that don't require a purchase plan (for example, Windows Server, Canonical Ubuntu, Red Hat, SUSE):

Operation	Status after enforcement	Explanation
Running VMs	Continue operating normally	After creation, VMs boot from their OS disk—not from the Marketplace image—and no purchase plan validation is required.
Start / Stop / Restart / Redeploy	Continue working	These operations don't require the source image.
VM backup and restore	Continue working	Restoring a backup, including restoring to create a new VM, continues to work.
Azure Site Recovery and disaster recovery	Continue working	Recovery operations continue to work for Microsoft-endorsed images.
VMSS existing instances	Continue running	Existing instances aren't affected by deprecation.
VMSS scale-out	Blocked only if new instances must be created from the deprecated version	Scale-out with automatic OS upgrade or "latest" version continues to work.

Operations that are blocked after deprecation

Operation	Applies to	Status after enforcement	Explanation
Creating new VMs	All images	Blocked	New VM creation from the deprecated image is blocked regardless of purchase plan status.
Reimage	All images	Blocked	Reimage fails because it requires recreating the OS disk from the deprecated source image.
Restoring backups	Images with a purchase plan	Might fail	Backup restore operations that require Marketplace purchase validation might fail. Restore continues to work for images without a purchase plan.
VMSS scale-out	Images with a purchase plan	Blocked	Scale-out is blocked for images with a purchase plan. For images without a purchase plan, scale-out with automatic OS upgrade or "latest" version continues to work.

Note

The VM's image reference property might disappear from the Azure portal, but this doesn't affect VM operation. The OS disk is authoritative for boot.

The deprecation impact depends on whether your image requires a Marketplace purchase plan. Use one of the following methods to check.

Option 1: Use Azure CLI

Check the Marketplace image directly:

az vm image show --location eastus --urn <publisher>:<offer>:<sku>:<version> --query plan

Or check an existing VM:

az vm show --resource-group <resource-group> --name <vm-name> --query plan

Option 2: Use PowerShell

Check from an existing VM:

(Get-AzVM -ResourceGroupName <resource-group> -Name <vm-name>).Plan

Check from a Marketplace image:

Get-AzVMImage -Location "eastus" -PublisherName <publisher> -Offer <offer> -Skus <sku> -Version <version> | Select-Object -ExpandProperty PurchasePlan

Interpreting the results

• If the command returns null or empty output, the image doesn't have a purchase plan. Deprecation has minimal impact on your workloads.
• If the command returns name, publisher, and product values, the image has a purchase plan. You should migrate to a supported image before the enforcement date.

For more information, see Supply Azure Marketplace purchase plan information when creating images.

Yes—if your image doesn't require a purchase plan.

• For Microsoft first-party and endorsed Linux images (for example, Windows Server, Canonical Ubuntu, Red Hat, SUSE), restoring a backup—even to create a new VM—is supported after deprecation. This is expected behavior.
• For third-party images that require a purchase plan, restore behavior might be blocked after deprecation because of Marketplace enforcement checks.

If you're using an image that requires a purchase plan, migrate to a supported image before the enforcement date. For more information, see purchase plan information.

Migration isn't always required. Review the following scenarios to determine whether you need to take action.

Migration is not required if:

• Your image doesn't require a purchase plan, even if it's deprecated.
• You're using automatic OS image upgrades for VMSS and only the image version is deprecated.
• You aren't performing reimage or scale-out operations that require the original Marketplace image.

Migration is required if:

• Your image requires a purchase plan.
• You need to scale out, reimage, or create new workloads after the enforcement date.
• The entire offer or SKU is deprecated, your image requires a purchase plan, and automatic OS image upgrade can't handle the migration.

Recommended actions

Images without a purchase plan:

• Don't panic when you receive a deprecation notice. Deprecation doesn't imply immediate disruption for first-party images.
• Existing workloads, backup restore, and disaster recovery scenarios continue to work after deprecation. No migration is required for these operations.
• To avoid future dependency on Marketplace image availability, consider capturing your workload as a custom image in Azure Compute Gallery. Custom images aren't subject to Marketplace deprecation.

Images with a purchase plan:

• Coordinate migration with the publisher before the enforcement date. Backup restore, reimage, and scale-out operations might fail after deprecation.
• Custom images that include purchase plan information are still subject to Marketplace enforcement checks. Migrate to a newer, non-deprecated image to avoid disruption.

All images:

• Review which VMs and virtual machine scale sets use the deprecated image. See How do I find VMs using deprecated images? and How do I find virtual machine scale sets using deprecated images?.

Option 1: Use automated script (recommended)

Run Get-AzVMImageDeprecationStatus.ps1 to list all VMs in a subscription that were created from deprecated or soon-to-be-deprecated images.

Option 2: Use Azure Resource Graph

Run the following query in Azure Resource Graph to list all VMs and their image details:

resources 
| where type == "microsoft.compute/virtualmachines" 
//| where properties.storageProfile.imageReference.publisher =~ 'MicrosoftWindowsServer' //Optional: Filter by publisher
//| where properties.storageProfile.imageReference.sku =~ '2016-Datacenter' //Optional: Filter by SKU (Plan)
//| where properties.storageProfile.imageReference.version == '14393.4467.2106061537' //Optional: Filter by version
| project name, subscriptionId, resourceGroup, ImagePublisher=properties.storageProfile.imageReference.publisher, ImageOffer=properties.storageProfile.imageReference.offer, imageSku=properties.storageProfile.imageReference.sku, imageVersion=properties.storageProfile.imageReference.exactVersion

Option 3: Use Azure CLI

To list all VMs using a specific SKU (replace 2016-Datacenter with your deprecated SKU):

az vm list --query "[?storageProfile.imageReference.sku=='2016-Datacenter'].{VM:id, imageOffer:storageProfile.imageReference.offer, imagePublisher:StorageProfile.imageReference.publisher, imageSku: storageProfile.imageReference.sku, imageVersion:storageProfile.imageReference.version}"

To list all VMs using a specific image version (replace with your deprecated version):

az vm list --query "[?storageProfile.imageReference.version=='14393.4402.2105052108'].{VM:id, imageOffer:storageProfile.imageReference.offer, imagePublisher:StorageProfile.imageReference.publisher, imageSku: storageProfile.imageReference.sku, imageVersion:storageProfile.imageReference.version}"

Option 4: Use PowerShell

To list all VMs using a specific SKU (replace 2016-Datacenter with your deprecated SKU):

Get-AzVM | Where-Object {$_.StorageProfile.ImageReference.Sku -eq '2016-Datacenter'} | Select-Object -Property ResourceGroupName, Name, @{label='imageOffer'; expression={$_.StorageProfile.ImageReference.Offer}}, @{label='imagePublisher'; expression={$_.StorageProfile.ImageReference.Publisher}}, @{label='imageSKU'; expression={$_.StorageProfile.ImageReference.Sku}}, @{label='imageVersion'; expression={$_.StorageProfile.ImageReference.ExactVersion}}

To list all VMs using a specific image version (replace with your deprecated version):

Get-AzVM | Where-Object {$_.StorageProfile.ImageReference.ExactVersion -eq '14393.4402.2105052108'} | Select-Object -Property ResourceGroupName, Name, @{label='imageOffer'; expression={$_.StorageProfile.ImageReference.Offer}}, @{label='imagePublisher'; expression={$_.StorageProfile.ImageReference.Publisher}}, @{label='imageSKU'; expression={$_.StorageProfile.ImageReference.Sku}}, @{label='imageVersion'; expression={$_.StorageProfile.ImageReference.ExactVersion}}

Option 1: Use automated script (recommended)

Run Get-AzVMImageDeprecationStatus.ps1 to list all virtual machine scale sets in a subscription that were created from deprecated or soon-to-be-deprecated images.

Option 2: Use Azure Resource Graph

Run the following query in Azure Resource Graph to list all virtual machine scale sets and their image details:

resources 
| where type == "microsoft.compute/virtualmachinescalesets" 
//| where properties.virtualMachineProfile.storageProfile.imageReference.publisher =~ 'MicrosoftWindowsServer' //Optional: Filter by publisher
//| where properties.virtualMachineProfile.storageProfile.imageReference.sku =~ '2016-Datacenter' //Optional: Filter by SKU (Plan)
//| where properties.virtualMachineProfile.storageProfile.imageReference.version == '14393.4467.2106061537' //Optional: Filter by version
//| where properties.virtualMachineProfile.storageProfile.imageReference.version != "latest" //Optional: Exclude scale sets using "latest"
| project name, subscriptionId, resourceGroup, ImagePublisher=properties.virtualMachineProfile.storageProfile.imageReference.publisher, ImageOffer=properties.virtualMachineProfile.storageProfile.imageReference.offer, imageSku=properties.virtualMachineProfile.storageProfile.imageReference.sku, imageVersion=properties.virtualMachineProfile.storageProfile.imageReference.version

Option 3: Use Azure CLI

To list all virtual machine scale sets using a specific SKU (replace 2016-Datacenter with your deprecated SKU):

az vmss list --query "[?virtualMachineProfile.storageProfile.imageReference.sku=='2016-Datacenter'].{VMSS:id, imageOffer:virtualMachineProfile.storageProfile.imageReference.offer, imagePublisher:virtualMachineProfile.storageProfile.imageReference.publisher, imageSku:virtualMachineProfile.storageProfile.imageReference.sku, imageVersion:virtualMachineProfile.storageProfile.imageReference.version}"

To list all virtual machine scale sets using a specific image version (replace with your deprecated version):

az vmss list --query "[?virtualMachineProfile.storageProfile.imageReference.version=='14393.4402.2105052108'].{VMSS:id, imageOffer:virtualMachineProfile.storageProfile.imageReference.offer, imagePublisher:virtualMachineProfile.storageProfile.imageReference.publisher, imageSku:virtualMachineProfile.storageProfile.imageReference.sku, imageVersion:virtualMachineProfile.storageProfile.imageReference.version}"

Option 4: Use PowerShell

To find virtual machine scale sets using a specific SKU (replace 2016-Datacenter with your deprecated SKU):

$vmsslist = Get-AzVmss
$vmsslist | Where-Object {$_.virtualMachineProfile.storageProfile.imageReference.Sku -eq '2016-Datacenter'} | Select-Object -Property ResourceGroupName, Name, @{label='imageOffer'; expression={$_.virtualMachineProfile.storageProfile.imageReference.Offer}}, @{label='imagePublisher'; expression={$_.virtualMachineProfile.storageProfile.imageReference.Publisher}}, @{label='imageSKU'; expression={$_.virtualMachineProfile.storageProfile.imageReference.Sku}}, @{label='imageVersion'; expression={$_.virtualMachineProfile.storageProfile.imageReference.Version}}

To find virtual machine scale sets using a specific image version (replace with your deprecated version):

$vmsslist = Get-AzVmss
$vmsslist | Where-Object {$_.virtualMachineProfile.storageProfile.imageReference.Version -eq '14393.4402.2105052108'} | Select-Object -Property ResourceGroupName, Name, @{label='imageOffer'; expression={$_.virtualMachineProfile.storageProfile.imageReference.Offer}}, @{label='imagePublisher'; expression={$_.virtualMachineProfile.storageProfile.imageReference.Publisher}}, @{label='imageSKU'; expression={$_.virtualMachineProfile.storageProfile.imageReference.Sku}}, @{label='imageVersion'; expression={$_.virtualMachineProfile.storageProfile.imageReference.Version}}

Azure VMs don't support in-place OS upgrades. Create a new VM with a supported image, migrate your data, and decommission the old VM.

Important

For deprecated images that require a Marketplace purchase plan, you can't create new VMs or perform backup restore operations after the enforcement date. Migrate before the enforcement date.

Part 1: Create a new VM

1. Identify the replacement image: Check your deprecation email for the recommended replacement. For more information, see Find and use images using the Azure CLI or Find and use images using Azure PowerShell.

2. Configure the new VM: Match the region and networking settings of your existing VM for the simplest migration. You can change VM size or region if needed.

3. Deploy and test: Confirm the VM starts correctly and your application dependencies are present.

Part 2: Migrate data

Method A: Detach and attach data disks (recommended)

If your workload data is stored on data disks (not the OS disk):

1. Stop and deallocate the old VM.
2. Detach the data disks from the old VM. For more information, see Detach a data disk from a Linux VM or Detach a data disk from a Windows VM.
3. Attach the data disks to the new VM. For more information, see Attach a data disk to a Linux VM or Attach a data disk to a Windows VM.
4. Start the new VM and verify data accessibility.

Note

Data on the OS disk isn't preserved with this method. Only data on attached data disks is migrated.

Method B: Use snapshots (for OS disk data or backup requirements)

If you need to preserve OS disk data or create a backup before migration:

1. Create a snapshot of the data disks.
2. Create managed disks from the snapshots.
3. Attach the disks to the new VM. For more information, see Attach a data disk to a Linux VM or Attach a data disk to a Windows VM.

Method C: Use file-based transfer

Use OS transfer tools for selective data migration:

• Windows: Robocopy or SMB share
• Linux: rsync, scp, or sftp
• Cross-OS: AzCopy with Azure Storage as an intermediate location

Part 3: Switch over

1. Validate: Verify network connectivity, application functionality, firewall rules, and extensions.
2. Update references: Point DNS names, load balancers, or API endpoints to the new VM.
3. Decommission: Keep the old VM briefly for rollback, then deallocate and delete it.

The migration approach depends on whether an image version, plan/SKU, or entire offer is deprecated.

Note

If your image doesn't have a purchase plan and you have automatic OS image upgrade enabled, automatic OS upgrade handles migration automatically for all deprecation levels (version, plan/SKU, and offer), including changes to publisher, offer, SKU, and version. The manual steps in each section below apply only to images with a purchase plan or scale sets without automatic OS upgrade enabled.

Version deprecation

If only a specific image version is deprecated:

• Using "latest" version: No action required for new instances. Azure resolves to the newest available version at deployment time. Existing instances remain on their original version.
• Using automatic OS upgrades: No action required. Azure upgrades existing instances to the latest version automatically, regardless of whether your image reference uses "latest" or a pinned version. This applies to all images, including those with a purchase plan.
• Using a pinned version without automatic OS upgrades: Update the image reference to a supported version. See Modify an Azure virtual machine scale set. After updating the model, upgrade existing instances using one of these methods:
  • Manual upgrade: Use az vmss update-instances (CLI) or Update-AzVmssInstance (PowerShell) to upgrade specific instances.
  • Rolling upgrade policy: Configure the upgrade policy to "Rolling" so instances automatically upgrade when the model changes.

Tip

Enable automatic OS image upgrade to avoid manual intervention for future deprecations.

Plan/SKU deprecation

If an entire plan or SKU is deprecated:

• Images without a purchase plan and automatic OS upgrade enabled: No action required. Automatic OS upgrade migrates your scale set to the replacement SKU automatically.
• Images with a purchase plan, or automatic OS upgrade not enabled: Update to a different SKU from the same offer using a scale-out/scale-in approach:

1. Find an alternative SKU from your deprecation email. For more information, see Find and use images using the Azure CLI or Find and use images using Azure PowerShell.

2. Update the VMSS model to use the new SKU:

   az vmss update --resource-group <resource-group> --name <vmss-name> \
     --set virtualMachineProfile.storageProfile.imageReference.sku=<new-sku> \
     --set virtualMachineProfile.storageProfile.imageReference.version=latest
   

3. Scale out to create new instances using the updated image, then scale in to remove old instances. Or delete specific old instances and let the scale set replace them with new ones.

Important

Upgrading or reimaging existing instances replaces their OS disks. Use scale-out/scale-in to avoid data loss on OS disks.

Offer deprecation

If an entire offer is deprecated:

• Images without a purchase plan and automatic OS upgrade enabled: No action required. Automatic OS upgrade migrates your scale set to the replacement offer automatically, even if the publisher, offer, or SKU changes.
• Images with a purchase plan, or automatic OS upgrade not enabled: Create a new virtual machine scale set with a supported image:

1. Find a replacement offer from your deprecation email or search in the Azure Marketplace.

2. Create a new virtual machine scale set using the replacement image. Match your existing configuration (networking, extensions, scaling rules).

3. Test application compatibility thoroughly. A different publisher or offer may have significant OS or configuration differences.

4. Migrate traffic to the new scale set, then delete the old one.

Note

We recommend that you create a new VMSS instead of doing in-place updates when you change publishers or offers, because the differences between images are typically significant.

Azure notifies you about image deprecation through two channels:

• Email notifications: Sent directly to subscription administrators with the Owner or Account Admin role on the subscription.
• Azure Advisor recommendations: Deprecation recommendations appear in Azure Advisor.

Notify additional recipients

To notify team members who don't have Owner or Account Admin roles on the subscription, create an Advisor alert with an action group. Use action groups to specify email addresses, SMS numbers, or webhooks that receive notifications when new deprecation recommendations are published.

Option 1: Use Azure CLI

az vm image show --location eastus --urn MicrosoftWindowsServer:WindowsServer:2016-Datacenter:14393.4169.2101090332 --query [imageDeprecationStatus]

Option 2: Use PowerShell

To check a single image version:

Get-AzVMImage -Location "eastus" -PublisherName "MicrosoftWindowsServer" -Offer "WindowsServer" -Skus "2016-Datacenter" -Version "14393.4169.2101090332" | Select-Object -ExpandProperty "ImageDeprecationStatus"

To check all versions of a SKU with deprecation details:

Get-AzVMImage -Location "westus" `
  -PublisherName "center-for-internet-security-inc" `
  -Offer "cis-rocky" `
  -Skus "cis-rockylinux-9-l1-gen2-azure-observability" `
  -Expand "properties/imageDeprecationStatus" |
  Select-Object Version, @{
    Name = "DeprecationDetails"
    Expression = { $_.ImageDeprecationStatus | Out-String }
  } | Format-Table -Wrap -AutoSize

Option 3: Use REST API

Use the Virtual Machine Images - Get API. If the image is deprecated, you receive a response like:

{
  "error": {
    "code": "ImageVersionDeprecated",
    "message": "VM Image from publisher: MicrosoftWindowsServer with - Offer: WindowsServer, Sku: 2016-Datacenter, Version: 14393.4169.2101090332 is deprecated."
  }
}

Option 4: Use automated script

Run Get-AzVMImageDeprecationStatus.ps1 in Cloud Shell or locally to check all VMs and virtual machine scale sets in a subscription for deprecated images.

Active images are images that aren't scheduled for deprecation or already deprecated.

Option 1: Use Azure CLI

az vm image list --location eastus --publisher "MicrosoftWindowsServer" --offer "WindowsServer" --sku "2022-Datacenter" --all --query "[?imageDeprecationStatus.imageState=='Active']"

Option 2: Use PowerShell

Get-AzVMImage -Location "westus" `
  -PublisherName "center-for-internet-security-inc" `
  -Offer "cis-rocky" `
  -Skus "cis-rockylinux-9-l1-gen2-azure-observability" `
  -Expand "properties/imageDeprecationStatus" |
  Where-Object { $_.ImageDeprecationStatus.ImageState -eq "Active" } |
  Select-Object Version

Your SQL Server remains unaffected when a SQL Server Azure Marketplace image is deprecated:

• Your Azure VM continues to run without interruption.
• Your SQL Server instance continues to function normally.
• You can't deploy new VMs using the deprecated SQL Server image.

Existing deployments require no action.