Merge pull request #288358 from halkazwini/nw-qs-sfi

Updates: Quickstart: Diagnose a virtual machine network traffic filter problem using the Azure portal

Author: Stacyrch140

articles/network-watcher/diagnose-vm-network-traffic-filtering-problem.md

@@ -6,7 +6,7 @@ author: halkazwini
 ms.author: halkazwini
 ms.service: azure-network-watcher
 ms.topic: quickstart
-ms.date: 09/30/2024
+ms.date: 10/14/2024
 
 #Customer intent: I want to diagnose a virtual machine (VM) network traffic filter using IP flow verify to know which security rule is denying the traffic and causing the communication problem to the VM.
 ---
@@ -151,8 +151,6 @@ To determine why the rules in the previous section allow or deny communication,
 
 1. Under **Outbound rules**, select **AllowInternetOutBound** to see the allowed destination IP address prefixes under this security rule.
 
-    :::image type="content" source="./media/diagnose-vm-network-traffic-filtering-problem/internet-prefixes.png" alt-text="Screenshot of the prefixes of AllowInternetOutBound rule." lightbox="./media/diagnose-vm-network-traffic-filtering-problem/internet-prefixes.png" :::
-
     You can see that address prefix **13.104.0.0/13** is among the address prefixes of **AllowInternetOutBound** rule. This prefix encompasses IP address **13.107.21.200** which you tested in step 4 of previous section.
 
     Similarly, you can check the other rules to see the source and destination IP address prefixes under each rule.