I’ve dealt with this exact scenario before—when your Azure Student Subscription gets disabled due to exceeding the free credit limit, direct resource migration is blocked by that "Can't move resources from disabled subscription" error. Here are the most reliable workarounds to get your resources over to a Pay-as-You-Go subscription:

Option 1: Export and Redeploy with ARM Templates #

This is the cleanest method for infrastructure-as-code style resources:

• Log into the Azure Portal and navigate to the resource group in your disabled Student Subscription.
• Select Export template from the left menu. Download the generated JSON template and parameter files (these capture your resource configurations).
• Switch to your active Pay-as-You-Go subscription, create a new resource group (or use an existing one).
• Go to the new resource group, select Deploy a custom template > Build your own template in the editor, then upload the template JSON you downloaded. Fill in the required parameters (like resource names, regions) and deploy.

Note: Some specialized resources (e.g., certain Azure AI services, custom VM extensions) might not export perfectly. You’ll need to manually adjust the template or reconfigure those services post-deployment.

Option 2: Request Temporary Subscription Unlock from Azure Support #

If you have complex resources that are hard to redeploy, you can ask Azure support to temporarily unlock your disabled subscription:

• In the Azure Portal, click the question mark icon in the top-right corner and select Help + support.
• Create a new support request:
  • Choose Subscription management as the issue type.
  • Explain your situation clearly: "My Azure Student Subscription was disabled after exceeding the free credit limit ($129 used / $100 allocated). I need to migrate resources to a Pay-as-You-Go subscription and request a temporary unlock to complete this process."
• Azure support typically grants a 24-48 hour unlock window to let you perform the migration.

Option 3: Manual Migration of Data and Configurations #

For resources with critical data (like storage accounts, databases), you’ll need to transfer data directly:

• Storage Accounts: Use Azure Storage Explorer to download blobs, files, or tables to your local machine, then upload them to a new storage account in your Pay-as-You-Go subscription.
• Databases: Export a backup of your SQL database (to a storage account) and restore it to a new SQL server in the target subscription.
• Web Apps: Download the publish package (from the Web App’s Deployment Center > Advanced Tools > Zip Deploy) and deploy it to a new Web App in the Pay-as-You-Go subscription.

Key Reminders #

• Always back up all data before starting any migration process to avoid accidental loss.
• After migrating, double-check resource dependencies (e.g., app service connections to databases, storage account links) to ensure everything works as expected.
• Once migration is done, delete resources from the disabled subscription to avoid any unexpected charges (though disabled subscriptions usually don’t incur fees, it’s a good practice).

内容的提问来源于stack exchange，提问作者Pan Michal