Building Azure Capacity Checker: Closing the Migration-Day Gap

Disclosure: I work for Altra, the company behind Dr. Migrate. This project reads Dr. Migrate rightsizing exports, so that’s worth naming up front. The tool itself is a personal side-project — opinions, bugs, and weekend commits are my own. The problem nobody tells you about until migration day You run a rightsizing exercise. You get a lovely Excel file with 1,200 servers each mapped to a neat Azure VM SKU. Sign-off happens. Change windows go in the calendar. Migration day arrives. And then you discover that the Standard_D4s_v5 you planned for 300 servers is allocated out in your target region — or worse, not available in that region at all, or not available on your subscription tier — and the whole plan wobbles.