Merge pull request #8620 from MicrosoftDocs/main

Publish 07/27/2023, 3:30 PM

windows/deployment/do/mcc-isp-overview.md

@@ -6,7 +6,7 @@ ms.prod: windows-client
 author: amymzhou
 ms.author: amyzhou
 ms.topic: article
-ms.date: 05/09/2023
+ms.date: 07/27/2023
 ms.technology: itpro-updates
 ms.collection: tier3
 ---
@@ -18,7 +18,7 @@ ms.collection: tier3
 - Windows 10
 - Windows 11
 
-Microsoft Connected Cache (MCC) for Internet Service Providers (preview) is a software-only caching solution that delivers Microsoft content. MCC can be deployed to as many bare-metal servers or VMs as needed and is managed from a cloud portal. When deployed, MCC can help to reduce your network bandwidth usage for Microsoft software content and updates. Cache nodes are created in the cloud portal and are configured to deliver traffic to customers by manual CIDR or BGP routing.
+Microsoft Connected Cache (MCC) for Internet Service Providers (preview) is a free software-only caching solution that delivers Microsoft content. MCC can be deployed free of charge to as many bare-metal servers or VMs as needed and is managed from a cloud portal. When deployed, MCC can help to reduce your network bandwidth usage for Microsoft software content and updates. Cache nodes are created in the cloud portal and are configured to deliver traffic to customers by manual CIDR or BGP routing.
 
 ## Supported scenarios
 
@@ -37,4 +37,37 @@ Microsoft Connected Cache uses Delivery Optimization as the backbone for Microso
 - Endpoint protection: Windows Defender definition updates
 - Xbox: Xbox Game Pass (PC only)
 
+Do you peer with [Microsoft (ASN 8075)](/azure/internet-peering/)? Microsoft Connected Cache complements peering by offloading static content that is served off of multiple CDNs such as Akamai, Lumen, and Edgecast. Microsoft Peering mainly caches dynamic content - by onboarding to Microsoft Connected Cache, you'll cache static content that otherwise would be served from the CDN. 
+
 For the full list of content endpoints that Microsoft Connected Cache for ISPs supports, see [Microsoft Connected Cache content and services endpoints](delivery-optimization-endpoints.md).
+
+## How MCC works
+
+:::image type="content" source="./images/mcc-isp-diagram.png" alt-text="Data flow diagram of how Microsoft Connected Cache works." lightbox="./images/mcc-isp-diagram.png":::
+
+The following steps describe how MCC is provisioned and used:
+
+1. The Azure portal is used to create and manage MCC nodes.
+
+1. A shell script is used to provision the server and deploy the MCC application.
+
+1. A combination of the Azure portal and shell script is used to configure Microsoft Delivery Optimization Services to route traffic to the MCC server.
+
+    - The publicly accessible IPv4 address of the server is configured on the portal.
+
+    - **Manual Routing:** Providing the CIDR blocks that represent the client IP address space, which should be routed to the MCC node.
+
+    - **BGP Routing:** A shell script is used to initiate a peering session with a router in the operator network, and the operator initiates a session with the MCC node.
+
+        > [!NOTE]
+        > Only IPv4 addresses are supported at this time. Entering IPv6 addresses will result in an error.
+
+1. Microsoft end-user devices (clients) periodically connect with Microsoft Delivery Optimization Services, and the services match the IP address of the client with the IP address of the corresponding MCC node.
+
+1. Microsoft clients make the range requests for content from the MCC node.
+
+1. An MCC node gets content from the CDN, seeds its local cache stored on disk, and delivers the content to the client.
+
+1. Subsequent requests from end-user devices for content will be served from cache.
+
+1. If the MCC node is unavailable, the client gets content from the CDN to ensure uninterrupted service for your subscribers.