|
| 1 | +--- |
| 2 | +title: How to manage upgrade settings - Azure Data Manager for Energy |
| 3 | +description: Learn how to configure upgrade settings to control how milestone upgrades are applied to your Azure Data Manager for Energy instance. |
| 4 | +author: japicket |
| 5 | +ms.author: japicket |
| 6 | +ms.service: azure-data-manager-energy |
| 7 | +ms.topic: how-to |
| 8 | +ms.date: 01/27/2026 |
| 9 | +ms.custom: |
| 10 | + - template-how-to |
| 11 | +--- |
| 12 | + |
| 13 | +# Manage upgrade settings in Azure Data Manager for Energy |
| 14 | + |
| 15 | +This article describes how to view and manage upgrade settings for your Azure Data Manager for Energy instance. Upgrade settings allow you to control how milestone upgrades are applied to your instance. |
| 16 | + |
| 17 | +## What are milestone upgrades? |
| 18 | + |
| 19 | +Milestone upgrades are major version upgrades to Azure Data Manager for Energy, such as moving from M25 to M26. These upgrades may include significant changes to functionality and features. |
| 20 | + |
| 21 | +## Upgrade policy options |
| 22 | + |
| 23 | +Azure Data Manager for Energy provides two upgrade policy options: |
| 24 | + |
| 25 | +| Policy | Description | |
| 26 | +|--------|-------------| |
| 27 | +| **Automatic** | Your instance is automatically upgraded when a new milestone release is available. This is the default setting for all instances. | |
| 28 | +| **Deferred** | Your instance upgrade is deferred, giving you up to 30 days to validate the new milestone release before your instance is upgraded. | |
| 29 | + |
| 30 | +If you have multiple Azure Data Manager for Energy instances, you can set different upgrade policies for each one. For example, you might set one instance to **Automatic** so it upgrades immediately when a new milestone is released, allowing you to test and validate the changes. Meanwhile, you can set your production instance to **Deferred** to delay the upgrade until you've completed your testing. At any point during the 30-day window, you can mark your deferred instance as ready for upgrade. If you don't take action, the instance is automatically upgraded at the end of the 30-day window. |
| 31 | + |
| 32 | +## View upgrade settings |
| 33 | + |
| 34 | +1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to your Azure Data Manager for Energy instance. |
| 35 | + |
| 36 | +1. In the left menu under **Advanced**, select **Upgrade Settings**. |
| 37 | + |
| 38 | + ADD SCREENSHOT HERE |
| 39 | + |
| 40 | +1. On the **Upgrade Settings** page, you can view: |
| 41 | + - **Current milestone version**: The current milestone version your instance is running (for example, M25 or M26). |
| 42 | + - **Upgrade policy**: Whether your instance is set to **Automatic** or **Deferred** upgrades. |
| 43 | + - **Auto upgrade after date**: If your upgrade policy is set to **Deferred** and a milestone upgrade is available, this field shows the date when your instance will be automatically upgraded. |
| 44 | + |
| 45 | + ADD SCREENSHOT HERE |
| 46 | + |
| 47 | +> [!NOTE] |
| 48 | +> The current milestone version is also displayed on the **Overview** page for your Azure Data Manager for Energy instance. |
| 49 | +
|
| 50 | +## Configure upgrade settings during instance creation |
| 51 | + |
| 52 | +You can configure upgrade settings when you create a new Azure Data Manager for Energy instance. |
| 53 | + |
| 54 | +1. When creating a new instance, navigate to the **Advanced Settings** tab. |
| 55 | + |
| 56 | +1. In the **Upgrade Settings** section, you can choose to enable **Defer Milestone Upgrades**. |
| 57 | + |
| 58 | + ADD SCREENSHOT HERE |
| 59 | + |
| 60 | +1. Complete the remaining tabs and select **Create** to create your instance with the configured upgrade settings. |
| 61 | + |
| 62 | +## Change the upgrade policy for an existing instance |
| 63 | + |
| 64 | +You can change the upgrade policy for an existing Azure Data Manager for Energy instance at any time. |
| 65 | + |
| 66 | +1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to your Azure Data Manager for Energy instance. |
| 67 | + |
| 68 | +1. In the left menu under **Advanced**, select **Upgrade Settings**. |
| 69 | + |
| 70 | +1. Select either **Automatic** or **Deferred** to change your upgrade policy. |
| 71 | + |
| 72 | + ADD SCREENSHOT HERE |
| 73 | + |
| 74 | +1. Select **Save** to apply your changes. |
| 75 | + |
| 76 | +## Mark your instance as ready for upgrade |
| 77 | + |
| 78 | +If your upgrade policy is set to **Deferred** and a milestone upgrade is available, you can mark your instance as ready for upgrade at any time during the 30-day window. |
| 79 | + |
| 80 | +1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to your Azure Data Manager for Energy instance. |
| 81 | + |
| 82 | +1. In the left menu under **Advanced**, select **Upgrade Settings**. |
| 83 | + |
| 84 | +1. Select the **Mark Ready for Milestone Upgrade** button. |
| 85 | + |
| 86 | + ADD SCREENSHOT HERE |
| 87 | + |
| 88 | + > [!NOTE] |
| 89 | + > The **Mark Ready for Milestone Upgrade** button is only available when: |
| 90 | + > - Your upgrade policy is set to **Deferred**. |
| 91 | + > - A milestone upgrade is available (the **30-Day Window End Date** is set). |
| 92 | +
|
| 93 | +1. Confirm that you want to mark your instance as ready for upgrade. |
| 94 | + |
| 95 | +> [!IMPORTANT] |
| 96 | +> Once you mark your instance as ready for upgrade, this action cannot be undone. Your instance will be upgraded during the next upgrade cycle. |
| 97 | +
|
| 98 | +## Understanding the 30-day upgrade window |
| 99 | + |
| 100 | +When a new milestone release is available and your upgrade policy is set to **Deferred**: |
| 101 | + |
| 102 | +1. After all instances with the **Automatic** upgrade policy have been upgraded, the Azure Data Manager for Energy team sets the **30-Day Window End Date**, which is approximately 30 days from that point. |
| 103 | + |
| 104 | +1. The **30-Day Window End Date** is displayed on the **Upgrade Settings** page in the Azure portal. |
| 105 | + |
| 106 | +1. During this 30-day window, you can: |
| 107 | + - Test the new milestone release in a nonproduction environment. |
| 108 | + - Mark your instance as ready for upgrade when you're satisfied with your testing. |
| 109 | + - Take no action and let your instance be automatically upgraded at the end of the window. |
| 110 | + |
| 111 | +1. After your instance is upgraded, the **30-Day Window End Date** is cleared until the next milestone release. |
| 112 | + |
| 113 | +## Frequently asked questions |
| 114 | + |
| 115 | +### What happens if I find an issue with Azure Data Manager for Energy during the 30-day window? |
| 116 | + |
| 117 | +If you discover an issue during the 30-day window, contact Azure support. Depending on the severity of the issue, the Azure Data Manager for Energy team may deploy a hotfix. If a hotfix is required, the 30-day timer is paused when the issue is identified and resumes once the hotfix has been deployed. |
| 118 | + |
| 119 | +## Next steps |
| 120 | + |
| 121 | +Learn more about what's included in each milestone release and Azure Data Manager for Energy: |
| 122 | + |
| 123 | +> [!div class="nextstepaction"] |
| 124 | +> [Release notes](release-notes.md) |
0 commit comments