
A synchronization issue between Microsoft systems left at least one customer facing an unexpected bill after two portals showed different credit balances. A Register reader found themself on the hook for $16,000 in September after a balance that looked healthy had actually hit rock bottom and a subscription switched to pay-as-you-go. Our reader was one of many who signed up for Microsoft for Startups, a program that offers eligible businesses credits and other resources to build on Microsoft's platforms. Amazon and Google have similar deals, but our reader signed up for Microsoft's version. According to our reader, Microsoft's Founders Hub showed a healthy balance of credits remaining as their company fired up services on Azure. They shared a screenshot from portal.startups.microsoft.com that showed plenty of credits remaining. Sadly, that was not the accurate figure. In reality, those credits had been exhausted in August, and the subscription switched to a pay-as-you-go plan, causing charges to mount quickly. Worse, the notification went to a former administrator who was no longer with the company, even though the account ownership had been transferred. Since August 17, the company has run up $16,000 in charges, mostly from AI workloads routed to Azure because the portal showed that credits were still available. However, a look at a different portal - in this case, the Azure Sponsorships portal - revealed the balance was indeed zero. Our reader shared an email from a Microsoft for Startups representative explaining, "The discrepancy you are seeing in the Microsoft for Startups portal is due to an ongoing synchronization issue between backend systems." The Azure Sponsorships portal was accurate. The Microsoft for Startups portal... not so much. "Our engineering team is aware of this behavior and is actively working on a resolution," wrote the representative. Very comforting when a surprise invoice arrives days or weeks before an automatic charge is made. Even more comforting was the comment, "We do not have an estimated timeline to share for when the synchronization will be fully corrected." And, of course, since the sponsorship credits had, in reality, been exhausted, "any additional usage may result in billable charges according to your subscription configuration." It is not clear whether Microsoft will waive the charges that were spotted too late thanks to its "ongoing synchronization issue." Our reader said they were told only the Startups team could grant an exception. The experience is a warning that just because one portal says a balance is healthy, another might tell an altogether different story. The challenge is finding that other portal and acting before a switchover happens and a credit card gets hammered in the name of AI progress. The Register contacted Microsoft about this tale of woe late last week, and the company asked that we give it until 1500 UK on September 21 to investigate. That deadline has passed without further comment. Perhaps our request is sitting in the wrong portal? (R) Updated at 1404 UTC on September 22, 2026, to add: Microsoft contacted The Register following publication of this article to confirm that its review has concluded. "Microsoft's review found that the startup received $25K in credits and had been provided with multiple communications and instructions on monitoring its credit usage and remaining balance through the Sponsorship Balance portal. In January, support specifically directed the customer to that portal to check its balance, and the customer also received notifications as its credits were depleted and when they were exhausted. "In April, the startup requested additional credits. While that request was not approved, Microsoft provided a three-month extension to the existing credits, which the founder acknowledged. "The review did find a discrepancy between the balance displayed in the Microsoft for Startups portal and the Sponsorship Balance portal. However, the customer had previously been directed to the Sponsorship Balance portal for the accurate balance and had received the additional credit-usage notifications outlined above."