Is migration from FMC2500 to FMCv300 supported on Azure Cloud?

[LOUIS-LEE]

Current FMC2500 (v6.6.7) is managing 35 FTD devices (mix of FP11xx, FP21xx, ASA5508-X)

1. is FMCv300 is supported on Azure Cloud?

2. Is migration from FMC2500 to FMCv300 supported?

3. What is the recommended upgrade/migration path?

Thanks in advance.

[Sheraz.Salim]

FMCv300 is supported on Azure Cloud started from version 6.4 Here 

Is migration from FMC2500 to FMCv300 supported?  Here this link already mentioned a similar ask as your requirment.

for the recommended upgrade/migration path the Gold star version is 7.2. FMC. for you software upgrade path Here is the link it give you all the require information from current running software to target software. in your case 6.6.7 you can upgrade directly to version 7.0.0 or any 7.0.x maintenance release.

[LOUIS-LEE]

Thanks for the response on item 2 & 3.

As per datasheet, FMCv(2/10/25) is supported on Azure Cloud. But not explicitly stated for FMCv300.

Cisco Secure Firewall Management Center (formerly Firepower Management Center) Data Sheet - Cisco

Appreciate if someone can help to confirm this.

[Marvin Rhoads]

I don't believe FMCv300 is currently supported in Azure - even as of the the current release 7.4.1. the smaller version, yes - but not the v300.

https://www.cisco.com/c/en/us/td/docs/security/secure-firewall/roadmap/management-center-new-features-by-release.html

Even if it were, the type of migration you are contemplating is challenging.

I worked with a customer to do a similar one (from on-premises FMC 4500 to FMCv300 in AWS. We had multiple challenges to overcome with device manageability (some had to be left on the old FMC as they were old IPS appliances or ASA with Firepower service modules slated for upcoming retirement) and versions (the cloud only supported 7.1+ and we wanted to be on the current Gold Star suggested release in the 7.2 train while the on premises FMC was 7.0.1). It's also difficult to change manager address as the cloud of course had an assignment in the AWS VPC vs the on-premise IP address.

So we ended up having to do model migration to a VM on-premises, upgrade that VM to match the target cloud release, model migrate it to the cloud version and then do a backup on-premises and restore it to the actual AWS instance. Once we had that in place, each managed device was de-registered from on-prem FMC and then registered to the cloud instance and device config restored from a backup taken on-premise.