<?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 Management of palo alto vms  for DR in Azure in different regions via Panorama in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/management-of-palo-alto-vms-for-dr-in-azure-in-different-regions/m-p/546484#M1914</link>
    <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Currently, in our organization we are using Transit Vnet Model and utilizing hub &amp;amp; spoke concept in Azure Cloud. We have different set of firewalls which are filtering East-West &amp;amp; North-South direction traffic respectively in Azure. This setup is available only in one region (East US) of Azure. If something goes wrong in that region, we might loose connectivity via Transit firewalls from On-prem as well within Azure from different regions. We are looking for a solution for DR so that we can have a similar setup of Transit firewalls in different region (e.g. Central US) as well which will remain inactive till the primary region is active and once East US goes down, we can have Central US as a DR solution.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can anyone please guide/suggest me any document/blogs etc which can help me in designing architecture and managing these Transit firewalls in DC &amp;amp; DR regions via Panorama?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/213716"&gt;@panorama&lt;/a&gt;&amp;nbsp;,&amp;nbsp;@VM-Series&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Bilal&lt;/P&gt;</description>
    <pubDate>Tue, 20 Jun 2023 13:06:17 GMT</pubDate>
    <dc:creator>BilalMohd</dc:creator>
    <dc:date>2023-06-20T13:06:17Z</dc:date>
    <item>
      <title>Management of palo alto vms  for DR in Azure in different regions via Panorama</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/management-of-palo-alto-vms-for-dr-in-azure-in-different-regions/m-p/546484#M1914</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Currently, in our organization we are using Transit Vnet Model and utilizing hub &amp;amp; spoke concept in Azure Cloud. We have different set of firewalls which are filtering East-West &amp;amp; North-South direction traffic respectively in Azure. This setup is available only in one region (East US) of Azure. If something goes wrong in that region, we might loose connectivity via Transit firewalls from On-prem as well within Azure from different regions. We are looking for a solution for DR so that we can have a similar setup of Transit firewalls in different region (e.g. Central US) as well which will remain inactive till the primary region is active and once East US goes down, we can have Central US as a DR solution.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can anyone please guide/suggest me any document/blogs etc which can help me in designing architecture and managing these Transit firewalls in DC &amp;amp; DR regions via Panorama?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/213716"&gt;@panorama&lt;/a&gt;&amp;nbsp;,&amp;nbsp;@VM-Series&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Bilal&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2023 13:06:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/management-of-palo-alto-vms-for-dr-in-azure-in-different-regions/m-p/546484#M1914</guid>
      <dc:creator>BilalMohd</dc:creator>
      <dc:date>2023-06-20T13:06:17Z</dc:date>
    </item>
  </channel>
</rss>

