Open akitson-degreed opened 1 year ago
Same thing happening to our workflows that use this action. I can also confirm that pinning the action version to 2.2.9
works as expected.
We are getting same error with v2. Has anything changed in App service security? Please help.
Seeing the same exact thing. No network restrictions on the web app.
Have had an Azure support ticket on this, but seems the issue is with the action. It works fine with az webapp deploy
from local machine, but the latest v2 action is failing with the 403 error.
This issue is idle because it has been open for 14 days with no activity.
@rasmus-watjen @akitson-degreed can you share the app names for which you are facing the issue? Also were you using Publish-profile or az login in your workflow yaml while deploying the app service?
We're doing az login with a service principal that has contributor rights on the app service. The app name is called apsazewd-admiral-beaconsj.
@rasmus-watjen, @akitson-degreed is Basic Auth enabled for your app ? If yes, can you turnoff Basic-auth for your App and try again.
There's no auth configured in Azure. The app we're having the issue with is an API only app that uses in-app request validation.
This issue is idle because it has been open for 14 days with no activity.
In our case, the cause was an expired free tier Azure subscription
This issue is idle because it has been open for 14 days with no activity.
Any update on this issue?
We would like to move to the most recent version Azure/webapps-deploy@v3.0.0
but not sure if this issue is resolved in that version either.
A couple days ago version 2.2.10 was released and since then our deployments have been failing with the error
The deployment to your web app failed with HTTP status code 403. Your web app may have networking features enabled which are blocking access (such as Private Endpoints). For more information about deploying to virtual network integrated web apps, please follow https://aka.ms/gha/deploying-to-network-secured-sites
.If we pin the version to 2.2.9 it works as expected.