msaad22
February 23, 2026, 2:12am
#1
this error appears with me when trying to create application gateway
Resource ‘devops-agw’ was disallowed by policy. (Code: RequestDisallowedByPolicy)
Hi @msaad22
Please provide more details about the configuration you used to create the Application Gateway. You can also refer to the solution linked here and follow its configuration steps to create it correctly.
## Task: Configuring Azure VM with Application Gateway
The Nautilus Development Team needs to set up a new Azure Virtual Machine (VM) and configure it to run a web server. This VM should be part of an Azure Application Gateway (AGW) setup to ensure high availability and better traffic management. The task involves creating a VM, setting up an AGW, configuring a backend pool, and ensuring the web server is accessible via the AGW public IP.
**Create a Network Security Group (NSG):** Create an NSG named `nautilus-nsg` and add an inbound security rule `Allow-HTTP` to allow `TCP` traffic on port `80`.
**Create a Virtual Machine:** Create a VM named `nautilus-vm` using any available Ubuntu image. Configure the instance with the following settings:
- Size: Choose a lightweight VM size (e.g., `Standard_B1s`)
- Authentication: Use `SSH public key` authentication (Please select `use existing public key` option, create public-key locally and paste contents of `~/.ssh/id_rsa.pub`)
- OS Disk: Use a `Standard HDD`
- Networking: Under the Advanced section, attach an existing NSG (e.g., `nautilus-nsg`)
Additionally, configure the instance to run a user data script during launch that:
- Install the Nginx package
- Start the Nginx service
**Set up an Application Gateway:** Set up an Azure Application Gateway named `nautilus-agw` with the following:
- Associate it with a public IP address named `nautilus-agw-ip`
- Attach the backend pool: `nautilus-backendpool` to the VM `nautilus-vm`
- Select a subnet for the Application Gateway (you can create a new one if needed)
show original
msaad22
February 23, 2026, 9:27am
#3
Hello,
The issue has been resolved.
The deployment was failing because I was using the Standard_v2 SKU for the Application Gateway. After changing the SKU to Basic the deployment completed successfully.
Thank you for your support and assistance.