Merge pull request #206 from MicrosoftDocs/main

9/23/2024 AM Publish
MicrosoftDocs · Sep 23, 2024 · 0146a21 · 0146a21
2 parents dd01af5 + ca64f16
commit 0146a21
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 2 deletions.
diff --git a/articles/virtual-machine-scale-sets/standby-pools-faq.md b/articles/virtual-machine-scale-sets/standby-pools-faq.md
@@ -57,6 +57,8 @@ Virtual machines in the standby pool inherit the same virtual machine profile as
 ### Can I change the size of my standby pool without needing to recreate it? 
 Yes. To change the size of your standby pool update the max ready capacity setting.  
 
+### Can a standby pool resource be moved?
+No. Standby Pools doesn't currently support that capability. If you need to move a standby pool, you can consider deleting it recreating it in another location.
 
 ### I created a standby pool and I noticed that some virtual machines are coming up in a failed state. 
 Ensure you have enough quota to complete the standby pool creation. Insufficient quota results in the platform attempting to create the virtual machines in the standby pool but unable to successfully complete the create operation. Check for multiple types of quotas such as Cores, Network Interfaces, IP Addresses, etc.

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
@@ -50,8 +50,8 @@ Register-AzProviderFeature -FeatureName MaxSurgeRollingUpgrade -ProviderNamespac
 ## Considerations
 
 - When using rolling upgrades with MaxSurge, new virtual machines are created using the latest scale set model to replace virtual machines using the old scale set model. These newly created virtual machines counts towards your overall core quota. Additionally, these new virtual machines have new IP addresses and are placed into an existing subnet. You also need to have enough IP address quota and subnet space available to deploy these newly created virtual machines. 
-
-- During the MaxSurge rolling upgrade processes, Azure performs a quota check before each new batch. If that quota check fails, the upgrade will default to a non-MaxSurge upgrade and be upgraded in place. 
+- During the MaxSurge rolling upgrade processes, Azure performs a quota check before each new batch. If that quota check fails, the upgrade will default to a non-MaxSurge upgrade and be upgraded in place.
+- When using rolling upgrades with MaxSurge on Virtual Machine Scale Sets with Uniform Orchestration, the new virtual machine that is created with the updated model to replace the virtual machine with the older model may be placed into a different update domain than the previous virtual machine. 
 
 ## MaxSurge vs in place upgrades