AppService deployment failing with badGateway forbidden message

Question

Hello

I'm trying to deploy an AppService using Visual Studio and it does seem to be just hanging. When I check on the Portal the website deployment log is showing a status of 'Bad Gateway' with the error details:
"The subscription

Answer 1

Hi Gautam Kaushal,

Based on the error message , I suggest to verify below list of actions:

• Make sure that you have created an app service in the same region as your service plan
• Check permissions: Ensure you have necessary permissions in Azure portal.
• Check App Service Plan: Ensure it’s correctly configured and has necessary resources.
• Check deployment settings: Ensure settings in Visual Studio are correct.
• Check IP restrictions: Ensure necessary IPs are whitelisted.
• Create a new resource group with the appropriate permissions and proceed with the deployment there

References:

• https://learn.microsoft.com/en-us/azure/role-based-access-control/role-assignments-portal-subscription-admin
• https://learn.microsoft.com/en-us/visualstudio/deployment/quickstart-deploy-aspnet-web-app?view=vs-2022&tabs=azure

If the information helped address your question, please Accept the answer.

Luis

Answer 2

I have the same issue here. I tracked it down to the serverfarm. It literally worked some weeks before with a different VS Enterprise subscription.

{
    "status": "Failed",
    "error": {
        "code": "Forbidden",
        "message": "The subscription '***' is not allowed to create or update the serverfarm.",
        "details": [
            {
                "message": "The subscription '***' is not allowed to create or update the serverfarm."
            },
            {
                "code": "Forbidden"
            },
            {}
        ]
    }
}

I already did that;

• subscription: grant myself Owner rights to the subscription.
• entra id: "[user] can manage access to all Azure subscriptions and management groups in this tenant" is ticked in "Properties".
• "Management Groups": grant yourself Owner access to the Tennant Root Group

nothing worked.