1. Review the error message in the console

   • Look for the policyAssignment and policyDefinition details.

   • These names and IDs identify which Azure Policy blocked deployment.
     
     

2. Check the Azure Policy definition

   • The policy definition describes the rule that was violated.

   • Use Azure CLI to retrieve details:

     az policy definition show --name <policy-name>

3. Check the Azure Policy assignment

   • The assignment shows how and where the policy is applied.

   • Retrieve assignment details with Azure CLI:

     az policy assignment show --name <assignment-name> --resource-group <resource-group-name>

       

4. Review the rule that blocked deployment

   • Look for rules that limit VM sizes, networking, storage, or other configuration requirements.

   • Examples include:

     • Allowed VM size lists

     • Restrictions on public IPs

     • Requirements for specific network configurations
       
       

5. Update your deployment or policy

   • Adjust the Elastigroup configuration to comply with the policy.

   • Or update the Azure Policy if your organization allows changes to policy scope or rules.

After you identify the policy and update either your deployment or the policy settings, Elastigroup should be able to launch the virtual machine without triggering the “RequestDisallowedByPolicy” message.