Merge pull request #10331 from MicrosoftDocs/main

Publish main to live, 10/25, 11:00 AM IST

windows/client-management/mdm/policy-csp-deliveryoptimization.md

@@ -164,7 +164,7 @@ One or more values can be added as either fully qualified domain names (FQDN) or
 <!-- DOCacheHost-Editable-Begin -->
 <!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
 > [!NOTE]
-> Clients don't talk to multiple Microsoft Connected Cache (MCC) servers at the same time. If you configure a list of MCC servers in this policy, the clients will round robin until they successfully connect to an MCC server. The clients have no way to determine if the MCC server has the content or not. If the MCC server doesn't have the content, it caches the content as it is handing the content back to the client.
+> Clients don't talk to multiple Microsoft Connected Cache servers at the same time. If you configure a list of Connected Cache servers in this policy, the clients will round robin until they successfully connect to a Connected Cache server. The clients have no way to determine if the Connected Cache server has the content or not. If the Connected Cache server doesn't have the content, it caches the content as it is handing the content back to the client.
 <!-- DOCacheHost-Editable-End -->
 
 <!-- DOCacheHost-DFProperties-Begin -->
@@ -578,7 +578,7 @@ Specifies the download method that Delivery Optimization can use in downloads of
 <!-- DODownloadMode-Editable-Begin -->
 <!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
 > [!NOTE]
-> The Delivery Optimization service on the clients checks to see if there are peers and/or an MCC server which contains the content and determines the best source for the content.
+> The Delivery Optimization service on the clients checks to see if there are peers and/or a Connected Cache server which contains the content and determines the best source for the content.
 <!-- DODownloadMode-Editable-End -->
 
 <!-- DODownloadMode-DFProperties-Begin -->

windows/deployment/do/TOC.yml

@@ -33,21 +33,21 @@
   items:
     - name: What is Microsoft Connected Cache?
       href: waas-microsoft-connected-cache.md
-    - name: MCC for Enterprise and Education
+    - name: Microsoft Connected Cache for Enterprise and Education
       items:
-      - name: MCC for Enterprise and Education Overview
+      - name: Connected Cache for Enterprise and Education Overview
         href: mcc-ent-edu-overview.md
       - name: Requirements
         href: mcc-enterprise-prerequisites.md
       - name: Deploy Microsoft Connected Cache
         href: mcc-enterprise-deploy.md
-      - name: Update or uninstall MCC
+      - name: Update or uninstall Connected Cache
         href: mcc-enterprise-update-uninstall.md
       - name: Appendix
         href: mcc-enterprise-appendix.md
-    - name: MCC for ISPs
+    - name: Microsoft Connected Cache for ISPs
       items:
-      - name: MCC for ISPs Overview
+      - name: Connected Cache for ISPs Overview
         href: mcc-isp-overview.md
       - name: How-to guides
         items:  
@@ -67,7 +67,7 @@
           href: mcc-isp-vm-performance.md
         - name: Support and troubleshooting
           href: mcc-isp-support.md
-        - name: MCC for ISPs (early preview)
+        - name: Connected Cache for ISPs (early preview)
           href: mcc-isp.md
 - name: Endpoints for Microsoft Connected Cache content and services
   href: delivery-optimization-endpoints.md 

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

@@ -35,7 +35,7 @@ Use this checklist to guide you through different aspects when modifying Deliver
     * System resources
     * Improve P2P efficiencies
 
-1. Using Connected Cache (MCC)
+1. Using Microsoft Connected Cache
 1. Choose where to set Delivery Optimization policies
 
 ## 1. Prerequisites to allow Delivery Optimization communication
@@ -189,7 +189,7 @@ Regardless of P2P, consider setting the following policies to avoid network disr
 > [!NOTE]
 > The absolute policies are recommended in low bandwidth environments.
 
-## 3. Using Connected Cache (MCC)
+## 3. Using Connected Cache
 
 :::image type="content" source="images/do-setup-connected-cache.png" alt-text="Screenshot of Delivery Optimization options when using Connected Cache." lightbox="images/do-setup-connected-cache.png":::
 

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/images/elixir_ux/readme-elixir-ux-files.md

@@ -25,4 +25,4 @@ This file contains the images that are included in this GitHub repository that a
 
 :::image type="content" source="ux-iot-edge-list.png" alt-text="A screenshot of the terminal after the command 'iotedge list', showing all three containers running successfully.":::
 
-:::image type="content" source="ux-mcc-failed.png" alt-text="A screenshot of the terminal after the command 'iotedge list', showing the MCC container in a failure state.":::
+:::image type="content" source="ux-mcc-failed.png" alt-text="A screenshot of the terminal after the command 'iotedge list', showing the Microsoft Connected Cache container in a failure state.":::

windows/deployment/do/includes/get-azure-subscription.md

@@ -14,6 +14,6 @@ ms.localizationpriority: medium
 1. Sign in to the [Azure portal](https://portal.azure.com).
 1. Select **Subscriptions**. If you don't see **Subscriptions**, type **Subscriptions** in the search bar. As you begin typing, the list filters based on your input.
 1. If you already have an Azure Subscription, skip to step 5. If you don't have an Azure Subscription, select **+ Add** on the top left. 
-1. Select the **Pay-As-You-Go** subscription. You'll be asked to enter credit card information, but you'll not be charged for using the MCC service. 
+1. Select the **Pay-As-You-Go** subscription. You'll be asked to enter credit card information, but you'll not be charged for using the Microsoft Connected Cache service. 
 1. On the **Subscriptions** page, you'll find details about your current subscription. Select the subscription name. 
 1. After you select the subscription name, you'll find the subscription ID in the **Overview** tab. Select the **Copy to clipboard** icon next to your Subscription ID to copy the value. 

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).