Addressed Issues in the Panorama Plugin for Azure 5.2.2
Table of Contents
Expand all | Collapse all
-
-
-
-
- Features Introduced in Zero Touch Provisioning 2.0
- Known Issues in the Zero Touch Provisioning 2.0.4 Release
- Known Issues in the Zero Touch Provisioning 2.0.3 Release
- Known Issues in the Zero Touch Provisioning 2.0.2 Release
- Known Issues in the Zero Touch Provisioning 2.0.1 Release
- Known Issues in the Zero Touch Provisioning 2.0.0 Release
- Limitations
-
-
Addressed Issues in the Panorama Plugin for Azure 5.2.2
Panorama Plugin for Azure 5.2.1
The following list describes issues addressed in the Panorama plugin for
Azure 5.2.2:
PLUG-16299
Fixed an issue where Inactive Cloud NGFWs that were previously deployed continued to
consume Panorama licenses.
PLUG-17405
Cloud NGFW resources now rely on Azure-provided NTP (Network Timing Protocol) rather than
being synchronized via Panorama.
PLUG-18149
Fixed an issue where you could not select an individual Cloud NGFW instance when
deploying AV content.
PLUG-18220
Fixed a situation where, by default, changes to a template stack were automatically
pushed to the Cloud NGFW resource. Panorama erroneously allowed you to change this
default setting by selecting the option to automatically push content changes to the
device registered with Panorama in the Template Stack screen.
This option is now greyed out.