Fail to create Static Web App

For this error, the supported fix is to create the Azure Static Web App using the Deployment token option instead of linking it directly to GitHub during creation, then use that newly created token in the GitHub Actions workflow.

Based on the documented resolution for this exact symptom:

1. Create a new Static Web App.
2. During creation, choose Deployment token rather than the direct GitHub-linked setup.
3. Use the new deployment token generated by that app.
4. Update the GitHub Actions secret used by the workflow with that new token.
5. Run the workflow again.

Since these steps were already tried in part, the key detail is that the token must come from a Static Web App that was created with the Deployment token path. In the documented case, the error was not caused by an expired or malformed token; it was caused by the initial Static Web App setup.

If the deployment still fails, check the GitHub Actions run logs to confirm whether the failure is still the API key validation step or whether the issue has moved to build or folder configuration:

1. Open the GitHub repository.
2. Select Actions.
3. Open the failed workflow run.
4. Select Build and Deploy Job.
5. Select Build And Deploy.
6. Review the log output.

If the logs show folder-related errors instead, verify the workflow folder settings match the repository structure:

• App Directory Location must point to a real folder.
• Output location must match the actual build artifact folder.
• Api location should be empty if no Azure Functions API is being deployed.

References:

• My GitHub Actions build for Azure Static Web Apps completes and uploads, but the deploy step fails with ‘Invalid API key’ even though AZURE_STATIC_WEB_APPS_API_TOKEN is set? - Microsoft Q&A
• Troubleshooting deployment and runtime errors