<?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 Re: migrating a VM firewall to availability zones within Azure? in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/migrating-a-vm-firewall-to-availability-zones-within-azure/m-p/393701#M1141</link>
    <description>&lt;P&gt;My current thinking for the method is to take a backup of the gateway. And also to export a named config. Followed by:&lt;/P&gt;&lt;P&gt;- Delete the gateway in Azure.&lt;/P&gt;&lt;P&gt;- Create a new gateway (from Marketplace) with the same name, subnet, and ip address as the old.&lt;/P&gt;&lt;P&gt;- Once the new gateway is up and reachable, import the named config.&lt;/P&gt;&lt;P&gt;- Update the license/subscriptions, as saved in the Palo portal, with the new gateway ID.&lt;/P&gt;&lt;P&gt;Is there a better way? Or any missing steps?&lt;/P&gt;</description>
    <pubDate>Thu, 25 Mar 2021 05:53:24 GMT</pubDate>
    <dc:creator>JimMcGrady</dc:creator>
    <dc:date>2021-03-25T05:53:24Z</dc:date>
    <item>
      <title>migrating a VM firewall to availability zones within Azure?</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/migrating-a-vm-firewall-to-availability-zones-within-azure/m-p/391899#M1139</link>
      <description>&lt;P&gt;My Azure region has recently become availability zone capable. Is there a recommended process for converting/migrating Palo VM firewalls so they make use of this feature?&lt;/P&gt;</description>
      <pubDate>Thu, 18 Mar 2021 05:09:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/migrating-a-vm-firewall-to-availability-zones-within-azure/m-p/391899#M1139</guid>
      <dc:creator>JimMcGrady</dc:creator>
      <dc:date>2021-03-18T05:09:02Z</dc:date>
    </item>
    <item>
      <title>Re: migrating a VM firewall to availability zones within Azure?</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/migrating-a-vm-firewall-to-availability-zones-within-azure/m-p/393701#M1141</link>
      <description>&lt;P&gt;My current thinking for the method is to take a backup of the gateway. And also to export a named config. Followed by:&lt;/P&gt;&lt;P&gt;- Delete the gateway in Azure.&lt;/P&gt;&lt;P&gt;- Create a new gateway (from Marketplace) with the same name, subnet, and ip address as the old.&lt;/P&gt;&lt;P&gt;- Once the new gateway is up and reachable, import the named config.&lt;/P&gt;&lt;P&gt;- Update the license/subscriptions, as saved in the Palo portal, with the new gateway ID.&lt;/P&gt;&lt;P&gt;Is there a better way? Or any missing steps?&lt;/P&gt;</description>
      <pubDate>Thu, 25 Mar 2021 05:53:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/migrating-a-vm-firewall-to-availability-zones-within-azure/m-p/393701#M1141</guid>
      <dc:creator>JimMcGrady</dc:creator>
      <dc:date>2021-03-25T05:53:24Z</dc:date>
    </item>
  </channel>
</rss>

