Azure Feature Compatibility with Microsoft HPC Pack


Updated: December 21, 2016

Applies To: HPC Pack 2016, Microsoft HPC Pack 2012, Microsoft HPC Pack 2012 R2

This topic lists many of the Azure features that can be used in Azure burst deployments with HPC Pack. Certain features and services are compatible with only certain versions of HPC Pack, and some require additional configuration in the Azure subscription or the Azure node template that is used for the deployment. For more information about configuring an Azure node template to use these features, see Configuring an Azure Node Template for Microsoft HPC Pack.

For general requirements to add Azure nodes to a Windows HPC cluster, see Requirements to Add Azure Nodes with Microsoft HPC Pack.

Azure burst deployments with HPC Pack are supported in subscriptions in the global Azure service. Starting in HPC Pack 2012 R2 Update 1, customers who have a subscription in the Azure China service can also deploy Azure nodes with HPC Pack. To change the Azure service endpoint used for Azure burst deployments, run the Update-HpcAzureEndpoint.ps1 script that is provided in the %CCP_HOME%bin folder on the head node. For more information about the Azure China Service operated by 21ViaNet, see

System_CAPS_ICON_note.jpg Note

  • Burst deployments to worker role instances use the classic deployment model. You can't use Azure resources that are created in the Azure Resource Manager deployment model.
  • In some cases, Azure features or services that are in preview or beta can be configured in an Azure node template, if your subscription and your version of HPC Pack enable them. Before you use a preview or beta feature, review the terms of use. We recommend that you only use preview or beta features in test or proof-of-concept deployments of Azure nodes, not in production deployments.
  • Certain versions of HPC Pack may include settings to configure Azure features that are now deprecated or retired, and which therefore should not be used in Azure burst deployments. For more information, see Deprecated or retired features in this topic.
FeatureDescriptionMinimum version of Microsoft HPC PackAdditional requirements
Worker role nodes- Run an Azure guest operating system that is substantially similar to Windows Server
- Are automatically deployed with HPC Pack components
- Can use Azure virtual machines of various sizes (see Azure worker role instance sizes that can be used in burst deployments)
- Optionally mount an application VHD file (an Azure drive)
 Note: Azure drive is currently in preview.
HPC Pack 2008 R2 with SP1

Note: Mounting an application VHD requires at least HPC Pack 2012
- For information about the guest operating systems that can run on Azure nodes, see Configure the Azure Node Role in a Node Template.
- To mount an application VHD, a compatible VHD must be created and uploaded as a page blob to the Azure storage account for the deployment. For more information, see Mount an Application VHD on Azure Worker Nodes.
Azure Virtual Network (classic)- Enables secure site-to-site network connectivity between Azure and the on-premises network – for example, to connect Azure nodes to an on-premises license server
- Enables connectivity between a head node configured on an Azure virtual machine and Azure worker nodes
HPC Pack 2012 

Note: Starting with HPC Pack 2012 with SP1, connectivity between Azure and an on-premises network can be configured using a VPN hardware device or the Routing and Remote Access service (RRAS) running in Windows Server 2012.
- A classic Azure virtual network must be configured in the subscription. To enable connectivity to an on-premises network, use a supported VPN gateway, configure a gateway subnet, and specify a local network to connect to. For more information, see Understanding Azure Virtual Network for Azure Node Deployments with Microsoft HPC Pack.
Remote Desktop Connection- Allows remote connections to Azure nodesHPC Pack 2008 R2 with SP2- To configure the credentials, see Configure Remote Desktop Credentials to Connect to Azure Nodes.
Azure startup script- Runs a script, such as a batch file, that configures a set of Azure nodes when they are started (provisioned)HPC Pack 2008 R2 with SP2- A startup script must be created, packaged, and uploaded to the Azure storage account for the deployment. For more information, see Use a Startup Script for Azure Nodes.

The following table lists the Azure worker role instance sizes that you can choose from when adding Azure nodes to a Windows HPC cluster. The minimum version of HPC Pack that supports each size is listed. For details about the sizes for virtual machine-based compute resources, see Sizes for Cloud Services. For pricing information, see Cloud Services Pricing Details.

Available sizes for worker role instances can differ from those for Azure virtual machines.

System_CAPS_ICON_note.jpg Note

Starting with the HPC Pack 2012 R2 Update 1 release, HPC Pack automatically detects and allows you to select additional supported worker role sizes if they are introduced later to the Azure platform.

Worker role sizeMinimum version of HPC Pack
SmallHPC Pack 2008 R2 with SP1
MediumHPC Pack 2008 R2 with SP1
LargeHPC Pack 2008 R2 with SP1
Extra LargeHPC Pack 2008 R2 with SP1
A5HPC Pack 2012 R2
A6HPC Pack 2012 with SP1
A7HPC Pack 2012 with SP1
A8HPC Pack 2012 R2
A9HPC Pack 2012 R2
STANDARD_D1 – STANDARD_D14HPC Pack 2012 R2 Update 1

The following Azure features are retired. These features are no longer available for use in Azure node deployments with versions of HPC Pack that provide related configuration settings.

  • VM Role (beta) Retirement date: May 2013

    System_CAPS_ICON_note.jpg Note

    The node template settings to select VM role instances for deployments of Azure nodes are removed as of HPC Pack 2012 with SP1.

  • Azure Connect (CTP) Retirement date: July 2013

    System_CAPS_ICON_note.jpg Note

    The node template settings to enable Azure Connect in deployments of Azure nodes are removed as of HPC Pack 2012.

Burst to Azure Worker Instances with Microsoft HPC Pack
Azure Cloud Services Support Lifecycle Policy
Azure Subscription and Service Limits, Quotas, and Constraints