Focus

Cloud NGFW for Azure

Cloud NGFW for Azure Addressed Issues

Table of Contents

Cloud NGFW for Azure Addressed Issues

Cloud NGFW for AWS addressed issues.

The following issues have been addressed at this release of Cloud NGFW for Azure.

ID	Description
FWAAS-3919	It is observed that invalid rule names could be generated in Local Rulestacks that could cause commit failures.
FWAAS-4546	Rulehit counter DB entries are not deleted after deleting the rule, resulting in old values if a rule is created again with the same name.
FWAAS-4767	The DNS proxy does not update simultaneously on the firewall, following a firewall update call.
FWAAS-4805	Firewall host names are erroneously displayed in logs.
FWAAS-7430	If you try to delete a new Cloud NGFW resource before the creation is complete, the deletion fails.
FWAAS-7542	Panorama does not always automatically push content and antivirus updates to newly created Cloud NGFW for Azure resources.
FWAAS-8696	Log forwarding to a Panorama virtual appliance may take a long time to complete.
FWAAS-9041	Device server profiles (for example, LDAP, syslog) erroneously appear disabled in Panorama templates used for CNGFW devices.
FWAAS-9050	In some cases, a license on a VM-Series firewall may be removed from the Panorama virtual appliance.
FWAAS-9055	The CNGFW reaches an unhealthy state and loses connectivity to Panorama when the Cloud Device Group name is changed.
PAN-217460	Cloud NGFW resources managed by a Panorama HA pair might show disconnected on the secondary Panorama. However, on the primary Panorama, the Cloud NGFW resource shows connected.

Cloud NGFW for Azure Known Issues