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/energy-data-services/how-to-manage-upgrade-settings.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,10 +24,10 @@ Azure Data Manager for Energy provides two upgrade policy options:
24
24
25
25
| Policy | Description |
26
26
|--------|-------------|
27
-
|**Automatic**| Your instance is automatically upgraded when a new milestone release is available. This is the default setting for all instances. |
27
+
|**Automatic**| Your instance is automatically upgraded when a new milestone release is available. This option is the default setting for all instances. |
28
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
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.
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 complete 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
31
32
32
## View upgrade settings
33
33
@@ -40,7 +40,7 @@ If you have multiple Azure Data Manager for Energy instances, you can set differ
40
40
1. On the **Upgrade Settings** page, you can view:
41
41
-**Current milestone version**: The current milestone version your instance is running (for example, M25 or M26).
42
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.
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 is automatically upgraded.
44
44
45
45
ADD SCREENSHOT HERE
46
46
@@ -99,7 +99,7 @@ If your upgrade policy is set to **Deferred** and a milestone upgrade is availab
99
99
100
100
When a new milestone release is available and your upgrade policy is set to **Deferred**:
101
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.
102
+
1. After all instances with the **Automatic** upgrade policy are upgraded, the Azure Data Manager for Energy team sets the **30-Day Window End Date**, which is approximately 30 days from that point.
103
103
104
104
1. The **30-Day Window End Date** is displayed on the **Upgrade Settings** page in the Azure portal.
105
105
@@ -114,11 +114,11 @@ When a new milestone release is available and your upgrade policy is set to **De
114
114
115
115
### What happens if I find an issue with Azure Data Manager for Energy during the 30-day window?
116
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.
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 is deployed.
118
118
119
119
## Next steps
120
120
121
-
Learn more about what's included in each milestone release and Azure Data Manager for Energy:
121
+
Learn more about each milestone release and Azure Data Manager for Energy:
0 commit comments