Azure Static Web App Trigger Stopped Working

Question

Azure Static Web App Trigger Stopped Working

Ziggy Zulueta 495 MVP

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

Ziggy Zulueta 495 Reputation points MVP

2023-05-31T09:56:09.6466667+00:00

I checked the application. The Azure Web App is to call AzureStaticWebAppHTTPTrigger to get some configuration settings need to run another API. Once the variables are retrieved, the AzureStaticWebAppHTTPTrigger would call the next API thru Azure API Management Service (APIM).

I manually called the next API in (APIM) by getting the config variables in my Azure Static Web App and was able to call the API. Hence the issue is indeed in the AzureStaticWebAppHTTPTrigger. Altho I am not sure why it is not working all of a sudden
Ziggy Zulueta 495 Reputation points MVP

2023-05-31T17:23:56.34+00:00
I was able to solve this by checking the code of the api.

[FunctionName("AzureStaticWebAppHttpTrigger")] public static async Task<IActionResult> Run( [HttpTrigger(AuthorizationLevel.Function, "get", "post", Route = null)] HttpRequest req, ILogger log)

I noticed that the AuthorizationLevel.Function is restricting the access. I changed it to Anonymous and everything works out now.

I dont understand how this code change can happen though because I have been using this application for quite a while. I never recall changing the AuthorizationLevel setting

Accepted answer

0 additional answers

Your answer

Ziggy Zulueta 495 Reputation points MVP

2023-05-31T09:56:09.6466667+00:00

I checked the application. The Azure Web App is to call AzureStaticWebAppHTTPTrigger to get some configuration settings need to run another API. Once the variables are retrieved, the AzureStaticWebAppHTTPTrigger would call the next API thru Azure API Management Service (APIM).

I manually called the next API in (APIM) by getting the config variables in my Azure Static Web App and was able to call the API. Hence the issue is indeed in the AzureStaticWebAppHTTPTrigger. Altho I am not sure why it is not working all of a sudden
Ziggy Zulueta 495 Reputation points MVP

2023-05-31T17:23:56.34+00:00

I was able to solve this by checking the code of the api.

[FunctionName("AzureStaticWebAppHttpTrigger")] public static async Task<IActionResult> Run( [HttpTrigger(AuthorizationLevel.Function, "get", "post", Route = null)] HttpRequest req, ILogger log)

I noticed that the AuthorizationLevel.Function is restricting the access. I changed it to Anonymous and everything works out now.

I dont understand how this code change can happen though because I have been using this application for quite a while. I never recall changing the AuthorizationLevel setting

Answer 1

SnehaAgrawal-MSFT 22,711 Moderator

@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.

geoff brooks 5 Reputation points

2023-06-01T15:05:47.5766667+00:00

I am experiencing this issue also. It started happening about 6 hours ago.

I can confirm that replacing AuthorizationLevel.Function with AuthorizationLevel.Anonymous for all functions solves the issue.
Ziggy Zulueta 495 Reputation points MVP

2023-06-02T03:40:02.5166667+00:00

Hi Sneha - are you saying that this is an issue now for all Azure Static Web apps?
SnehaAgrawal-MSFT 22,711 Reputation points Moderator

2023-06-05T04:32:38.96+00:00

@Ziggy Zulueta Since approx 2023-05-18, we're seeing multiple customers hit into 401 unauthorized errors for the requests going to their backend function app from SWA without any change from their side to the app. The issue is now mitigated, Please try from your end and let us know.
SnehaAgrawal-MSFT 22,711 Reputation points Moderator

2023-06-08T08:27:35.49+00:00

@Ziggy Zulueta

Just checking if you have chance to see recent response.

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.

Please let us know if further query or issue remains.

Please accept as "Yes" if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.
geoff brooks 5 Reputation points

2023-06-08T11:35:52.7266667+00:00

Since the Anonymous AuthenticationLevel limits access to the function to only the related SWA (at least that is my understanding - is it in fact true?) is there any reason to change back to an AuthenticationLevel of Function?

Share via

Azure Static Web App Trigger Stopped Working

0 additional answers

Your answer