Overview
You deploy the management center virtual in Microsoft Azure using a solution template available in the Azure Marketplace. When you deploy the management center virtual using the Azure portal you can use an existing empty resource group and storage account (or create them new). The solution template walks you through a set of configuration parameters that provide the initial setup of your management center virtual, allowing you to login to the management center virtual web interface after first boot.
Management Center Virtual Requires 28 GB RAM for Upgrade (6.6.0+)
The management center virtual platform has introduced a new memory check during upgrade. The management center virtual upgrades to Version 6.6.0+ will fail if you allocate less than 28 GB RAM to the virtual appliance.
![]() Important |
As of the Version 6.6.0 release, lower-memory instance types for cloud-based management center virtual deployments (AWS, Azure) are fully deprecated. You cannot create new management center virtual instances using them, even for earlier versions. You can continue running existing instances. See Table 1. |
As a result of this memory check, we will not be able to support lower memory instances on supported platforms.
The management center virtual on Azure must be deployed in a virtual network (VNet) using the Resource Manager deployment mode. You can deploy the management center virtual in the standard Azure public cloud environment. The management center virtual in the Azure Marketplace supports the Bring Your Own License (BYOL) model.
The following table summarizes the Azure instances types that the management center virtual supports; those that Versions 6.5.x and earlier support, and those that Version 6.6.0+ support.
Platform |
Version 6.6.0+ |
Version 6.5.x and earlier* |
---|---|---|
Management Center Virtual |
Standard_D4_v2: 8 vCPUs, 28 GB |
Standard_D3_v2: 4 vCPUs, 14 GB |
— |
Standard_D4_v2: 8 vCPUs, 28 GB |
|
*Note that the management center virtual will no longer support the Standard_D3_v2 instance after Version 6.6.0 is released. Beginning with Version 6.6.0, you must deploy the management center virtual (any version) using an instance with at least 28 GB RAM. See Resizing Instances. |
Platform |
Version 7.3.0 |
---|---|
Management Center Virtual 300 (FMCv300) |
Standard_D32ds_v5: 32 vCPUs, 128 GB |
Deprecated Instances
You can continue running your current Version 6.5.x and earlier the management center virtual deployments using Standard_D3_v2, but you will not be able to launch new management center virtual deployments (any version) using this instance.
Resizing Instances
Because the upgrade path from any earlier version of management center virtual (6.2.x, 6.3.x, 6.4.x, and 6.5.x) to Version 6.6.0 includes the 28 GB RAM memory check, if you are using the Standard_D3_v2, you need to resize your instance type to Standard_D4_v2 (see Table 1).
You can use the Azure portal or PowerShell to resize your instance. If the virtual machine is currently running, changing its size will cause it to be restarted. Stopping the virtual machine may reveal additional sizes.
For instructions on how to resize your instance, see the Azure documentation “Resize a Windows VM” (https://docs.microsoft.com/en-us/azure/virtual-machines/windows/resize-vm).