Urgent billing review requested: unexpected Claude charges through Microsoft Foundry under Microsoft for Startups

I am a Microsoft for Startups participant and have been using Azure under the Startup sponsorship subscription since February 2026.

I am requesting an Azure Billing review and discretionary adjustment for unexpected Claude charges incurred through Microsoft Foundry.

I understand that Anthropic models are currently classified as outside Microsoft for Startups sponsorship-credit coverage. My question is therefore not whether Anthropic is technically eligible for Startup credits, but whether the resulting charges can be reviewed as an unintended billing incident and considered for a one-time courtesy adjustment.

In August 2026, our Azure billing data shows approximately ₹24,884.33 (~US$285) in Claude charges through Microsoft Foundry, with ₹0 Azure Startup credits applied to those transactions.

In September, Cost Analysis subsequently showed approximately ₹1.25 lakh (~US$1,450) of additional Claude/Foundry-related SaaS exposure. We have since removed the Claude deployments to prevent further charges.

Claude was presented in Microsoft Foundry under “Available in my project.” At the point of deployment, we did not understand that using the model would bypass our Microsoft for Startups credits and generate separate Marketplace/SaaS charges.

I have supporting billing records and screenshots documenting the above.

I have also found documented Microsoft cases involving Microsoft for Startups customers who incurred unexpected Claude/Foundry charges of a similar magnitude, where Microsoft subsequently provided special-exception credits following review.

I have already contacted our Microsoft for Startups contact, who has asked us to obtain an Azure Support case for further review.

Unfortunately, when we attempt to create the appropriate Azure Billing support request through the portal, the workflow routes us to “Resolve inability to sign up,” which is unrelated to this billing issue. I have a screen recording demonstrating this problem.

Could an Azure Support Engineer please review this case and either assist with the billing adjustment request directly or create/escalate the appropriate Azure Billing support case on our behalf?

The matter is time-sensitive because the payment cycle is approaching.

Thank you.