fix blocking pr issues

Author: duongau

articles/expressroute/expressroute-optimize-routing.md

@@ -21,7 +21,7 @@ To ensure traffic flows over the desired path with multiple ExpressRoute circuit
 
 Consider the following example scenario:
 
-![Diagram showing suboptimal routing from customer to Microsoft](./media/expressroute-optimize-routing/expressroute-localPreference.png)
+![Diagram showing suboptimal routing from customer to Microsoft.](./media/expressroute-optimize-routing/expressroute-localPreference.png)
 
 To prefer ExpressRoute paths, configure Local Preference as follows:
 
@@ -48,13 +48,13 @@ user@R1# set protocols bgp group ibgp local-preference 150
 
 Imagine you have two offices in the US, one in Los Angeles and one in New York, connected via a WAN. You have two ExpressRoute circuits, one in US West and one in US East, both connected on the WAN. You intend for Los Angeles users to connect to Azure US West and New York users to Azure US East. However, without knowing which prefix is from which region, your WAN may route both offices' traffic to the US East circuit, causing suboptimal routing for Los Angeles users.
 
-![Suboptimal routing from customer to Microsoft](./media/expressroute-optimize-routing/expressroute-case1-problem.png)
+![Diagram of suboptimal routing from customer to Microsoft.](./media/expressroute-optimize-routing/expressroute-case1-problem.png)
 
 ### Solution: use BGP Communities
 
 To optimize routing, use [BGP Community values](expressroute-routing.md) to identify prefixes from each Azure region. For example, `12076:51004` for US East and `12076:51006` for US West. Configure higher local preference values for the appropriate prefixes in each region to ensure traffic takes the optimal path.
 
-![Solution using BGP Communities](./media/expressroute-optimize-routing/expressroute-case1-solution.png)
+![Diagram of a solution using BGP Communities.](./media/expressroute-optimize-routing/expressroute-case1-solution.png)
 
 > [!NOTE]
 > The same technique can be applied to routing from customer to Azure virtual network using private peering. Configure your routers to prefer one ExpressRoute circuit over another based on your virtual network deployments.
@@ -63,13 +63,13 @@ To optimize routing, use [BGP Community values](expressroute-routing.md) to iden
 
 In this scenario, Microsoft connections take a longer path to reach your network. For example, Exchange Online connections to on-premises servers may route through the wrong ExpressRoute circuit. Without hints, Microsoft can't determine which on-premises prefix is closer to which circuit.
 
-![Suboptimal routing from Microsoft to customer](./media/expressroute-optimize-routing/expressroute-case2-problem.png)
+![Diagram of suboptimal routing from Microsoft to customer's on-premises.](./media/expressroute-optimize-routing/expressroute-case2-problem.png)
 
 ### Solution: use AS PATH prepending
 
 Advertise your on-premises prefixes on the appropriate ExpressRoute circuits or use AS PATH prepending to influence routing. Lengthen the AS PATH for prefixes in the less preferred region to ensure Microsoft prefers the optimal path.
 
-![Solution using AS PATH prepending](./media/expressroute-optimize-routing/expressroute-case2-solution.png)
+![Diagram of a solution using AS PATH prepending.](./media/expressroute-optimize-routing/expressroute-case2-solution.png)
 
 > [!IMPORTANT]
 > We remove private AS numbers in the AS PATH for prefixes received on Microsoft Peering when using a private AS number. Peer with a public AS and append public AS numbers in the AS PATH to influence routing for Microsoft Peering.
@@ -78,13 +78,13 @@ Advertise your on-premises prefixes on the appropriate ExpressRoute circuits or
 
 With ExpressRoute, you can enable VNet-to-VNet communication by linking them to an ExpressRoute circuit. Suboptimal routing can occur when VNets are linked to multiple circuits. For example, VNets in US West and US East may route traffic through the remote circuit due to ECMP routing.
 
-![Suboptimal routing between virtual networks](./media/expressroute-optimize-routing/expressroute-case3-problem.png)
+![Diagram of suboptimal routing between virtual networks.](./media/expressroute-optimize-routing/expressroute-case3-problem.png)
 
 ### Solution: assign a high weight to local connection
 
 Assign a higher weight to the local connection to ensure VNets prefer the optimal path. This configuration ensures traffic takes the shortest path between VNets.
 
-![Solution assigning high weight to local connection](./media/expressroute-optimize-routing/expressroute-case3-solution.png)
+![Diagram of a solution assigning high weight to local connection.](./media/expressroute-optimize-routing/expressroute-case3-solution.png)
 
 > [!NOTE]
 > You can also influence routing from VNet to your on-premises network by configuring the connection weight instead of using AS PATH prepending. The connection weight is considered before the AS Path length when deciding how to send traffic.

articles/expressroute/expressroute-prerequisites.md

@@ -34,10 +34,6 @@ To connect to Microsoft cloud services using ExpressRoute, ensure the following
 * **QoS**: Skype for Business services (e.g., voice, video, text) requires differentiated QoS treatment. Follow the [QoS requirements](expressroute-qos.md) with your provider.
 * **Network Security**: Consider [network security](/azure/cloud-adoption-framework/reference/networking-vdc) when connecting to the Microsoft Cloud via ExpressRoute.
 
-## Microsoft 365
-
-If you plan to enable Microsoft 365 on ExpressRoute, review the following documents for more information about Microsoft 365 requirements.
-
 ## Microsoft 365 requirements
 
 If you plan to use Microsoft 365 with ExpressRoute, review the following resources for detailed requirements and guidelines: