Replace MCC with Connected Cache

windows/deployment/do/mcc-ent-create-resource-and-cache.md

@@ -1,6 +1,6 @@
 ---
-title: Create and configure MCC cache nodes
+title: Create and configure Microsoft Connected Cache nodes
-description: Details on how to create and configure Microsoft Connected Cache for Enterprise and Education (MCC) cache nodes.
+description: Details on how to create and configure Microsoft Connected Cache for Enterprise and Education cache nodes.
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: how-to
@@ -16,17 +16,17 @@ ms.date: 06/03/2024
 
 # Create Microsoft Connected Cache Azure resource and cache nodes
 
-This article outlines how to create and configure your Microsoft Connected Cache for Enterprise and Education (MCC) cache nodes. The creation and configuration of your cache node takes place in Azure. The deployment of your cache node requires downloading and running an OS-specific provisioning package on your host machine.
+This article outlines how to create and configure your Microsoft Connected Cache for Enterprise and Education cache nodes. The creation and configuration of your cache node takes place in Azure. The deployment of your cache node requires downloading and running an OS-specific provisioning package on your host machine.
 
 ## Prerequisites
 
 1. **Azure Pay-As-You-Go subscription**: Microsoft Connected Cache is a free-of-charge service hosted in Azure. You'll need a pay-as-you-go Azure subscription in order to onboard to our service. To create a subscription, go to [pay-as-you-go subscription page](https://azure.microsoft.com/offers/ms-azr-0003p/).
-2. **Hardware to host MCC**: The recommended configuration serves approximately 35,000 managed devices, downloading a 2-GB payload in 24-hour timeframe at a sustained rate of 6.5 Gbps.
+2. **Hardware to host Connected Cache**: The recommended configuration serves approximately 35,000 managed devices, downloading a 2-GB payload in 24-hour timeframe at a sustained rate of 6.5 Gbps.
 
-For more information on sizing and OS requirements, see [the prerequisites for using MCC](mcc-ent-prerequisites.md).
+For more information on sizing and OS requirements, see [the prerequisites for using Connected Cache](mcc-ent-prerequisites.md).
 
 
-## Create MCC Azure resource
+## Create Connected Cache Azure resource
 
 # [Azure portal](#tab/portal)
 
