commit

Author: cfields475

articles/virtual-wan/How to configure Route-maps to drop inbound routes from Branch sites.md renamed to articles/virtual-wan/how-to-configure-route-maps-to-drop-inbound-routes-from-branch-sites.md

@@ -28,7 +28,7 @@ Verify that you've met the following criteria before beginning your configuratio
 
 In this situation we have two hubs. Hub 1 has 2 VNets and a VPN branch office. One of the VNets has an NVA peered with the hub.  Hub 2 also has 2 VNets and a VPN branch office. 
 
- :::image type="content" source="./media/route-maps-how-to-summarize/Environment.png" alt-text="Screenshot shows how to the Enviroment." lightbox="./media/route-maps-how-to-summarize/Environment.png":::
+ :::image type="content" source="./media/route-maps-how-to-summarize/environment.png" alt-text="Screenshot shows how to the Enviroment." lightbox="./media/route-maps-how-to-summarize/environment.png":::
 
 Here is the addressing for this environment:  
 
@@ -48,35 +48,35 @@ Here is the addressing for this environment:
 
 In this scenario, the goal is to drop routes being advertised from VPN branch site 1.  In this example we will be taking the routes 10.122.1.0/24,10.122.2.0/24, 10.122.3.0/24 and dropping them.   
 
- :::image type="content" source="./media/route-maps-how-to-Drop/drop.png" alt-text="Screenshot that shows the Scenario." lightbox="./media/route-maps-how-to-Drop/drop.png":::
+ :::image type="content" source="./media/route-maps-how-to-drop/drop.png" alt-text="Screenshot that shows the Scenario." lightbox="./media/route-maps-how-to-drop/drop.png":::
 
 ## Workflow
 
 1.  Use the Route-Map dashboard in hub 1 to verify what routes are being advertised from the VPN branch. 
 
-   :::image type="content" source="./media/route-maps-how-to-Drop/DB_Before.png" alt-text="Screenshot that shows routes before." lightbox="./media/route-maps-how-to-Drop/DB_Before.png":::  
+   :::image type="content" source="./media/route-maps-how-to-drop/db_before.png" alt-text="Screenshot that shows routes before." lightbox="./media/route-maps-how-to-drop/db_before.png":::  
 
    Verify the routes are showing up in the effective route table for hub 1.
 
-   :::image type="content" source="./media/route-maps-how-to-Drop/ER_Before.png" alt-text="Screenshot that shows routes before." lightbox="./media/route-maps-how-to-Drop/ER_Before.png":::   
+   :::image type="content" source="./media/route-maps-how-to-drop/er_before.png" alt-text="Screenshot that shows routes before." lightbox="./media/route-maps-how-to-drop/er_before.png":::   
 
 2. Create a Route-Map to drop the routes. If this is your frist time creating a Route-Map, see [How to configure Route-maps](route-maps-how-to.md) for more information. 
 
    The Route-Map will have a match rule for route 10.122.2.0/16. The action **Drop** will be selected. 
 
-   :::image type="content" source="./media/route-maps-how-to-Drop/RM.png" alt-text="Screenshot that shows the Route-map." lightbox="./media/route-maps-how-to-Drop/RM.png":::
+   :::image type="content" source="./media/route-maps-how-to-drop/rm.png" alt-text="Screenshot that shows the Route-map." lightbox="./media/route-maps-how-to-drop/rm.png":::
 
 3. Apply the Route-Map on the VPN branch 1 site connection. The Route-Map will be applied in the inbound direction. 
 
-   :::image type="content" source="./media/route-maps-how-to-Drop/Apply.png" alt-text="Screenshot that shows applying the Route-Map." lightbox="./media/route-maps-how-to-Drop/Apply.png":::
+   :::image type="content" source="./media/route-maps-how-to-drop/apply.png" alt-text="Screenshot that shows applying the Route-Map." lightbox="./media/route-maps-how-to-drop/apply.png":::
 
 4. Using the Route-Map dashboard in Hub 1, Verify that routes 10.122.1.0/24,10.122.2.0/24, 10.122.3.0/24 are being dropped.   
 
