Azure Retiring Resources

As Azure grows and resources continue to improve, Microsoft will continuously retire old and outdated resources. Any resources not migrated by the retirement date may stop working as Microsoft shuts down the endpoints on which they run. Below is a list of all resources that will be retired within the next six months.

Date	Retiring Resource	Feature/Version	New Resource	Migration Plan
2025-03-01	Speech	Conversation Transcription Multichannel Audio Diarization	Speech to Text Enhanced Add-on	Transition
2025-03-01	Azure Resource Manager	TLS 1.0/1.1	TLS 1.2	Update
2025-03-01	Availability Tests	TLS 1.0/1.1	TLS 1.2	Update
2025-03-03	Azure Kubernetes	HTTP application routing add-on	Web application routing add-on	Migrate
2025-03-14	Azure Machine Learning	Explanation and Fairness Dashboard	Responsible AI Dashboard	Transition
2025-03-15	Redis Enterprise	Every-write AOF	Every-second AOF	Transition
2025-03-15	Application Insights	Instrumentation key–based ingestion	Connection string–based ingestion	Update
2025-03-31	API Management	Git Repository	APIOps	Migrate
2025-03-31	Azure Computer Vision	Spatial Analysis Edge container	Azure AI Video Indexer	Transition
2025-03-31	Azure Maps	Feature State Services	Azure Maps Creator Custom Styling	MIgrate
2025-03-31	Azure Container Registry	Helm repositories	OCI Artifacts	Transition
2025-03-31	Azure Functions	Service Bus Extension v4	Service Bus Extension v5	MIgrate
2025-03-31	Visual Studio App Center	Entire Service	N/A	Find Alternative
2025-03-31	Cost Management	Connector for AWS	N/A	Find Alternative
2025-03-31	Azure Maps	Native SDK for Android & IOS	Azure Maps Web SDK	Migrate
2025-03-31	Azure SQL	Connector v1 actions and triggers	Connector v2 actions and triggers	Transition
2025-03-31	App Service	Platform Enabled DR for App Service Web Apps	Implement managed DR plan	Update\Upgrade
2025-03-31	Container Insights	Container Monitoring solution	Azure Monitor container insights	Transition
2025-03-31	Azure Database for PostgreSQL	Azure Database for PostgreSQL Single Server	Azure Database for PostgreSQL Flexible Server	Migrate
2025-03-31	Azure Synapse	Azure Synapse Runtime for Apache Spark 3.3	Azure Synapse Runtime for Apache Spark 3.4	Upgrade
2025-03-31	Cognitive Services	QnA Maker	Custom Question Answering	Migrate
2025-03-31	HDInsight	4.0/5.0	5.1	Migrate
2025-03-31	Virtual Machines	Standard_NC24rs_v3	NC24ads_A100_v4 (or similar)	Resize
2025-03-31	Azure Spring Apps	Standard consumption and dedicated plan (preview)	Azure Container Apps	Migrate
2025-03-31	Azure Portal	Public preview templates	Template Specs	Convert
2025-04-23	Azure Batch	Ubuntu 20.04	Ubuntu 22.04 or later	Migrate
2025-04-30	App Service	Node 18	Node 20	Upgrade
2025-05-01	Application Insights	TLS 1.0/1.1	TLS 1.2	Update
2025-05-24	Azure Arc-enabled Kubernetes	Flux v1	Flux v2	MIgrate
2025-06-30	SAP HANA Large Instances (HLIs)	Entire Service	Azure Virtual Machines	Migrate
2025-08-31	Application Gateway	TLS 1.0/1.1	TLS 1.2	Update
2025-08-31	Azure SQL DB	TLS 1.0/1.1	TLS 1.2	Update
2025-08-31	Azure IoT Hub	TLS 1.0/1.1	TLS 1.2	Update
2025-08-31	Azure SQL Managed Instance	TLS 1.0/1.1	TLS 1.2	Update

**Updated 3/9/2025**

There are several ways to determine if your environment is running these retiring resources.

Email

Microsoft will send out emails regularly with information about resources in your tenant that are being retired. It will include a list of resources affected, information about what is being retired, and a plan to transition to the latest version of each resource.

Portal

When accessing resources in the portal, Microsoft will show a notification on any resource that is being retired. It may include a link to documentation on transitioning to the latest version and a link to do a step-by-step migration using their wizard.

Azure Advisor

Azure provides a resource called Advisor, which contains a Workbook that compiles a list of all resources announced as retiring. To access this, log into the portal and go to Advisor. On the left panel, select Workbooks. Choose the Service Retirement (Preview) from the list by clicking on it. Here, you can see a list of all resources being retired and any affected resources in your tenant. You can edit and save the Workbook and pin it to a Dashboard for easy access.

CLI

Either Azure CLI or PowerShell can be used to search for resources programmatically.  In the below example, the Azure CLI can be used to find all Classic resources. 

# Define the tenant ID
$tenantId = "XXXXXXXXXXX"

# Connect to Azure with the specific tenant
az login --tenant $tenantId

# Get all subscriptions in the specified tenant
$subscriptions = az account list --query "[?tenantId=='$tenantId'].{id:id, name:name}" --output json | ConvertFrom-Json

# Initialize array to hold all classic resources across all subscriptions
$allClassicResources = @()

# Loop through each subscription
foreach ($subscription in $subscriptions) {
    Write-Output "Processing subscription: $($subscription.name)"

    # Set the current subscription context
    az account set --subscription $subscription.id

    # List classic resources in the current subscription
    $classicResources = az resource list --query "[?contains(type, 'Classic')]" --output json | ConvertFrom-Json

    # Add subscription ID and name to each resource for context
    foreach ($resource in $classicResources) {
        $resource | Add-Member -MemberType NoteProperty -Name SubscriptionId -Value $subscription.id
        $resource | Add-Member -MemberType NoteProperty -Name SubscriptionName -Value $subscription.name
        $allClassicResources += $resource
    }
}

# Display the classic resources
if ($allClassicResources.Count -eq 0) {
    Write-Output "No classic resources found across all subscriptions."
} else {
    Write-Output "Classic resources found across all subscriptions:"
    $allClassicResources | ForEach-Object {
        Write-Output "Subscription: $($_.SubscriptionName) ($($_.SubscriptionId))"
        Write-Output "Name: $($_.name)"
        Write-Output "Type: $($_.type)"
        Write-Output "Resource Group: $($_.resourceGroup)"
        Write-Output "Location: $($_.location)"
        Write-Output "---------------------------"
    }
}

For more information or any questions, please contact us.