adjustments from Yair

Author: vhorne

articles/firewall/protect-windows-virtual-desktop.md

@@ -30,9 +30,8 @@ The Azure virtual machines you create for Windows Virtual Desktop must have acce
 
 - Deploy Azure Firewall and configure your WVD host pool subnet User Defined Route (UDR) to route all traffic via the Azure Firewall. Your default route now points to the firewall.
 - Create an application rule collection and add a rule to enable the *WindowsVirtualDesktop* FQDN tag. The source IP address range is the host pool virtual network, the protocol is **https**, and the destination is **WindowsVirtualDesktop**.
-- Enable Storage and Service Bus Service Endpoints on your WVD host pool subnet.
 
-   The set of required storage and service bus accounts for your WVD host pool is deployment specific, so it isn't yet captured in the WindowsVirtualDesktop FQDN tag. You can address this in one of the following ways:
+- The set of required storage and service bus accounts for your WVD host pool is deployment specific, so it isn't yet captured in the WindowsVirtualDesktop FQDN tag. You can address this in one of the following ways:
 
    - Allow https access from your host pool subnet to *xt.blob.core.windows.net and *eh.servicebus.windows.net. These wildcard FQDNs enable the required access, but are less restrictive.
    - Use the following log analytics query to list the exact required FQDNs, and then allow them explicitly in your firewall application rules: