Skip to content

Commit e402777

Browse files
Merge pull request #298339 from SnehaSudhirG/16April-AUM-FAQ
Updated the info in scenario - Arc enabled server
2 parents df48bb6 + 055b80a commit e402777

File tree

1 file changed

+14
-13
lines changed

1 file changed

+14
-13
lines changed

articles/update-manager/update-manager-faq.md

Lines changed: 14 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.service: azure-update-manager
55
ms.custom:
66
- ignite-2024
77
ms.topic: faq
8-
ms.date: 10/10/2024
8+
ms.date: 04/16/2025
99
author: snehasudhirG
1010
ms.author: sudhirsneha
1111
#Customer intent: As an implementer, I want answers to various questions.
@@ -26,13 +26,13 @@ Following are the benefits of using Azure Update Manager:
2626
- Manage [extended security updates (ESUs)](/azure/azure-arc/servers/prepare-extended-security-updates) for your Azure Arc-enabled Windows Server 2012/2012 R2 machines. Get consistent experience for deployment of ESUs and other updates.
2727
- Define recurring time windows during which your machines receive updates and might undergo reboots using [scheduled patching](scheduled-patching.md). Enforce machines grouped together based on standard Azure constructs (Subscriptions, Location, Resource Group, Tags etc.) to have common patch schedules using [dynamic scoping](dynamic-scope-overview.md). Sync patch schedules for Windows machines in relation to patch Tuesday, the unofficial term for month.
2828
- Enable incremental rollout of updates to Azure VMs in off-peak hours using [automatic VM guest patching](/azure/virtual-machines/automatic-vm-guest-patching) and reduce reboots by enabling [hotpatching](updates-maintenance-schedules.md#hotpatching).
29-
- Automatically [assess](assessment-options.md#periodic-assessment) machines for pending updates every 24 hours, and flag machines that are out of compliance. Enforce enabling periodic assessments on multiple machines at scale using [Azure Policy](periodic-assessment-at-scale.md).
29+
- [assess](assessment-options.md#periodic-assessment) automatically the machines for pending updates every 24 hours, and flag machines that are out of compliance. Enforce enabling periodic assessments on multiple machines at scale using [Azure Policy](periodic-assessment-at-scale.md).
3030
- Create [custom reports](workbooks.md) for deeper understanding of the updates data of the environment.
3131
- Granular access management to Azure resources with Azure roles and identity, to control who can perform update operations and edit schedules.
3232

3333
### How does the new Azure Update Manager work on machines?
3434

35-
Whenever you trigger any Azure Update Manager operation on your machine, it pushes an extension on your machine that interacts with the VM agent (for Azure machine) or Arc agent (for Arc-enabled machines) to fetch and install updates.
35+
Whenever you trigger any Azure Update Manager operation on your machine, it pushes an extension on your machine. It interacts with the VM agent (for Azure machine) or Arc agent (for Arc-enabled machines) to fetch and install updates.
3636

3737
### Is enabling Azure Arc mandatory for patch management for machines not running on Azure?
3838

@@ -48,7 +48,7 @@ All Azure Update Manager data is stored in Azure Resource Graph (ARG). Custom re
4848

4949
### Are there programmatic ways to interact with Azure Update Manager?
5050

51-
Yes, Azure Update Manager supports REST API, CLI and PowerShell for [Azure machines](manage-vms-programmatically.md) and [Arc-enabled machines](manage-arc-enabled-servers-programmatically.md).
51+
Yes, Azure Update Manager supports REST API, CLI, and PowerShell for [Azure machines](manage-vms-programmatically.md) and [Arc-enabled machines](manage-arc-enabled-servers-programmatically.md).
5252

5353
### Do I need MMA or AMA for using Azure Update Manager to manage my machines?
5454

@@ -72,7 +72,7 @@ Follow the [guidance](guidance-migration-automation-update-management-azure-upda
7272

7373
### LA agent (also known as MMA) is retiring and will be replaced with AMA. Is it necessary to move to Update Manager or can I continue to use Automation Update Management with AMA?
7474

75-
The Azure Log Analytics agent, also known as the Microsoft Monitoring Agent (MMA) will be [retired in August 2024](https://azure.microsoft.com/updates/were-retiring-the-log-analytics-agent-in-azure-monitor-on-31-august-2024/). Azure Automation Update management solution relies on this agent and might encounter issues once the agent is retired. It doesn't work with Azure Monitoring Agent (AMA) either.
75+
The Azure Log Analytics agent, also known as the Microsoft Monitoring Agent (MMA) has [retired in August 2024](https://azure.microsoft.com/updates/were-retiring-the-log-analytics-agent-in-azure-monitor-on-31-august-2024/). Azure Automation Update management solution relies on this agent and might encounter issues once the agent is retired. It doesn't work with Azure Monitoring Agent (AMA) either.
7676

7777
Therefore, if you're using Azure Automation Update management solution, you're encouraged to move to Azure Update Manager for their software update needs. All capabilities of Azure Automation Update Management Solution will be available on Azure Update Manager before the retirement date. Follow the [guidance](guidance-migration-automation-update-management-azure-update-manager.md) to move update management for your machines to Azure Update Manager.
7878

@@ -86,7 +86,7 @@ Yes. Automation Update Management isn't compatible with AMA. We recommend that y
8686

8787
Automation Update Management uses Log Analytics workspace for storing updates data. Azure Update Manager uses Azure Resource Graph for data storage. You can continue using the historical data in Log Analytics workspace for old data and use Azure Resource Graph for new data.
8888

89-
### I have some reports/dashboards built for Automation Update Management. How do I move those?
89+
### I have some reports/dashboards built for Automation Update Management. How do I move them?
9090

9191
You can rebuild custom dashboards/reports on updates data from Azure Resource Graph (ARG). For more information, see [how to query ARG data](query-logs.md) and [sample queries](sample-query-logs.md). These are a few built-in workbooks that you can modify as per your needs to get started. For more information, see [how to create reports using workbooks](manage-workbooks.md).
9292

@@ -97,7 +97,7 @@ Arc-enabling of machines is a prerequisite for management with Update Manager. T
9797

9898
### If I have been using pre and post-script or alerting capability in Automation Update management, how can I move to Azure Update Manager?
9999

100-
These capabilities will be added to Azure Update Manager. For more information, see [guidance for moving from Automation Update management to Azure Update Manager](guidance-migration-automation-update-management-azure-update-manager.md).
100+
These capabilities are added to Azure Update Manager. For more information, see [guidance for moving from Automation Update management to Azure Update Manager](guidance-migration-automation-update-management-azure-update-manager.md).
101101

102102
### I'm using Automation Update Management on sovereign clouds; will I get region support in the new Azure Update Manager?
103103

@@ -121,26 +121,27 @@ An Arc-enabled server is considered managed by Azure Update Manager for days on
121121

122122
### Are there scenarios in which Arc-enabled Server isn't charged for Azure Update Manager?
123123

124-
An Arc-enabled server managed with Azure Update Manager is not charged in following scenarios:
124+
An Arc-enabled server managed with Azure Update Manager isn't charged in following scenarios:
125125
- If the machine is enabled for delivery of Extended Security Updates (ESUs) enabled by Azure Arc.
126-
- Microsoft Defender for Servers Plan 2 is enabled for the subscription hosting the Arc-enabled server. However, if customer is using Defender using Security connector, they will be charged.
126+
- Microsoft Defender for Servers Plan 2 is enabled for the subscription hosting the Arc-enabled server. However, if customer is using Defender using Security connector, they'll be charged.
127+
- Windows Server licenses that have active Software Assurances or Windows Server licenses that are active subscription licenses, and Windows Server pay-as-you-go enabled by Azure Arc. For more information, see [Windows Server Management enabled by Azure Arc](/azure/azure-arc/servers/windows-server-management-overview).
127128

128129
### Will I be charged if I move from Automation Update Management to Update Manager?
129130

130-
Customers will not be charged for already existing Arc-enabled servers which were using Automation Update Management for free as of Sep 1, 2023. Any new Arc-enabled machines which will be onboarded to Azure Update Manager in the same subscription will also be exempted from charge. This exception will be provided till LA agent retires. Post that date, these customers will be charged.
131+
Customers won't be charged for already existing Arc-enabled servers which were using Automation Update Management for free as of September 1, 2023. Any new Arc-enabled machines which are onboarded to Azure Update Manager in the same subscription will also be exempted from charge. This exception is provided till LA agent retires. Post that date, these customers are charged.
131132

132133
### I'm a Defender for Server customer and use update recommendations powered by Azure Update Manager namely "periodic assessment should be enabled on your machines" and "system updates should be installed on your machines". Would I be charged for Azure Update Manager?
133134

134135
If you have purchased a Defender for Servers Plan 2, then you won't have to pay to remediate the unhealthy resources for the above two recommendations. But if you're using any other Defender for server plan for your Arc machines, then you would be charged for those machines at the daily prorated $0.16/server by Azure Update Manager.
135136

136137
### Is Azure Update Manager chargeable on Azure Local?
137-
Azure Update Manager is not charged for:
138-
- Management of Azure Local instance(s) via **Azure Local** and [Azure Update Manager on Azure Local](/azure/azure-local/update/azure-update-manager-23h2)
138+
Azure Update Manager isn't charged for:
139+
- Management of Azure Local instances via **Azure Local** and [Azure Update Manager on Azure Local](/azure/azure-local/update/azure-update-manager-23h2)
139140
- [Arc-enabled Azure Local VMs](/azure/azure-local/manage/azure-arc-vm-management-overview) created via the Arc Resource Bridge. For example *Machine-Azure Arc (Azure Local)* resource.
140141

141142
All other resources including, but not limited to the following will be charged.
142143
- Management of individual Azure Local machines. For example, *Machine - Azure Arc* resource or *Azure Update Manager - Machines*.
143-
- All VMs on Azure Local that are not created by Arc resource bridge - VMs projected as Arc-enabled servers and/or VMs on Azure Local managed by Azure Arc-enabled SCVMM.
144+
- All VMs on Azure Local that is not created by Arc resource bridge - VMs projected as Arc-enabled servers and/or VMs on Azure Local managed by Azure Arc-enabled SCVMM.
144145

145146

146147
## Update Manager support and integration

0 commit comments

Comments
 (0)