Unexpected charges for Azure Static Web App began after Feb 17

Question

Unexpected charges for Azure Static Web App began after Feb 17

Artur Rossi 0

Starting on February 17th, the bill tripled for no reason.
Important notes:

The graph refers to only 1 Static web app with the Standard plan, which was supposed to cost $9, but it cost $27.
The "Enterprise-grade edge" function is disabled.
No additional bandwidth is being applied.
No one from the company worked on February 17th.

0 comments

2 answers

Your answer

Answer 1

Siva shunmugam Nadessin 10,900 Microsoft External Staff Moderator

Hello Artur Rossi,

Thank you for reaching out to the Microsoft Q&A forum.

When investigated it looks like sudden jump on Feb 17 usually means you went from 1 billable “unit” to 3. In Azure Static Web Apps (Standard) you pay a flat fee per active environment (production + any preview/staging slots) or per scaled-out instance of an App Service plan if you’re hosting via an App Service back end. A few things to check:

Verify how many instances/environments you’re actually running
- In the portal go to your Static Web App → “Environments” (preview/staging) – each one on Standard just counts as a full $9/mo unit.
- If you used an App Service plan for your API, open the App Service Plan → Scale-out settings. If it’s accidentally scaled to 3 instances (perhaps an autoscale rule), you’ll see a 3× charge vs. the single-instance rate.
Drill into Cost Analysis for exact meter details
- In Cost Management → Cost analysis, filter on your Static Web App resource or the App Service plan resource.
- Group by “Meter” or “Resource” to see exactly which meter is accruing the extra hours (e.g. “StaticWebApp Standard Plan” vs. “AppServicePlan Standard”) and how many instance hours you’re billed for.
Right-size or delete what you don’t need

If you don’t actually need 3 preview slots running, delete or disable them.
- If autoscale ramped you to multiple instances, set minimum instances back to 1.

Hope that helps you pinpoint the extra $18—once you drop back to a single billable unit your monthly cost will return to ~$9 USD.

References

Azure Static Web Apps hosting plans: https://learn.microsoft.com/azure/static-web-apps/plans
Static Web Apps quotas (preview envs & bandwidth): https://learn.microsoft.com/azure/static-web-apps/quotas
App Service plan overview & pricing: https://azure.microsoft.com/pricing/details/app-service/
Cost analysis quickstart: https://docs.microsoft.com/azure/cost-management-billing/costs/quick-acm-cost-analysis

Artur Rossi 0 Reputation points

2026-04-20T17:34:53.83+00:00
Thank you for your reply.

I tried all 3 suggested approaches:

I only have 1 environment on my Static Web App with Standard plan, because i use another Static Web App with Free plan for the staging environment. And I don't use any App Service plan either.

Even with the filters, only 1 instance of the Static Web App appears without additional bandwidth costs.

I'll try to delete and recreate the Static web app to see if that resolves the issue.
Siva shunmugam Nadessin 10,900 Reputation points Microsoft External Staff Moderator

2026-04-20T23:29:34.81+00:00

Hello Artur Rossi,

Just checking in to see if the solution shared above help you to resolve your issue. please reach out to us If you have any further questions.

Thanks
Siva shunmugam Nadessin 10,900 Reputation points Microsoft External Staff Moderator

2026-04-23T01:05:13.3166667+00:00

Hello Artur Rossi,

Kindly Accept Answer this can be beneficial to other community members.
Artur Rossi 0 Reputation points

2026-04-29T01:34:01.5766667+00:00
@Siva shunmugam Nadessin Thank you for your help.
The only solution that resolved the problem was to recreate the application.

I've attached a screenshot with the result.
Notes:

Both apps have exactly the same configuration.

The light blue represents the old app, and the dark blue represents the new one

The analysis was conducted over a period of one day.
Artur Rossi 0 Reputation points

2026-04-29T01:36:23.7066667+00:00
The only solution that resolved the problem was to recreate the application.

I've attached a screenshot with the result.
Notes:

Both apps have exactly the same configuration.

The light blue represents the old app, and the dark blue represents the new one

The analysis was conducted over a period of one day.
Siva shunmugam Nadessin 10,900 Reputation points Microsoft External Staff Moderator

2026-04-29T17:02:36.6466667+00:00

Hello Artur Rossi,

Customer deleted and recreated the static web app which helped in resolving the issue.

Reference Document:

https://learn.microsoft.com/en-us/azure/static-web-apps/static-web-apps-cli-deploy

https://learn.microsoft.com/en-us/cli/azure/staticwebapp?view=azure-cli-latest

Answer 2

Kim R. T. Hansen 0

We have also seen this issue in at least two different accounts. We have paid 150%-200% extra for the SWA in a period of about 3 months. Until it was silently fixed on May 14.

0 comments