<?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: Azure Palo Alto VM Setup - QA/Dev/Prod/Stg in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/azure-palo-alto-vm-setup-qa-dev-prod-stg/m-p/469601#M1484</link>
    <description>&lt;P&gt;I would take a look at the Palo Alto Azure Reference Architecture Guide.&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.paloaltonetworks.com/apps/pan/public/downloadResource?pagePath=/content/pan/en_US/resources/guides/azure-architecture-guide" target="_blank"&gt;https://www.paloaltonetworks.com/apps/pan/public/downloadResource?pagePath=/content/pan/en_US/resources/guides/azure-architecture-guide&lt;/A&gt;. In short, you have to configure UDRs to get traffic over to the Palo Alto for inspection.&lt;/P&gt;</description>
    <pubDate>Tue, 01 Mar 2022 20:48:29 GMT</pubDate>
    <dc:creator>DanaHawkins</dc:creator>
    <dc:date>2022-03-01T20:48:29Z</dc:date>
    <item>
      <title>Azure Palo Alto VM Setup - QA/Dev/Prod/Stg</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/azure-palo-alto-vm-setup-qa-dev-prod-stg/m-p/468432#M1475</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I has successfully deployed the VM-200 series in our Azure subscription. Trying to figure out how to do the segregation of environments (QA/Dev/Prod/Stg).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Currently setup as Hub-and-spoke, the trust interface is connected to Core Subscription which will be use to setup, AD, Proxy, GW subnet and so on. The un-trust interface is associate with GW subnet that we already establish the s2s VPN tunnel.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I cannot figure out is what is the best practice to setup the different environment using Palo Alto?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If we create additional subscription (or VNET), when doing VNET peering, it will consider as trust interface and inter-zone are allow by defaults.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do we create multiple interface for each PROD/QA/DEV/STG environment? not too say we might have Special Project subscription(or VNET).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If anyone have any suggestion how we can create different environment using Palo Alto, will really appreciate.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Feb 2022 00:59:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/azure-palo-alto-vm-setup-qa-dev-prod-stg/m-p/468432#M1475</guid>
      <dc:creator>BoonKeatGan</dc:creator>
      <dc:date>2022-02-25T00:59:09Z</dc:date>
    </item>
    <item>
      <title>Re: Azure Palo Alto VM Setup - QA/Dev/Prod/Stg</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/azure-palo-alto-vm-setup-qa-dev-prod-stg/m-p/469601#M1484</link>
      <description>&lt;P&gt;I would take a look at the Palo Alto Azure Reference Architecture Guide.&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.paloaltonetworks.com/apps/pan/public/downloadResource?pagePath=/content/pan/en_US/resources/guides/azure-architecture-guide" target="_blank"&gt;https://www.paloaltonetworks.com/apps/pan/public/downloadResource?pagePath=/content/pan/en_US/resources/guides/azure-architecture-guide&lt;/A&gt;. In short, you have to configure UDRs to get traffic over to the Palo Alto for inspection.&lt;/P&gt;</description>
      <pubDate>Tue, 01 Mar 2022 20:48:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/azure-palo-alto-vm-setup-qa-dev-prod-stg/m-p/469601#M1484</guid>
      <dc:creator>DanaHawkins</dc:creator>
      <dc:date>2022-03-01T20:48:29Z</dc:date>
    </item>
  </channel>
</rss>

