<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic The provisioning state on Azure is failed in Cloud NGFW for Azure Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cloud-ngfw-for-azure-discussions/the-provisioning-state-on-azure-is-failed/m-p/578808#M30</link>
    <description>&lt;P&gt;Hello everyone,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am writing to address an issue encountered during the deployment and configuration of a Cloud Native Firewall on the Azure platform. Initially, the deployment proceeded smoothly, with all functionalities operating as expected. However, difficulties arose upon attempting to modify the device group and its association with the firewall.&lt;/P&gt;
&lt;P&gt;It came to my attention that the device group is encapsulated within a Base64 hash within the Azure resource configuration. Consequently, the attempted modifications led to unexpected outcomes and subsequent failure.&lt;/P&gt;
&lt;P&gt;Subsequently, I reverted the changes to their previous state, restoring the firewall's functionality to its proper operation. Despite this successful resolution, it is noteworthy that the provisioning status within the Azure resource overview indicates failure, with the JSON value appearing as empty.&lt;/P&gt;
&lt;P&gt;In light of the aforementioned circumstances, I seek guidance on rectifying this situation and restoring the provisioning status to a successful state. Any assistance or insights provided would be greatly appreciated.&lt;/P&gt;
&lt;P&gt;Thank you for your attention to this matter.&lt;/P&gt;</description>
    <pubDate>Thu, 29 Feb 2024 09:24:31 GMT</pubDate>
    <dc:creator>a.keskempes</dc:creator>
    <dc:date>2024-02-29T09:24:31Z</dc:date>
    <item>
      <title>The provisioning state on Azure is failed</title>
      <link>https://live.paloaltonetworks.com/t5/cloud-ngfw-for-azure-discussions/the-provisioning-state-on-azure-is-failed/m-p/578808#M30</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am writing to address an issue encountered during the deployment and configuration of a Cloud Native Firewall on the Azure platform. Initially, the deployment proceeded smoothly, with all functionalities operating as expected. However, difficulties arose upon attempting to modify the device group and its association with the firewall.&lt;/P&gt;
&lt;P&gt;It came to my attention that the device group is encapsulated within a Base64 hash within the Azure resource configuration. Consequently, the attempted modifications led to unexpected outcomes and subsequent failure.&lt;/P&gt;
&lt;P&gt;Subsequently, I reverted the changes to their previous state, restoring the firewall's functionality to its proper operation. Despite this successful resolution, it is noteworthy that the provisioning status within the Azure resource overview indicates failure, with the JSON value appearing as empty.&lt;/P&gt;
&lt;P&gt;In light of the aforementioned circumstances, I seek guidance on rectifying this situation and restoring the provisioning status to a successful state. Any assistance or insights provided would be greatly appreciated.&lt;/P&gt;
&lt;P&gt;Thank you for your attention to this matter.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Feb 2024 09:24:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cloud-ngfw-for-azure-discussions/the-provisioning-state-on-azure-is-failed/m-p/578808#M30</guid>
      <dc:creator>a.keskempes</dc:creator>
      <dc:date>2024-02-29T09:24:31Z</dc:date>
    </item>
  </channel>
</rss>

