Overview
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.
When you deploy the Firewall Management Center Virtual in Azure the following resources are created:
-
The Firewall Management Center Virtual Machine with a single interface (requires a new or an existing virtual network with 1 subnet).
-
A Resource Group.
The Firewall Management Center Virtual is always deployed into a new Resource Group. However, you can attach it to an existing Virtual Network in another Resource Group.
-
A security group named vm name-mgmt-SecurityGroup.
The security group will be attached to the VM’s Nic0.
The security group includes rules to allow SSH (TCP port 22) and the management traffic for the Firewall Management Center interface (TCP port 8305). You can modify these values after deployment.
-
A Public IP Address (named according to the value you chose during deployment).
The public IP address is associated with VM Nic0, which maps to Management.
You can create a new public IP or choose an existing one. You can also choose NONE. Without a public IP address, any communication to the Firewall Management Center Virtual must originate within the Azure virtual network
-
A Routing Table for the subnet (updated if it already exists).
-
A boot diagnostics file in the selected storage account.
The boot diagnostics file will be in Blobs (binary large objects).
-
Two files in the selected storage account under Blobs and container VHDs named VM name-disk.vhd and VM name-<uuid>.status.
-
A Storage account (unless you chose an existing storage account).
When you delete a VM, you must delete each of these resources individually, except for any resources you want to keep.