-   :::image type="content" source="./media/route-maps-how-to-Drop/DB_After.png" alt-text="Screenshot that shows routes after applying Route-Map." lightbox="./media/route-maps-how-to-Drop/DB_After.png":::
+   :::image type="content" source="./media/route-maps-how-to-drop/db_after.png" alt-text="Screenshot that shows routes after applying Route-Map." lightbox="./media/route-maps-how-to-drop/db_after.png":::
 
    Verify the routes are no longer in the effective route table.
 
-   :::image type="content" source="./media/route-maps-how-to-Drop/ER_After.png" alt-text="Screenshot that shows routes after applying Route-Map." lightbox="./media/route-maps-how-to-Drop/ER_After.png":::
+   :::image type="content" source="./media/route-maps-how-to-drop/er_after.png" alt-text="Screenshot that shows routes after applying Route-Map." lightbox="./media/route-maps-how-to-drop/ER_after.png":::
 
 ## Next steps
 

articles/virtual-wan/How to configure Route-maps to prepend routes.md renamed to articles/virtual-wan/how-to-configure-route-maps-to-prepend-routes.md

@@ -27,7 +27,7 @@ Verify that you've met the following criteria before beginning your configuratio
 ## Design
 In this situation we have two hubs. Hub 1 has 2 VNets and a VPN branch office. One of the VNets has an NVA peered with the hub.  Hub 2 also has 2 VNets and a VPN branch office. 
 
-   :::image type="content" source="./media/route-maps-how-to-summarize/Environment.png" alt-text="Screenshot shows how to the Enviroment." lightbox="./media/route-maps-how-to-summarize/Environment.png":::
+   :::image type="content" source="./media/route-maps-how-to-summarize/environment.png" alt-text="Screenshot shows how to the Enviroment." lightbox="./media/route-maps-how-to-summarize/environment.png":::
 
 Here is the addressing for this environment:  
 
@@ -55,29 +55,29 @@ In this scenario, the goal is to prepend route 10.5.0.192/26 from VNet 3 on Hub
 
 1.  Use the Route-Map dashboard in hub 2 to verify the ASNs on routes are being advertised from the VNet connection. 
 
-   :::image type="content" source="./media/route-maps-how-to-prepend/DB_Before_1.png" alt-text="Screenshot that shows the routes before Route-Map." lightbox="./media/route-maps-how-to-prepend/DB_Before_1.png":::
+   :::image type="content" source="./media/route-maps-how-to-prepend/db_before_one.png" alt-text="Screenshot that shows the routes before Route-Map." lightbox="./media/route-maps-how-to-prepend/db_before_one.png":::
 
    look at the Route-Map dashboard for the VPN brach 2 to verify the ASNs for route 10.5.0.192/26 that are being sent to the branch office. 
 
-   :::image type="content" source="./media/route-maps-how-to-prepend/DB_Before_2.png" alt-text="Screenshot that shows the routes before Route-Map." lightbox="./media/route-maps-how-to-prepend/DB_Before_2.png"::: 
+   :::image type="content" source="./media/route-maps-how-to-prepend/db_before_two.png" alt-text="Screenshot that shows the routes before Route-Map." lightbox="./media/route-maps-how-to-prepend/db_before_two.png"::: 
 
 2. Create a Route-Map to tag the route. If this is your frist time creating a Route-Map, see [How to configure Route-maps](route-maps-how-to.md) for more information. 
 
    The Route-Map will have a match rule for route 10.5.0.192/26. The action **modify** will be selected. Route Modification will have an **Prepend** for **AS Path** 65533.  
 
-   :::image type="content" source="./media/route-maps-how-to-prepend/RM.png" alt-text="Screenshot that shows the Route-Map." lightbox="./media/route-maps-how-to-prepend/RM.png":::
+   :::image type="content" source="./media/route-maps-how-to-prepend/rm.png" alt-text="Screenshot that shows the Route-Map." lightbox="./media/route-maps-how-to-prepend/rm.png":::
 
 3. Apply the Route-Map on the VNet 3 connection. The Route-Map will be applied in the inbound direction. 
 
