---
title: "Deploying NIOS-X Servers from the Azure Marketplace"
canonical: "https://docs.infoblox.com/space/BloxOneInfrastructure/204800816/Deploying%20NIOS-X%20Servers%20from%20the%20Azure%20Marketplace"
format: markdown
---
You can download and deploy NIOS-X virtual servers directly from the Microsoft® Azure Marketplace. The NIOS-X virtual server is pre-configured for Microsoft Azure. 

## Prerequisites 

With the current image, you can choose a disk size ranging from 60GB to 2500GB, tailored to their specific requirements. Additionally, the following prerequisites are important:

- **Deploying a VM with Availability Zone:**
  - Ensure that your subscription and region have zonal deployment enabled.
  - Once enabled, there will be a quota for each region, including specific VM sizes. This quota must be sufficient to deploy a VM of the desired size in that region.
  - VM deployment supports all sizes but **Infoblox** recommends using Azure VM sizes, that support Accelerated Networking and meet the minimum CPU and memory requirements for NIOS-X. Azure VM size availability varies by region and subscription quota.
    Accelerated networking is not supported on the following VM families/series (including all sizes within those families):
    - Fals_v6 (example: Standard_F4als_v6)
    - Dasv6 / Dads_v6 (example: Standard_D2ads_v5, and the ads_v6 series)
    - Ebsv5 / Ebdsv6
    - Lsv2 / Lsv3 / Lasv3
- **Enabling Accelerated Networking:**
  - To enable accelerated networking, choose a VM size that supports this feature.
  - If you select a size that does not support accelerated networking, the corresponding checkbox will not be available or visible.

## Deploying NIOS-X server from the Azure Marketplace

To deploy a NIOS-X server from the Azure Marketplace:

1. In a browser window, go to the Microsoft Azure website.
2. Log in to your Microsoft Azure account.
3. In the Microsoft Azure Portal, enter `infoblox` as the search filter under **Marketplace services**, and then choose one of the Azure application offer plans from the search results, as follows:
  - **Infoblox NIOS-X Server Virtual Machine (BYOL)**: For deploying a NIOS-X server in Microsoft Azure to deliver Infoblox services, such as DNS, IPAM, or Threat Defense to instances in your Azure-based deployments.
4. Click **Create **and complete the following steps to deploy NIOS-X server for Azure.
5. On the** Basics** tab, configure the basic settings:
  - In the **Project details** section, do the following:
    - **Subscription**: Choose the subscription for which you want to create the virtual appliance.
    - **Resource group**: Choose the resource group from the drop-down list, or click **Create New** to create one.
  - In the **Instance details** section, do the following:
    - **Region**: From the drop-down list, select the region in which the virtual appliance resides. Note that the selected region will affect the **Availability options** and **Zone options**, which are available only if the selected region supports availability zones.
    - **Availability options**: This option appears only if the selected region supports availability zones. From the drop-down list, select **Availability zone** or **No infrastructure required**.
    - **Zone options**: This option appears only if the selected region supports availability zones and when you select **Availability zone** from **Availability options**. Select one of the following:
      - **Self-selected**: When you select this, the **Availability zone** option is visible.
        - **Availability zone**: From the drop-down list, select any available zone, such as **Zone 1,** if you have selected a supported **Region,** such as **East US**. Note that for certain regions, there are more than one available zones. When you deploy the VM, it will display the location (or region) and the zone in the **Essentials** section.
      - **Azure-selected**: When you select this, Azure evaluates the available zones within the selected region and places your VM in the zone that offers the best performance and reliability at the time of deployment.
    - **NIOS-X VM name**: Enter the name of the NIOS-X server.
    - **VM size**: The recommended VM flavor is **Standard_F8S_v2, **which is selected by default** (Scheduled for retirement on 15 November 2028) **however can deploy the appliance using this size and change it later before EOL.
      Optional: Once deployed, go to **NIOS-X-VM** -> Availability + scale -> Size -> chose the size
      You can also choose the size to **Standard_D8s_v5 **is equivalent to Standard_F8s_v2. You can click **Change size** to see all available options and choose a flavor that fits your business requirements. Click **Select** to save your selection.
    - **JOINTOKEN**: Enter the join token you obtained from the Cloud Service Portal. For information on how to obtain a join token, see *[Creating Join Tokens](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/87229997)*.
    - **HTTP Proxy**: This is optional. You can configure an HTTP or HTTPS proxy server to handle the requests.
