Merge pull request #79005 from HJToland3/localworking

Localworking

Author: GitHubber17

articles/dms/resource-network-topologies.md

@@ -1,6 +1,6 @@
 ---
-title: Network topologies for Azure SQL Database Managed Instance migrations using the Azure Database Migration Service | Microsoft Docs
-description: Learn the source and target configurations for Database Migration Service.
+title: Network topologies for Azure SQL Database Managed Instance migrations using Azure Database Migration Service | Microsoft Docs
+description: Learn the source and target configurations for Azure Database Migration Service.
 services: database-migration
 author: HJToland3
 ms.author: jtoland
@@ -10,54 +10,62 @@ ms.service: dms
 ms.workload: data-services
 ms.custom: mvc
 ms.topic: article
-ms.date: 03/12/2019
+ms.date: 06/07/2019
 ---
 
-# Network topologies for Azure SQL DB Managed Instance migrations using the Azure Database Migration Service
-This article discusses various network topologies that the Azure Database Migration Service can work with to provide a comprehensive migration experience from on-premises SQL Servers to Azure SQL Database Managed Instance.
+# Network topologies for Azure SQL DB Managed Instance migrations using Azure Database Migration Service
+
+This article discusses various network topologies that Azure Database Migration Service can work with to provide a comprehensive migration experience from on-premises SQL Servers to Azure SQL Database Managed Instance.
 
 ## Azure SQL Database Managed Instance configured for Hybrid workloads 
+
 Use this topology if your Azure SQL Database Managed Instance is connected to your on-premises network. This approach provides the most simplified network routing and yields maximum data throughput during the migration.
 
 ![Network Topology for Hybrid Workloads](media/resource-network-topologies/hybrid-workloads.png)
 
 **Requirements**
