Skip to content

Enable Front Door Classic instance#

Cost Optimization · Front Door · 2020_06

Enable Azure Front Door Classic instance.

Description#

The operational state of a Front Door Classic instance is configurable, either enabled or disabled. By default, a Front Door is enabled.

Optionally, a Front Door Classic instance may be disabled to temporarily prevent traffic being processed.

Recommendation#

Consider enabling the Front Door service or remove the instance if it is no longer required. This applies to Azure Front Door Classic instances only.

Examples#

Configure with Azure template#

To deploy a Front Door resource that passes this rule:

  • Set the properties.enabledState property to Enabled.

For example:

Azure Template snippet
{
  "type": "Microsoft.Network/frontDoors",
  "apiVersion": "2021-06-01",
  "name": "[parameters('name')]",
  "location": "global",
  "properties": {
    "enabledState": "Enabled",
    "frontendEndpoints": "[variables('frontendEndpoints')]",
    "loadBalancingSettings": "[variables('loadBalancingSettings')]",
    "backendPools": "[variables('backendPools')]",
    "healthProbeSettings": "[variables('healthProbeSettings')]",
    "routingRules": "[variables('routingRules')]"
  }
}

Configure with Bicep#

To deploy a Front Door resource that passes this rule:

  • Set the properties.enabledState property to Enabled.

For example:

Azure Bicep snippet
resource afd_classic 'Microsoft.Network/frontDoors@2021-06-01' = {
  name: name
  location: 'global'
  properties: {
    enabledState: 'Enabled'
    frontendEndpoints: frontendEndpoints
    loadBalancingSettings: loadBalancingSettings
    backendPools: backendPools
    healthProbeSettings: healthProbeSettings
    routingRules: routingRules
  }
}
Last update: 2023-02-18

Comments