Cisco Secure Firewall Management Center Virtual Getting Started Guide

Deploy the Firewall Management Center Virtual on Azure

Updated: February 5, 2026

Overview

Provides instructions to deploy Cisco Secure Firewall Management Center Virtual (FMCv) on Azure by preparing the Azure environment and configuring the required resources.

You can deploy the Firewall Management Center Virtual as a virtual machine on the Microsoft Azure public cloud.

The Firewall Management Center Virtual is supported on Microsoft Azure starting with Cisco software version 6.4 and later.

Overview

An overview of deploying Management Center Virtual in Microsoft Azure using supported VM sizes and required configurations. Understand memory requirements, deprecated sizes, and resizing guidance to ensure successful upgrades and compliant deployments across supported versions.

Prerequisites

Learn about the prerequisites for deploying Management Center Virtual in Microsoft Azure. Understand how to verify required accounts, marketplace access, and licensing through a Cisco Smart Account before deployment to ensure compatibility and a successful setup.

Guidelines and Limitations

Consider these guidelines and limitations for deploying Management Center Virtual on Azure. Learn about the supported VM sizes, licensing requirements, shutdown procedures, and unsupported capabilities to avoid configuration issues. Use this information to plan a compliant deployment and operate the virtual appliance within platform constraints.

Resources Created During Deployment

Learn how to identify the Azure resources created when deploying Management Center Virtual. Understand the virtual machine, resource group, network security group, public IP, routing table, and storage components that are provisioned so you can manage, modify, or remove them correctly after deployment.

Deploy the Firewall Management Center Virtual

Learn how to deploy Management Center Virtual in Azure using Marketplace solution templates or ARM templates. Understand the available offer types, required selections, and deployment methods so you can provision the virtual appliance and its associated resources correctly in your Azure environment.

Deploy the Azure Marketplace offers in the restricted Azure Private Marketplace environment

Learn how to enable and deploy Azure Marketplace offers in a restricted Azure Private Marketplace. Understand how to activate required application and hidden VM plans, use CLI commands to permit specific offers, and resolve common eligibility errors so deployments succeed within tenant restrictions.

Deploy the IPv6 Supported Secure Firewall Management Center Virtual on Azure

About IPv6 Supported Deployment on Azure

Deploy from Azure Using Custom IPv6 Template with Marketplace Image Reference

Deploy from Azure Using a VHD and Custom IPv6 Template

Verify the Firewall Management Center Virtual Deployment

Learn how to verify a completed deployment in Azure by reviewing the resource group, virtual machine status, and associated resources. Confirm that the VM is running, identify the assigned public IP address, and access the web interface to validate successful setup and connectivity.

Monitoring and Troubleshooting

Learn how to monitor and troubleshoot the virtual appliance in Azure using portal tools, system logs, and console access. Identify startup and provisioning issues, review relevant log files, and address common deployment failures to maintain system availability and resolve errors efficiently.

Feature History

Learn how to identify when Azure public cloud deployment support for the virtual appliance was introduced and in which release. Use this information to track feature availability across versions and plan upgrades or deployments accordingly.

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.