---
title: "Deploying NIOS-X Servers in Azure Using a VHD Image"
canonical: "https://docs.infoblox.com/space/BloxOneInfrastructure/204670105/Deploying%20NIOS-X%20Servers%20in%20Azure%20Using%20a%20VHD%20Image"
format: markdown
---
> š Deploy from a VHD image only when your Azure environment is locked down and cannot use the Marketplace. Otherwise, use the recommended Marketplace method. See [Deploying NIOS-X Servers from the Azure Marketplace](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/204800816).
Before deploying the NIOS-X server, ensure that you have fulfilled the prerequisites, as described inĀ *[Microsoft Azure Deployment](https://docs.infoblox.com/space/BloxOneInfrastructure/204800676/Microsoft+Azure+Deployment#Prerequisite)*.
To deploy aĀ NIOS-X server in Microsoft Azure, complete the following:
1. Set up a Microsoft Azure account and create a resource manager in Azure. For information, refer to the Microsoft Azure documentation.
2. Download the *.vhd* package from the Infoblox Portal.Ā
3. Upload theĀ *.vhd* package to your Azure storage account.Ā
4. Create an image from the uploaded *.vhd* package.
5. Optionally, if you want to enable accelerated networking, create a NIC with accelerated networking enabled.
6. Deploy theĀ NIOS-X server from the image you created.Ā
> š If you prefer deploying theĀ NIOS-X server using the Azure CLI, ensure that you install the Azure CLI on Linux.
# Supported Azure VM FlavorsĀ
| | | | |
| --- | --- | --- | --- |
| **Overall DiskĀ ** | **# of vCPU** | **Memory Allocation** | **Azure FlavorĀ ** |
| 60 GB | Ā 8 | 16 GB | Standard_F4s |
# Downloading VHD Packages
To download the *.vh*d package, complete the following:
1. Log in to the Infoblox Portal.
2. Go to **System > Downloads**.
3. Go to theĀ **NIOS-X** section, click **NIOS-X Servers **drop-down and selectĀ **Download VHD**.
# Uploading VHD to Azure Storage Account
After you have downloaded the Azure* .vhd* package from the Infoblox Portal, you can upload the package to your Azure storage account using theĀ Docker commands (if you have a Docker environment) or Azure commands.
Before using the Docker or Azure commands, ensure that you have created a storage account. Refer to the *[Microsoft Azure Documentation](https://learn.microsoft.com/en-us/azure/storage/common/storage-account-create?tabs=azure-portal)* for detailed instructions. Record the `storage_account_name` and `storage_account_access_key` for use in the commands. You can find the access key under **Security + Networking** > **Access Keys** for the storage account.
## Using Docker Commands to Upload VHD
In your Docker environment, enter the following commands:
`docker run --rm -v :/vhd -v $HOME/.azure:$HOME/.azure infoblox/azurevhdutils upload`
`--localvhdpath /vhd/.vhd --stgaccountname --stgaccountkey `
`--containername --blobname .vhd`
## Using Azure Commands to Upload VHD
To use the Azure commands, you need to first build theĀ *Azure-vhd-utils* binary from Git. The *Azure-vhd-utils* binary can be built from the public Git repo atĀ *[https://github.com/microsoft/azure-vhd-utils](https://github.com/microsoft/azure-vhd-utils)**.*
> ā ļø ### Note
> ā ļø
> ā ļø Azure only supports disks with a fixed size format; if you use *azure-vhd-utils* to perform the upload, it will convert the image to a fixed size format.
To build theĀ *Azure-vhd-utils* binary, complete the following:Ā
1. Run the `mkdir ~/tmp` command to make a temporary directory.
2. Run the `cp -r ~/upload/src/`[github.com/Microsoft/azure-vhd-utils](http://github.com/Microsoft/azure-vhd-utils)` ~/tmp` command to copy *azure-vhd-utils* to the temporary directory.
3. Run the `cd ~/tmp/azure-vhd-utils` command.
4. Run the `make` command to install *azure-vhd-utils*.
If the command displays the **if exec: "gcc": executable file not found in $PATH **error message, run the `export CGO_ENABLED="0"` command and then run the `make` command again.
5. Run the `sudo cp azure-vhd-utils /usr/bin/` command.
After you have built theĀ *Azure-vhd-utils* binary, run the following command to upload the *.vhd* file to Azure using the following format:
`azure-vhd-utils upload --localvhdpath --stgaccountname storage_account_name> --stgaccountkey `
`--containername --blobname .vhd`
# Creating an Image from the Uploaded VHD
After you have successfully uploaded the *.vhd* file to the Azure storage account, you can create an image in Azure using one of the following methods:
- Microsoft Azure CLIĀ
- Microsoft Azure Portal
## Using Azure CLI to Create an Image
To create an image using the Azure CLI, complete the following:
1. Sign in to the Azure CLI using your account credentials.
2. Create an image using the uploaded VHD from the storage account.
For Gen 1:
`az image create -g "" -n .vhd --os-type Linux --source `
For Gen 2:
`az image create -g "" -n --os-type Linux --hyper-v-generation V2 --source `
Optionally, if you want to enable accelerate networking, create a NIC using the following command:
`az network nic create --resource-group "" --name --location --accelerated-networking true --vnet-name --subnet --network-security-group `
> š You must use the Azure CLI to create a NIC for accelerated networking. You cannot do so through the Azure Portal.
Optionally, if you want to enable dualstack networking, see [https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/2123792420](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/2123792420).
## Using Azure Portal to Create an Image
To create an image using the Azure Portal, complete the following:
1. Log in to your Azure Portal.
2. Go to **Images**, and click **Create** to create an imageĀ from the *.vh*d package in the storage account.
3. Enter all the relevant fields. Select either Gen 1 or Gen 2 VM generation. In the **Storage blob** field, ensure that you navigate to and locate the *.vhd* file you uploaded to the storage account.
4. Click **Review + Create** to review the image before you create it.
> Macro (inline-media-image)
# Deploying NIOS-X Server (VM) from the Image
After you have created an image, you can deploy the NIOS-X server using one of the following methods:
- Microsoft Azure CLI
- Microsoft Azure Portal
> š If you have enabled accelerate networking, you must use the Azure CLI to deploy the NIOS-X server.
## Using the Azure CLI to Deploy the NIOS-X Server
1. Sign in to the Azure CLI using your account credentials.
2. Run the following command to deploy the NIOS-X server:
`az vm create --resource-group "" --name < --nics --location --image --admin-username azureuser --public-ip-address "" --custom-data userdata --size Standard_F4s`
## Using the Azure Portal to Deploy the NIOS-X Server
1. Log in to your Azure Portal.
2. Create a virtual machine using the image you created. In the **Size** field, ensure that you select the supported flavor, which isĀ **Standard_F4S**.
3. In the **Custom data** field, ensure that you add the parameters that are specific to your NIOS-X server. You can download a YML file and customize your user data file. You can then copy the information and paste it here. For information on how to use the *userdata* file, see *[YML and JSON Templates](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneThreatDefense/pages/35408412)*.
Note that when you enter the following schema in the **Custom data** field, ensure that you add a space before the keys you want to include for host_setup. In this case, you must include a space beforeĀ **jointoken**, and then enter the join token value you obtained from the Infoblox Portal. For information about how to obtain a join token, seeĀ *[Creating Join Tokens](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/87229997)*.`Ā Ā `
4. Optionally, you can resize the disk size above 64 GB. In the **Disk** tab of the Azure Portal, select the desired disk size from the **OS disk size** drop-down list.
> ā ļø When resizing the disk, use the disk resize `user-data` file from *[Appendix B: YAML and JSON Templates](https://docs.infoblox.com/space/BloxOneThreatDefense/35408412)*. Skipping any of the specified values may prevent the disk from expanding, so the server cannot use the additional space.
5. Click **Review + Create** to launch the NIOS-X server.
6. 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 Server Status](https://infoblox-docs.atlassian.net/wiki/pages/createpage.action?spaceKey=BloxOneInfrastructure&title=Viewing%20Host%20Information)*.
> ā ļø **Note**
> ā ļø
> ā ļø You cannot use the IP Interface Settings In 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. Once an Azure host is deployed, additional interfaces cannot be added. All required interfaces must be configured during the initial deployment. If interfaces are initially added through the Azure Portal, they will persist in the Infoblox Portal. Even if they are later deleted from the Azure Portal, they will still be visible in the Infoblox Portal. However, this does not affect the functionality of other interfaces.