AP Manager encounters issues with central AP management because some channels may not be supported.

FortiManager is attempting to install SNMP configurations that are not supported by the FortiGate VM, such as power-supply-failure, temperature-high, and voltage-alert.

ADOM 7.4 converts SD-WAN rules route-tags into empty route-tag address objects, breaking compatibility with FortiOS 7.2 devices.

The FGT90G/91G Gen2 are not supported in Device Model.

Device count is not correct.

The FortiExtender API connection status is returning incorrect value for the FortiExtender device when in an "unknown" state.

FortiExtender Page 'Data Usage' value does not display the updated values.

After creating the SSID and assigning it to the FortiExtender profile, the configuration is not pushing to the FortiGate, resulting in an installation failure.

Users might experiencing Attempting to reconnect messages every few minutes while logged in to the GUI.

FortiManager may not recognize the 1000F serial number as valid for applying the corresponding Device Blueprint, preventing the CSV file from being loaded.

In FortiClient EMS 7.4.5, the communication protocol has been upgraded from HTTP/1.0 to HTTP/2. Unlike HTTP/1.x, HTTP/2 does not return a traditional "200 OK" text response, so previous versions of FortiManager that expect this format cannot interpret the new HTTP/2 replies. Because of this, versions prior to FortiManager 7.4.9 and 7.6.5 are not compatible with the EMS version 7.4.5 and later.

FortiManager attempts to configure the service in the ISDB6 policy (IPv6), but FortiOS rejects it, causing the installation to fail.

Unable to create ZTNA Server with SAML SSO Server.

When using the Install Object(s) function after renaming an object, FortiManager pushes the old object name to the firewall policy.

No interface mapping listed when importing config for a device (device mapping undefined).

Application control category "GenAI" is missing in FortiManager, but present in FortiGate.

Installation might fail to these devices "FGT/FWF-30G/31G" due to some unsupported syntax.

Unable to create new section "Add Section" in policy after upgrade FortiManager to 7.4.7 while using interface pair view mode. Operation "Add Section" triggers nothing. Field "label" or "global-label" are empty.

NAT64 policy and CNAT cannot be created or modified in FortiManager.

After importing the policies and objects from the FortiGate, even though the FortiManager settings were selected, the configuration status for all FortiGates changed to Modified.

During the auto-linking process, FortiManager attempts to push a policy package containing Internet-Service based rules, but the FortiGates outdated ISDB causes the installation to fail.

The FortiManager configuration attempted to change the order of custom service objects, but this returned an "Unknown action 0" error.

EMS server security posture tags are not fully synchronized with FortiManager Cloud; ZTNA tags comment are missing.

The installation may fail with a “Current passphrase is invalid” error. This can occur when installing an SSID with an MPSK profile, where the MPSK passphrase is not inherited during copy operations or after a FortiManager upgrade.

Existing Objects shown as "Not found" in "Where Used".

Reinstalling policy packages for more than three devices may cause the Application Security Console to crash.

Installation hang when pushing configurations to firewall groups.

FortiManager may delete policies or settings during device installation due to concurrent database interactions from tasks like auto-updates, policy installs, or HA-related updates running simultaneously.

Alternative Resources setting under AWS connector is not pushed to FortiGate.