Known 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
-
-
Known Issues in the Panorama Plugin for Azure 5.2.2
Known issues in the Panorama Plugin for Azure 5.2.2.
The following list describes known issues in the Panorama plugin for Azure 5.2.2:
FWAAS-7880
When pushing a configuration from Panorama to Cloud NGFWs, you are erroneously allowed to
select one or more Cloud NGFWs individually. This functionality should be disallowed
because the firewalls will not be identical after pushing the configuration change.
PLUG-15050
Service principal fails deployment due to permissions.
PLUG-16111
Uncommitted changes exist when a new Cloud NGFW is registered through Panorama; when a
new device connects to Panorama, some changes appear in a device group, template stack
and device and network. Manually committing these changes results in a message
indicating nothing pending to commit.
PLUG-16469
Issuing the command show system info may result in a delay displaying
the information.
PLUG-17684
The number of scaled-in instances due to traffic fluctuations accumulate in Panorama and
are only cleaned up after a period of time (typically, 72 hours).
PLUG-18490
When you use Panorama to configure Zone Protection profiles, the profiles remain hidden
in the Network Profiles screen.