@@ -58,9 +58,9 @@ For more information on sizing and OS requirements, see [the prerequisites for u
 
     * Install Azure CLI extension **mcc** by following the instructions [here](/cli/azure/azure-cli-extensions-overview#how-to-install-extensions).
 
-    * Resource group under which an MCC resource can be created. Use the [az group create](/cli/azure/group#az-group-create) command to create a new Resource group if you don't already have one.
+    * Resource group under which a Connected Cache resource can be created. Use the [az group create](/cli/azure/group#az-group-create) command to create a new Resource group if you don't already have one.
 
-#### Create MCC Azure resource
+#### Create Connected Cache Azure resource
 
 Replace the following placeholders with your own information:
 * *\<resource-group>*: Name of an existing resource group in your subscription.
@@ -73,7 +73,7 @@ az mcc ent resource create --mcc-resource-name <mymccresource> --resource-group
 
 ---
 
-## Create MCC cache node
+## Create Connected Cache cache node
 
 # [Azure portal](#tab/portal)
 
@@ -117,7 +117,7 @@ az mcc ent node create --cache-node-name <mycachenode> --mcc-resource-name <mymc
 
 ---
 
-## Configure MCC cache node
+## Configure Connected Cache node
 
 # [Azure portal](#tab/portal)
 Enter required values to configure your cache node. To learn more about the definitions of each field, review the [Configuration](#general-configuration-fields) fields at the bottom of this article.
@@ -126,7 +126,7 @@ Don't forget to select save after adding configuration information.
 
 # [Azure CLI](#tab/cli)
 
-### Configure Linux MCC
+### Configure Linux-hosted Connected Cache node
 Use the following command to configure cache node for deployment to a **Linux** host machine.
 
 Replace the following placeholders with your own information:
@@ -138,7 +138,7 @@ Replace the following placeholders with your own information:
 * *\<size-in-gb>*: The size of cache drive. Must be at least 50 Gb.
 * *\<proxy>*: If proxy needs to be enabled or not.<br>
   Accepted values: enabled, disabled<br>
-  Proxy should be set to enabled if the cache node will need to pass through a network proxy to download content. The provided proxy will also be used during deployment of the MCC cache node to your host machine.
+  Proxy should be set to enabled if the cache node will need to pass through a network proxy to download content. The provided proxy will also be used during deployment of the Connected Cache cache node to your host machine.
 * *\<proxy-host>*: The proxy host name or ip address. Required if proxy is set to enabled.
 * *\<proxy-port>*: Proxy port number. Required if proxy is set to enabled.
 * *\<auto-update-ring>*: Update ring the cache node should have.<br>
@@ -158,7 +158,7 @@ az mcc ent node update --cache-node-name <mycachenode> --mcc-resource-name <mymc
 <br>
 <br>
 
-### Configure Windows MCC
+### Configure Windows-hosted Connected Cache node
 Use the following command to configure cache node for deployment to a **Windows** host machine.
 
 Replace the following placeholders with your own information:
@@ -171,7 +171,7 @@ Replace the following placeholders with your own information:
 * *\<size-in-gb>*: The size of cache drive. Must be at least 50 Gb.
 * *\<proxy>*: If proxy needs to be enabled or not.<br>
   Accepted values: enabled, disabled<br>
-  Proxy should be set to enabled if the cache node will need to pass through a network proxy to download content. The provided proxy will also be used during deployment of the MCC cache node to your host machine.
+  Proxy should be set to enabled if the cache node will need to pass through a network proxy to download content. The provided proxy will also be used during deployment of the Connected Cache cache node to your host machine.
 * *\<proxy-host>*: The proxy host name or ip address. Required if proxy is set to enabled.
 * *\<proxy-port>*: Proxy port number. Required if proxy is set to enabled.
 * *\<auto-update-ring>*: Update ring the cache node should have.<br>
@@ -240,7 +240,7 @@ To deploy cache nodes using Azure CLI, see
 
 #### Proxy settings
 <br>
-You can choose to enable or disable proxy settings on your cache node. Proxy should be set to enabled if the cache node will need to pass through a network proxy to download content. The provided proxy will also be used during deployment of the MCC cache node to your host machine.
+You can choose to enable or disable proxy settings on your cache node. Proxy should be set to enabled if the cache node will need to pass through a network proxy to download content. The provided proxy will also be used during deployment of the Connected Cache node to your host machine.
 
 <br>
 
@@ -258,14 +258,14 @@ You can choose to enable or disable proxy settings on your cache node. Proxy sho
 ## Other operations on resource and cache nodes
 <br>
 
-### List all MCC resource
+### List all Connected Cache resources
 
 # [Azure portal](#tab/portal)
-Navigate to the resource group under which you would like to see the MCC resources.
+Navigate to the resource group under which you would like to see the Connected Cache resources.
 
 
 # [Azure CLI](#tab/cli)
-Use the following command to list all the MCC resources under the resource group. 
+Use the following command to list all the Connected Cache resources under the resource group. 
 
 Replace the following placeholders with your own information:
 * *\<resource-group>*: An existing resource group in your subscription.
@@ -279,7 +279,7 @@ az mcc ent resource list  --resource-group <myrg>
 ### List all cache nodes
 
 # [Azure portal](#tab/portal)
-On the left pane, click on 'Cache Nodes' under 'Cache Node Management' to see all the cache nodes under the MCC resource.
+On the left pane, click on 'Cache Nodes' under 'Cache Node Management' to see all the cache nodes under the Connected Cache resource.
 
 
 # [Azure CLI](#tab/cli)
@@ -296,14 +296,14 @@ az mcc ent node list --mcc-resource-name <mymccresource> --resource-group <myrg>
 ---
 <br>
 
-### Delete MCC resource
+### Delete Connected Cache resource
 
 # [Azure portal](#tab/portal)
-Navigate to the MCC resource to delete and click on the delete button on top.
+Navigate to the Connected Cache resource to delete and click on the delete button on top.
 
 
 # [Azure CLI](#tab/cli)
-Use the following command to delete the MCC resource. 
+Use the following command to delete the Connected Cache resource.
 
 Replace the following placeholders with your own information:
 * *\<resource-group>*: Name of the resource group in your subscription.
@@ -319,7 +319,7 @@ az mcc ent node delete --cache-node-name <mycachenode> --mcc-resource-name <mymc
 ### Delete cache node
 
 # [Azure portal](#tab/portal)
-On the left pane, click on 'Cache Nodes' under 'Cache Node Management' to see all the cache nodes under the MCC resource. Select the cache node you wish to delete and click delete button on top of the page.
+On the left pane, click on 'Cache Nodes' under 'Cache Node Management' to see all the cache nodes under the Connected Cache resource. Select the cache node you wish to delete and click delete button on top of the page.
 
 
 # [Azure CLI](#tab/cli)

windows/deployment/do/mcc-ent-deploy-to-linux.md

@@ -1,6 +1,6 @@
 ---
-title: Deploy MCC cache software to a Linux host machine
+title: Deploy Microsoft Connected Cache software to a Linux host machine
-description: Details on how to deploy Microsoft Connected Cache for Enterprise and Education (MCC) cache software to a Linux host machine.
+description: Details on how to deploy Microsoft Connected Cache for Enterprise and Education cache software to a Linux host machine.
 author: chrisjlin
 ms.author: lichris
 manager: naengler
@@ -15,11 +15,11 @@ appliesto:
 
 # Deploy Microsoft Connected Cache caching software to a Linux host machine
 
-This article describes how to deploy Microsoft Connected Cache for Enterprise and Education (MCC) caching software to a Linux host machine.
+This article describes how to deploy Microsoft Connected Cache for Enterprise and Education caching software to a Linux host machine.
 
-Before deploying MCC to a Linux host machine, ensure that the host machine meets all [requirements](mcc-ent-prerequisites.md), and that you have [created and configured your MCC Azure resource and cache node](mcc-ent-create-resource-and-cache.md).
+Before deploying Connected Cache to a Linux host machine, ensure that the host machine meets all [requirements](mcc-ent-prerequisites.md), and that you have [created and configured your Connected Cache Azure resource and cache node](mcc-ent-create-resource-and-cache.md).
 
-## Steps to deploy MCC cache node to Linux
+## Steps to deploy Connected Cache cache node to Linux
 
 # [Azure portal](#tab/portal)
 
@@ -40,7 +40,7 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the
    ```
 
 1. Save the resulting output. These values will be passed as parameters within the provisioning command.
-1. Download and extract the [MCC provisioning package for Linux](https://aka.ms/MCC-Ent-InstallScript-Linux) to your host machine.
+1. Download and extract the [Connected Cache provisioning package for Linux](https://aka.ms/MCC-Ent-InstallScript-Linux) to your host machine.
 1. Open a command line window *as administrator* on the host machine, then change directory to the extracted provisioning package.
 1. Set access permissions to allow the `provisionmcc.sh` script within the provisioning package directory to execute.
 1. Replace the values in the following provisioning command before running it on the host machine.
@@ -57,4 +57,4 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the
 ## Related content
 
 - [Deploy to a Windows host machine](mcc-ent-deploy-to-windows.md)
-- [Uninstall MCC](mcc-ent-uninstall-cache-node.md)
+- [Uninstall Connected Cache node](mcc-ent-uninstall-cache-node.md)

windows/deployment/do/mcc-ent-deploy-to-windows.md

@@ -1,6 +1,6 @@
 ---
-title: Deploy MCC cache software to a Windows host machine
+title: Deploy Microsoft Connected Cache software to a Windows host machine
-description: Details on how to deploy Microsoft Connected Cache for Enterprise and Education (MCC) cache software to a Windows host machine.
+description: Details on how to deploy Microsoft Connected Cache for Enterprise and Education cache software to a Windows host machine.
 author: chrisjlin
 ms.author: lichris
 manager: naengler
@@ -15,13 +15,13 @@ appliesto:
 
 # Deploy Microsoft Connected Cache caching software to a Windows host machine
 
-This article describes how to deploy Microsoft Connected Cache for Enterprise and Education (MCC) caching software to a Windows host machine.
+This article describes how to deploy Microsoft Connected Cache for Enterprise and Education caching software to a Windows host machine.
 
-Deploying MCC to a Windows host machine requires designating a [Group Managed Service Account (gMSA)](/windows-server/security/group-managed-service-accounts/getting-started-with-group-managed-service-accounts) or a [Local User Account](https://support.microsoft.com/windows/create-a-local-user-or-administrator-account-in-windows-20de74e0-ac7f-3502-a866-32915af2a34d) as the MCC runtime account. This prevents tampering with the MCC container and the cached content on the host machine.
+Deploying Connected Cache to a Windows host machine requires designating a [Group Managed Service Account (gMSA)](/windows-server/security/group-managed-service-accounts/getting-started-with-group-managed-service-accounts) or a [Local User Account](https://support.microsoft.com/windows/create-a-local-user-or-administrator-account-in-windows-20de74e0-ac7f-3502-a866-32915af2a34d) as the Connected Cache runtime account. This prevents tampering with the Connected Cache container and the cached content on the host machine.
 
-Before deploying MCC to a Windows host machine, ensure that the host machine meets all [requirements](mcc-ent-prerequisites.md), and that you have [created and configured your MCC Azure resource](mcc-ent-create-resource-and-cache.md).
+Before deploying Connected Cache to a Windows host machine, ensure that the host machine meets all [requirements](mcc-ent-prerequisites.md), and that you have [created and configured your Connected Cache Azure resource](mcc-ent-create-resource-and-cache.md).
 
-## Steps to deploy MCC cache node to Windows
+## Steps to deploy Connected Cache node to Windows
 
 # [Azure portal](#tab/portal)
 
@@ -29,9 +29,9 @@ Before deploying MCC to a Windows host machine, ensure that the host machine mee
 1. Download the provisioning package using the button at the top of the Cache Node Configuration page and extract the package onto the host machine.
 1. Open a PowerShell window *as administrator* on the host machine, then change directory to the extracted provisioning package.
 1. Set the Execution Policy to "Unrestricted" to allow the provisioning scripts to run.
-1. Create a `$User` environment variable containing the username of the account you intend to designate as the MCC runtime account. For gMSAs, the value should be formatted as `"Domain\Username$"`. For Local User accounts, `$User` should be formatted as `"LocalMachineName\Username"`.
+1. Create a `$User` environment variable containing the username of the account you intend to designate as the Connected Cache runtime account. For gMSAs, the value should be formatted as `"Domain\Username$"`. For Local User accounts, `$User` should be formatted as `"LocalMachineName\Username"`.
 
-   If you're using a Local User account as the MCC runtime account, you'll also need to create a [PSCredential Object](/dotnet/api/system.management.automation.pscredential) named `$myLocalAccountCredential`.
+   If you're using a Local User account as the Connected Cache runtime account, you'll also need to create a [PSCredential Object](/dotnet/api/system.management.automation.pscredential) named `$myLocalAccountCredential`.
 
 1. Run the provisioning command on the host machine.
 
@@ -46,14 +46,14 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the
    ```
 
 1. Save the resulting output. These values will be passed as parameters within the provisioning command.
-1. Download and extract the [MCC provisioning package for Windows](https://aka.ms/MCC-Ent-InstallScript-WSL) to your host machine.
+1. Download and extract the [Connected Cache provisioning package for Windows](https://aka.ms/MCC-Ent-InstallScript-WSL) to your host machine.
 1. Open a PowerShell window *as administrator* on the host machine, then change directory to the extracted provisioning package.
 1. Set the Execution Policy to "Unrestricted" to allow the provisioning scripts to run.
-1. Create a `$User` environment variable containing the username of the account you intend to designate as the MCC runtime account. For gMSAs, the value should be formatted as `"Domain\Username$"`. For Local User accounts, `$User` should be formatted as `"LocalMachineName\Username"`.
+1. Create a `$User` environment variable containing the username of the account you intend to designate as the Connected Cache runtime account. For gMSAs, the value should be formatted as `"Domain\Username$"`. For Local User accounts, `$User` should be formatted as `"LocalMachineName\Username"`.
 
-   If you're using a Local User account as the MCC runtime account, you'll also need to create a [PSCredential Object](/dotnet/api/system.management.automation.pscredential) named `$myLocalAccountCredential`.
+   If you're using a Local User account as the Connected Cache runtime account, you'll also need to create a [PSCredential Object](/dotnet/api/system.management.automation.pscredential) named `$myLocalAccountCredential`.
 
-1. Replace the values in the following provisioning command before running it on the host machine. Note that `-mccLocalAccountCredential $myLocalAccountCredential` is only needed if you are using a Local User account as the MCC runtime account.
+1. Replace the values in the following provisioning command before running it on the host machine. Note that `-mccLocalAccountCredential $myLocalAccountCredential` is only needed if you are using a Local User account as the Connected Cache runtime account.
 
    ```powershell-interactive
    ./provisionmcconwsl.ps1 -installationFolder c:\mccwsl01 -customerid [enter mccResourceId here] -cachenodeid [enter cacheNodeId here] -customerkey [enter customerKey here] -registrationkey [enter registration key] -cacheDrives "/var/mcc,enter drive size"  -shouldUseProxy [enter true if present, enter false if not] -proxyurl "http://[enter proxy host name]:[enter port]"  -mccRunTimeAccount $User -mccLocalAccountCredential $myLocalAccountCredential
@@ -67,4 +67,4 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the
 ## Related content
 
 - [Deploy to a Linux host machine](mcc-ent-deploy-to-linux.md)
-- [Uninstall MCC](mcc-ent-uninstall-cache-node.md)
+- [Uninstall Connected Cache node](mcc-ent-uninstall-cache-node.md)

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

@@ -1,6 +1,6 @@
 ---
-title: MCC Overview
+title: Microsoft Connected Cache for Enterprise and Education Overview
-description: Overview, supported scenarios, and content types for Microsoft Connected Cache for Enterprise and Education (MCC).
+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
@@ -21,64 +21,67 @@ ms.date: 05/09/2023
 > [!IMPORTANT]
 > - 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/).
 
-Microsoft Connected Cache (MCC) for Enterprise and Education (preview) is a software-only caching solution that delivers Microsoft content within Enterprise and Education networks. MCC can be managed from an Azure portal or through Azure CLI and can be deployed to as many Windows devices, Linux devices, or VMs as needed. Managed Windows devices can be configured to download cloud content from a Connected Cache server by applying the client policy using management tools such as Intune.<br>
+Microsoft Connected Cache for Enterprise and Education (preview) is a software-only caching solution that delivers Microsoft content within Enterprise and Education networks. Connected Cache can be managed from an Azure portal or through Azure CLI and can be deployed to as many Windows devices, Linux devices, or VMs as needed. Managed Windows devices can be configured to download cloud content from a Connected Cache server by applying the client policy using management tools such as Intune.
 
-Microsoft Connected Cache (MCC) for Enterprise and Education (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](/configmgr/core/plan-design/hierarchy/microsoft-connected-cache).
+Microsoft Connected Cache for Enterprise and Education (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](/configmgr/core/plan-design/hierarchy/microsoft-connected-cache).
 
-Microsoft Connected Cache deployed directly to Windows relies on [Windows Subsystem for Linux](/windows/wsl/about) and either a [Group Managed Service Account](/windows-server/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/getting-started-with-group-managed-service-accounts), local user account, or domain user account are required to run WSL. WSL needs to run in a user context and any user, even if the currently logged-in user, could be used to run WSL and Microsoft Connected Cache.<br>
+Microsoft Connected Cache deployed directly to Windows relies on [Windows Subsystem for Linux](/windows/wsl/about) and either a [Group Managed Service Account](/windows-server/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/getting-started-with-group-managed-service-accounts), local user account, or domain user account are required to run WSL. WSL needs to run in a user context and any user, even if the currently logged-in user, could be used to run WSL and Microsoft Connected Cache.
 
-### Supported scenarios and deployments
+## Supported scenarios and configurations
 
-Microsoft Connected Cache for Enterprise and Education (preview) is intended to support the following content delivery scenarios:<br>
+Microsoft Connected Cache for Enterprise and Education (preview) is intended to support the following content delivery scenarios:
-* Pre-provisioning of devices using Windows Autopilot<br>
+
-* Co-managed clients that get monthly update and Win32 apps from Microsoft Intune. For more information, see Support for Intune Win32 apps.<br>
+- Pre-provisioning of devices using Windows Autopilot
-* Cloud-only managed devices, such as Intune-enrolled devices without the Configuration Manager client, that get monthly update and Win32 apps from Microsoft Intune. For more information, see Support for cloud-managed devices.<br>
+- Co-managed clients that get monthly updates and Win32 apps from Microsoft Intune
+- Cloud-only managed devices, such as Intune-enrolled devices without the Configuration Manager client, that get monthly updates and Win32 apps from Microsoft Intune
 
 Microsoft Connected Cache is built for flexible deployments to support a number of enterprise configurations:
 
-##### Branch office
+### Branch office
+
 Customers may have globally dispersed offices that meet the following parameters:
-* 10 – 50 Windows Clients
-* No dedicated server hardware
-* Internet bandwidth is great to limited (satellite internet)
-* Possibly intermittent connectivity
-<br>
-To support the branch the branch office scenario, customers can deploy to a Windows 11 client (see Host machine requirements) device.
 
-##### Large Enterprise
+- 10 – 50 Windows Clients
+- No dedicated server hardware
+- Internet bandwidth is great to limited (satellite internet)
+- Possibly intermittent connectivity
+
+To support the branch office scenario, customers can deploy a Connected Cache node to a Windows 11 client device.
+
+### Large Enterprise
+
 Customers may have office spaces, data centers, or Azure deployments that meet the following parameters:  
-* 100's or 1,000's of Windows devices (client or server).
-* Existing hardware – Decommissioned DP, file server, cloud print server
-* Azure VMs and Azure Virtual Desktop
-* Internet bandwidth is great to limited (T1)
 
+- 100's or 1,000's of Windows devices (client or server).
+- Existing hardware – Decommissioned DP, file server, cloud print server
+- Azure VMs and Azure Virtual Desktop
+- Internet bandwidth is great to limited (T1)
 
-### Supported content types
+To support the large enterprise scenario, customers can deploy a Connected Cache node to a server running Windows Server 2022 or Ubuntu 22.04.
+
+See [Connected Cache node host machine requirements](mcc-ent-prerequisites.md) for recommended host machine specifications in each configuration.
+
+| Enterprise configuration | Download speed range | Download speeds and approximate content volume delivered in 8 Hours |
+|---|---|---|
+|Branch Office|< 1 Gbps Peak| 500 Mbps => 1,800 GB </br></br> 250 Mbps => 900 GB </br></br> 100 Mbps => 360 GB </br></br> 50 Mbps => 180 GB|
+|Small to Medium Enterprises/Autopilot Provisioning Center (50 - 500 devices in a single location) |1 - 5 Gbps| 5 Gbps => 18,000 GB </br></br>3 Gbps => 10,800 GB </br></br>1 Gbps => 3,600 GB|
+|Medium to Large Enterprises/Autopilot Provisioning Center (500 - 5,000 devices in a single location) |5 - 101 Gbps Peak|   9 Gbps => 32,400 GB </br></br> 5 Gbps => 18,000 GB </br></br>3 Gbps => 10,800 GB|
+
+## Supported content types
 When clients download cloud-managed content, they use Delivery Optimization from the cache server installed on a Windows server or VM. Cloud-managed content includes the following types:
-* Windows updates: Windows feature and quality updates
-* Office Click-to-Run apps: Microsoft 365 Apps and updates
-* Client apps: Intune, store apps, and updates
-* Endpoint protection: Windows Defender definition updates
 
-For the full list of content endpoints that Microsoft Connected Cache for Enterprise and Education supports, see [Microsoft Connected Cache content and services endpoints](delivery-optimization-endpoints.md).<br>
+- Windows updates: Windows feature and quality updates
+- Office Click-to-Run apps: Microsoft 365 Apps and updates
+- Client apps: Intune, store apps, and updates
+- Endpoint protection: Windows Defender definition updates
 
-### Hardware or VM Requirements
+For the full list of content endpoints that Microsoft Connected Cache for Enterprise and Education supports, see [Microsoft Connected Cache content and services endpoints](delivery-optimization-endpoints.md).
-See [Host machine requirements](mcc-ent-prerequisites.md) for complete details.
-
-|Deployment Scenarios| Download Speed Range | Download Speeds and Content Volume Delivered in 8 Hours | VM/Hardware Recommendation |
-|---|---|---|---|
-|Branch Office|< 1 Gbps Peak| 500 Mbps - 1,800 GB </br></br> 250 Mbps - 900 GB </br></br> 100 Mbps - 360 GB </br></br> 50 Mbps - 180 GB| 4 Cores </br></br> Up to 8 GB Memory with 4 GB of Free </br></br> 100 GB free disk space|
-|Small to Medium Enterprises/Autopilot Provisioning Center - 50 - 500 devices in a single location|1 - 5 Gbps| 5 Gbps - 18,000 GB </br></br>3 Gbps - 10,800 GB </br></br>1 Gbps - 3,600 GB| 8 Cores </br></br> Up to 16 GB Memory with 4 GB of Free </br></br> 500 GB free disk space|
-|Medium to Large Enterprises/Autopilot Provisioning Center - 500 - 5,000 devices|5 - 101 Gbps Peak|   9 Gbps - 32,400 GB </br></br> 5 Gbps - 18,000 GB </br></br>3 Gbps - 10,800 GB| 16 Cores</br></br> 32 GB Memory with 4 GB of Free </br></br> 2 200-500 GB SSDs|
-
-<br>
 
 ## How it works
 
-The following diagram displays an overview of how MCC functions:<br>
+The following diagram displays an overview of how Connected Cache functions:
-
-:::image type="content" source="./images/mcc_ent_publicpreview.png" alt-text="Diagram displaying the components of MCC." lightbox="./images/mcc_ent_publicpreview.png":::
 
+:::image type="content" source="./images/mcc_ent_publicpreview.png" alt-text="Diagram displaying the components of Connected Cache." lightbox="./images/mcc_ent_publicpreview.png":::
 
 1. The Azure management portal for Microsoft Connected Cache or CLI are used to create cache nodes, configure deployments, including unauthenticated proxy settings.
 1. Prepare Windows or Linux devices. If deploying to Windows devices, prepare accounts - gMSA, local user account, domain account. Deploy to Windows or Linux devices using scripts.
@@ -88,8 +91,7 @@ The following diagram displays an overview of how MCC functions:<br>
 1. Devices can fallback to CDN if cache server is unavailable for any reason or use Delivery Optimization delay fallback to http (CDN )settings to prefer the local cache server.
 Customers can view data regarding Microsoft Connected Cache downloads on management portal and Windows Update for Business reports
 
-
+## Next steps
-## Next step
 
 >[!div class="nextstepaction"]
->[Create MCC Azure resources](mcc-ent-create-resource-and-cache.md)
+>[Create Connected Cache Azure resources](mcc-ent-create-resource-and-cache.md)

windows/deployment/do/mcc-ent-faq.yml

@@ -1,7 +1,7 @@
 ### YamlMime:FAQ
 metadata:
-  title: MCC Frequently Asked Questions
+  title: Microsoft Connected Cache for Enterprise and Education Frequently Asked Questions
-  description: The following article is a list of frequently asked questions for Microsoft Connected Cache for Enterprise (MCC).
+  description: The following article is a list of frequently asked questions for Microsoft Connected Cache for Enterprise.
   ms.service: windows-client
   ms.subservice: itpro-updates
   ms.topic: faq
@@ -25,8 +25,8 @@ sections:
     questions:
       - question: What are the licesning requirement?
         answer: Microsoft Connected Cache for Enterprise and Education is available to all Windows E3, E5 and F3 and Education A3 and A5 customers.
-      - question: Is there a charge to create MCC resources and cache node on Azure?
+      - question: Is there a charge to create Connected Cache resources and cache node on Azure?
-        answer: No. You won't be charged to create MCC resource and cache nodes on Azure. However, you need an Azure pay-as-you-go subscription to create the resources but there is no charge for the resource itself.
+        answer: No. You won't be charged to create Connected Cache resource and cache nodes on Azure. However, you need an Azure pay-as-you-go subscription to create the resources but there is no charge for the resource itself.
       - question: Is there a nondisclosure agreement to sign?
         answer: No, a nondisclosure agreement isn't required.
       - question: What will Microsoft Connected Cache for Enterprise and Education do for me? 
@@ -40,7 +40,7 @@ sections:
          - [Azure pay-as-you-go subscription](https://azure.microsoft.com/offers/ms-azr-0003p/).
          - [Hardware to host Microsoft Connected Cache](mcc-ent-edu-overview.md)
          - [Host machine requirements](mcc-ent-prerequisites.md)
-      - question: What host OS do I need to deploy MCC?
+      - question: What host OS do I need to deploy Connected Cache?
         answer: You can use Linux or Windows OS. Depending on the OS, the provisioning script and certain provisioning steps are different. 
       - question: What content is cached by Microsoft Connected Cache?
         answer: For more information about content cached, see [Delivery Optimization and Microsoft Connected Cache content endpoints](delivery-optimization-endpoints.md).
@@ -64,7 +64,7 @@ sections:
         answer: No. It's important to keep the Microsoft Connected Cache software up to date, especially when it comes to security issues. Microsoft validates updates prior to releasing Enterprises Connected Cache updates and only releases updates when it's necessary to keep customers secure or to ensure the continued successful operation of Connected Cache nodes for customers.  
       - question: How do I set up CLI?
         answer: For more information, see [How to install the Azure CLI](/cli/azure/install-azure-cli).
-      - question: How do I install MCC extension?
+      - question: How do I install the Microsoft Connected Cache Azure CLI extension?
         answer: For more information, see [Install the Microsoft Connected Cache extension](mcc-ent-manage-cache-using-cli.md#prerequisites).
       - question: What do I do if I have to set up or change existing proxy?
         answer: You can enable proxy and provide proxy information on Azure portal or use the CLI. Don't forget to rerun the provisioning script after making any proxy changes. For more information, see [Set up or change existing proxy](mcc-ent-create-resource-and-cache.md#proxy-settings).

windows/deployment/do/mcc-ent-manage-using-cli.md

@@ -1,6 +1,6 @@
 ---
-title: Manage MCC cache nodes using CLI
+title: Manage Microsoft Connected Cache nodes using CLI
-description: Details on how to manage Microsoft Connected Cache for Enterprise (MCC) cache nodes via Azure CLI commands.
+description: Details on how to manage Microsoft Connected Cache for Enterprise cache nodes via Azure CLI commands.
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: how-to
@@ -20,18 +20,18 @@ ms.date: 06/03/2024
 
 <br>
 
-This article outlines how to create, configure, and deploy Microsoft Connected Cache for Enterprise (MCC) cache nodes using Azure CLI.
+This article outlines how to create, configure, and deploy Microsoft Connected Cache for Enterprise cache nodes using Azure CLI.
 
  
 ## Prerequisites:
 1. **Install Azure CLI**: [How to install the Azure CLI](/cli/azure/install-azure-cli)
-1. **Install MCC extension**: Install MCC extension via the command below
+1. **Install Connected Cache extension**: Install Connected Cache extension via the command below
 
 ```azurecli-interactive
 az extension add --name mcc
 ```
 
-To learn more about installting extensions, visit [Install the MCC extension.](/cli/azure/azure-cli-extensions-overview#how-to-install-extensions)
+To learn more about installting extensions, visit [Install the Connected Cache extension.](/cli/azure/azure-cli-extensions-overview#how-to-install-extensions)
 
 <br>
 <br>
@@ -50,11 +50,11 @@ az group create --name myrg --location westus
 
 Once the resource group is created, you'll need to create a Microsoft Connected Cache for Enterprise resource.
 
-### 2. Create an MCC Azure resource
+### 2. Create a Connected Cache Azure resource
 
-An MCC Azure resource is a top-level Azure resource under which cache nodes can be created.
+A Connected Cache Azure resource is a top-level Azure resource under which cache nodes can be created.
 
-To create an MCC Azure resource, use `az mcc ent resource create`
+To create an Connected Cache Azure resource, use `az mcc ent resource create`
 
 ```azurecli-interactive
 az mcc ent resource create --mcc-resource-name mymccresource --resource-group myrg
@@ -63,7 +63,7 @@ az mcc ent resource create --mcc-resource-name mymccresource --resource-group my
 <br>
 
 >[!IMPORTANT]
->In the output, look for operationStatus. **operationStatus = Succeeded** indicates that our services have successfully started creating MCC resource.
+>In the output, look for operationStatus. **operationStatus = Succeeded** indicates that our services have successfully started creating your Connected Cache resource.
 
 <br>
 
@@ -142,7 +142,7 @@ az mcc ent node get-provisioning-details --cache-node-name mycachenode --mcc-res
 
 ### Example script:
 
-Below is a pseudocode example of how to script bulk creation and configuration of an MCC Azure resource and multiple MCC cache nodes.
+Below is a pseudocode example of how to script bulk creation and configuration of a Connected Cache Azure resource and multiple Connected Cache cache nodes.
 
 <!--# [Bash](#tab/bash)
 

windows/deployment/do/mcc-ent-monitoring.md

@@ -1,6 +1,6 @@
 ---
-title: Monitor usage of MCC cache nodes
+title: Monitor usage of Microsoft Connected Cache nodes
-description: Details on how to monitor the usage of Microsoft Connected Cache for Enterprise (MCC) cache nodes.
+description: Details on how to monitor the usage of Microsoft Connected Cache for Enterprise cache nodes.
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: how-to
@@ -16,36 +16,36 @@ ms.date: 09/04/2024
 
 # Monitor cache node usage
 
-Tracking the status of your MCC node is essential to making sure you are getting the most out of the service.
+Tracking the status of your Connected Cache node is essential to making sure you are getting the most out of the service.
 
-For basic monitoring, navigate to the "Overview" tab. Here you will be able to view a cache node summary dashboard and charts for key metrics. No additional work is necessary, all the monitoring in this section will function right after your MCC node has been installed.
+For basic monitoring, navigate to the "Overview" tab. Here you will be able to view a cache node summary dashboard and charts for key metrics. No additional work is necessary, all the monitoring in this section will function right after your Connected Cache node has been installed.
 
 For advanced monitoring, navigate to the "Metrics" section under the "Monitoring" tab. Here you will be able to access more sampled metrics (hits, misses, inbound traffic) and specify different aggregations (count, avg, min, max, sum). You can then use this data to create customized dashboards and configure alerts. Overall, this section is designed to cater to your specific monitoring needs and preferences.
 
-Between the two monitoring sections, you will be able to gather essential insights into the health, performance, and efficiency of your MCC nodes.
+Between the two monitoring sections, you will be able to gather essential insights into the health, performance, and efficiency of your Connected Cache nodes.
 
 ## Basic Monitoring
 
 ### Cache node summary
 
-The preset monitoring data for MCC is displayed on the Overview page in the Azure portal. Below are the metrics you will find in the "Cache Node Summary" dashboard, along with their descriptions. Please take note that this dashboard only reflects data from all cache nodes the last 24 hours. The filters that are displayed below the dashboard only affect the data shown in the "Key Metrics" charts.
+The preset monitoring data for Connected Cache is displayed on the Overview page in the Azure portal. Below are the metrics you will find in the "Cache Node Summary" dashboard, along with their descriptions. Please take note that this dashboard only reflects data from all cache nodes the last 24 hours. The filters that are displayed below the dashboard only affect the data shown in the "Key Metrics" charts.
 
 <!-- Add Cache node summary picture here -->
 ![Screenshot of cache node summary in the Azure portal interface.](../images/mcc-ent-cache-node-summary.png)
 
 | Metric | Description |
 | --- | --- |
-| Healthy nodes | Your MCC node will frequently send heartbeat messages to our backend. If your node has responded in the last 24 hours, it will be labeled as healthy. |
+| Healthy nodes | Your Connected Cache node will frequently send heartbeat messages to our backend. If your node has responded in the last 24 hours, it will be labeled as healthy. |
 | Unhealthy nodes | If your node has not sent a heartbeat message in the last 24 hours, it will be labeled as unhealthy. |
 | Max in | The maximum ingress in Mbps (Megabits per second) that your node has pulled from CDN in the last 24 hours. |
 | Max out | The minimum egress in Mbps that your node has pushed out to devices in your network over the last 24 hours. |
 | Average in | The average ingress in Mbps that your node has pulled from CDN in the last 24 hours. |
 | Average out | The average egress in Mbps that your node has pushed out to devices in your network over the last 24 hours. |
-| Cache efficiency | The percentage of all content requests your MCC node receives that are ultimately delivered by your MCC node. An well-performing node should have an efficiency > 90%. |
+| Cache efficiency | The percentage of all content requests your Connected Cache node receives that are ultimately delivered by your Connected Cache node. An well-performing node should have an efficiency > 90%. |
 
 ### Key Metrics
 
-The two monitoring charts on the Overview page more visually represent the usage of your MCC node, as well as the types cached content delivered by your node over various time intervals.
+The two monitoring charts on the Overview page more visually represent the usage of your Connected Cache node, as well as the types cached content delivered by your node over various time intervals.
 
 <!-- Add Charts picture here -->
 ![Screenshot of key metric charts in the Azure portal interface.](../images/mcc-ent-key-metric-charts.png)
@@ -55,15 +55,15 @@ The two monitoring charts on the Overview page more visually represent the usage
 Both filters displayed will only impact the data shown in the 2 charts below.
 
       - By time: View data from the last 1 hour to 30 days
-      - By cache node: View data from individual cache nodes or the sum of all your active MCC nodes.
+      - By cache node: View data from individual cache nodes or the sum of all your active Connected Cache nodes.
 
 #### Outbound Traffic Chart
 
-This chart displays the egress in Mbps that your MCC node was delivering at specific timestamps. The value in the chart's key represents the average egress over the specified time period.  
+This chart displays the egress in Mbps that your Connected Cache node was delivering at specific timestamps. The value in the chart's key represents the average egress over the specified time period.  
 
 #### Volume by Content Type
 
-This chart displays the amount (in GB) of each supported content type that your MCC node is delivering at specific timestamps. You can find the complete list of supported content types here: [Microsoft Connected Cache content and services endpoints | Microsoft Learn](https://learn.microsoft.com/en-us/windows/deployment/do/delivery-optimization-endpoints)
+This chart displays the amount (in GB) of each supported content type that your Connected Cache node is delivering at specific timestamps. You can find the complete list of supported content types here: [Microsoft Connected Cache content and services endpoints | Microsoft Learn](https://learn.microsoft.com/en-us/windows/deployment/do/delivery-optimization-endpoints)
 
 The content types in the key are sorted from highest to lowest volume an each have a distinct color. The bar chart is stacked such that you can visually compare total volume being delivered at different timestamps
 
@@ -75,18 +75,18 @@ Listed below are the additional metrics you can access in this section:
 
 | Metric | Description |
 | --- | --- |
-| Inbound | The number of content requests your MCC node receives over a specified period of time. |
+| Inbound | The number of content requests your Connected Cache node receives over a specified period of time. |
-| Hits | The number of times your MCC node fulfills a content request by pulling from its cache. |
+| Hits | The number of times your Connected Cache node fulfills a content request by pulling from its cache. |
-| Misses | The number of times your MCC node is not able to fulfill a content request by pulling from its cache |
+| Misses | The number of times your Connected Cache node is not able to fulfill a content request by pulling from its cache |
 
 ### Customizable Dashboards
 
-Once you select the charts you would like to track, you can save them over to a personalized dashboard. This dashboard enables you to configure the chart title, filters, range, legend, and more. You can also use this personalized dashboard to set up alerts that will notify you if your MCC dips in performance.
+Once you select the charts you would like to track, you can save them over to a personalized dashboard. This dashboard enables you to configure the chart title, filters, range, legend, and more. You can also use this personalized dashboard to set up alerts that will notify you if your Connected Cache node dips in performance.
 
 Some scenarios where you would want to set up these alerts:
-      • My MCC node is being shown as unhealthy and I want to know exactly when it stopped egressing last.
+      • My Connected Cache node is being shown as unhealthy and I want to know exactly when it stopped egressing last.
-A new Xbox update just released last night and I want to know if my MCC node is helping deliver this content to my client machines.
+A new Xbox update just released last night and I want to know if my Connected Cache node is helping deliver this content to my client machines.
 
 ## Additional Metrics
 
-Once the content has left the MCC to be delivered, the node cannot track whether the content has successfully been delivered. To access client-side data, you can refer to this page: [Monitor Delivery Optimization | Microsoft Learn](https://learn.microsoft.com/en-us/windows/deployment/do/waas-delivery-optimization-monitor)
+Once the content has left the Connected Cache node, the node cannot track whether the content has successfully been delivered to the requesting Windows client. To access client-side data, you can refer to this page: [Monitor Delivery Optimization | Microsoft Learn](https://learn.microsoft.com/en-us/windows/deployment/do/waas-delivery-optimization-monitor)

windows/deployment/do/mcc-ent-prerequisites.md

@@ -1,6 +1,6 @@
 ---
-title: MCC prerequisites
+title: Microsoft Connected Cache for Enterprise and Education prerequisites
-description: Details of prerequisites and recommendations for using Microsoft Connected Cache for Enterprise and Education (MCC).
+description: Details of prerequisites and recommendations for using Microsoft Connected Cache for Enterprise and Education.
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: conceptual
@@ -15,17 +15,17 @@ ms.date: 09/27/2024
 
 # Microsoft Connected Cache for Enterprise and Education Requirements
 
-This article details the requirements and recommendations for using Microsoft Connected Cache for Enterprise and Education (MCC).
+This article details the requirements and recommended specifications for using Microsoft Connected Cache for Enterprise and Education.
 
 ## Licensing requirements
 
-- **Valid Azure subscription**: To use the Microsoft Connected Cache for Enterprise and Education (MCC) service, you'll need a valid Azure subscription that can be used to provision the necessary [Azure resources](/azure/cloud-adoption-framework/govern/resource-consistency/resource-access-management).
+- **Valid Azure subscription**: To use the Microsoft Connected Cache for Enterprise and Education service, you'll need a valid Azure subscription that can be used to provision the necessary [Azure resources](/azure/cloud-adoption-framework/govern/resource-consistency/resource-access-management).
 
     If you don't have an Azure subscription already, you can create an Azure [pay-as-you-go](https://azure.microsoft.com/offers/ms-azr-0003p/) account, which requires a credit card for verification purposes. For more information, see the [Azure Free Account FAQ](https://azure.microsoft.com/free/free-account-faq/).
 
-    The Azure resources used for MCC will be free to you during this public preview.
+    The Azure resources used for Connected Cache will be free to you during this public preview.
 
-- **E3/E5 or A3/A5 license**: Your organization must have one of the following license subscriptions for each device that downloads content from an MCC cache node.
+- **E3/E5 or A3/A5 license**: Your organization must have one of the following license subscriptions for each device that downloads content from an Connected Cache node.
 
     - [Windows Enterprise E3 or E5](/windows/whats-new/windows-licensing#windows-11-enterprise), included in [Microsoft 365 F3, E3, or E5](https://www.microsoft.com/microsoft-365/enterprise/microsoft365-plans-and-pricing?msockid=32c407b43d5968050f2b13443c746916)
     - Windows Education A3 or A5, included in [Microsoft 365 A3 or A5](https://www.microsoft.com/education/products/microsoft-365?msockid=32c407b43d5968050f2b13443c746916#Education-plans)
@@ -34,7 +34,7 @@ This article details the requirements and recommendations for using Microsoft Co
 
 ### General requirements
 
-- Any previous installations of MCC must be [uninstalled](mcc-ent-uninstall-cache-node.md) before installing the latest version of MCC.
+- Any previous installations of Connected Cache must be [uninstalled](mcc-ent-uninstall-cache-node.md) from the host machine before installing the latest version of Connected Cache.
 - [These listed endpoints](delivery-optimization-endpoints.md) must be reachable by the host machine.
 - The host machine must have no other services / applications utilizing port 80 (for example, ConfigManager or Distribution Point).
 - The host machine must have at least 4 GB of free memory.
@@ -55,18 +55,19 @@ This article details the requirements and recommendations for using Microsoft Co
     - Red Hat Enterprise Linux (RHEL) 8.* or 9.*
         - If using RHEL, the default container engine (Podman) must be replaced with [Moby](https://github.com/moby/moby#readme)
 
-### Networking recommendations for host machines
+### Recommended host machine networking specifications
 
-- Multiple network interface cards (NICs) on a single MCC instance aren't supported.
+- Multiple network interface cards (NICs) on a single Connected Cache host machine isn't supported.
 - 1 Gbps NIC is the minimum speed recommended but any NIC is supported.
 - The NIC and BIOS should support SR-IOV for best performance.
 
-### Host machine sizing recommendations
+### Recommended host machine hardware specifications
 
-| Component  | Branch Office / Small Enterprise | Large Enterprise |
+Based on your [enterprise configuration](mcc-ent-edu-overview.md), it is recommended to deploy your Connected Cache nodes to host machines that meet the following recommended hardware specifications.
-| --- | --- | --- |
+
-| OS|  Windows Server 2022 <br> Windows 11 (Pro or Enterprise) | Same |
+|   | Branch Office | Small Enterprise | Large Enterprise |
-|NIC | 1 Gbps | 5 Gbps |
+| --- | --- | --- | --- |
-|Disk | SSD <br>1 drive <br>50 GB each  |SSD <br>1 drive <br>200 GB each  |
+| CPU cores | 4 | 8 | 16 |
-|Memory | 4 GB | 8 GB |
+| Memory | 8 GB, 4GB free | 16 GB, 4GB free | 32 GB, 4GB free |
-|Cores | 4 | 8  |
+| Disk storage | 100 GB free  | 500 GB free | 2x 200-500 GB free |
+| NIC | 1 Gbps | 5 Gbps | 10 Gbps |

windows/deployment/do/mcc-ent-private-preview.md

@@ -1,6 +1,6 @@
 ---
-title: MCC Private Preview
+title: Microsoft Connected Cache for Enterprise and Education Private Preview
-description: Details on Microsoft Connected Cache for Enterprise (MCC) Private Preview
+description: Details on Microsoft Connected Cache for Enterprise Private Preview
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: conceptual
@@ -12,15 +12,15 @@ appliesto:
 ms.date: 06/03/2024
 ---
 
-# Microsoft Connected Cache for Enterprise and Education (MCC) Private Preview
+# Microsoft Connected Cache for Enterprise and Education Private Preview
 
-If you participated in the MCC early preview, thank you for your collaboration and feedback.
+If you participated in the Connected Cache early preview, thank you for your collaboration and feedback.
 
-To continue using MCC, we strongly recommend that you upgrade your existing cache nodes to the Public Preview release. Cache nodes created and deployed during early preview should still function but can no longer be managed or monitored remotely via the MCC Azure service.
+To continue using Connected Cache, we strongly recommend that you upgrade your existing cache nodes to the Public Preview release. Cache nodes created and deployed during early preview should still function but can no longer be managed or monitored remotely via the Connected Cache Azure service.
 
-As such, we strongly recommend you [recreate your existing resources in Azure](mcc-ent-create-resource-and-cache.md) and then [redeploy the MCC caching software to your host machines](mcc-ent-deploy-to-windows.md) using the latest OS-specific installer.
+As such, we strongly recommend you [recreate your existing resources in Azure](mcc-ent-create-resource-and-cache.md) and then [redeploy the Connected Cache software to your host machines](mcc-ent-deploy-to-windows.md) using the latest OS-specific installer.
 
 ## Next step
 
 > [!div class="nextstepaction"]
-> [View documentation for MCC Public Preview](mcc-ent-edu-overview.md)
+> [View documentation for Connected Cache Public Preview](mcc-ent-edu-overview.md)

windows/deployment/do/mcc-ent-release-notes.md

@@ -1,6 +1,6 @@
 ---
-title: MCC Release Notes
+title: Microsoft Connected Cache Release Notes
-description: Release Notes for Microsoft Connected Cache for Enterprise and Education (MCC).
+description: Release Notes for Microsoft Connected Cache for Enterprise and Education.
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: conceptual
@@ -14,9 +14,9 @@ appliesto:
 ms.date: 09/27/2024
 ---
 
-# Release Notes for Microsoft Connected Cache for Enterprise and Education (MCC)
+# Release Notes for Microsoft Connected Cache for Enterprise and Education
 
-This article contains details about the latest releases of MCC. Since MCC is a Preview service, some releases may contain breaking changes that will be highlighted as such.
+This article contains details about the latest releases of Connected Cache. Since Connected Cache is a Preview service, some releases may contain breaking changes that will be highlighted as such.
 
 ## Release v0.1.0 (Public Preview launch)
 
@@ -30,11 +30,11 @@ This article contains details about the latest releases of MCC. Since MCC is a P
 
 - Added new "Outbound egress" and "Volume by Content type" monitoring charts to Azure portal user interface
 - Added ability to create custom monitoring charts under the Metrics tab in the Azure portal user interface
-- Added support for creating both Windows-hosted and Linux-hosted cache nodes under the same MCC Azure resource
+- Added support for creating both Windows-hosted and Linux-hosted cache nodes under the same Connected Cache Azure resource
-- Added Azure CLI support for programmatic creation and management of MCC Azure resources and cache nodes
+- Added Azure CLI support for programmatic creation and management of Connected Cache Azure resources and cache nodes
 - Added support for unauthenticated proxy and cloud proxy integration
-- Added ability to set each cache node's Update Ring to govern cadence of MCC container updates
+- Added ability to set each cache node's Update Ring to govern cadence of Connected Cache container updates
 
 ## Related content
 
-- [Overview of MCC](mcc-ent-edu-overview.md)
+- [Overview of Connected Cache](mcc-ent-edu-overview.md)

windows/deployment/do/mcc-ent-troubleshooting.md

@@ -1,6 +1,6 @@
 ---
-title: MCC troubleshooting
+title: Microsoft Connected Cache for Enterprise and Education troubleshooting
-description: Details on how to troubleshoot common issues for Microsoft Connected Cache for Enterprise (MCC).
+description: Details on how to troubleshoot common issues for Microsoft Connected Cache for Enterprise.
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: how-to
@@ -15,9 +15,9 @@ ms.date: 09/27/2024
 ---
 
 
-# Troubleshoot Microsoft Connected Cache for Enterprise and Education (MCC)
+# Troubleshoot Microsoft Connected Cache for Enterprise and Education
 
-This article contains instructions on how to troubleshoot different issues you may encounter while using MCC. These issues are categorized by the task in which they may be encountered. For example, this next section covers troubleshooting [MCC Azure resource creation](mcc-ent-create-resource-and-cache.md).
+This article contains instructions on how to troubleshoot different issues you may encounter while using Connected Cache. These issues are categorized by the task in which they may be encountered. For example, this next section covers troubleshooting [Connected Cache Azure resource creation](mcc-ent-create-resource-and-cache.md).
 
 ## Steps to obtain an Azure subscription ID
 
@@ -26,11 +26,11 @@ This article contains instructions on how to troubleshoot different issues you m
 
 ## Troubleshooting Azure resource creation
 
-MCC Azure resource creation can be initiated using either the Azure portal or the Azure CLI command set. If you're encountering an error during resource creation, check that you have the necessary RPaaS permissions and have filled out all required fields.
+Connected Cache Azure resource creation can be initiated using either the Azure portal or the Azure CLI command set. If you're encountering an error during resource creation, check that you have the necessary RPaaS permissions and have filled out all required fields.
 
 ## Troubleshooting cache node issue
-If you are facing issues with your cache node, it could be due to cache node being on the early preview version of MCC. Cache nodes belonging to early preview version will be under MCC resource that will have 'early preview' in its name. Please delete these cache nodes and associated MCC resource and create a new MCC resource on the new version.
+If you are facing issues with your cache node, it could be due to cache node being on the early preview version of Connected Cache. Cache nodes belonging to early preview version will be under Connected Cache resource that will have 'early preview' in its name. Please delete these cache nodes and associated Connected Cache resource and create a new Connected Cache resource on the new version.
-For detailed instructions on creating MCC resource, see [Create MCC Azure resources](mcc-ent-create-resource-and-cache.md)
+For detailed instructions on creating Connected Cache resource, see [Create Connected Cache Azure resources](mcc-ent-create-resource-and-cache.md)
 
 
 ## Troubleshooting cache node deployment
@@ -61,9 +61,9 @@ Optional: You have two options for manually curated links in this pattern: Next
 
 ## Diagnose and Solve
 
-If this article isn't resolving the issue you're facing with your cache node, you can use the **Diagnose and solve problems** functionality within your MCC resource to continue troubleshooting. **Diagnose and solve problems** contains solutions to most common problems that users might face as they onboard.
+If this article isn't resolving the issue you're facing with your cache node, you can use the **Diagnose and solve problems** functionality within your Connected Cache resource to continue troubleshooting. **Diagnose and solve problems** contains solutions to most common problems that users might face as they onboard.
 
-You can find **Diagnose and solve problems** on the left pane within your MCC resource.
+You can find **Diagnose and solve problems** on the left pane within your Connected Cache resource.
 
 Within **Diagnose and solve problems**, select **Troubleshoot** under the type of problem you're facing and follow the prompts that narrow down the solution to the issue.
 

windows/deployment/do/mcc-ent-uninstall-cache-node.md

@@ -1,6 +1,6 @@
 ---
-title: Uninstall MCC cache nodes
+title: Uninstall Microsoft Connected Cache for Enterprise and Education cache nodes
-description: Details on how to uninstall Microsoft Connected Cache for Enterprise and Education (MCC) from a host machine.
+description: Details on how to uninstall Microsoft Connected Cache for Enterprise and Education from a host machine.
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: how-to
@@ -14,22 +14,22 @@ appliesto:
 ms.date: 09/27/2024
 ---
 
-# Uninstall MCC caching software from a host machine
+# Uninstall Connected Cache caching software from a host machine
 
-This article describes how to uninstall Microsoft Connected Cache for Enterprise and Education (MCC) caching software from a host machine. These steps should be taken after deleting the cache node in the Azure portal.
+This article describes how to uninstall Microsoft Connected Cache for Enterprise and Education caching software from a host machine. These steps should be taken after deleting the cache node in the Azure portal.
 
-## Steps to uninstall MCC from a Windows host machine
+## Steps to uninstall Connected Cache from a Windows host machine
 
-1. Launch a PowerShell window *as administrator* and navigate to the MCC installation directory (C:\mcconwsl01 by default)
+1. Launch a PowerShell window *as administrator* and navigate to the Connected Cache installation directory (C:\mcconwsl01 by default)
 1. Run the `uninstallmcconwsl.ps1` script
 
-## Steps to uninstall MCC from a Linux host machine
+## Steps to uninstall Connected Cache from a Linux host machine
 
-The `uninstallmcc.sh` script within the provisioning package uninstalls the MCC caching software and all related components, including:
+The `uninstallmcc.sh` script within the provisioning package uninstalls the Connected Cache caching software and all related components, including:
 
 - IoT Edge
 - IoT Edge Agent
 - IoT Edge Hub
-- MCC
+- Connected Cache container
 - Moby CLI
 - Moby engine

windows/deployment/do/mcc-ent-update-cache-node.md

@@ -1,6 +1,6 @@
 ---
-title: Update MCC cache nodes
+title: Update Microsoft Connected Cache for Enterprise and Education cache nodes
-description: Details on how Microsoft Connected Cache for Enterprise and Education (MCC) cache nodes are updated by Microsoft.
+description: Details on how Microsoft Connected Cache for Enterprise and Education cache nodes are updated by Microsoft.
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: how-to
@@ -13,28 +13,28 @@ appliesto:
 - ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a> 
 ms.date: 09/27/2024
 ---
-# Configure container update frequency for Microsoft Connected Cache for Enterprise and Education (MCC)
+# Configure container update frequency for Microsoft Connected Cache for Enterprise and Education
 
-Microsoft Connected Cache for Enterprise and Education (MCC) caching software is deployed to host machines as a container. The container OS and any software component within the container need to be updated to address security vulnerabilities and improve quality and performance. These Microsoft-published container updates are referred to as "MCC updates" in this article.
+Microsoft Connected Cache for Enterprise and Education caching software is deployed to host machines as a container. The container OS and any software component within the container need to be updated to address security vulnerabilities and improve quality and performance. These Microsoft-published container updates are referred to as "Connected Cache updates" in this article.
 
-Microsoft silently deploys MCC updates to your cache nodes based on the Update Ring setting you configure for each cache node.
+Microsoft silently deploys Connected Cache updates to your cache nodes based on the Update Ring setting you configure for each cache node.
 
 ## Update rings
 
-MCC cache nodes can be configured to either the "Fast" or "Slow" update ring. If configured to update as part of the Fast ring, the cache node will be silently updated by Microsoft soon after the update is made available. If configured to update as part of the Slow ring, the cache node is silently updated by Microsoft within five weeks of the update becoming available.
+Connected Cache nodes can be configured to either the "Fast" or "Slow" update ring. If configured to update as part of the Fast ring, the cache node will be silently updated by Microsoft soon after the update is made available. If configured to update as part of the Slow ring, the cache node is silently updated by Microsoft within five weeks of the update becoming available.
 
-In other words, configuring cache nodes to update as part of the Slow ring provides users with the option to delay the update process until they have validated that the latest MCC update works within their environment. For example, a user could configure a test cache node to update as part of the Fast ring and validate that clients can successfully interact with the test cache node after the latest MCC update has been applied. This builds confidence that service won't be interrupted when the production cache nodes are updated as part of the Slow ring.
+In other words, configuring cache nodes to update as part of the Slow ring provides users with the option to delay the update process until they have validated that the latest Connected Cache update works within their environment. For example, a user could configure a test cache node to update as part of the Fast ring and validate that clients can successfully interact with the test cache node after the latest Connected Cache update has been applied. This builds confidence that service won't be interrupted when the production cache nodes are updated as part of the Slow ring.
 
 ### Update ring options
 
 >[!IMPORTANT]
->In the event of a critical security patch, Microsoft may elect to initiate an MCC update to your cache node as soon as possible (even if the cache node has been set to the Slow Ring). Visit the [Release notes](mcc-ent-release-notes.md) page for a detailed changelog of each MCC update.
+>In the event of a critical security patch, Microsoft may elect to initiate an Connected Cache update to your cache node as soon as possible (even if the cache node has been set to the Slow Ring). Visit the [Release notes](mcc-ent-release-notes.md) page for a detailed changelog of each Connected Cache update.
 
 #### Fast Ring
-All MCC cache nodes are configured to update as part of the Fast ring by default. MCC cache nodes in the Fast ring will be updated soon after an update is made available. Microsoft will silently update cache nodes at a time of day when update traffic is likely to be minimal, such as 3:00 AM (local time) on Saturday.
+All Connected Cache nodes are configured to update as part of the Fast ring by default. Connected Cache nodes in the Fast ring will be updated soon after an update is made available. Microsoft will silently update cache nodes at a time of day when update traffic is likely to be minimal, such as 3:00 AM (local time) on Saturday.
 
 #### Slow Ring
-Configuring an MCC cache node to update as part of the Slow ring provides users with the option to delay MCC software updates until the update can be validated. There are three settings that control when MCC updates will be applied to MCC cache nodes. All update ring settings can be managed from the Azure portal or through Azure CLI.
+Configuring an Connected Cache node to update as part of the Slow ring provides users with the option to delay Connected Cache software updates until the update can be validated. There are three settings that control when Connected Cache updates will be applied to Connected Cache nodes. All update ring settings can be managed from the Azure portal or through Azure CLI.
 
 | Setting | Description |
 | --- | --- |
@@ -44,15 +44,15 @@ Configuring an MCC cache node to update as part of the Slow ring provides users
 
 ## Update process
 
-When Microsoft publishes an MCC update, the MCC service attempts to update all MCC cache nodes based on their Update Ring membership. If a cache node can't complete the silent MCC update within 6 hours of starting, an error message is surfaced in the Azure portal.
+When Microsoft publishes an Connected Cache update, the Connected Cache service attempts to update all Connected Cache nodes based on their Update Ring membership. If a cache node can't complete the silent Connected Cache update within 6 hours of starting, an error message is surfaced in the Azure portal.
 
 ## Update terminology, criteria, and SLA
 
-MCC updates will be released based on need instead of on a set cadence.
+Connected Cache updates will be released based on need instead of on a set cadence.
 
 | Update type | Criteria and SLA |
 | --- | --- |
 | Security | Security updates are the highest priority and will be released based on the severity rating of the vulnerability. [Critical and High](https://nvd.nist.gov/vuln-metrics/cvss) vulnerabilities will be released by Microsoft within 60 days of discovery. [Medium and Low](https://nvd.nist.gov/vuln-metrics/cvss) vulnerabilities will be released by Microsoft within 120 days |
 | Quality | Quality updates fix a specific problem and addresses a noncritical, non-security-related bug. Quality updates could include performance fixes for a specific problem or changes related to cache efficiency or maximum egress for example. Quality updates are released along with security updates or when necessary to ensure proper functioning of the Microsoft Connected Cache software. |
 
-For information on all released Microsoft Connected Cache updates, see the [MCC release notes](mcc-ent-release-notes.md).
+For information on all released Microsoft Connected Cache updates, see the [Connected Cache release notes](mcc-ent-release-notes.md).

windows/deployment/do/mcc-ent-verify-cache-node.md

@@ -1,6 +1,6 @@
 ---
-title: Verify MCC cache node functionality
+title: Verify Microsoft Connected Cache for Enterprise and Education cache node functionality
-description: Details on how to verify functionality of Microsoft Connected Cache for Enterprise and Education (MCC) cache nodes.
+description: Details on how to verify functionality of Microsoft Connected Cache for Enterprise and Education cache nodes.
 author: chrisjlin
 ms.author: lichris
 manager: naengler
@@ -9,20 +9,20 @@ ms.subservice: itpro-updates
 ms.topic: how-to
 ms.date: 09/27/2024
 appliesto: 
-- ✅ Windows-hosted MCC cache nodes
+- ✅ Windows-hosted Connected Cache cache nodes
-- ✅ Linux-hosted MCC cache nodes
+- ✅ Linux-hosted Connected Cache cache nodes
 - ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>	
 ---
 
-# Verify MCC cache node functionality
+# Verify Connected Cache node functionality
 
-This article describes how to verify that a Microsoft Connected Cache for Enterprise and Education (MCC) cache node is functioning correctly.
+This article describes how to verify that a Microsoft Connected Cache for Enterprise and Education cache node is functioning correctly.
 
-These steps should be taken after deploying MCC caching software to a [Windows](mcc-ent-deploy-to-windows.md) or [Linux](mcc-ent-deploy-to-linux.md) host machine.
+These steps should be taken after deploying Connected Cache software to a [Windows](mcc-ent-deploy-to-windows.md) or [Linux](mcc-ent-deploy-to-linux.md) host machine.
 
-## Steps to verify functionality of MCC cache node
+## Steps to verify functionality of Connected Cache node
 
-1. To verify that the MCC container on the host machine is running and reachable, run the following command from the host machine:
+1. To verify that the Connected Cache container on the host machine is running and reachable, run the following command from the host machine:
 
     ```powershell
     wget http://localhost/filestreamingservice/files/7bc846e0-af9c-49be-a03d-bb04428c9bb5/Microsoft.png?cacheHostOrigin=dl.delivery.mp.microsoft.com
@@ -30,13 +30,13 @@ These steps should be taken after deploying MCC caching software to a [Windows](
 
     If successful, there should be an HTTP response with StatusCode 200.
 
-1. To verify that Windows clients in your network can reach the MCC cache node, visit the following address from a web browser on a Windows client device:
+1. To verify that Windows clients in your network can reach the Connected Cache node, visit the following address from a web browser on a Windows client device:
 
     `http://[HostMachine-IP-address]/filestreamingservice/files/7bc846e0-af9c-49be-a03d-bb04428c9bb5/Microsoft.png?cacheHostOrigin=dl.delivery.mp.microsoft.com`
 
-    If successful, the Windows client device should begin to download a small image file from the MCC cache node.
+    If successful, the Windows client device should begin to download a small image file from the Connected Cache node.
 
-1. To check how much content an individual Windows client has pulled from an MCC cache node, open the [Delivery Optimization activity monitor](/microsoft-365-apps/updates/delivery-optimization#viewing-data-about-the-use-of-delivery-optimization) on the Windows client device.
+1. To check how much content an individual Windows client has pulled from an Connected Cache node, open the [Delivery Optimization activity monitor](/microsoft-365-apps/updates/delivery-optimization#viewing-data-about-the-use-of-delivery-optimization) on the Windows client device.
 
     You should see a donut chart titled Download Statistics. If the Windows client has pulled content from the cache node, you'll see a segment of the donut labeled "From Microsoft cache server".