Skip to content

Commit eac03d4

Browse files
authored
format
1 parent cbc0e4a commit eac03d4

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

articles/reliability/migrate-app-service.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,12 +24,11 @@ An App Service lives in an App Service plan (ASP), and the App Service plan exis
2424

2525
- For App Services that are configured to be zone redundant, the platform automatically spreads the VM instances in the App Service plan across all three zones in the selected region. If a VM instance capacity larger than three is specified and the number of instances is a multiple of three (3 * N), the instances will be spread evenly. However, if the number of instances is not a multiple of three, the remainder of the instances will get spread across the remaining one or two zones.
2626

27-
> [NOTE!]
27+
> [!NOTE]
2828
> [App Service SLA](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1) is calculated based on the Maximum Available Minutes and Downtime which is standard irrespective of availability zone enablement. Downtime for the App Service is defined as the following.
2929
>
3030
> “Downtime: The total accumulated Deployment Minutes, across all Apps deployed by Customer in a given Microsoft Azure subscription, during which the App is unavailable. A minute is considered unavailable for a given App when there is no connectivity between the App and Microsoft’s Internet gateway.”
3131
32-
3332
## Prerequisites
3433

3534
Availability zone support is a property of the App Service plan. The following are the current requirements/limitations for enabling availability zones:

0 commit comments

Comments
 (0)