Skip to content

Commit f15ea2f

Browse files
Merge pull request #226439 from rpsqrd/auto-extension-upgrade
Auto extension upgrade timing guidance
2 parents 3693115 + 536dc98 commit f15ea2f

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/azure-arc/servers/manage-automatic-vm-extension-upgrade.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,10 @@ If an extension upgrade fails, Azure will try to repair the extension by perform
4444

4545
If you continue to have trouble upgrading an extension, you can [disable automatic extension upgrade](#manage-automatic-extension-upgrade) to prevent the system from trying again while you troubleshoot the issue. You can [enable automatic extension upgrade](#manage-automatic-extension-upgrade) again when you're ready.
4646

47+
### Timing of automatic extension upgrades
48+
49+
When a new version of a VM extension is published, it becomes available for installation and manual upgrade on Arc-enabled servers. For servers that already have the extension installed and automatic extension upgrade enabled, it may take up to 5 weeks for every server with that extension to get the automatic upgrade. Upgrades are issued in batches across Azure regions and subscriptions, so you may see the extension get upgraded on some of your servers before others. If you need to upgrade an extension immediately, follow the guidance to manually upgrade extensions using the [Azure portal](manage-vm-extensions-portal.md#upgrade-extensions), [Azure PowerShell](manage-vm-extensions-cli.md#upgrade-extensions) or [Azure CLI](manage-vm-extensions-powershell.md#upgrade-extension).
50+
4751
## Supported extensions
4852

4953
Automatic extension upgrade supports the following extensions:

0 commit comments

Comments
 (0)