Static Web App deployment permanently fails with generic "An unknown exception has occurred" — East US 2

Subject: Static Web App deployment permanently fails with generic "An unknown exception has occurred" — East US 2

Resource: green-mud-06ff7530f (Free tier), resource group iaw-resource, subscription fefd1635-a57a-4d54-acbe-98f60da664c9, region East US 2

Issue: Every deployment attempt via GitHub Actions (Azure/static-web-apps-deploy@v1) fails identically. The Oryx build for the API completes successfully, but the deployment fails immediately after with the generic message "An unknown exception has occurred," with no further detail and no server-side build record visible in deployment history.

Troubleshooting already performed:

Regenerated and confirmed the deployment token — ruled out (no "invalid token" error appears)
Verified Node engine pin in api/package.json — build still fails identically regardless of Node version warnings
Confirmed resource has never had a successful deployment since creation

DeploymentIds: 54901ecf-2f9f-407c-8ace-fe399b2a7f87, 0d0c2b50-7040-40f7-9a1f-89deaec4703e, 27d5d8f7-6e83-408b-9372-dd5b831456a7

Related report: This matches [Azure/static-web-apps#1750](https://github.com/Azure/static-web-apps/issues/1750), reported against the same region (East US 2) though on Standard SKU — this resource is Free tier, suggesting the issue may span both tiers.

Request: Please investigate the East US 2 deployment slice, or advise if this is a known outage with an ETA.

Start with the GitHub Actions workflow using Azure/static-web-apps-deploy@v1, api/package.json, and the listed deployment IDs; compare the East US 2 failure with related issue #1750 and deployment history. Done means identifying whether the failure is an East US 2 service issue affecting Free and Standard tiers, or documenting a reproducible cause and clear mitigation.

Written by the indexing model from the issue text.