Skip to content

Commit 0399893

Browse files
committed
proof reading
1 parent 2ba00bc commit 0399893

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

articles/app-service/environment/how-to-upgrade-preference.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -27,15 +27,15 @@ When you use an automatic upgrade preference, the platform will upgrade your App
2727
* *Early* will apply the upgrade automatically, but will prioritize it as one of the first instances in the region to be upgraded.
2828
* *Late* will apply the upgrade automatically, but the instance will be one of the last in the region to be upgraded.
2929

30-
> [!NOTE]
31-
> In smaller regions, Early and Late upgrade preferences might be very close to each other.
32-
>
30+
In smaller regions, Early and Late upgrade preferences might be very close to each other.
3331

3432
## Manual upgrade preference
3533

36-
Manual upgrade preference will give you the option to receive a notification when an upgrade is available. After the upgrade is available, you'll have 15 days to start the upgrade process. If you don't start the upgrade within the 15 days, the upgrade will be processed with the remaining automatic upgrades in the region.
34+
Manual upgrade preference will give you the option to receive a notification when an upgrade is available. The availability will also be visible in the Azure portal. After the upgrade is available, you'll have 15 days to start the upgrade process. If you don't start the upgrade within the 15 days, the upgrade will be processed with the remaining automatic upgrades in the region.
3735

38-
::: zone pivot="experience-azp"
36+
> [!NOTE]
37+
> In rare cases the upgrade availability might be impacted by a security hotfix superseding the planned upgrade, or a regression found in the planned upgrade before it has been applied to your instance. In these rare cases, the available upgrade will be removed and will transition to automatic upgrade.
38+
>
3939
4040
## Configure notifications
4141

@@ -51,10 +51,12 @@ To configure alerts for upgrade notifications, select the **Add service health a
5151

5252
As you build your automation and notification logic, you may want to test it before the actual upgrade is available as this upgrade could be more than a month out. The Azure portal has the ability to send a special test upgrade available notification, which you can use to verify your automation logic. The message will be similar to the real notification, but the title will be prefixed with "[Test]" and the description will be different. You can send test notifications after you've configured your upgrade preference to Manual.
5353

54-
To send a test notification, navigate to the **Configuration** page for your App Service Environment and select the **Send test notification** link. The notifications are sent in batches every hour.
54+
To send a test notification, navigate to the **Configuration** page for your App Service Environment and select the **Send test notification** link. The test notifications are sent in batches every 15 minutes.
5555

5656
:::image type="content" source="./media/upgrade-preference/send-test-notification.png" alt-text="Screenshot of a configuration pane to send test notifications for the App Service Environment.":::
5757

58+
::: zone pivot="experience-azp"
59+
5860
## Use the Azure portal to configure upgrade preference
5961

6062
1. From the [Azure portal](https://portal.azure.com), navigate to the **Configuration** page for your App Service Environment.

0 commit comments

Comments
 (0)