Merge pull request #758 from MicrosoftDocs/main

12/13 11:00 AM IST Publish
MicrosoftDocs · Dec 13, 2024 · 5ee0afc · 5ee0afc
2 parents 2d253c1 + ece9e3b
commit 5ee0afc
Show file tree

Hide file tree

Showing 3 changed files with 7 additions and 3 deletions.
diff --git a/...ual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md b/...ual-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: <br>
+> `Register-AzProviderFeature -FeatureName MaxSurgeRollingUpgrade -ProviderNamespace Microsoft.Compute`<br><br>
 > To update the image reference version during an upgrade, register the following feature flag: <br>
 > `Register-AzProviderFeature -FeatureName ImageReferenceUpgradeForVmoVMs -ProviderNamespace Microsoft.Compute`
 

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
@@ -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: <br>
+> `Register-AzProviderFeature -FeatureName MaxSurgeRollingUpgrade -ProviderNamespace Microsoft.Compute` <br><br>
 > To update the image reference version during an upgrade, register the following feature flag: <br>
 > `Register-AzProviderFeature -FeatureName ImageReferenceUpgradeForVmoVMs -ProviderNamespace Microsoft.Compute`
 

diff --git 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*.