Skip to content

Commit f37fbb1

Browse files
authored
Merge pull request #224799 from JackStromberg/patch-101
Adding update clarification
2 parents 95871a2 + 248c984 commit f37fbb1

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

articles/application-gateway/application-gateway-faq.yml

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ metadata:
66
author: greg-lindsay
77
ms.service: application-gateway
88
ms.topic: faq
9-
ms.date: 10/19/2022
9+
ms.date: 02/08/2023
1010
ms.author: greglin
1111
ms.custom: references_regions
1212
title: Frequently asked questions about Application Gateway
@@ -118,7 +118,9 @@ sections:
118118
119119
- question: How does application gateway handle routine maintenance?
120120
answer: |
121-
Updates initiated to Application Gateway are applied one [update domain](../../articles/virtual-machines/availability-set-overview.md#how-do-availability-sets-work) at a time, during off business hours for the region the gateway is deployed in. As each update domain's instances are being updated, the remaining instances in other update domains will continue to serve traffic. Active connections are gracefully drained from the instances being updated for up to 5 minutes to help establish connectivity to instances in a different update domain before the update begins. During update, Application Gateway will temporarily run at reduced max capacity, which is determined by the number of instances configured. The update process will proceed to the next set of instances only if the current set of instances have been upgraded successfully.
121+
Updates initiated to Application Gateway are applied one [update domain](../../articles/virtual-machines/availability-set-overview.md#how-do-availability-sets-work) at a time. As each update domain's instances are being updated, the remaining instances in other update domains will continue to serve traffic<sup>1</sup>. Active connections are gracefully drained from the instances being updated for up to 5 minutes to help establish connectivity to instances in a different update domain before the update begins. During update, Application Gateway will temporarily run at reduced max capacity, which is determined by the number of instances configured. The update process will proceed to the next set of instances only if the current set of instances have been upgraded successfully.
122+
123+
<sup>1</sup> A minimum instance count of 2 is recommended to be configured for Application Gateway v1 SKU deployments to ensure at least one instance can serve traffic while updates are applied.
122124
123125
- question: Can I use Exchange Server as a backend with Application Gateway?
124126
answer: Application Gateway doesn't support email protocols such as SMTP, IMAP, and POP3. HTTP/HTTPS services such as OWA, ActiveSync, and AutoDiscovery traffic may flow through Application Gateway, however WAF exclusions may be required if using WAF sku.
@@ -388,7 +390,7 @@ sections:
388390
answer: |
389391
Yes, the Application Gateway v2 SKU supports Key Vault. For more information, see [TLS termination with Key Vault certificates](key-vault-certs.md).
390392
391-
- question: How do I configure HTTPS listeners for .com and .net sites?
393+
- question: How do I configure HTTPS listeners for .com and .NET sites?
392394
answer: |
393395
For multiple domain-based (host-based) routing, you can create multisite listeners, set up listeners that use HTTPS as the protocol, and associate the listeners with the routing rules. For more information, see [Hosting multiple sites by using Application Gateway](./multiple-site-overview.md).
394396
@@ -433,7 +435,7 @@ sections:
433435
434436
1. In the [Azure portal](https://portal.azure.com/), navigate to your Azure KeyVault settings which are associated with the Application Gateway.
435437
2. Add/import the reissued certificate in your store. See documentation [here](../key-vault/certificates/quick-create-portal.md) for more information on how-to.
436-
3. Once the certificate has been imported, navigate to your Application Gateway listener settings and under “Choose a certificate from Key Vault”, click on the “Certificate” drop down and choose the recently added certificate
438+
3. Once the certificate has been imported, navigate to your Application Gateway listener settings and under “Choose a certificate from Key Vault”, click on the “Certificate” drop-down and choose the recently added certificate
437439
4. Click Save
438440
For more information on TLS termination on Application Gateway with Key Vault certificates, see [TLS termination with Key Vault certificates](./key-vault-certs.md).
439441

0 commit comments

Comments
 (0)