Focus

VM-Series and Panorama Plugins Release Notes

Known Issues in Panorama Plugin for Azure 3.2.0

Table of Contents

Known Issues in Panorama Plugin for Azure 3.2.0

The following list describes known issues in the Panorama plugin for Azure 3.2.0.

PLUG-10478

Out of Memory issues are observed on smaller Panorama instances with resources of around 4/16 CPU/Memory and running around 100+ subscriptions.

PLUG-10476

If you have a one or more other Panorama plugins installed, the upgrade and installation of the Panorama plugin for Azure to version 3.2.0 can take longer than expected.

PLUG-10452

Device groups are not listed in the plugin debug command debug plugins azure azure-tags dump-all monitoring-definition MD1 action send-to-file when multiple monitoring definitions are configured.

PLUG-10437

After a successful VM-Series firewall deployment in PAN-OS 10.0.9 and above, and Azure Plugin 3.2.0; it is observed that the deployment status displays as Warning, even though the firewalls are successfully connected to the Panorama.

PLUG-10435

In fully scaled environments on an HA setup, the plugin installation is observed to take around 20 minutes on the Primary node.

PLUG-10409

In environments with many subscriptions, tags updated on Azure are reflected on the Panorama with a delay.

PLUG-10338

On successful deletion of a deployment, it is observed that the PA-VMs are not deleted from the device summary and are displayed as disconnected under Managed Devices. This issue is observed in PAN OS 10.1.x and later.

PLUG-9978

In the plugin_client.log file, it is observed that the Proxy password is displayed as plain text, instead of being masked.

PLUG-9905

When proxy is configured on a Panorama, the Monitoring status is observed to be failing due to rejection of the connection.

Workaround: Manually configure the Public IP of the Panorama, at the interface level.

What’s New in Panorama Plugin for Azure 3.2.0

Addressed Issues in Panorama Plugin for Azure 3.2.0