Replies: 2 comments
-
Relatedly, since I'm using a linked backend when I try to use the Application Insights associated to the SWA I receive the message:
So it doesn't seem possible to use App Insights with a linked backend. Yet, there are metrics being written about the SWA which I see on the overview page. So metrics must still get written somewhere. But I don't know where. Is there a way to see more details about the errors occurring when using a linked backend? |
Beta Was this translation helpful? Give feedback.
-
I determined the issue exists when using the APIM Consumption SKU but not when using the Developer SKU. There must be a limitation when linking a SWA to a Consumption APIM and when using the built-in SWA auth. |
Beta Was this translation helpful? Give feedback.
-
I have a Static Web App which I have linked to APIM. All works well.
But then when I use auth to log in, /.auth/login/aad, and I'm redirected back to the web app the request to the API now fails with a HTTP status code 500. Looking at the browser's developer console when I inspect the API response I see the default asp.net yellow screen of death. When I log back out then everything works again.
If I link directly to an Azure Function App instead of the APIM then everything works when I'm both logged in and when I'm logged out.
Any ideas on what is causing the error when logged in and linked to APIM?
Beta Was this translation helpful? Give feedback.
All reactions