-- In this scenario, the Azure SQL Database Managed Instance and the Azure Database Migration Service instance are created in the same Azure VNET, but they use different subnets.  
-- The VNET used in this scenario is also connected to the on-premises network by using either [ExpressRoute](https://docs.microsoft.com/azure/expressroute/expressroute-introduction) or [VPN](https://docs.microsoft.com/azure/vpn-gateway/vpn-gateway-about-vpngateways).
+
+- In this scenario, the Azure SQL Database managed instance and the Azure Database Migration Service instance are created in the same Azure VNet, but they use different subnets.  
+- The VNet used in this scenario is also connected to the on-premises network by using either [ExpressRoute](https://docs.microsoft.com/azure/expressroute/expressroute-introduction) or [VPN](https://docs.microsoft.com/azure/vpn-gateway/vpn-gateway-about-vpngateways).
 
 ## Azure SQL Database Managed Instance isolated from the on-premises network
+
 Use this network topology if your environment requires one or more of the following scenarios:
-- The Azure SQL Database Managed Instance is isolated from on-premises connectivity, but your Azure Database Migration Service instance is connected to the on-premises network.
-- If Role Based Access Control (RBAC) policies are in place and you need to limit the users to accessing the same subscription that is hosting the Azure SQL Database Managed Instance.
-- The VNETs used for the Azure SQL Database Managed Instance and the Azure Database Migration Service are in different subscriptions.
+
+- The Azure SQL Database managed instance is isolated from on-premises connectivity, but your Azure Database Migration Service instance is connected to the on-premises network.
+- If Role Based Access Control (RBAC) policies are in place and you need to limit the users to accessing the same subscription that is hosting the Azure SQL Database managed instance.
+- The VNets used for the Azure SQL Database Managed Instance and Azure Database Migration Service are in different subscriptions.
 
 ![Network Topology for Managed Instance isolated from the on-premises network](media/resource-network-topologies/mi-isolated-workload.png)
 
 **Requirements**
-- The VNET that Azure Database Migration Service uses for this scenario must also be connected to the on-premises network by using either (https://docs.microsoft.com/azure/expressroute/expressroute-introduction) or [VPN](https://docs.microsoft.com/azure/vpn-gateway/vpn-gateway-about-vpngateways).
-- Set up [VNET network peering](https://docs.microsoft.com/azure/virtual-network/virtual-network-peering-overview) between the VNET used for Azure SQL Database Managed Instance and the Azure Database Migration Service.
 
+- The VNet that Azure Database Migration Service uses for this scenario must also be connected to the on-premises network by using either (https://docs.microsoft.com/azure/expressroute/expressroute-introduction) or [VPN](https://docs.microsoft.com/azure/vpn-gateway/vpn-gateway-about-vpngateways).
+- Set up [VNet network peering](https://docs.microsoft.com/azure/virtual-network/virtual-network-peering-overview) between the VNet used for Azure SQL Database managed instance and Azure Database Migration Service.
 
-## Cloud-to-cloud migrations: shared VNET
+## Cloud-to-cloud migrations: shared VNet
 
-Use this topology if the source SQL Server is hosted in an Azure VM and shares the same VNET with Azure SQL Database Managed Instance and the Azure Database Migration Service.
+Use this topology if the source SQL Server is hosted in an Azure VM and shares the same VNET with Azure SQL Database managed instance and Azure Database Migration Service.
 
-![Network Topology for Cloud-to-Cloud migrations with a shared vnet](media/resource-network-topologies/cloud-to-cloud.png)
+![Network Topology for Cloud-to-Cloud migrations with a shared VNet](media/resource-network-topologies/cloud-to-cloud.png)
 
 **Requirements**
+
 - No additional requirements.
 
-## Cloud to cloud migrations: isolated VNET
+## Cloud to cloud migrations: isolated VNet
 
 Use this network topology if your environment requires one or more of the following scenarios:
-- The Azure SQL Database Managed Instance is provisioned in an isolated VNET.
-- If Role Based Access Control (RBAC) policies are in place and you need to limit the users to accessing the same subscription that is hosting the Azure SQL Database Managed Instance.
-- The VNETs used for Azure SQL Database Managed Instance and the Azure Database Migration Service are in different subscriptions.
 
-![Network Topology for Cloud-to-Cloud migrations with an isolated vnet](media/resource-network-topologies/cloud-to-cloud-isolated.png)
+- The Azure SQL Database managed instance is provisioned in an isolated VNet.
+- If Role Based Access Control (RBAC) policies are in place and you need to limit the users to accessing the same subscription that is hosting the Azure SQL Database managed instance.
+- The VNets used for Azure SQL Database Managed Instance and Azure Database Migration Service are in different subscriptions.
+
+![Network Topology for Cloud-to-Cloud migrations with an isolated VNet](media/resource-network-topologies/cloud-to-cloud-isolated.png)
 
 **Requirements**
-- Set up [VNET network peering](https://docs.microsoft.com/azure/virtual-network/virtual-network-peering-overview) between the VNET used for Azure SQL Database Managed Instance and the Azure Database Migration Service.
+
+- Set up [VNet network peering](https://docs.microsoft.com/azure/virtual-network/virtual-network-peering-overview) between the VNet used for Azure SQL Database managed instance and Azure Database Migration Service.
 
 ## Inbound security rules
 
@@ -76,11 +84,13 @@ Use this network topology if your environment requires one or more of the follow
 | SMB share                 | 445                                                   | TCP          | Any        | On-premises address space | Allow      | SMB network share for DMS to store database backup files for migrations to Azure SQL Database MI and SQL Servers on Azure VM <br/>(If you have site-to-site connectivity, you may not need this rule). |
 | DMS_subnet                | Any                                                   | Any          | Any        | DMS_Subnet                | Allow      |                                                                                                                                                                                                  |
 
-## See Also
+## See also
+
 - [Migrate SQL Server to Azure SQL Database Managed Instance](https://docs.microsoft.com/azure/dms/tutorial-sql-server-to-managed-instance)
-- [Overview of prerequisites for using the Azure Database Migration Service](https://docs.microsoft.com/azure/dms/pre-reqs)
+- [Overview of prerequisites for using Azure Database Migration Service](https://docs.microsoft.com/azure/dms/pre-reqs)
 - [Create a virtual network using the Azure portal](https://docs.microsoft.com/azure/virtual-network/quick-create-portal)
 
 ## Next steps
-- For an overview of the Azure Database Migration Service, see the article [What is the Azure Database Migration Service?](dms-overview.md).
-- For current information about regional availability of the Azure Database Migration Service, see the [Products available by region](https://azure.microsoft.com/global-infrastructure/services/?products=database-migration) page.
+
+- For an overview of Azure Database Migration Service, see the article [What is Azure Database Migration Service?](dms-overview.md).
+- For current information about regional availability of Azure Database Migration Service, see the [Products available by region](https://azure.microsoft.com/global-infrastructure/services/?products=database-migration) page.