You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/app-service/environment/how-to-upgrade-preference.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,15 +27,15 @@ When you use an automatic upgrade preference, the platform will upgrade your App
27
27
**Early* will apply the upgrade automatically, but will prioritize it as one of the first instances in the region to be upgraded.
28
28
**Late* will apply the upgrade automatically, but the instance will be one of the last in the region to be upgraded.
29
29
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.
33
31
34
32
## Manual upgrade preference
35
33
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.
37
35
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
+
>
39
39
40
40
## Configure notifications
41
41
@@ -51,10 +51,12 @@ To configure alerts for upgrade notifications, select the **Add service health a
51
51
52
52
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.
53
53
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.
55
55
56
56
:::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.":::
57
57
58
+
::: zone pivot="experience-azp"
59
+
58
60
## Use the Azure portal to configure upgrade preference
59
61
60
62
1. From the [Azure portal](https://portal.azure.com), navigate to the **Configuration** page for your App Service Environment.
0 commit comments