New GPv1 account creation blocked
New-account blocking is a platform boundary, not proof that the pasted estate has been inventoried.
Local processing: pasted text stays in this tab and is not persisted by the site.
Measurement: Cloudflare Web Analytics may provide page-level metrics after deployment. This source sends no product events or pasted evidence.
Upgrade plan
GPv2 readiness inventory
Run the planner to create a bounded readiness table.
No result yet.
The table will appear here after local analysis.
Sensitive evidence detected
Redact the flagged value and rerun before sharing any result.
| Account or resource | Detected kind | Retirement exposure | Upgrade action | Access-tier decision | Transaction and operation clues | Replication and egress clues | Missing Monitor metrics | Owner | Blocker | Exact next action and evidence boundary |
|---|
Azure Monitor evidence checklist
Missing evidence remains unknown. It is never converted into a zero or a safe state.
Hot or Cool decision prompts
Choose a default tier only after current operation and transfer patterns are reviewed.
Reviewed command checklist
GPv1 retirement deadline
Microsoft says GPv1 accounts must be upgraded to GPv2 by this date to avoid service disruption.
Automatic migration and billing risk
Unmigrated accounts may be migrated by Microsoft. Access-tier, operation, replication, and transfer costs still need review.
Upgrade is not reversible
GPv1 and BlobStorage accounts can move to GPv2 but cannot be downgraded after upgrade.
This static tool cannot query Azure, calculate exact future billing, change an account, prove complete coverage, certify cost safety, or confirm a successful upgrade.