Uploading an Azure-compliant VHD to Azure and creating an Azure Image

To deploy a virtual machine in Microsoft Azure, an Azure-compliant VHD file that contains the Security Access Manager firmware must be uploaded to a storage account and then used to create an image. The created image artifact acts as a template and can be deployed multiple times.

1. Upload the VHD file using the Azure Portal.
   1. In the Azure Portal, select Storage Accounts.
   2. Select the storage account where the Security Access Manager VHD file will be uploaded to.
      • If you do not have a storage account, click Add to create one.
      • Note that the selected location will dictate where the image can be created and subsequently deployed to.
   3. Under BLOB SERVICE, select Containers.
   4. Select a container to upload the Security Access Manager VHD file to.
      • If you do not have a storage container, click Add Container to create one.
   5. Click Upload and select the Azure-compliant Security Access Manager VHD file to upload.
      • Ensure that the Blob type is set to Page Blob.

   This process might take a long time depending on your network connection and the location of your Azure storage account.

2. Create an image using the Azure Portal.
   1. In the Azure Portal, select Images.
   2. Click Add to create a new image.
      1. Give the image a name. Remember that this image is a template that will later be deployed to a virtual machine with a different name.
      2. Ensure that the location is the same as the location of your storage account.
      3. In the OS disk section:
         1. Select Linux and the OS type.
         2. Click Browse on the Storage Blob field. A new panel will list your storage accounts. Using this panel, navigate through the storage account and container to locate the Security Access Manager VHD that was uploaded.
      4. Click Create to begin the image creation process. This process typically takes minutes to complete.
   3. When the process has completed, return to the Images panel and verify that the new image was created.

   This image can now be used to deploy new Security Access Manager virtual machines in Azure.