Share via

Azure Static WebApp: "404: Not Found" suddenly

Jesus Garcia Gutierrez 20 Reputation points
2026-05-12T10:58:02.4+00:00

Hi there! I have a website, fosfoyesos.info, powered by SWA.

Until yesterday, the website was fine, but today I'm getting a 404 error without making any changes.

I've deployed in order to fix the error, but it is still there.

Any idea? Thank you.

Azure Static Web Apps
Azure Static Web Apps

An Azure service that provides streamlined full-stack web app development.


Answer accepted by question author

Golla Venkata Pavani 6,085 Reputation points Microsoft External Staff Moderator
2026-05-14T18:39:46.4666667+00:00

Hi @Jesus Garcia Gutierrez

Thank you for the update. This explains the sudden 404 error perfectly. The root cause is that your Azure subscription (the one hosting the Static Web App) is currently disabled and operating in read-only mode. Because of this, Azure cannot process deployments, apply configuration changes, or properly serve the custom domain binding and SSL certificate, which results in the “404 Web Site not found” page. This situation is common with Azure for Students subscriptions when the $100 credit has been exhausted, the 12-month validity period has expired, or the subscription was accidentally canceled or hit a service limit. Even though Azure Static Web Apps may use a free tier, a disabled subscription still prevents normal operation of the service.

To resolve the issue, please go to the Azure Portal > Subscriptions and verify the status of your subscription (it will likely show as “Disabled”). The recommended solution is usually to reactivate or upgrade the subscription to Pay-As-You-Go, which allows continued use beyond the student subscription limits. If needed, you can also contact Azure Support through Help + support > New support request and select the Billing/Subscription category to request reactivation assistance. After the subscription becomes active again, redeploy the application (even without code changes) and then go to Settings > Custom domains to remove and re-add the fosfoyesos.info domain if necessary so Azure can refresh the domain binding and SSL certificate. Please note that DNS propagation and certificate reissuance may take several minutes or, in some cases, a few hours.

Reference:
https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/azurestudents-subscription-disabled
https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/subscription-disabled

Kindly let us know if the above helps or you need further assistance on this issue.

Please "accept" if the information helped you. This will help us and others in the community as well.

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. AI answer

    2026-05-12T10:58:15.24+00:00

    A transient platform or caching issue is the most likely cause when an Azure Static Web App that was working suddenly starts returning a generic Azure 404 without any code changes, especially if redeploying does not change the behavior.

    In similar cases, the issue has resolved on its own after some time without any configuration changes, suggesting delayed cache invalidation or a temporary platform problem. Because Azure Static Web Apps automatically handles cache invalidation after deployments, no manual purge is normally required.

    Recommended actions:

    1. Wait and recheck the site periodically (both the default *.azurestaticapps.net URL and the custom domain).
    2. If the issue persists for an extended period, open a support request with Azure Support so they can check the specific Static Web App resource and deployment history.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.