Azure for Students suspension: help following up existing cases and secure verification

Microsoft Q&A cannot access or escalate private support cases, so continue through Azure portal → Help + support → All support requests and add a message to the open November 12 case requesting review, secure verification instructions, and a decision on preservation or export before December 11, 2026.

Follow up through the existing case

1. Sign in with the account used to create the request.
2. Open Help + support → All support requests.
3. Adjust the date/status filters if the request is not initially visible.
4. Select the November 12 request, choose New message, enter the follow-up, and select Submit. This is the official documented channel for adding details to an open Azure case.^1^
5. Include:
   • The original case number and the new case number.
   • The displayed subscription state and scheduled deletion date.
   • A request for confirmation that the new case has been routed to the Subscription/Account Review or security team.
   • A request for the exact verification evidence still required.
   • A request for a Secure File Exchange workspace if sensitive documents are needed.
   • A request to confirm whether deletion can be held while review is pending.
   • If reactivation is denied, a request for temporary controlled access or an engineer-approved export procedure for each named resource type.

A concise message could be:

Please associate this request with case [original case number]. The subscription is disabled for suspicious activity and shows scheduled deletion on December 11, 2026. Please confirm whether further Account Review is available and specify the outstanding verification requirements. If sensitive evidence is required, please provide a case-specific Secure File Exchange link. Please also confirm whether deletion can be placed on hold while this request is open. If reactivation is unavailable, please determine whether temporary controlled access or a supported export can be authorized for the listed resources.

Do not post either case number, subscription identifiers, identity documents, or account details publicly in Q&A.

Secure verification channel

For ordinary correspondence, use New message inside the support request. The case also offers Upload file, but Microsoft advises against including personal information in ordinary case uploads. After case creation, up to five files can be uploaded, subject to the documented file-size and extension restrictions.^1^

For sensitive verification material, ask the assigned support professional to create a Secure File Exchange workspace. Microsoft sends its case-specific link by email; it should not be shared. Access is restricted to accounts associated with the case and Microsoft support professionals actively working on it.^2^

Secure File Exchange is therefore not a workspace that can be created independently—the assigned support professional must provide the link. Verify that any invitation corresponds to the existing case before uploading documents.

Deletion hold and export limitations

The available public documentation does not describe a self-service control that pauses scheduled deletion for a suspicious-activity suspension. Ask support to confirm a hold explicitly; do not assume that an open request automatically changes the displayed deletion date.

While a subscription is Disabled:

• Resources cannot be created or updated.
• Action operations are disabled.
• Resources can generally still be retrieved or deleted through GET and DELETE.
• Storage is read-only, virtual machines are deallocated, and other services are disabled.
• Subscription ownership cannot be transferred.^3^

Consequently, an export may be possible only where the specific service supports a read-only download using operations still permitted in the disabled state. Exports that require starting a job, creating a destination, changing configuration, or transferring the subscription are likely blocked by the disabled-state operational restrictions. Microsoft documents product-specific portal, API, and PowerShell export mechanisms, but not a universal Azure-subscription export.^4^

In the case message, list each resource precisely—for example, storage accounts and containers, managed disks, databases, Key Vaults, or App Service content—and ask support to state which service-specific retrieval method remains authorized. Do not delete resources while the preservation/export request is being evaluated.

If the case cannot be managed

Managing a subscription-linked request requires Owner, Contributor, or Support Request Contributor at subscription scope. A request created without a subscription requires an administrator role.^1^

If the request disappears because it was closed, use Reopen request when that option remains available. If it is no longer visible or cannot be reopened, Microsoft’s documented fallback is another support request specifically explaining the problem managing the original request.^1^ Billing and subscription-management support is available to Azure customers without a paid technical support plan.^5^

References

1. Manage an Azure support request
2. How to securely transfer files to Microsoft Support
3. Azure subscription states
4. Exporting customer data and enabling cloud choice
5. Microsoft Azure Support Ticket | Microsoft Azure