Answers: <p>I had the same issue, I downloaded the Template from Azure which effectively had my Load Balancer's Backend Address Pool as a &quot;dependsOn&quot; and as a &quot;property&quot;.</p>
  <p>This is under the load balancer's &quot;dependsOn&quot; list :</p>
  <pre><code>    &quot;[resourceId('Microsoft.Network/loadBalancers/backendAddressPools', 'LB-db-phi-dbphipri', 'LoadBalancerBEAddressPool')]&quot;
  </code></pre>
  <p>And the property under the Load Balancer's property list:</p>
  <pre><code>    &quot;backendAddressPools&quot;: [
        {
          &quot;name&quot;: &quot;LoadBalancerBEAddressPool&quot;,            
          &quot;properties&quot;: {}
        }
      ]
  </code></pre>
  <p>Lastly, I had a child definition of the backendAddressPool as well</p>
  <pre><code>{
    &quot;type&quot;: &quot;Microsoft.Network/loadBalancers/backendAddressPools&quot;,
    &quot;apiVersion&quot;: &quot;2020-05-01&quot;,
    &quot;name&quot;: &quot;LB-db-phi-dbphipri/LoadBalancerBEAddressPool&quot;,
    &quot;properties&quot;: {}
  }
  </code></pre>
  <p>You don't need both. In my case I removed the &quot;child&quot; and the &quot;dependsOn&quot; and just have the property defined under the load balancer.</p>
  
Answers: CC BY-SA 4.0
Answers: 2020-11-17T21:46:48.757Z
Answers: 2020-11-17T21:46:48.757Z
Answers: DNapoleon
Body: <p>I'm attempting to create a backend address pool via an ARM template for a load balancer with the following code:</p>
  <pre><code>            &quot;type&quot;: &quot;Microsoft.Network/loadBalancers/backendAddressPools&quot;,
          &quot;apiVersion&quot;: &quot;2020-05-01&quot;,
          &quot;name&quot;: &quot;[concat(variables('engineLbName'), '/LoadBalancerBEAddressPool')]&quot;,
          &quot;dependsOn&quot;: [
              &quot;[resourceId('Microsoft.Network/loadBalancers', variables('engineLbName'))]&quot;
          ],
          &quot;properties&quot;: {}
  </code></pre>
  <p>The loadbalancer it is targetting is using a basic SKU. When i attempt to deploy this arm template through the azure portal, I am given the following error message:</p>
  <pre><code>{
  &quot;error&quot;: {
      &quot;code&quot;: &quot;BackendOperationOnlyAllowedForStandardLB&quot;,
      &quot;message&quot;: &quot;Operation on backend pool /subscriptions/****/resourceGroups/*******/providers/Microsoft.Network/loadBalancers/LB-engine/backendAddressPools/LoadBalancerBEAddressPool not allowed. This operation is only allowed for standard SKU load balancers.&quot;,
      &quot;details&quot;: []
  }
  </code></pre>
  <p>}</p>
  <p>Obviously, this indicates that i need to make my LB/LBIP of a standard SKU, however i specifically need this done on a basic SKU.</p>
  <p>I am very confused as to why this error occurs, as we have many basic LB's that have backend configuration, and you are freely able to create a BE pool through the portal on a basic LB - I am unsure on how to do this via an ARM template.</p>
  
Tags: <azure><load-balance>
Title: Create backend Address pool for basic load balancer azure arm template
UserDisplayName: MantyQuestions
ThreadText: # Create backend Address pool for basic load balancer azure arm template
  
  (Asked by: username_0 on 2020-11-05)
  
  I'm attempting to create a backend address pool via an ARM template for a load balancer with the following code:
  
  ```
              "type": "Microsoft.Network/loadBalancers/backendAddressPools",
          "apiVersion": "2020-05-01",
          "name": "[concat(variables('engineLbName'), '/LoadBalancerBEAddressPool')]",
          "dependsOn": [
              "[resourceId('Microsoft.Network/loadBalancers', variables('engineLbName'))]"
          ],
          "properties": {}
  
  ```
  
  The loadbalancer it is targetting is using a basic SKU. When i attempt to deploy this arm template through the azure portal, I am given the following error message:
  
  ```
  {
  "error": {
      "code": "BackendOperationOnlyAllowedForStandardLB",
      "message": "Operation on backend pool /subscriptions/****/resourceGroups/*******/providers/Microsoft.Network/loadBalancers/LB-engine/backendAddressPools/LoadBalancerBEAddressPool not allowed. This operation is only allowed for standard SKU load balancers.",
      "details": []
  }
  
  ```
  
  }
  
  Obviously, this indicates that i need to make my LB/LBIP of a standard SKU, however i specifically need this done on a basic SKU.
  
  I am very confused as to why this error occurs, as we have many basic LB's that have backend configuration, and you are freely able to create a BE pool through the portal on a basic LB - I am unsure on how to do this via an ARM template.
  
  **Tags:** azure, load-balance
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-11-17. Score: 1
  
  I had the same issue, I downloaded the Template from Azure which effectively had my Load Balancer's Backend Address Pool as a "dependsOn" and as a "property".
  
  This is under the load balancer's "dependsOn" list :
  
  ```
      "[resourceId('Microsoft.Network/loadBalancers/backendAddressPools', 'LB-db-phi-dbphipri', 'LoadBalancerBEAddressPool')]"
  
  ```
  
  And the property under the Load Balancer's property list:
  
  ```
      "backendAddressPools": [
        {
          "name": "LoadBalancerBEAddressPool",            
          "properties": {}
        }
      ]
  
  ```
  
  Lastly, I had a child definition of the backendAddressPool as well
  
  ```
  {
    "type": "Microsoft.Network/loadBalancers/backendAddressPools",
    "apiVersion": "2020-05-01",
    "name": "LB-db-phi-dbphipri/LoadBalancerBEAddressPool",
    "properties": {}
  }
  
  ```
  
  You don't need both. In my case I removed the "child" and the "dependsOn" and just have the property defined under the load balancer.
  
  
  ---
  
  