I have a Blazor webassembly that runs as an app service. It calls a .net core api also running as an app service in the same resource group. I set this up a while ago and it has been running with no issues. Now I wanted to add a second api. I created a new app service again in the same resource group, but I am getting CORS errors when I try to call the new api. I have the AddCors set in the api code. If I comment that out in the code and use the portal CORS settings, I then get a 500 internal server error.
I created another new app service and deployed the old api to it and it also gets the same issues. But it works fine when deployed to the old app service that was created a while ago.
What changed when creating a new app service? I noticed the app insights gets created by default now and that was not the case before. I tried creating a new app service without app insights turned on, but still the issues are there when calling any api code deployed to that app service.
Is there some setting on a new app service that can be changed to get this to work? What changes have been made to app services?
