Microsoft for Startups (Founders Hub) sponsorship credits not applying to running subscription — Invoices overdue & Support ticket pending

Submit a Microsoft for Startups Program Support request specifically for an entitlement transfer and refund/credit-adjustment investigation, while treating payment of the overdue balance as the only documented way to guarantee protection from nonpayment suspension during the review.

1. Escalate through the correct support channel

Microsoft for Startups Program Support owns incorrect sponsorship offer types, entitlement transfers, and coordination of program-related refund investigations with central billing teams.^1^

In the Azure portal:

1. Open Program Overview.
2. Under Your Microsoft Team, select Get program support.
3. Reference the existing Azure billing case rather than opening duplicate billing cases.
4. Request these actions explicitly:
   • Entitlement transfer: Move the Founders Hub sponsorship entitlement to the account containing the production Pay-As-You-Go subscription, or migrate that subscription to the account holding the credits.
   • Refund/adjustment investigation: Review the specified invoices for a discretionary program-related adjustment.
   • Billing hold or continuity guidance: Ask whether Billing Operations can place an approved hold on collection or disablement while the review is pending.
   • Urgent escalation: State that the subscription hosts a production VM and AI services and is already receiving overdue notices.

Attach the Founders Hub approval, sponsorship activation and balance evidence, invoice dates and usage periods, both subscription offer types, and the existing case number. Do not post full subscription IDs, invoices, or case identifiers publicly.

A waiver is not automatic or guaranteed. Startup credits apply to the sponsorship entitlement and do not automatically offset usage charged to an unrelated Pay-As-You-Go subscription. Program Support can coordinate the refund investigation, but Billing Operations must decide whether an adjustment is approved.^1^

2. Keep the workload without rebuilding

There are two supported paths.

Preferred: entitlement or subscription migration

Microsoft documents that when a Pay-As-You-Go subscription is under another account, support can either move the startup credits to that account or migrate the subscription to the account containing the credits.^2^

This is not a documented self-service Sponsorship conversion. The portal’s Switch Offer feature lists specific supported destinations, and Azure Sponsorship is not among them; other offer changes require support.^3^

If support changes the offer, download invoices and usage data first. An offer switch generates an invoice for outstanding charges on the switch date, changes the billing anniversary, and resets quota increases above defaults; existing VMs continue running.^3^

Fallback: move resources to the Sponsorship subscription

Use this only if support cannot transfer the entitlement/subscription and portal validation confirms that every required resource supports a move:

1. Ensure both subscriptions are active and in the same Microsoft Entra tenant.
2. Confirm the VM, managed disks, network resources, Cognitive Services resources, and dependencies support cross-subscription moves.
3. Ensure destination quotas and resource-provider registrations are sufficient.
4. In the portal, open the source Resource group.
5. Select the resources, then Move → Move to another subscription.
6. Select the Sponsorship subscription and destination resource group.
7. Complete validation before approving the move.

Existing resources remain operational during a supported move, although the source and destination resource groups are temporarily locked against creation, deletion, or updates. Resource IDs change, so scripts, dashboards, policies, and other references must be updated; Azure role assignments do not move and must be recreated.^4^

3. Prevent service interruption

A Past Due subscription remains active initially, but it can later become warned or disabled if payment is not resolved. In the disabled state, VMs are deallocated, temporary IP addresses are released, storage becomes read-only, and other services are disabled.^5^

An open support case does not, in the published documentation, guarantee that collections or disablement will pause. If production continuity cannot tolerate that risk, settle the overdue amount and continue pursuing a refund or adjustment afterward.

First identify the billing account type:

1. Go to Cost Management + Billing.
2. If there is one billing scope, select Properties and read Type.
3. If there are multiple scopes, select Billing scopes and check Billing account type.^6^

Then use the matching route:

• Microsoft Online Subscription Program / classic Pay-As-You-Go: The Account Administrator opens Cost Management + Billing → Invoices → Settle balance, selects a payment method, and pays the outstanding amount.^6^
• Microsoft Customer Agreement: Select the overdue banner to open the invoice within the Billing Profile scope and use its payment workflow.^7^

If the subscription has already been disabled, payment-based reactivation can take up to 24 hours.^7^

References

1. Microsoft for Startups Program Support
2. Understanding Azure Usage and Billing
3. Change your Azure subscription to a different offer
4. Move Azure resources to a new resource group or subscription
5. Azure subscription states
6. Resolve a past-due balance for your pay-as-you-go Azure subscription
7. Reactivate a disabled Azure subscription