> 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/cortex-xsoar-6-installation-guides/6.15/cortex-xsoar-installation-guide/system-requirements/cloud-deployment-specifications/azure-virtual-machines-deployment-guidelines.md).

# Azure Virtual Machines Deployment Guidelines

Cortex XSOAR 6.15 Azure VM deployment requirements, sizing, and best practices.

Azure Virtual Machine (VM) deployments have specific technical and sizing requirements and a set of Cortex XSOAR best practices.

After you configure and verify your Azure Virtual Machine, install the Cortex XSOAR Server.

**Supported Azure VM sizes**

Cortex XSOAR server installation is supported on the following Azure VM sizes.

| Instance Type                       | Instance Name |
| ----------------------------------- | ------------- |
| D-Series v4 - General Purpose       | D16as\_v4     |
| D48as\_v4                           |               |
| D96as\_v4                           |               |
| F-Series v2 - Compute-Optimized     | F48s\_v2      |
| F64s\_v2                            |               |
| F72s\_v2                            |               |
| H-Series - High Performance Compute | H16           |
| H16m                                |               |
| H16r                                |               |
| L-Series v2                         | L16s\_v2      |
| L48s\_v2                            |               |
| L80s\_v2                            |               |
| D-Series v3 - General Purpose       | D16s\_v3      |
| D48s\_v3                            |               |
| D64s\_v3                            |               |

{% hint style="info" %}

### Note

The guideline for VM selection is to start with a VM from at least the General Purpose family with a minimum of 16 vCPUs and 64 GB of memory.
{% endhint %}

**Supported Azure managed disk**

We recommend that you use a managed disk from the Premium SSD family with a minimum IOPS of 5000+ and minimum disk space of 500 GB.

**Network Security**

Inbound connections: Cortex XSOAR server requires that you open HTTPS port 443 for inbound connections.

Outbound connections: outbound ports depend on your integrations and specific requirements. By default, Azure Network Security groups allow all outbound traffic.

**Supported OS**

Cortex XSOAR supports server installation on these [Linux distributions](/cortex-xsoar-6-installation-guides/6.15/cortex-xsoar-installation-guide/system-requirements/cortex-xsoar-system-requirements.md).

**Azure Backup**

You can use Azure Snapshots to back up your Azure VM and disks. Use snapshots for incremental backups, point-in-time restoration, and to view historical data.


---

# 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/cortex-xsoar-6-installation-guides/6.15/cortex-xsoar-installation-guide/system-requirements/cloud-deployment-specifications/azure-virtual-machines-deployment-guidelines.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.