-   :::image type="content" source="./media/route-maps-how-to-prepend/Apply.png" alt-text="Screenshot the Route-map being applied." lightbox="./media/route-maps-how-to-prepend/Apply.png":::
+   :::image type="content" source="./media/route-maps-how-to-prepend/apply.png" alt-text="Screenshot the Route-map being applied." lightbox="./media/route-maps-how-to-prepend/apply.png":::
 
 4. Using the Route-Map dashboard in Hub 2, Verify that route 10.5.0.192/26 has an ASN of 65533 added.    
 
-   :::image type="content" source="./media/route-maps-how-to-prepend/DB_After_1.png" alt-text="Screenshot of routes after Route-map being applied." lightbox="./media/route-maps-how-to-prepend/DB_After_1.png":::
+   :::image type="content" source="./media/route-maps-how-to-prepend/db_after_one.png" alt-text="Screenshot of routes after Route-map being applied." lightbox="./media/route-maps-how-to-prepend/db_after_one.png":::
 
    look at the Route-Map dashboard for VPN branch 2 connection to verify route 10.5.0.192/26 has the ASNs 65533 advertised to VPN branch 2.
 
-   :::image type="content" source="./media/route-maps-how-to-prepend/DB_After_2.png" alt-text="Screenshot of routes after Route-map being applied." lightbox="./media/route-maps-how-to-prepend/DB_After_2.png":::
+   :::image type="content" source="./media/route-maps-how-to-prepend/db_after_two.png" alt-text="Screenshot of routes after Route-map being applied." lightbox="./media/route-maps-how-to-prepend/db_after_two.png":::
 
 ## Next steps
 

articles/virtual-wan/How to configure Route-maps to summarize routes from an NVA in a spoke VNet .md renamed to articles/virtual-wan/how-to-configure-route-maps-to-summarize-routes-from-an-device-a-spoke-vNet .md

@@ -27,7 +27,7 @@ Verify that you've met the following criteria before beginning your configuratio
 ## Design
 In this situation we have two hubs. Hub 1 has 2 VNets and a VPN branch office. One of the VNets has an NVA peered with the hub.  Hub 2 also has 2 VNets and a VPN branch office. 
 
-   :::image type="content" source="./media/route-maps-how-to-summarize/Environment.png" alt-text="Screenshot shows how to the Enviroment." lightbox="./media/route-maps-how-to-summarize/Environment.png":::
+   :::image type="content" source="./media/route-maps-how-to-summarize/environment.png" alt-text="Screenshot shows how to the Enviroment." lightbox="./media/route-maps-how-to-summarize/environment.png":::
 
 Here is the addressing for this environment:  
 
@@ -47,33 +47,35 @@ Here is the addressing for this environment:
 
 In this scenario, the goal is to summarize some routes being advertised to the hub from the NVA in VNet 1. In this example we will be taking the routes 10.150.1.0/24, 10.150.2.0/24, 10.150.3.0/24, 10.150.4.0/24, and summarizing them to 10.150.0.0/16   
 
-   :::image type="content" source="./media/route-maps-how-to-NVA/NVA.png" alt-text="Screenshot that shows the Scenario." lightbox="route-maps-how-to-NVA/NVA.png":::
+   :::image type="content" source="./media/route-maps-how-to-nva/nva.png" alt-text="Screenshot that shows the Scenario." lightbox="route-maps-how-to-nva/nva.png":::
 
 ## Workflow
 
 1.  Use the Route-Map dashboard in hub 1 to verify the correct routes are currently being advertised from VNet 1 to the hub.
 
-   :::image type="content" source="./media/route-maps-how-to-NVA/DB_Before_1.png" alt-text="Screenshot that shows the routes before Route-maps." lightbox="route-maps-how-to-NVA/DB_Before_1.png":::
+   :::image type="content" source="./media/route-maps-how-to-nva/db_before_one.png" alt-text="Screenshot that shows the routes before Route-maps." lightbox="route-maps-how-to-nva/db_before_one.png":::
 
    use the Route-Map dashboard to verify the routes being sent to VPN branch 1.  
