Merge pull request #263319 from wtnlee/paloupdates

added regions

Author: prmerger-automator[bot]

articles/virtual-wan/how-to-palo-alto-cloud-ngfw.md

@@ -79,9 +79,8 @@ To create a new virtual WAN, use the steps in the following article:
 
 ## Known limitations
 
-* Palo Alto Networks Cloud NGFW is only available in the following Azure regions: Central US, East US, East US 2, West US, West US 2, West US 3, North Europe, West Europe, Australia East, Australia Southeast, UK South, UK West, Canada Central and East Asia. Other Azure regions are on the roadmap.
+* Palo Alto Networks Cloud NGFW is only available in the following Azure regions: Central US, East US, East US 2, West US, West US 2, West US 3, North Central US, Brazil South, North Europe, West Europe, UK South, UK West, Australia East, Australia Southeast, UK South, UK West, Canada Central, Japan East, Southeast Asia, and East Asia. Other Azure regions are on the roadmap.
 * Palo Alto Networks Cloud NGFW can't be deployed with Network Virtual Appliances in the Virtual WAN hub.
-* For routing between Virtual WAN and Palo Alto Networks Cloud NGFW to work properly, your entire network (on-premises and Virtual Networks) must be within RFC-1918 (subnets within 10.0.0.0/8, 192.168.0.0/16, 172.16.0.0/12). For example, you may not use a subnet such as 40.0.0.0/24 within your Virtual Network or on-premises. Traffic to 40.0.0.0/24 may not be routed properly.  
 * All other limitations in the [Routing Intent and Routing policies documentation limitations section](how-to-routing-policies.md) apply to Palo Alto Networks Cloud NGFW deployments in Virtual WAN.
 
 ## Register resource provider
@@ -157,7 +156,7 @@ The following section describes common issues seen when using Palo Alto Networks
 
 ### Troubleshooting Cloud NGFW creation
 
-* Ensure your Virtual Hubs are deployed in one of the following regions: Central US, East US, East US 2, West US, West US 2, West US 3, North Europe, West Europe, Australia East, Australia Southeast, UK South, UK West, Canada Central and East Asia. Other regions are in the roadmap.
+* Ensure your Virtual Hubs are deployed in one of the following regions:Central US, East US, East US 2, West US, West US 2, West US 3, North Central US, Brazil South, North Europe, West Europe, UK South, UK West, Australia East, Australia Southeast, UK South, UK West, Canada Central, Japan East, Southeast Asia, and East Asia. Other regions are in the roadmap.
 * Ensure the Routing status of the Virtual Hub is "Provisioned." Attempts to create Cloud NGFW prior to routing being provisioned will fail.
 * Ensure registration to the **PaloAltoNetworks.Cloudngfw** resource provider is successful.
 
@@ -170,7 +169,7 @@ The following section describes common issues seen when using Palo Alto Networks
 ### Troubleshooting Routing intent and policies
 
 * Ensure Cloud NGFW deployment is completed successfully before attempting to configure Routing Intent.
-* Ensure all your on-premises and Azure Virtual Networks are in RFC1918 (subnets within 10.0.0.0/8, 192.168.0.0/16, 172.16.0.0/12).
+* Ensure all your on-premises and Azure Virtual Networks are in RFC1918 (subnets within 10.0.0.0/8, 192.168.0.0/16, 172.16.0.0/12). If there are networks that are not in RFC1918, make sure those prefixes are listed in the Private Traffic prefixes text box.
 * For more information about troubleshooting routing intent, see [Routing Intent documentation](how-to-routing-policies.md). This document describes pre-requisites,  common errors associated with configuring routing intent and troubleshooting tips.
 
 ### Troubleshooting Palo Alto Networks Cloud NGFW configuration