6. Click **Next: Disks**.
7. On the **Disks** page, do the following:
  - **OS Disk Size**: Use the default disk size of **60 GB**. Resizing the OS disk is currently not working, so retain the default size.
  - **OS Disk type**: Choose the type of OS disk.   
To review the configured disk information, click **Settings** > **Disks** from the left navigation panel.
8. Click **Next: Networking **from the left navigation panel.
9. On the **Networking** page, do the following:
  - **Virtual network (VNET)**: Choose an existing virtual network or create a new one in which the virtual appliance resides. To create a new network, click **Create new** and complete the following in the **Create virtual network** panel:
    - **Name**: Enter the name of the virtual network.
    - **Address space**: Enter the range of the IP address space for the virtual network in CIDR format. Example: 10.xx.x.x/16.
  - **Subnet**: Choose the required subnet from the drop-down list.
  - **Public IP Address**:: If you want to communicate with the virtual appliance outside of the virtual network, choose an existing public IP address from the drop-down list or click **Create new** to create a new one.
  - **Enable IP Forwarding**: Select the check-box if you want to enable IP forwarding while deploying the VM. To do so, navigate to **Networking** > **Network Settings** from the left navigation panel. In the **Essentials** section, click the network interface, and then navigation to **Settings** > **IP configurations** from the left navigation panel. On the **IP Settings** page, you can see that the check box is enabled. You can enable or disable IP forwarding here in the furtuer based on your organization’s requirement.
  - **Enable accelerated networking**: Select the check-box if you want to enable accelerated Networking while deploying the VM.
    Navigate to **Networking** > **Network Settings** from the left navigation panel. In the **Essentials** section, click the network interface, and you can review the accelerated networking status. If you need to enable or disable accelerated networking in the future, click **Edit Accelerated Networking** in the top navigation bar to open the tab, make your changes, and save them.
10. On the **Advanced** page, do the following:
  - **Serial Console**: Choose **Yes** if you want to access the instance via a serial console.
  - **Storage account: **Choose an existing storage account from the dropdown list to use for boot diagnostics and serial console access. If you do not have a storage account, click **Create new** to create a standard storage account for boot diagnostics and access to the serial console of the running instance.
11. Click **Next: Review + Create**.
12. After you save the VM configuration, you can review the information in the **Summary** panel. If you need to change any configuration, you can return to **Configure VM settings** to do so.
13. Click **Create** to accept the configuration and deploy the new NIOS-X server in Azure.
14. To check the current status of the NIOS-X server, you can go to **Network > Services & Servers > Servers **in the Infoblox Portal. For more information about the server status, see *[Viewing Host Status](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/119210967)*.

> ⚠️ You cannot use the **IP Interface Settings** In the Infoblox Portal to modify IP configurations for the NIOS-X server in Azure. Instead, use the options provided in the Azure Cloud Portal to change IP configurations for the NIOS-X server.

> ⚠️ **Azure Static IP and DHCP Mode Display**:
> ⚠️ 
> ⚠️ Azure delivers all private IP addresses to virtual machines through its native DHCP service, even when the network interface is configured with a static IP in the Azure portal. Because of this, the Infoblox Portal displays **IPv4 Network Mode** as **DHCP** for NIOS-X servers deployed on Azure. This is expected behavior and it is recommended to verify that the IP address shown in the Infoblox Portal reflects the same static IP assigned in Azure.