-   :::image type="content" source="./media/route-maps-how-to-NVA/DB_Before_2.png" alt-text="Screenshot that shows the routes before Route-maps." lightbox="route-maps-how-to-NVA/DB_Before_2.png":::  
+
+   :::image type="content" source="./media/route-maps-how-to-nva/db_before_2.png" alt-text="Screenshot that shows the routes before Route-maps." lightbox="route-maps-how-to-nva/db_before_2.png":::  
 
 2. Create a Route-Map to tag the route. If this is your frist time creating a Route-Map, see [How to configure Route-maps](route-maps-how-to.md) for more information. 
 
    The Route-Map will have a match rule for route 10.150.0.0/16. The action **modify** will be selected. Route Modification will have an **Replace** for **RoutePrefix** 10.150.0.0/16.  
-   :::image type="content" source="./media/route-maps-how-to-NVA/RM.png" alt-text="Screenshot that shows the Route-map." lightbox="route-maps-how-to-NVA/RM.png":::
+
+   :::image type="content" source="./media/route-maps-how-to-nva/rm.png" alt-text="Screenshot that shows the Route-map." lightbox="route-maps-how-to-nva/rm.png":::
 
 3. Apply the Route-Map on the VNet 1 connection. The Route-Map will be applied in the inbound direction. 
 
-   :::image type="content" source="./media/route-maps-how-to-NVA/Apply.png" alt-text="Screenshot that shows the Route-map being applied." lightbox="route-maps-how-to-NVA/Apply.png":::
+   :::image type="content" source="./media/route-maps-how-to-nva/apply.png" alt-text="Screenshot that shows the Route-map being applied." lightbox="route-maps-how-to-nva/apply.png":::
 
 4. Using the Route-Map dashboard in Hub 1, Verify that route 10.150.0.0/16 is being summarized.    
 
-   :::image type="content" source="./media/route-maps-how-to-NVA/DB_After_1.png" alt-text="Screenshot that shows the Route-map being applied." lightbox="route-maps-how-to-NVA/DB_After_1.png":::
+   :::image type="content" source="./media/route-maps-how-to-nva/db_after_one.png" alt-text="Screenshot that shows the Route-map being applied." lightbox="route-maps-how-to-NVA/db_after_one.png":::
 
    Using the Route-Map dashboard verify route 10.150.0.0/16 has been advertised to VPN branch 1
 
-   :::image type="content" source="./media/route-maps-how-to-NVA/DB_After_2.png" alt-text="Screenshot that shows the Route-map being applied." lightbox="route-maps-how-to-NVA/DB_After_2.png":::
+   :::image type="content" source="./media/route-maps-how-to-nva/db_after_two.png" alt-text="Screenshot that shows the Route-map being applied." lightbox="route-maps-how-to-nva/db_after_two.png":::
 
 ## Next steps
 

articles/virtual-wan/How to configure Route-maps to tag routes.md renamed to articles/virtual-wan/how-to-configure-route-maps-to-tag-routes.md

@@ -27,7 +27,7 @@ Verify that you've met the following criteria before beginning your configuratio
 ## Design
 In this situation we have two hubs. Hub 1 has 2 VNets and a VPN branch office. One of the VNets has an NVA peered with the hub.  Hub 2 also has 2 VNets and a VPN branch office. 
 
-   :::image type="content" source="./media/route-maps-how-to-summarize/Environment.png" alt-text="Screenshot shows how to the Enviroment." lightbox="./media/route-maps-how-to-summarize/Environment.png":::
+   :::image type="content" source="./media/route-maps-how-to-summarize/environment.png" alt-text="Screenshot shows how to the Enviroment." lightbox="./media/route-maps-how-to-summarize/environment.png":::
 
 Here is the addressing for this environment:  
 
@@ -47,34 +47,35 @@ Here is the addressing for this environment:
 
 In this scenario, the goal is to tag route 10.5.0.192/26 form VNet 3 on Hub 2 with BGP community 3356:70   
 
