Hello Sankararao Gulipalli
Thanks for reaching out. The retirement email is sent to every Azure subscription that is currently associated with a Blueprint definition, version, or assignment either at the subscription scope or at any management group scope above the subscription. So receiving the notice does not necessarily mean your subscription owns a blueprint — it usually means a blueprint exists somewhere in the hierarchy that touches it.
There are a few common reasons you don't see any impacted resource when you click through Service Health:
- The Blueprint is defined at the Management Group level, not at your subscription
Blueprint definitions can be created at a management group and then assigned to one or many child subscriptions. The Service Health blade shows the impacted subscription, but the definition/assignment object itself may live at the MG. As a Subscription Owner only, you won't see MG-scoped objects unless you also have read access (e.g., Reader/Contributor) on the parent management group.
- Permissions on the Blueprints resource provider
Viewing Blueprint definitions and assignments requires permissions on Microsoft.Blueprint/*. Subscription Owner covers subscription-scoped blueprints, but not blueprints defined at a higher management group. Ask your tenant/MG admin to check at the MG scope.
- The Service Health "impacted resources" view is informational
The Health Advisory is broadcast based on the back-end inventory of Blueprint objects associated with the subscription ID; the portal's impacted resources tile is not always populated for governance services like Blueprints. The authoritative places to check are the Azure Blueprints blade and Azure Advisor, both of which surface a recommendation listing exactly where Blueprints is in use.
- Resources previously deployed by a Blueprint
Even if the blueprint assignment was deleted, resources it created remain in the subscription and may still carry Blueprint Locks (Deny Assignments). The notice covers these as well, because those Deny Assignments will be removed at retirement on 31 January 2027.
How to confirm whether Blueprints actually exists in your scope:
Run these checks (you'll need at least Reader at the MG level for #2):
A. Azure Portal
- Go to Azure portal → Blueprints → check both Blueprint definitions and Assigned blueprints tabs (switch the scope selector to your subscription and to each parent management group).
- Go to Advisor → Operational excellence → look for the Migrate from Azure Blueprints recommendation; it lists every subscription/MG where Blueprints is in use.
B. Azure PowerShell (Az.Blueprint module)
Install-Module -Name Az.Blueprint
# At subscription scope
Get-AzBlueprint -SubscriptionId <your-sub-id>
Get-AzBlueprintAssignment -SubscriptionId <your-sub-id>
# At management group scope (run for each parent MG)
Get-AzBlueprint -ManagementGroupId <mg-id>
turn1search1
C. REST API
GET https://management.azure.com/subscriptions/{subId}/providers/Microsoft.Blueprint/blueprintAssignments?api-version=2018-11-01-preview
If all of the above return empty for your subscription and every parent MG, then the email is effectively informational for you and no migration action is required from your side the notification is sent at subscription granularity and sometimes catches subscriptions whose only association was a now-removed assignment.
- If anything is found, export the blueprint definition/assignment before 31 January 2027 (after that date, unexported objects are permanently deleted).
- Plan migration to Azure Deployment Stacks (recommended) or Template Specs.
- Reference docs: Azure Blueprints retirement and Retirement FAQ.
Hope this clarifies it. Mark it as Answer/Upvote if it helps so others with the same question can find it.
Thank you.