More updates

windows/deployment/do/waas-delivery-optimization-faq.yml

@@ -45,7 +45,6 @@ sections:
           **For Delivery Optimization metadata**:
 
           - `*.dl.delivery.mp.microsoft.com`
-          - `*.emdl.ws.microsoft.com`
 
           **For the payloads (optional)**:
 
@@ -80,7 +79,6 @@ sections:
 
           Delivery Optimization metadata:
           
-          - `http://emdl.ws.microsoft.com`
           - `http://download.windowsupdate.com`
           - `http://*.dl.delivery.mp.microsoft.com`
 
@@ -108,14 +106,14 @@ sections:
         answer: |
           Delivery Optimization uses the cache content on the device to determine what's available for peering. For the upload source device, there's a limited number (4) of slots for cached content that's available for peering at a given time. Delivery Optimization contains logic that rotates the cached content in those slots.
       
-      - question: What is the recommended configuration for Delivery Optimization used with Zscaler?
+      - question: What is the recommended configuration for Delivery Optimization used with cloud proxies (e.g. Zscaler)?
         answer: |
-          The best configuration with Zscaler is to bypass the [hostnames](waas-delivery-optimization-faq.yml#what-hostnames-should-i-allow-through-my-firewall-to-support-delivery-optimization) for Delivery Optimization services, allowing traffic to go directly to the Internet and not through Zscaler. 
-          For communication between clients and the Delivery Optimization cloud service:
-  
+          The recommended configuration for Delivery Optimization Peer-to-Peer to work most efficiently along with cloud proxy solutions (e.g. Zscaler) is to allow traffic to the Delivery Optimization services to go directly to the internet and not through the cloud proxy.
+          At a minimum, the following FQDN that is used for communication between clients and the Delivery Optimization service should be allowed with direct Internet access and bypass the cloud proxy service: 
+
               •	*.do.dsp.mp.microsoft.com
 
-            If that's not an option, try using Group Download mode '2' to define the peering group. [Learn more](waas-delivery-optimization-reference.md#select-the-source-of-group-ids) about using Group Download mode.
+          If allowing direct Internet access is not an option, try using Group Download Mode '2' to define the peering group. [Learn more](waas-delivery-optimization-reference.md#select-the-source-of-group-ids) about using Group Download mode.
           
       - question: How do I turn off Delivery Optimization?
         answer: |

windows/deployment/do/whats-new-do.md

@@ -23,9 +23,11 @@ ms.collection: tier3
 
 Microsoft Connected Cache (MCC) is a software-only caching solution that delivers Microsoft content within Enterprise networks. MCC can be deployed to as many bare-metal servers or VMs as needed, and is managed from a cloud portal. Cache nodes are created in the cloud portal and are configured by applying the client policy using management tools such as Intune.
 
-For more information about MCC, see [Microsoft Connected Cache overview](waas-microsoft-connected-cache.md).
+For more information about MCC, see [Microsoft Connected Cache overview](waas-microsoft-connected-cache.md) There are two different verions, [Microsoft Connected Cache for Enterprise and Education](mcc-ent-edu-overview.md) and [Microsoft Connected Cache for ISPs](mcc-isp-overview.md).
 
-## New in Delivery Optimization for Windows 10, version 20H2 and Windows 11
+## New in Delivery Optimization for Windows
+
+- Delivery Optimization introduced support for receiver side ledbat (rLedbat) in Windows 22H2.
 
 - New peer selection options: Currently the available options include: 0 = None, 1 = Subnet mask, and 2 = Local Peer Discovery. The subnet mask option applies to both Download Modes LAN (1) and Group (2). If Group mode is set, Delivery Optimization will connect to locally discovered peers that are also part of the same Group (have the same Group ID)."
 - Local Peer Discovery: a new option for **[Restrict Peer Selection By](waas-delivery-optimization-reference.md#select-a-method-to-restrict-peer-selection)** (in Group Policy) or **DORestrictPeerSelectionBy** (in MDM). This option restricts the discovery of local peers using the DNS-SD protocol. When you set Option 2, Delivery Optimization will restrict peer selection to peers that are locally discovered (using DNS-SD). If Group mode is enabled, Delivery Optimization will connect to locally discovered peers that are also part of the same group, for those devices with the same Group ID).