From a0e67fe142e17f54b6cad052ec5e36e6ea118fab Mon Sep 17 00:00:00 2001 From: Micah McKittrick <32313503+mimckitt@users.noreply.github.com> Date: Thu, 12 Dec 2024 15:41:17 -0800 Subject: [PATCH 1/5] Update virtual-machine-scale-sets-maxsurge.md --- .../virtual-machine-scale-sets-maxsurge.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-maxsurge.md b/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-maxsurge.md index a280518bab..bbc5c8587d 100644 --- a/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-maxsurge.md +++ b/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-maxsurge.md @@ -14,6 +14,8 @@ ms.custom: upgradepolicy. maxsurge, ignite-2024 Rolling upgrades with MaxSurge can help improve service uptime during upgrade events. With MaxSurge enabled, new instances are created in batches using the latest scale model. When the new instances are fully created and healthy, the scale set then deletes instances in batches matching the old scale set model. The process continues until all instances are brought up-to-date. > [!NOTE] +> To configure MaxSurge upgrades, register the following feature flag:
+> 'Register-AzProviderFeature -FeatureName MaxSurgeRollingUpgrade -ProviderNamespace Microsoft.Compute' > To update the image reference version during an upgrade, register the following feature flag:
> `Register-AzProviderFeature -FeatureName ImageReferenceUpgradeForVmoVMs -ProviderNamespace Microsoft.Compute` From 4ff9bda55003f4571abb7cdf6673ac7590152492 Mon Sep 17 00:00:00 2001 From: Micah McKittrick <32313503+mimckitt@users.noreply.github.com> Date: Thu, 12 Dec 2024 15:41:59 -0800 Subject: [PATCH 2/5] Update virtual-machine-scale-sets-configure-rolling-upgrades.md --- .../virtual-machine-scale-sets-configure-rolling-upgrades.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md b/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md index 8ff6bfed34..ac5b679002 100644 --- a/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md +++ b/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md @@ -16,6 +16,8 @@ Using a rolling upgrade policy is the safest way to apply updates to instances i Rolling upgrade policy is best suited for production workloads. > [!NOTE] +> > To configure MaxSurge upgrades, register the following feature flag:
+> `Register-AzProviderFeature -FeatureName MaxSurgeRollingUpgrade -ProviderNamespace Microsoft.Compute` > To update the image reference version during an upgrade, register the following feature flag:
> `Register-AzProviderFeature -FeatureName ImageReferenceUpgradeForVmoVMs -ProviderNamespace Microsoft.Compute` From a2fc600814a66dd78886f0be5da033cedfb9c604 Mon Sep 17 00:00:00 2001 From: Micah McKittrick <32313503+mimckitt@users.noreply.github.com> Date: Thu, 12 Dec 2024 15:42:13 -0800 Subject: [PATCH 3/5] Update virtual-machine-scale-sets-configure-rolling-upgrades.md --- .../virtual-machine-scale-sets-configure-rolling-upgrades.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md b/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md index ac5b679002..f22bed9896 100644 --- a/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md +++ b/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md @@ -17,7 +17,7 @@ Rolling upgrade policy is best suited for production workloads. > [!NOTE] > > To configure MaxSurge upgrades, register the following feature flag:
-> `Register-AzProviderFeature -FeatureName MaxSurgeRollingUpgrade -ProviderNamespace Microsoft.Compute` +> `Register-AzProviderFeature -FeatureName MaxSurgeRollingUpgrade -ProviderNamespace Microsoft.Compute`

> To update the image reference version during an upgrade, register the following feature flag:
> `Register-AzProviderFeature -FeatureName ImageReferenceUpgradeForVmoVMs -ProviderNamespace Microsoft.Compute` From 9ac53e8562a3eba568140c78ae632ff0d5f68a08 Mon Sep 17 00:00:00 2001 From: Micah McKittrick <32313503+mimckitt@users.noreply.github.com> Date: Thu, 12 Dec 2024 15:42:53 -0800 Subject: [PATCH 4/5] Format code block in documentation --- .../virtual-machine-scale-sets-maxsurge.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-maxsurge.md b/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-maxsurge.md index bbc5c8587d..bcf16a2429 100644 --- a/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-maxsurge.md +++ b/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-maxsurge.md @@ -15,7 +15,7 @@ Rolling upgrades with MaxSurge can help improve service uptime during upgrade ev > [!NOTE] > To configure MaxSurge upgrades, register the following feature flag:
-> 'Register-AzProviderFeature -FeatureName MaxSurgeRollingUpgrade -ProviderNamespace Microsoft.Compute' +> `Register-AzProviderFeature -FeatureName MaxSurgeRollingUpgrade -ProviderNamespace Microsoft.Compute`

> To update the image reference version during an upgrade, register the following feature flag:
> `Register-AzProviderFeature -FeatureName ImageReferenceUpgradeForVmoVMs -ProviderNamespace Microsoft.Compute` From 3462f50c6fecac39f57c654c24ce1f9aed0abb87 Mon Sep 17 00:00:00 2001 From: Matt McInnes Date: Thu, 12 Dec 2024 16:12:25 -0800 Subject: [PATCH 5/5] Update attach-os-disk.md --- articles/virtual-machines/attach-os-disk.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/articles/virtual-machines/attach-os-disk.md b/articles/virtual-machines/attach-os-disk.md index dfc15a3e1f..4f63ae74d0 100644 --- a/articles/virtual-machines/attach-os-disk.md +++ b/articles/virtual-machines/attach-os-disk.md @@ -4,11 +4,11 @@ description: Create a new Windows VM by attaching a specialized OS disk. author: ju-shim ms.service: azure-virtual-machines ms.topic: how-to -ms.date: 03/30/2023 +ms.date: 12/12/2024 ms.author: jushiman ms.custom: devx-track-azurepowershell --- -# Create a VM from a specialized disk by using PowerShell +# Create a VM from a specialized disk using PowerShell **Applies to:** :heavy_check_mark: Windows VMs @@ -136,7 +136,7 @@ To enable communication with the virtual machine in the virtual network, you'll $pip = New-AzPublicIpAddress ` -Name $ipName -ResourceGroupName $destinationResourceGroup ` -Location $location ` - -AllocationMethod Dynamic + -AllocationMethod Static ``` 2. Create the NIC. In this example, the NIC name is set to *myNicName*.