An Azure service that is used to provision Windows and Linux virtual machines.
To confirm whether anything active still needs action, check across all subscriptions and directories, not just the one currently open in the portal.
- Verify the correct directory and subscription
- In Azure portal, open Directories + subscriptions.
- Confirm whether the email might refer to a different tenant or subscription than the one currently selected.
- Retirement notifications are generated at the subscription level and might not match the subscription currently being viewed.
- Check for active retirement recommendations
- In Azure portal, go to Advisor → Recommendations.
- Look for VM retirement-related recommendations.
- If nothing appears, that is a strong sign there are no currently impacted active VMs in the selected scope.
- Check health advisories
- In Azure portal, go to Service Health → Health advisories.
- Review whether the notice is tied to any specific impacted resources.
- Search all subscriptions for VMs
- Use Resource Graph Explorer in Azure portal to search across all subscriptions available to the signed-in account.
- This is the recommended way to confirm whether any VMs still exist, including stopped or deallocated ones.
- If no VMs are returned, there are no virtual machines across the subscriptions accessible to that account.
- Review past VM activity if needed
- In Activity Log, filter for Delete Virtual Machine.
- This helps confirm whether VMs existed previously and were already removed.
- If the email refers to an old or unfamiliar tenant
- In Azure portal, sign in and review the list of directories associated with the account.
- Match the tenant mentioned in the email against the directories shown.
- If it was an old trial, test, or backup-related tenant that is no longer needed, it may simply be an inactive tenant.
- If no active resources are found
- If Advisor, Service Health, Resource Graph Explorer, and Activity Log do not show impacted resources, the notification can be treated as informational and no VM migration action is required.
If support is needed for a VM that is still present and affected by retirement, create a support request in Azure portal with:
- Issue type: Technical
- Service: My services
- Service type: Virtual Machine running Windows/Linux
- Resource: the affected VM
- Problem type: Assistance with resizing my VM