mcc-branding

windows/deployment/do/delivery-optimization-troubleshoot.md

@@ -29,7 +29,7 @@ This article discusses how to troubleshoot Delivery Optimization.
 
 - -HealthCheck: Provides an overall check of the device setup to ensure Delivery Optimization communication is possible on the device.
 - -P2P: Provides output specific to P2P settings, efficiency, and errors.
-- -MCC: Provides output specific to MCC settings and verifies the client can access the cache server.
+- -MCC: Provides output specific to Microsoft Connected Cache settings and verifies the client can access the cache server.
 
 ## Common problems and solutions
 

windows/deployment/do/index.yml

@@ -32,7 +32,7 @@ landingContent:
             url: waas-delivery-optimization.md
           - text: What's new in Delivery Optimization
             url: whats-new-do.md
-          - text: Microsoft Connected Cache (MCC) overview
+          - text: Microsoft Connected Cache overview
             url: waas-microsoft-connected-cache.md
 
 
@@ -63,25 +63,25 @@ landingContent:
             url: /mem/intune/configuration/delivery-optimization-windows
 
   # Card
-  - title: Microsoft Connected Cache (MCC) for Enterprise and Education
+  - title: Microsoft Connected Cache for Enterprise and Education
     linkLists:
       - linkListType: deploy
         links:
-          - text: MCC for Enterprise and Education (early preview)
+          - text: Connected Cache for Enterprise and Education (early preview)
             url: waas-microsoft-connected-cache.md
           - text: Sign up
             url: https://aka.ms/MSConnectedCacheSignup
 
   # Card
-  - title: Microsoft Connected Cache (MCC) for Internet Service Providers (ISPs)
+  - title: Microsoft Connected Cache for Internet Service Providers (ISPs)
     linkLists:
       - linkListType: deploy
         links:
-          - text: MCC for ISPs (public preview)
+          - text: Connected Cache for ISPs (public preview)
             url: mcc-isp-signup.md
           - text: Sign up
             url: https://aka.ms/MCCForISPSurvey
-          - text: MCC for ISPs (early preview)
+          - text: Connected Cache for ISPs (early preview)
             url: mcc-isp.md
 
 

windows/deployment/do/mcc-ent-edu-overview.md

@@ -1,6 +1,6 @@
 ---
