You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Azure VM | Log Analytics agent VM extension for Windows/Linux | Agent is automatically upgraded by default unless you configured your Azure Resource Manager template to opt out by setting the property *autoUpgradeMinorVersion* to **false**. |
21
+
| Azure VM | Log Analytics agent VM extension for Windows/Linux | Agent is automatically upgraded by default [after the VM model changes](../../virtual-machines/extensions/features-linux.md#how-do-agents-and-extensions-get-updated), unless you configured your Azure Resource Manager template to opt out by setting the property *autoUpgradeMinorVersion* to **false**. |
22
22
| Custom Azure VM images | Manual install of Log Analytics agent for Windows/Linux | Updating VMs to the newest version of the agent needs to be performed from the command line running the Windows installer package or Linux self-extracting and installable shell script bundle.|
23
23
| Non-Azure VMs | Manual install of Log Analytics agent for Windows/Linux | Updating VMs to the newest version of the agent needs to be performed from the command line running the Windows installer package or Linux self-extracting and installable shell script bundle. |
24
24
@@ -290,4 +290,4 @@ Perform the following steps to configure the Log Analytics agent for Linux to re
290
290
291
291
- Review [Troubleshooting the Linux agent](agent-linux-troubleshoot.md) if you encounter issues while installing or managing the Linux agent.
292
292
293
-
- Review [Troubleshooting the Windows agent](agent-windows-troubleshoot.md) if you encounter issues while installing or managing the Windows agent.
293
+
- Review [Troubleshooting the Windows agent](agent-windows-troubleshoot.md) if you encounter issues while installing or managing the Windows agent.
Copy file name to clipboardExpand all lines: articles/virtual-machines/extensions/features-linux.md
+13-3Lines changed: 13 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -206,9 +206,9 @@ Moving the **command to execute** property to the **protected** configuration se
206
206
207
207
### How do agents and extensions get updated?
208
208
209
-
The Agents and Extensions share the same update mechanism. Some updates do not require additional firewall rules.
209
+
Agents and extensions share the same automatic update mechanism.
210
210
211
-
When an update is available, it is only installed on the VM when there is a change to extensions, and other VM Model changes such as:
211
+
When an update is available and automatic updates are enabled, the update is installed on the VM only after there is a change to an extension or after other VM model changes, such as:
212
212
213
213
- Data disks
214
214
- Extensions
@@ -217,8 +217,14 @@ When an update is available, it is only installed on the VM when there is a chan
217
217
- VM size
218
218
- Network profile
219
219
220
+
> [!IMPORTANT]
221
+
> The update is installed only after there is a change to the VM model.
222
+
220
223
Publishers make updates available to regions at different times, so it is possible you can have VMs in different regions on different versions.
221
224
225
+
> [!NOTE]
226
+
> Some updates might require additional firewall rules. See [Network access](#network-access).
227
+
222
228
#### Agent updates
223
229
224
230
The Linux VM Agent contains *Provisioning Agent Code* and *Extension Handling code* in one package, which cannot be separated. You can disable the *Provisioning Agent* when you want to provision on Azure using cloud-init. To do this, see [using cloud-init](../linux/using-cloud-init.md).
@@ -253,7 +259,9 @@ It is highly recommended that you always have auto update for the agent, [AutoUp
253
259
254
260
#### Extension updates
255
261
256
-
When an extension update is available, the Linux Agent downloads and upgrades the extension. Automatic extension updates are either *Minor* or *Hotfix*. You can opt in or opt out of extensions *Minor* updates when you provision the extension. The following example shows how to automatically upgrade minor versions in a Resource Manager template with *autoUpgradeMinorVersion": true,'*:
262
+
When an extension update is available and automatic updates are enabled, after a [change to the VM model](#how-do-agents-and-extensions-get-updated) occurs, the Linux Agent downloads and upgrades the extension.
263
+
264
+
Automatic extension updates are either *Minor* or *Hotfix*. You can opt in or opt out of extension *Minor* updates when you provision the extension. The following example shows how to automatically upgrade minor versions in a Resource Manager template with *"autoUpgradeMinorVersion": true,*:
257
265
258
266
```json
259
267
"publisher": "Microsoft.Azure.Extensions",
@@ -269,6 +277,8 @@ When an extension update is available, the Linux Agent downloads and upgrades th
269
277
270
278
To get the latest minor release bug fixes, it is highly recommended that you always select auto update in your extension deployments. Hotfix updates that carry security or key bug fixes cannot be opted out.
271
279
280
+
If you disable extension automatic updates or you need to upgrade a major version, use [az vm extension set](/cli/azure/vm/extension#az_vm_extension_set) and specify the target version.
281
+
272
282
### How to identify extension updates
273
283
274
284
#### Identifying if the extension is set with autoUpgradeMinorVersion on a VM
In the following example, the VM Access extension is used to reset the administrative password of a Windows VM to a temporary password. For more information on the VM Access extension, see [Reset Remote Desktop service in a Windows VM](/troubleshoot/azure/virtual-machines/reset-rdp). Once you have run this, you should reset the password at first login:
119
+
In the following example, the VM Access extension is used to reset the administrative password of a Windows VM to a temporary password. For more information on the VM Access extension, see [Reset Remote Desktop service in a Windows VM](/troubleshoot/azure/virtual-machines/reset-rdp). After you have run this, you should reset the password at first login:
120
120
121
121
```powershell
122
122
$cred=Get-Credential
@@ -247,9 +247,9 @@ These certificates secure the communication between the VM and its host during t
247
247
248
248
### How do agents and extensions get updated?
249
249
250
-
The Agents and Extensions share the same update mechanism. Some updates do not require additional firewall rules.
250
+
Agents and extensions share the same automatic update mechanism.
251
251
252
-
When an update is available, it is only installed on the VM when there is a change to extensions, and other VM Model changes such as:
252
+
When an update is available and automatic updates are enabled, the update is installed on the VM only after there is a change to an extension or other VM model changes, such as:
253
253
254
254
- Data disks
255
255
- Extensions
@@ -258,8 +258,14 @@ When an update is available, it is only installed on the VM when there is a chan
258
258
- VM size
259
259
- Network profile
260
260
261
+
> [!IMPORTANT]
262
+
> The update is installed only after there is a change to the VM model.
263
+
261
264
Publishers make updates available to regions at different times, so it is possible you can have VMs in different regions on different versions.
262
265
266
+
> [!NOTE]
267
+
> Some updates might require additional firewall rules. See [Network access](#network-access).
268
+
263
269
#### Listing Extensions Deployed to a VM
264
270
265
271
```powershell
@@ -283,7 +289,10 @@ To check what version you are running, see [Detecting installed Windows Guest Ag
283
289
284
290
#### Extension updates
285
291
286
-
When an extension update is available, the Windows Guest Agent downloads and upgrades the extension. Automatic extension updates are either *Minor* or *Hotfix*. You can opt in or opt out of extensions *Minor* updates when you provision the extension. The following example shows how to automatically upgrade minor versions in a Resource Manager template with *autoUpgradeMinorVersion": true,'*:
292
+
293
+
When an extension update is available and automatic updates are enabled, after a [change to the VM model](#how-do-agents-and-extensions-get-updated) occurs, the Windows Guest Agent downloads and upgrades the extension.
294
+
295
+
Automatic extension updates are either *Minor* or *Hotfix*. You can opt in or opt out of extension *Minor* updates when you provision the extension. The following example shows how to automatically upgrade minor versions in a Resource Manager template with *"autoUpgradeMinorVersion": true,*:
287
296
288
297
```json
289
298
"properties": {
@@ -300,6 +309,8 @@ When an extension update is available, the Windows Guest Agent downloads and upg
300
309
301
310
To get the latest minor release bug fixes, it is highly recommended that you always select auto update in your extension deployments. Hotfix updates that carry security or key bug fixes cannot be opted out.
302
311
312
+
If you disable extension automatic updates or you need to upgrade a major version, use [Set-AzVMExtension](/powershell/module/az.compute/set-azvmextension) and specify the target version.
313
+
303
314
### How to identify extension updates
304
315
305
316
#### Identifying if the extension is set with autoUpgradeMinorVersion on a VM
0 commit comments