<?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 &amp;quot;LAN&amp;quot; and &amp;quot;WAN&amp;quot; interfaces for the Palo Alto Networks Cloud NGFW SaaS offering within Azure Virtual WAN in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/quot-lan-quot-and-quot-wan-quot-interfaces-for-the-palo-alto/m-p/1233629#M6066</link>
    <description>&lt;P&gt;Hello Team,&lt;BR /&gt;&lt;BR /&gt;We are in the process of switching over from VM-Series PA to PA SaaS within Azure vWAN.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Palo Alto VM-Series firewall, we explicitly created and configured LAN and WAN, however for PA SaaS within Azure vWAN is there a need to create?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We also cannot create a new VNET/Subnet in Azure vWAN to associate it with the interfaces, so how does it work?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So there is no concept of Zones to apply the policies etc. in PA SaaS version within Azure vWAN?&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Please share the differences and the concept of LAN/WAN interfaces / Zones in PA SaaS within Azure vWAN.&lt;/P&gt;</description>
    <pubDate>Wed, 09 Jul 2025 12:29:04 GMT</pubDate>
    <dc:creator>Ravi-KumarS</dc:creator>
    <dc:date>2025-07-09T12:29:04Z</dc:date>
    <item>
      <title>"LAN" and "WAN" interfaces for the Palo Alto Networks Cloud NGFW SaaS offering within Azure Virtual WAN</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/quot-lan-quot-and-quot-wan-quot-interfaces-for-the-palo-alto/m-p/1233629#M6066</link>
      <description>&lt;P&gt;Hello Team,&lt;BR /&gt;&lt;BR /&gt;We are in the process of switching over from VM-Series PA to PA SaaS within Azure vWAN.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Palo Alto VM-Series firewall, we explicitly created and configured LAN and WAN, however for PA SaaS within Azure vWAN is there a need to create?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We also cannot create a new VNET/Subnet in Azure vWAN to associate it with the interfaces, so how does it work?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So there is no concept of Zones to apply the policies etc. in PA SaaS version within Azure vWAN?&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Please share the differences and the concept of LAN/WAN interfaces / Zones in PA SaaS within Azure vWAN.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Jul 2025 12:29:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/quot-lan-quot-and-quot-wan-quot-interfaces-for-the-palo-alto/m-p/1233629#M6066</guid>
      <dc:creator>Ravi-KumarS</dc:creator>
      <dc:date>2025-07-09T12:29:04Z</dc:date>
    </item>
  </channel>
</rss>

