> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/compute/appsec-azure-177.md).

# Windows VM Without Automatic Updates misconfiguration detected in code

## Windows VM Without Automatic Updates misconfiguration detected in code

### Rule Details

|                        |                                         |
| ---------------------- | --------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_177                      |
| Category - Subcategory | Compute - Unsanctioned Resource Or Type |
| Provider               | AZURE                                   |
| Severity               | MEDIUM                                  |
| Framework              | ARM, Bicep, Terraform, Terraform Plan   |

### Impact

Automatic updates are crucial for maintaining the security and performance of systems. Regular updates address vulnerabilities that might be exploited, provide enhancements, and deliver crucial security patches. For Windows Virtual Machines (VMs) and Virtual Machine Scale Sets in Azure, enabling automatic updates ensures that these instances remain up-to-date with the latest patches from Microsoft.

This rule checks to ensure that Windows VMs and VM Scale Sets are configured to have automatic updates enabled.

### How to Fix

*Resources:*

* azurerm\_windows\_virtual\_machine
* azurerm\_windows\_virtual\_machine\_scale\_set

*Argument:*

* enable\_automatic\_updates

### Note: It's recommended to enable automatic updates on all Windows VM and VM Scale Set instances in Azure to ensure they receive the latest security patches and updates from Microsoft. \[source,go]

resource "azurerm\_windows\_virtual\_machine" "example" { name = "example-vm" location = azurerm\_resource\_group.example.location resource\_group\_name = azurerm\_resource\_group.example.name

## ... other configurations ...

* enable\_automatic\_updates = true }

resource "azurerm\_windows\_virtual\_machine\_scale\_set" "example" { name = "example-vmss" location = azurerm\_resource\_group.example.location resource\_group\_name = azurerm\_resource\_group.example.name

## ... other configurations ...

* enable\_automatic\_updates = true }

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/compute/appsec-azure-177.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.