-title: MCC for Enterprise and Education Overview
-description: Overview, supported scenarios, and content types for Microsoft Connected Cache (MCC) for Enterprise and Education.
+title: Microsoft Connected Cache for Enterprise and Education Overview
+description: Overview, supported scenarios, and content types for Microsoft Connected Cache for Enterprise and Education.
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: conceptual
@@ -23,9 +23,9 @@ ms.date: 05/23/2024
 > - Microsoft Connected Cache is currently a preview feature. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 > - As we near the release of public preview, we have paused onboarding. Please continue to submit the form to express interest so we can follow up with you once public preview of Microsoft Connected Cache for Enteprise and Education is available. To register your interest, fill out the form located at [https://aka.ms/MSConnectedCacheSignup](https://aka.ms/MSConnectedCacheSignup).
 
-Microsoft Connected Cache (MCC) for Enterprise and Education (early preview) is a software-only caching solution that delivers Microsoft content within Enterprise and Education networks. MCC can be deployed to as many Windows servers, 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.
+Microsoft Connected Cache for Enterprise and Education (early preview) is a software-only caching solution that delivers Microsoft content within Enterprise and Education networks. Connected Cache can be deployed to as many Windows servers, 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.
 
-Microsoft Connected Cache (MCC) for Enterprise and Education (early preview) is a standalone cache for customers moving towards modern management and away from Configuration Manager distribution points. For information about Microsoft Connected Cache in Configuration Manager (generally available, starting Configuration Manager version 2111), see [Microsoft Connected Cache in Configuration Manager](/mem/configmgr/core/plan-design/hierarchy/microsoft-connected-cache).
+Microsoft Connected Cache for Enterprise and Education (early preview) is a standalone cache for customers moving towards modern management and away from Configuration Manager distribution points. For information about Microsoft Connected Cache in Configuration Manager (generally available, starting Configuration Manager version 2111), see [Microsoft Connected Cache in Configuration Manager](/mem/configmgr/core/plan-design/hierarchy/microsoft-connected-cache).
 
 ## Supported scenarios
 
@@ -47,27 +47,27 @@ For the full list of content endpoints that Microsoft Connected Cache for Enterp
 
 ## How it works
 
-MCC is a hybrid (mix of on-premises and cloud resources) SaaS solution built as an Azure IoT Edge module and Docker compatible Linux container deployed to your Windows devices. The Delivery Optimization team chose IoT Edge for Linux on Windows (EFLOW) as a secure, reliable container management infrastructure. EFLOW is a Linux virtual machine, based on Microsoft's first party CBL-Mariner operating system. It's built with the IoT Edge runtime and validated as a tier 1 supported environment for IoT Edge workloads. MCC is a Linux IoT Edge module running on the Windows Host OS.  
+Connected Cache is a hybrid (mix of on-premises and cloud resources) SaaS solution built as an Azure IoT Edge module and Docker compatible Linux container deployed to your Windows devices. The Delivery Optimization team chose IoT Edge for Linux on Windows (EFLOW) as a secure, reliable container management infrastructure. EFLOW is a Linux virtual machine, based on Microsoft's first party CBL-Mariner operating system. It's built with the IoT Edge runtime and validated as a tier 1 supported environment for IoT Edge workloads. Connected Cache is a Linux IoT Edge module running on the Windows Host OS.  
 
-1. The Azure Management Portal is used to create MCC nodes.
-1. The MCC container is deployed and provisioned to the server using the installer provided in the portal.
+1. The Azure Management Portal is used to create Connected Cache nodes.
+1. The Connected Cache container is deployed and provisioned to the server using the installer provided in the portal.
 1. Client policy is set in your management solution to point to the IP address or FQDN of the cache server.
-1. Microsoft end-user devices make range requests for content from the MCC node.
-1. The MCC node pulls content from the CDN, seeds its local cache stored on disk, and delivers the content to the client.
+1. Microsoft end-user devices make range requests for content from the Connected Cache node.
+1. The Connected Cache node pulls 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 now come from cache.
-1. If the MCC node is unavailable, the client pulls content from CDN to ensure uninterrupted service for your subscribers.
+1. If the Connected Cache node is unavailable, the client pulls content from CDN to ensure uninterrupted service for your subscribers.
 
-The following diagram displays an overview of how MCC functions:
+The following diagram displays an overview of how Connected Cache functions:
 
-:::image type="content" source="./images/waas-mcc-diag-overview.png" alt-text="Diagram displaying the components of MCC." lightbox="./images/waas-mcc-diag-overview.png":::
+:::image type="content" source="./images/waas-mcc-diag-overview.png" alt-text="Diagram displaying the components of Connected Cache." lightbox="./images/waas-mcc-diag-overview.png":::
 
 ## IoT Edge
 
-Even though your MCC scenario isn't related to IoT, Azure IoT Edge is used as a more generic Linux container deployment and management infrastructure. The Azure IoT Edge runtime sits on your designated MCC device and performs management and communication operations. The runtime performs several functions important to manage MCC on your edge device:
+Even though your Connected Cache scenario isn't related to IoT, Azure IoT Edge is used as a more generic Linux container deployment and management infrastructure. The Azure IoT Edge runtime sits on your designated Connected Cache device and performs management and communication operations. The runtime performs several functions important to manage Connected Cache on your edge device:
 
-1. Installs and updates MCC on your edge device.
+1. Installs and updates Connected Cache on your edge device.
 1. Maintains Azure IoT Edge security standards on your edge device.
-1. Ensures that MCC is always running.
-1. Reports MCC health and usage to the cloud for remote monitoring.
+1. Ensures that Connected Cache is always running.
+1. Reports Connected Cache health and usage to the cloud for remote monitoring.
   
 For more information on Azure IoT Edge, see the Azure IoT Edge [documentation](/azure/iot-edge/about-iot-edge).