<?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 PA-VM in Azure - multiple Zones? (e.g. DMZ,Trust,Unstrust,etc) in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/pa-vm-in-azure-multiple-zones-e-g-dmz-trust-unstrust-etc/m-p/563247#M2015</link>
    <description>&lt;P&gt;In the deployment guides and conversations I've had it seems that the PA-VM firewall in Azure is typically designed around only four interfaces: trust, untrust, mgmt, HA. Two zones only: Trust/Untrust.&amp;nbsp; Subnets used to isolate traffic.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In my on-prem setups I've always had zones associated with either the interfaces or VLANs on those interfaces to help differentiate application of policies. I feel like it makes in plainly obvious in the policy where that traffic is coming from and going but prevents inadvertently allowing something you don't want allowed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'd prefer to keep the ability to use the zones vs subnets and subnet groups. Is there a way to create another Zone for a subnet within Azure?&amp;nbsp; I don't believe VLAN's are available in Azure so that options seems out.&amp;nbsp; I'd like to setup a DMZ zone since that just seems more elegant to use and easier to read when looking at Policies.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Palo support had suggested adding another interface but that doesn't seem like an option nor does it seem advisable based on what is considered a standard setup in Azure. The VM that the PA-VM runs on right now too is limited to four interfaces.&lt;/P&gt;</description>
    <pubDate>Thu, 26 Oct 2023 12:10:34 GMT</pubDate>
    <dc:creator>TonyDeHart</dc:creator>
    <dc:date>2023-10-26T12:10:34Z</dc:date>
    <item>
      <title>PA-VM in Azure - multiple Zones? (e.g. DMZ,Trust,Unstrust,etc)</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/pa-vm-in-azure-multiple-zones-e-g-dmz-trust-unstrust-etc/m-p/563247#M2015</link>
      <description>&lt;P&gt;In the deployment guides and conversations I've had it seems that the PA-VM firewall in Azure is typically designed around only four interfaces: trust, untrust, mgmt, HA. Two zones only: Trust/Untrust.&amp;nbsp; Subnets used to isolate traffic.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In my on-prem setups I've always had zones associated with either the interfaces or VLANs on those interfaces to help differentiate application of policies. I feel like it makes in plainly obvious in the policy where that traffic is coming from and going but prevents inadvertently allowing something you don't want allowed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'd prefer to keep the ability to use the zones vs subnets and subnet groups. Is there a way to create another Zone for a subnet within Azure?&amp;nbsp; I don't believe VLAN's are available in Azure so that options seems out.&amp;nbsp; I'd like to setup a DMZ zone since that just seems more elegant to use and easier to read when looking at Policies.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Palo support had suggested adding another interface but that doesn't seem like an option nor does it seem advisable based on what is considered a standard setup in Azure. The VM that the PA-VM runs on right now too is limited to four interfaces.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Oct 2023 12:10:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/pa-vm-in-azure-multiple-zones-e-g-dmz-trust-unstrust-etc/m-p/563247#M2015</guid>
      <dc:creator>TonyDeHart</dc:creator>
      <dc:date>2023-10-26T12:10:34Z</dc:date>
    </item>
  </channel>
</rss>

