Skip to content

Commit a4cb5b0

Browse files
authored
Merge pull request #111446 from mayanknayar/master
Update VMSS API version
2 parents 7a7f677 + 29dc4f2 commit a4cb5b0

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-upgrade.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: mimckitt
55
tags: azure-resource-manager
66
ms.service: virtual-machine-scale-sets
77
ms.topic: conceptual
8-
ms.date: 03/18/2020
8+
ms.date: 04/14/2020
99
ms.author: mimckitt
1010

1111
---
@@ -104,7 +104,7 @@ GET on `/subscriptions/{subscriptionId}/providers/Microsoft.Features/providers/M
104104
Once the feature has been registered for your subscription, complete the opt-in process by propagating the change into the Compute resource provider.
105105

106106
```
107-
POST on `/subscriptions/{subscriptionId}/providers/Microsoft.Compute/register?api-version=2019-10-01`
107+
POST on `/subscriptions/{subscriptionId}/providers/Microsoft.Compute/register?api-version=2019-12-01`
108108
```
109109

110110
### Azure PowerShell
@@ -163,7 +163,7 @@ To configure automatic OS image upgrade, ensure that the *automaticOSUpgradePoli
163163
The following example describes how to set automatic OS upgrades on a scale set model:
164164

165165
```
166-
PUT or PATCH on `/subscriptions/subscription_id/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachineScaleSets/myScaleSet?api-version=2018-10-01`
166+
PUT or PATCH on `/subscriptions/subscription_id/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachineScaleSets/myScaleSet?api-version=2019-12-01`
167167
```
168168

169169
```json
@@ -242,7 +242,7 @@ You can check the history of the most recent OS upgrade performed on your scale
242242
The following example uses [REST API](/rest/api/compute/virtualmachinescalesets/getosupgradehistory) to check the status for the scale set named *myScaleSet* in the resource group named *myResourceGroup*:
243243

244244
```
245-
GET on `/subscriptions/subscription_id/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachineScaleSets/myScaleSet/osUpgradeHistory?api-version=2018-10-01`
245+
GET on `/subscriptions/subscription_id/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachineScaleSets/myScaleSet/osUpgradeHistory?api-version=2019-12-01`
246246
```
247247

248248
The GET call returns properties similar to the following example output:
@@ -302,7 +302,7 @@ You can get the available image versions for automatic OS upgrade supported SKUs
302302

303303
### REST API
304304
```
305-
GET on `/subscriptions/subscription_id/providers/Microsoft.Compute/locations/{location}/publishers/{publisherName}/artifacttypes/vmimage/offers/{offer}/skus/{skus}/versions?api-version=2018-10-01`
305+
GET on `/subscriptions/subscription_id/providers/Microsoft.Compute/locations/{location}/publishers/{publisherName}/artifacttypes/vmimage/offers/{offer}/skus/{skus}/versions?api-version=2019-12-01`
306306
```
307307

308308
### Azure PowerShell
@@ -327,7 +327,7 @@ For specific cases where you do not want to wait for the orchestrator to apply t
327327
Use the [Start OS Upgrade](/rest/api/compute/virtualmachinescalesetrollingupgrades/startosupgrade) API call to start a rolling upgrade to move all virtual machine scale set instances to the latest available image OS version. Instances that are already running the latest available OS version are not affected. The following example details how you can start a rolling OS upgrade on a scale set named *myScaleSet* in the resource group named *myResourceGroup*:
328328

329329
```
330-
POST on `/subscriptions/subscription_id/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachineScaleSets/myScaleSet/osRollingUpgrade?api-version=2018-10-01`
330+
POST on `/subscriptions/subscription_id/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachineScaleSets/myScaleSet/osRollingUpgrade?api-version=2019-12-01`
331331
```
332332

333333
### Azure PowerShell

0 commit comments

Comments
 (0)