Skip to content

Commit df7824b

Browse files
committed
acrolinx and images
1 parent 50d777f commit df7824b

File tree

3 files changed

+19
-17
lines changed

3 files changed

+19
-17
lines changed

articles/virtual-machines/deprecated-images.yml

Lines changed: 19 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -19,14 +19,14 @@ sections:
1919
questions:
2020
- question: I got an email that my image is scheduled for deprecation, what does this mean?
2121
answer: |
22-
You might have received an email telling you that your Virtual machine is running on images that are scheduled for deprecation or already deprecated as seen in the diagram below. There are several reasons an image can be deprecated by the publisher which might be due to security issues or the image reaching end of life.
22+
You might have received an email telling you that your Virtual machine is running on images that are scheduled for deprecation or already deprecated as seen in the diagram below. There are several reasons an image can be deprecated by the publisher, which might be due to security issues or the image reaching end of life.
2323
2424
2525
2626
An image can be deprecated on the version, plan or offer level:
2727
- Deprecation of an image version - the removal of an individual VM image version
28-
- Deprecation of a plan or SKU - the removal of a plan or SKU and subsequently all images within the plan
29-
- Deprecation of an offer - the removal of an entire VM offer, including all plans within the offer and subsequently all images within each plan.
28+
- Deprecation of a plan or SKU - the removal of a plan or SKU and all images within the plan
29+
- Deprecation of an offer - the removal of an entire VM offer, including all plans within the offer and all images within each plan.
3030
3131
- question: I received an email that my workloads are running on images that are scheduled for deprecation. What does this mean and does deprecation impact my existing workloads?
3232
answer: |
@@ -35,13 +35,13 @@ sections:
3535
After the scheduled deprecation date, you won't be able to deploy new instances using the affected images. If the plan is scheduled for deprecation, all image versions within the plan will no longer be available and if the entire offer is scheduled for deprecation, all plans within the offer will no longer be available following deprecation.
3636
3737
- Active VM instances won't be impacted.
38-
- New VM instances cannot be created from any of the impacted images.
39-
- Existing virtual machine scale sets deployments cannot be scaled out if configured with any of the impacted images. When a plan or offer is being deprecated, all existing scale sets deployments pinned to any image within the plan or offer respectively cannot be scaled out.
38+
- New VM instances can't be created from any of the impacted images.
39+
- Existing virtual machine scale sets deployments can't be scaled out if configured with any of the impacted images. When a plan or offer is being deprecated, all existing scale sets deployments pinned to any image within the plan or offer respectively can't be scaled out.
4040
4141
4242
**What do I need to do?**
4343
44-
If you want your scale set to scale out after the deprecation date, you will need to identify the scale set running on the deprecated image and then migrate your workload to a supported image. If you want to remain on the image after deprecation, you can create your own custom image and migrate to it (Steps outlined below). If you already have auto updates configured for your VM or scale set, you will only be impacted when an Offer or plan version is deprecated (No impact on image version deprecation).
44+
If you want your scale set to scale out after the deprecation date, you'll need to identify the scale set running on the deprecated image and then migrate your workload to a supported image. If you want to remain on the image after deprecation, you can create your own custom image and migrate to it (Steps outlined below). If you already have auto updates configured for your VM or scale set, you'll only be impacted when an Offer or plan version is deprecated (No impact on image version deprecation).
4545
4646
4747
@@ -159,34 +159,36 @@ sections:
159159
160160
Search for other plans under the same offer and then migrate to that plan.
161161
162-
PowerShell:
163-
164-
```
165-
Get-AzVMImage -Location "west europe" -PublisherName “MicrosoftWindowsServer” -Offer “WindowsServer”
166-
```
167162
168163
Azure CLI:
169164
170165
```
171166
az vm image list --location "west europe" --publisher "MicrosoftWindowsServer" --offer "WindowsServer"
172167
```
173168
169+
PowerShell:
170+
171+
```
172+
Get-AzVMImage -Location "west europe" -PublisherName “MicrosoftWindowsServer” -Offer “WindowsServer”
173+
```
174+
175+
174176
**To migrate to another version:**
175177
176178
Search for another version. We suggest migrating to the latest version.
177179
178-
PowerShell:
179-
180-
```
181-
Get-AzVMImage -Location "west europe" -PublisherName “MicrosoftWindowsServer” -Offer “WindowsServer” -Skus "2019-Datacenter-with-Containers"
182-
```
183180
184181
Azure CLI:
185182
186183
```
187184
az vm image list --location "west europe" --publisher "MicrosoftWindowsServer" --offer "WindowsServer" --sku "2019-Datacenter-with-Containers" --all"
188185
```
189186
187+
PowerShell:
188+
189+
```
190+
Get-AzVMImage -Location "west europe" -PublisherName “MicrosoftWindowsServer” -Offer “WindowsServer” -Skus "2019-Datacenter-with-Containers"
191+
```
190192
191193
You need to verify that your workloads are supported and will run properly on the new image before migrating your workloads to the new image.
192194
@@ -215,7 +217,7 @@ sections:
215217
You can check if an image is deprecated or scheduled for deprecation using the [REST API](/rest/api/compute/virtual-machine-images/get?tabs=HTTP).
216218
217219
218-
If the image is deprecated, you will get a **VM Image is Deprecated** response. If the image is scheduled for deprecation, the response would show the date of the scheduled deprecation.
220+
If the image is deprecated, you'll get a **VM Image is Deprecated** response. If the image is scheduled for deprecation, the response would show the date of the scheduled deprecation.
219221
220222
221223
The response indicates that this is deprecated:
Binary file not shown.
Binary file not shown.

0 commit comments

Comments
 (0)