Skip to content

β“πŸ‘‚ Question/Feedback - Deploy Application Gateway in a zone-redundant configurationΒ #785

@junichi-tanaka

Description

@junichi-tanaka

Question/Feedback

This is about the rule of Deploy Application Gateway in a zone-redundant configuration.

https://learn.microsoft.com/azure/well-architected/services/networking/azure-application-gateway#reliability

Regarding this article, it says the following things.

After you deploy a new gateway by using the Azure portal, the portal or other tooling might indicate that the gateway isn't zone-redundant. However, if the gateway is deployed in a region that supports availability zones, it's guaranteed to be zone-redundant.

we recommend that you omit the zone list so that your gateway can use all of the availability zones, unless you have a specific reason not to use a specific zone.

So, I think current KQL is incorrect.
isnull(zones) is unnecessary anymore.

Possible Answers/Solutions?

  • Recheck the current behavior of Application Gateway
  • Update the KQL if needed

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions