express vnet injection

swinarko · swinarko · commit b12cd4a400f4 · 2021-10-27T08:55:39.000+08:00
diff --git a/articles/data-factory/azure-ssis-integration-runtime-express-virtual-network-injection.md b/articles/data-factory/azure-ssis-integration-runtime-express-virtual-network-injection.md
@@ -60,7 +60,7 @@ For detailed instructions, see the [Grant virtual network permissions](azure-ssi
 
 ## <a name="ip"></a>Configure a static public IP address
 
-If you want to use a static public IP address for the outbound traffic of your Azure-SSIS IR, so you can allow it on your firewalls, you must configure [virtual network network address translation (NAT)](../virtual-network/nat-overview.md) to set it up.
+If you want to use a static public IP address for the outbound traffic of your Azure-SSIS IR, so you can allow it on your firewalls, you must configure [virtual network network address translation (NAT)](../virtual-network/nat-gateway/nat-overview.md) to set it up.
 
 ## <a name="dns"></a>Configure a custom DNS server
 
diff --git a/articles/data-factory/azure-ssis-integration-runtime-standard-virtual-network-injection.md b/articles/data-factory/azure-ssis-integration-runtime-standard-virtual-network-injection.md
@@ -68,7 +68,7 @@ If you want to bring your own static public IP addresses for the outbound traffi
 
 - Exactly two unused ones that are not already associated with other Azure resources should be provided. The extra one will be used when we periodically upgrade your Azure-SSIS IR. Note that one public IP address can't be shared among your active Azure-SSIS IRs.
 
-- They should both be static ones of standard type. Refer to the [SKUs of public IP address](../virtual-network/public-ip-addresses.md#sku) section for more details.
+- They should both be static ones of standard type. Refer to the [SKUs of public IP address](../virtual-network/ip-services/public-ip-addresses.md#sku) section for more details.
 
 - They should both have a DNS name. If you haven't provided a DNS name when creating them, you can do so on Azure portal.
 
@@ -186,7 +186,7 @@ Following our guidance in the [Configure an NSG](#nsg) section above, you must i
 
   - If you need to access Azure Files, you must open port *445* for outbound TCP traffic with *0.0.0.0/0* or your Azure Files FQDN as destination.
 
-- If you configure a virtual network service endpoint for Azure Storage/Container Registry/Event Hubs/SQL by enabling *Microsoft.Storage*/*Microsoft.ContainerRegistry*/*Microsoft.EventHub*/*Microsoft.Sql* resources, repectively, in your subnet, all traffic between your Azure-SSIS IR and these services in the same/paired regions will be routed to Azure backbone network instead of your firewall appliance/service.
+- If you configure a virtual network service endpoint for Azure Storage/Container Registry/Event Hubs/SQL by enabling *Microsoft.Storage*/*Microsoft.ContainerRegistry*/*Microsoft.EventHub*/*Microsoft.Sql* resources, respectively, in your subnet, all traffic between your Azure-SSIS IR and these services in the same/paired regions will be routed to Azure backbone network instead of your firewall appliance/service.
 
 - You should open port *80* for outbound TCP traffic with the following certificate revocation list (CRL) download sites as destination:
 
@@ -216,9 +216,9 @@ If you need not audit/inspect the outbound traffic from your Azure-SSIS IR, you
 
 To enable standard virtual network injection, your Azure-SSIS IR needs to create certain network resources in the same resource group as the virtual network. These resources include:
 
-- An Azure load balancer, with the name *<Guid>-azurebatch-cloudserviceloadbalancer*.
-- An Azure public IP address, with the name *<Guid>-azurebatch-cloudservicepublicip*.
-- An NSG, with the name *<Guid>-azurebatch-cloudservicenetworksecuritygroup*. 
+- An Azure load balancer, with the name _\<Guid\>-azurebatch-cloudserviceloadbalancer_.
+- An Azure public IP address, with the name _\<Guid\>-azurebatch-cloudservicepublicip_.
+- An NSG, with the name _\<Guid\>-azurebatch-cloudservicenetworksecuritygroup_. 
 
 > [!NOTE]
 > You can now bring your own static public IP addresses for Azure-SSIS IR. In this scenario, we'll create the Azure load balancer and NSG in the same resource group as your static public IP addresses instead of the virtual network.
diff --git a/articles/data-factory/azure-ssis-integration-runtime-virtual-network-configuration.md b/articles/data-factory/azure-ssis-integration-runtime-virtual-network-configuration.md
@@ -18,8 +18,8 @@ When using SQL Server Integration Services (SSIS) in Azure Data Factory (ADF), t
 
 Here’s a table highlighting the differences between standard and express virtual network injection methods:
 
-|   | Standard virtual network injection | Express virtual network injection |
-|---|------------------------------------|-----------------------------------|
+| Comparison | Standard virtual network injection | Express virtual network injection |
+|------------|------------------------------------|-----------------------------------|
 | **Azure-SSIS IR starting duration** | Around 30 minutes. | Around 5 minutes. | 
 | **Azure subscription & resource group settings** | *Microsoft.Batch* must be registered as a resource provider in the virtual network subscription.<br/><br/>Creation of a public IP address, load balancer, and network security group (NSG) must be allowed in the virtual network resource group. | *Microsoft.Batch* must be registered as a resource provider in the virtual network subscription. | 
 | **Virtual network subnet** | Subnet mustn’t be dedicated to other Azure services. | Subnet mustn’t be dedicated to other Azure services.<br/><br/>Subnet must be delegated to *Microsoft.Batch/batchAccounts*. | 
diff --git a/articles/data-factory/how-to-use-sql-managed-instance-with-ir.md b/articles/data-factory/how-to-use-sql-managed-instance-with-ir.md
@@ -1,12 +1,12 @@
 ---
 title: Use Azure SQL Managed Instance with Azure-SQL Server Integration Services (SSIS) in Azure Data Factory
 description: Learn how to use Azure SQL Managed Instance with SQL Server Integration Services (SSIS) in Azure Data Factory. 
-author: chugugrace
-ms.author: chugu
+author: swinarko
+ms.author: sawinark
 ms.service: data-factory
 ms.subservice: tutorials
 ms.topic: conceptual
-ms.date: 4/15/2020
+ms.date: 10/27/2021
 ---
 # Use Azure SQL Managed Instance with SQL Server Integration Services (SSIS) in Azure Data Factory
 
@@ -60,7 +60,7 @@ You can now move your SQL Server Integration Services (SSIS) projects, packages,
 
                 | Transport protocol | Source | Source port range | Destination |Destination port range |
                 |---|---|---|---|---|
-                |TCP|Static IP address of Azure-SSIS IR <br> For details, see [Bring Your Own Public IP for Azure-SSIS IR](azure-ssis-integration-runtime-virtual-network-configuration.md#publicIP).|*|VirtualNetwork|3342|
+                |TCP|Static IP address of Azure-SSIS IR <br> For details, see [Bring Your Own Public IP for Azure-SSIS IR](azure-ssis-integration-runtime-standard-virtual-network-injection.md#ip).|*|VirtualNetwork|3342|
 
              1. **Outbound requirement of Azure-SSIS IR**, to allow outbound traffic to SQL Managed Instance.
 
@@ -105,7 +105,7 @@ You can now move your SQL Server Integration Services (SSIS) projects, packages,
         |---|---|---|---|---|---|
         | TCP | VirtualNetwork | * | VirtualNetwork | 1433, 11000-11999 |Allow outbound traffic to SQL Managed Instance. If connection policy is set to **Proxy** instead of **Redirect**, only port 1433 is needed. |
         | TCP | VirtualNetwork | * | AzureCloud | 443 | The nodes of your Azure-SSIS IR in the virtual network use this port to access Azure services, such as Azure Storage and Azure Event Hubs. |
-        | TCP | VirtualNetwork | * | Internet | 80 | (Optional) The nodes of your Azure-SSIS IR in the virtual network use this port to download a certificate revocation list from the internet. If you block this traffic, you might experience performance downgrade when start IR and lose capability to check certificate revocation list for certificate usage. If you want to further narrow down destination to certain FQDNs, refer to [Use Azure ExpressRoute or User Defined Route(UDR)](./azure-ssis-integration-runtime-virtual-network-configuration.md#route).|
+        | TCP | VirtualNetwork | * | Internet | 80 | (Optional) The nodes of your Azure-SSIS IR in the virtual network use this port to download a certificate revocation list from the internet. If you block this traffic, you might experience performance downgrade when start IR and lose capability to check certificate revocation list for certificate usage. If you want to further narrow down destination to certain FQDNs, refer to [Configure User Defined Routes (UDRs)](azure-ssis-integration-runtime-standard-virtual-network-injection.md#udr).|
         | TCP | VirtualNetwork | * | Storage | 445 | (Optional) This rule is only required when you want to execute SSIS package stored in Azure Files. |
         |||||||
 
diff --git a/articles/data-factory/monitor-integration-runtime.md b/articles/data-factory/monitor-integration-runtime.md
@@ -4,7 +4,7 @@ description: Learn how to monitor different types of integration runtime in Azur
 ms.service: data-factory
 ms.subservice: monitoring
 ms.topic: conceptual
-ms.date: 08/11/2020
+ms.date: 10/27/2021
 author: minhe-msft
 ms.author: hemin 
 ms.custom: devx-track-azurepowershell
@@ -265,7 +265,7 @@ On the **DIAGNOSE CONNECTIVITY** tile of your Azure-SSIS IR monitoring page, you
 
 #### STATIC PUBLIC IP ADDRESSES tile
 
-If you bring your own static public IP addresses for Azure-SSIS IR, you'll see the **STATIC PUBLIC IP ADDRESSES** tile on your Azure-SSIS IR monitoring page (see [Bringing your own static public IP addresses for Azure-SSIS IR](azure-ssis-integration-runtime-virtual-network-configuration.md#publicIP)). On this tile, you can select links designating your first/second static public IP addresses for Azure-SSIS IR to pop up a window, where you can copy their resource ID (`/subscriptions/YourAzureSubscripton/resourceGroups/YourResourceGroup/providers/Microsoft.Network/publicIPAddresses/YourPublicIPAddress`) from a text box. On the pop-up window, you can also select the **See your first/second static public IP address settings** link to manage your first/second static public IP address in Azure portal.
+If you bring your own static public IP addresses for Azure-SSIS IR, you'll see the **STATIC PUBLIC IP ADDRESSES** tile on your Azure-SSIS IR monitoring page (see [Bringing your own static public IP addresses for Azure-SSIS IR](azure-ssis-integration-runtime-standard-virtual-network-injection.md#ip)). On this tile, you can select links designating your first/second static public IP addresses for Azure-SSIS IR to pop up a window, where you can copy their resource ID (`/subscriptions/YourAzureSubscripton/resourceGroups/YourResourceGroup/providers/Microsoft.Network/publicIPAddresses/YourPublicIPAddress`) from a text box. On the pop-up window, you can also select the **See your first/second static public IP address settings** link to manage your first/second static public IP address in Azure portal.
 
 :::image type="content" source="media/monitor-integration-runtime/monitor-azure-ssis-integration-runtime-static.png" alt-text="Monitor your Azure-SSIS IR - STATIC tile":::
 
