acrolinx and no SNAT

Author: solankisamir

articles/api-management/api-management-howto-disaster-recovery-backup-restore.md

@@ -68,11 +68,10 @@ All of the tasks that you do on resources using the Azure Resource Manager must
 
 ### Add an application
 
-1. Once the application is created, click **Settings**.
-2. Click **Required permissions**.
-3. Click **+Add**.
-4. Press **Select an API**.
-5. Choose **Windows** **Azure Service Management API**.
+1. Once the application is created, click **API permissions**.
+2. Click **+ Add a permission**.
+4. Press **Select Microsoft APIs**.
+5. Choose **Azure Service Management**.
 6. Press **Select**.
 
     ![Add permissions](./media/api-management-howto-disaster-recovery-backup-restore/add-app.png)
@@ -175,7 +174,11 @@ Note the following constraints when making a backup request:
 -   In addition, the following items are not part of the backup data: custom domain SSL certificates and any intermediate or root certificates uploaded by customer, developer portal content, and virtual network integration settings.
 -   The frequency with which you perform service backups affect your recovery point objective. To minimize it, we recommend implementing regular backups and performing on-demand backups after you make changes to your API Management service.
 -   **Changes** made to the service configuration, (for example, APIs, policies, and developer portal appearance) while backup operation is in process **might be excluded from the backup and will be lost**.
--   **Allow** access from control plane to Azure Storage Account. Customer should open the set of [Azure API Management Control Plane IP Addresses][control-plane-ip-address] on their Storage Account for Backup.
+-   **Allow** access from control plane to Azure Storage Account. Customer should open the set of [Azure API Management Control Plane IP Addresses][control-plane-ip-address] on their Storage Account for Backup. 
+
+> [!NOTE]
+> If you have firewall enabled on the Storage Account and the are trying to do backup/restore from an API Management service in the same Region, 
+> then this will not work, as the requests to Azure Storage are not SNATed to public IP from Compute deployed in the same region.
 
 ### <a name="step2"> </a>Restore an API Management service
 

articles/api-management/api-management-using-with-vnet.md

@@ -136,7 +136,7 @@ When an API Management service instance is hosted in a VNET, the ports in the fo
     |-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
     | Azure Public      | <ul><li>prod.warmpath.msftcloudes.com</li><li>shoebox2.metrics.nsatc.net</li><li>prod3.metrics.nsatc.net</li><li>prod3-black.prod3.metrics.nsatc.net</li><li>prod3-red.prod3.metrics.nsatc.net</li><li>prod.warm.ingestion.msftcloudes.com</li><li>`azure region`.warm.ingestion.msftcloudes.com where `East US 2` is eastus2.warm.ingestion.msftcloudes.com</li></ul> |
     | Azure Government  | <ul><li>fairfax.warmpath.usgovcloudapi.net</li><li>shoebox2.metrics.nsatc.net</li><li>prod3.metrics.nsatc.net</li></ul>                                                                                                                                                                                                                                                |
-    | Azure China       | <ul><li>mooncake.warmpath.chinacloudapi.cn</li><li>shoebox2.metrics.nsatc.net</li><li>prod3.metrics.nsatc.net</li></ul>                                                                                                                                                                                                                                                |
+    | Azure China 21Vianet     | <ul><li>mooncake.warmpath.chinacloudapi.cn</li><li>shoebox2.metrics.nsatc.net</li><li>prod3.metrics.nsatc.net</li></ul>                                                                                                                                                                                                                                                |
 
 + **SMTP Relay**: Outbound network connectivity for the SMTP Relay, which resolves under the host `smtpi-co1.msn.com`, `smtpi-ch1.msn.com`, `smtpi-db3.msn.com`, `smtpi-sin.msn.com` and `ies.global.microsoft.com`
 
@@ -192,7 +192,7 @@ Given the calculation above the minimum size of the subnet, in which API Managem
 
 The IP Addresses are divided by **Azure Environment**. When allowing inbound requests IP address marked with **Global** must be whitelisted along with the **Region** specific IP Address.
 
-| **Azure Environment**|   **Region**|  **IP Address**|
+| **Azure Environment**|   **Region**|  **IP address**|
 |-----------------|-------------------------|---------------|
 | Azure Public| South Central US (Global)| 104.214.19.224|
 | Azure Public| North Central US (Global)| 52.162.110.80|
@@ -238,12 +238,12 @@ The IP Addresses are divided by **Azure Environment**. When allowing inbound req
 | Azure Public| Germany North| 51.116.0.0|
 | Azure Public| Norway East| 51.120.2.185|
 | Azure Public| Norway West| 51.120.130.134|
-| Azure China 21 Vianet| China North (Global)| 139.217.51.16|
-| Azure China 21 Vianet| China East (Global)| 139.217.171.176|
-| Azure China 21 Vianet| China North| 40.125.137.220|
-| Azure China 21 Vianet| China East| 40.126.120.30|
-| Azure China 21 Vianet| China North 2| 40.73.41.178|
-| Azure China 21 Vianet| China East 2| 40.73.104.4|
+| Azure China 21Vianet| China North (Global)| 139.217.51.16|
+| Azure China 21Vianet| China East (Global)| 139.217.171.176|
+| Azure China 21Vianet| China North| 40.125.137.220|
+| Azure China 21Vianet| China East| 40.126.120.30|
+| Azure China 21Vianet| China North 2| 40.73.41.178|
+| Azure China 21Vianet| China East 2| 40.73.104.4|
 | Azure Government| USGov Virginia (Global)| 52.127.42.160|
 | Azure Government| USGov Texas (Global)| 52.127.34.192|
 | Azure Government| USGov Virginia| 52.227.222.92|