Azure Static Web App Trigger Stopped Working

Ziggy Zulueta 490 Reputation points MVP
2023-05-31T02:33:13.42+00:00

I created an Azure Static Web App with Function App - Managed Backend as shown below.

Untitled2

The whole system has been working for many weeks since April 2023 when I created the system. My Azure Web app calls the HTTP Trigger and is able to get the variables it needs. It was working till yesterday when it started to not work anymore today.

I get this error in my code. It seems that the Function App is no longer working. I need to know why it failed all of a sudden without me doing anything different with the code.

Screenshot 2023-05-31 102150

I checked Application Insights and I get this error. Altho I am not sure why my Azure Static web app is no longer authorized to call its own Managed Function.

Screenshot 2023-06-01 003842

Azure Static Web Apps
Azure Static Web Apps
An Azure service that provides streamlined full-stack web app development.
846 questions
{count} votes

Accepted answer
  1. SnehaAgrawal-MSFT 20,471 Reputation points
    2023-06-01T08:26:50.9966667+00:00

    @Ziggy Zulueta

    Apologies for facing issue on this! Thanks for reaching here!

    The issue has been identified- where the SWA apps, all the calls to backend API fail with 401 error, our team is working on fix, will update here accordingly.

    Suggested Workaround:

    You can change the AuthenticationLevel to Anonymous for your function.

    It's safe to set the AuthorizationLevel as Anonymous, as we have another layer of authorization checks (EasyAuth) in place so that only SWA can access the managed function endpoints and not anyone else.

    Hope this helps. Will keep posted here.

    Update-6/8-

    The fix has been rolled out to all affected SWA regions and the issue is mitigated now. You can redeploy your app if still experiencing issues.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful