update

Author: KumudD

articles/networking/connectivty-interoperability-configuration.md

@@ -1,5 +1,5 @@
 ---
-title: 'Interoperability in Azure: Configuration details'
+title: 'Interoperability in Azure back-end connectivity features: Configuration details | Microsoft Docs'
 description: This article describes configuration details for the test setup you can use to analyze interoperability between ExpressRoute, a site-to-site VPN, and virtual network peering in Azure.
 documentationcenter: na
 services: networking
@@ -14,7 +14,7 @@ ms.author: rambala
 
 ---
 
-# Interoperability in Azure: Test configuration details
+# Interoperability in Azure back-end connectivity features: Test configuration details
 
 This article describes the configuration details of the [test setup][Setup]. The test setup helps you analyze how Azure networking services interoperate at the control plane level and data plane level.
 
@@ -50,100 +50,100 @@ The following figure shows the connection configuration between the ExpressRoute
 
 The following list shows the primary CE router configuration for ExpressRoute private peering connectivity. (Cisco ASR1000 routers are used as CE routers in the test setup.) When site-to-site VPN and ExpressRoute circuits are configured in parallel to connect an on-premises network to Azure, Azure prioritizes the ExpressRoute circuit by default. To avoid asymmetrical routing, the on-premises network also should prioritize ExpressRoute connectivity over site-to-site VPN connectivity. The following configuration establishes prioritization by using the BGP **local-preference** attribute:
 
-    interface TenGigabitEthernet0/0/0.300
-     description Customer 30 private peering to Azure
-     encapsulation dot1Q 30 second-dot1q 300
-     ip vrf forwarding 30
-     ip address 192.168.30.17 255.255.255.252
-    !
-    interface TenGigabitEthernet1/0/0.30
-     description Customer 30 to south bound LAN switch
-     encapsulation dot1Q 30
-     ip vrf forwarding 30
-     ip address 192.168.30.0 255.255.255.254
-     ip ospf network point-to-point
-    !
-    router ospf 30 vrf 30
-     router-id 10.2.30.253
-     redistribute bgp 65021 subnets route-map BGP2OSPF
-     network 192.168.30.0 0.0.0.1 area 0.0.0.0
-    default-information originate always
-     default-metric 10
-    !
-    router bgp 65021
-     !
-     address-family ipv4 vrf 30
-      network 10.2.30.0 mask 255.255.255.128
-      neighbor 192.168.30.18 remote-as 12076
-      neighbor 192.168.30.18 activate
-      neighbor 192.168.30.18 next-hop-self
-      neighbor 192.168.30.18 soft-reconfiguration inbound
-      neighbor 192.168.30.18 route-map prefer-ER-over-VPN in
-      neighbor 192.168.30.18 prefix-list Cust30_to_Private out
-     exit-address-family
-    !
-    route-map prefer-ER-over-VPN permit 10
-     set local-preference 200
-    !
-    ip prefix-list Cust30_to_Private seq 10 permit 10.2.30.0/25
-    !
+	interface TenGigabitEthernet0/0/0.300
+	 description Customer 30 private peering to Azure
+	 encapsulation dot1Q 30 second-dot1q 300
+	 ip vrf forwarding 30
+	 ip address 192.168.30.17 255.255.255.252
+	!
+	interface TenGigabitEthernet1/0/0.30
+	 description Customer 30 to south bound LAN switch
+	 encapsulation dot1Q 30
+	 ip vrf forwarding 30
+	 ip address 192.168.30.0 255.255.255.254
+	 ip ospf network point-to-point
+	!
+	router ospf 30 vrf 30
+	 router-id 10.2.30.253
+	 redistribute bgp 65021 subnets route-map BGP2OSPF
+	 network 192.168.30.0 0.0.0.1 area 0.0.0.0
+	default-information originate always
+	 default-metric 10
+	!
+	router bgp 65021
+	 !
+	 address-family ipv4 vrf 30
+	  network 10.2.30.0 mask 255.255.255.128
+	  neighbor 192.168.30.18 remote-as 12076
+	  neighbor 192.168.30.18 activate
+	  neighbor 192.168.30.18 next-hop-self
+	  neighbor 192.168.30.18 soft-reconfiguration inbound
+	  neighbor 192.168.30.18 route-map prefer-ER-over-VPN in
+	  neighbor 192.168.30.18 prefix-list Cust30_to_Private out
+	 exit-address-family
+	!
+	route-map prefer-ER-over-VPN permit 10
+	 set local-preference 200
+	!
+	ip prefix-list Cust30_to_Private seq 10 permit 10.2.30.0/25
+	!
 
 ### Site-to-site VPN configuration details
 
 The following list shows the primary CE router configuration for site-to-site VPN connectivity:
 
-    crypto ikev2 proposal Cust30-azure-proposal
-     encryption aes-cbc-256 aes-cbc-128 3des
-     integrity sha1
-     group 2
-    !
-    crypto ikev2 policy Cust30-azure-policy
-     match address local 66.198.12.106
-     proposal Cust30-azure-proposal
-    !
-    crypto ikev2 keyring Cust30-azure-keyring
-     peer azure
-      address 52.168.162.84
-      pre-shared-key local IamSecure123
-      pre-shared-key remote IamSecure123
-    !
-    crypto ikev2 profile Cust30-azure-profile
-     match identity remote address 52.168.162.84 255.255.255.255
-     identity local address 66.198.12.106
-     authentication local pre-share
-     authentication remote pre-share
-     keyring local Cust30-azure-keyring
-    !
-    crypto ipsec transform-set Cust30-azure-ipsec-proposal-set esp-aes 256 esp-sha-hmac
-     mode tunnel
-    !
-    crypto ipsec profile Cust30-azure-ipsec-profile
-     set transform-set Cust30-azure-ipsec-proposal-set
-     set ikev2-profile Cust30-azure-profile
-    !
-    interface Loopback30
-     ip address 66.198.12.106 255.255.255.255
-    !
-    interface Tunnel30
-     ip vrf forwarding 30
-     ip address 10.2.30.125 255.255.255.255
-     tunnel source Loopback30
-     tunnel mode ipsec ipv4
-     tunnel destination 52.168.162.84
-     tunnel protection ipsec profile Cust30-azure-ipsec-profile
-    !
-    router bgp 65021
-     !
-     address-family ipv4 vrf 30
-      network 10.2.30.0 mask 255.255.255.128
-      neighbor 10.10.30.254 remote-as 65515
-      neighbor 10.10.30.254 ebgp-multihop 5
-      neighbor 10.10.30.254 update-source Tunnel30
-      neighbor 10.10.30.254 activate
-      neighbor 10.10.30.254 soft-reconfiguration inbound
-     exit-address-family
-    !
-    ip route vrf 30 10.10.30.254 255.255.255.255 Tunnel30
+	crypto ikev2 proposal Cust30-azure-proposal
+	 encryption aes-cbc-256 aes-cbc-128 3des
+	 integrity sha1
+	 group 2
+	!
+	crypto ikev2 policy Cust30-azure-policy
+	 match address local 66.198.12.106
+	 proposal Cust30-azure-proposal
+	!
+	crypto ikev2 keyring Cust30-azure-keyring
+	 peer azure
+	  address 52.168.162.84
+	  pre-shared-key local IamSecure123
+	  pre-shared-key remote IamSecure123
+	!
+	crypto ikev2 profile Cust30-azure-profile
+	 match identity remote address 52.168.162.84 255.255.255.255
+	 identity local address 66.198.12.106
+	 authentication local pre-share
+	 authentication remote pre-share
+	 keyring local Cust30-azure-keyring
+	!
+	crypto ipsec transform-set Cust30-azure-ipsec-proposal-set esp-aes 256 esp-sha-hmac
+	 mode tunnel
+	!
+	crypto ipsec profile Cust30-azure-ipsec-profile
+	 set transform-set Cust30-azure-ipsec-proposal-set
+	 set ikev2-profile Cust30-azure-profile
+	!
+	interface Loopback30
+	 ip address 66.198.12.106 255.255.255.255
+	!
+	interface Tunnel30
+	 ip vrf forwarding 30
+	 ip address 10.2.30.125 255.255.255.255
+	 tunnel source Loopback30
+	 tunnel mode ipsec ipv4
+	 tunnel destination 52.168.162.84
+	 tunnel protection ipsec profile Cust30-azure-ipsec-profile
+	!
+	router bgp 65021
+	 !
+	 address-family ipv4 vrf 30
+	  network 10.2.30.0 mask 255.255.255.128
+	  neighbor 10.10.30.254 remote-as 65515
+	  neighbor 10.10.30.254 ebgp-multihop 5
+	  neighbor 10.10.30.254 update-source Tunnel30
+	  neighbor 10.10.30.254 activate
+	  neighbor 10.10.30.254 soft-reconfiguration inbound
+	 exit-address-family
+	!
+	ip route vrf 30 10.10.30.254 255.255.255.255 Tunnel30
 
 ## On-premises Location 2 connectivity by using ExpressRoute
 

articles/virtual-network/manage-network-security-group.md

@@ -6,7 +6,7 @@ services: virtual-network
 documentationcenter: na
 author: KumudD
 ms.service: virtual-network
-ms.devlang: NA
+
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: infrastructure-services