-   :::image type="content" source="./media/route-maps-how-to-Tag/tag.png" alt-text="Screenshot that shows the Scenario." lightbox="./media/route-maps-how-to-Tag/tag.png":::
+   :::image type="content" source="./media/route-maps-how-to-tag/tag.png" alt-text="Screenshot that shows the Scenario." lightbox="./media/route-maps-how-to-tag/tag.png":::
 
 ## Workflow
 
 1. Use the Route-Map dashboard in hub 2 to verify the BGP community on the route 10.5.0.192/26 being advertised from the VNet connection.
 
-   :::image type="content" source="./media/route-maps-how-to-Tag/DB_Before.png" alt-text="Screenshot that shows routes before Route-map." lightbox="./media/route-maps-how-to-Tag/DB_Before.png"::: 
+   :::image type="content" source="./media/route-maps-how-to-tag/db_before.png" alt-text="Screenshot that shows routes before Route-map." lightbox="./media/route-maps-how-to-tag/db_before.png"::: 
 
    look at the Route-Map dashboard for the VPN Brach to verify the BGP community on the route for 10.5.0.192/26. The goal is to very what routes are being sent on prem.
-   :::image type="content" source="./media/route-maps-how-to-Tag/DB_Before_2.png" alt-text="Screenshot that shows routes before Route-map." lightbox="./media/route-maps-how-to-Tag/DB_Before_2.png":::   
+
+   :::image type="content" source="./media/route-maps-how-to-tag/db_before_2.png" alt-text="Screenshot that shows routes before Route-map." lightbox="./media/route-maps-how-to-tag/db_before_2.png":::   
 
 2. Create a Route-Map to tag the route. If this is your frist time creating a Route-Map, see [How to configure Route-maps](route-maps-how-to.md) for more information. 
 
    The Route-Map will have a match rule for route 10.5.0.192/26. The action **modify** will be selected. Route Modification will have an **add** for **community** 3356:70.  
 
-   :::image type="content" source="./media/route-maps-how-to-Tag/RM.png" alt-text="Screenshot that shows the Route-map." lightbox="./media/route-maps-how-to-Tag/RM.png":::
+   :::image type="content" source="./media/route-maps-how-to-tag/rm.png" alt-text="Screenshot that shows the Route-map." lightbox="./media/route-maps-how-to-tag/rm.png":::
 
 3. Apply the Route-Map on the VNet 3 connection. The Route-Map will be applied in the inbound direction. 
 
-   :::image type="content" source="./media/route-maps-how-to-Tag/RM.png" alt-text="Screenshot that shows the Route-map being applied." lightbox="./media/route-maps-how-to-Tag/Apply.png":::
+   :::image type="content" source="./media/route-maps-how-to-tag/rm.png" alt-text="Screenshot that shows the Route-map being applied." lightbox="./media/route-maps-how-to-tag/apply.png":::
 
 4. Using the Route-Map dashboard in Hub 2, Verify that route 10.5.0.192/26 has the BGP community of 3356:70 added on the VNet 3 connection.    
 
-   :::image type="content" source="./media/route-maps-how-to-Tag/DB_After.png" alt-text="Screenshot that shows routes after Route-map being applied." lightbox="./media/route-maps-how-to-Tag/DB_After.png":::
+   :::image type="content" source="./media/route-maps-how-to-tag/db_after.png" alt-text="Screenshot that shows routes after Route-map being applied." lightbox="./media/route-maps-how-to-tag/db_after.png":::
 
    look at the Route-Map dashboard for the VPN branch connection to verify route 10.5.0.192/26 has the BGP community 3356:70 being advertised to the VPN branch office 2.  
 
-   :::image type="content" source="./media/route-maps-how-to-Tag/RM_After_2.png" alt-text="Screenshot that shows routes after Route-map being applied." lightbox="./media/route-maps-how-to-Tag/RM_After_2.png":::
+   :::image type="content" source="./media/route-maps-how-to-Tag/rm_after_two.png" alt-text="Screenshot that shows routes after Route-map being applied." lightbox="./media/route-maps-how-to-tag/rm_after_two.png":::
 
 ## Next steps