Merge pull request #10272 from chrisjlin/edit-release-mcc-ent

lichris-docs-2

windows/deployment/do/TOC.yml

@@ -45,19 +45,19 @@
           href: mcc-ent-create-resource-and-cache.md
         - name: Configure, provision and deploy cache node
           items:
-          - name: Configure and provision cache node on Linux
+          - name: Deploy MCC to Linux
-            href: mcc-ent-configure-provision-linux.md
+            href: mcc-ent-deploy-to-linux.md
-          - name: Configure and provision cache node on Windows
+          - name: Deploy MCC to Windows
-            href: mcc-ent-configure-provision-windows.md
+            href: mcc-ent-deploy-to-windows.md
         - name: Using CLI to create and manage cache nodes
           href: mcc-ent-manage-cache-using-CLI.md 
         - name: Verify cache node functionality
           href: mcc-ent-verify-cache-node.md
         - name: Monitor cache node
-          href: mcc-ent-monitor-cache.md
+          href: mcc-ent-monitoring.md
         - name: Update MCC
-          href: mcc-ent-update-cache.md 
+          href: mcc-ent-update-cache-node.md 
-        - name: Uninstalling cache node
+        - name: Uninstall cache node
           href: mcc-ent-uninstall-cache-node.md     
       - name: Resources
         items:

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

@@ -1,31 +1,29 @@
 ---
-title: MCC for Enterprise provision create cache node
+title: Create and configure MCCE cache nodes
-description: Microsoft Connected Cache for Enterprise. Learn about how to create cache node.
+description: Details on how to create and configure Microsoft Connected Cache for Enterprise and Education (MCCE) cache nodes.
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: how-to
-manager: aaroncz
+manager: naengler
 ms.author: nidos
 author: doshnid
-ms.reviewer: mstewart
-ms.collection: tier3
 appliesto: 
 - ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
-- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
+- ✅ Supported Linux distributions
 - ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise</a>	
 ms.date: 06/03/2024
 ---
 
-# Create MCC resource and cache nodes
+# Create MCCE Azure resource and cache nodes
 
-This article outlines how to create and configure your Microsoft Connected Cache for Enterprise cache nodes. The creation and configuration of your cache node takes place in Azure portal. The deployment of your cache node requires downloading an installer script that will need to be run on your cache server.
+This article outlines how to create and configure your Microsoft Connected Cache for Enterprise and Education (MCCE) 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 completely free-of-charge service hosted in Azure. You'll need to have a Pay-As-You-Go 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/).
+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.
-For more information on sizing and OS requirements, please visit [Host OS Requirement](mcc-ent-prerequisites.md)
+For more information on sizing and OS requirements, see [the prerequisites for using MCCE](mcc-ent-prerequisites.md).
 
-## Create MCC resource
+## Create MCCE Azure resource
 
 # [Azure portal](#tab/portal)
 
@@ -34,13 +32,13 @@ For more information on sizing and OS requirements, please visit [Host OS Requir
     :::image type="content" source="images/mcc-isp-provision-cache-node-numbered.png" alt-text="Screenshot of the Azure portal depicting the cache node configuration page of a cache node. This screenshot shows all of the fields you can choose to configure the cache node." lightbox="./images/mcc-isp-provision-cache-node-numbered.png":::  
 -->
 
-1. Select Microsoft Connected Cache for Enterprise resource. When prompted, choose the subscription, resource group, and location for the resource. Also, enter a name for the resource and click Review + Create.
+1. Select the Microsoft Connected Cache for Enterprise resource. When prompted, choose the subscription, resource group, and location for the resource. Then enter a name for the resource and select Review + Create.
 <!--
     :::image type="content" source="images/mcc-isp-provision-cache-node-numbered.png" alt-text="Screenshot of the Azure portal depicting the cache node configuration page of a cache node. This screenshot shows all of the fields you can choose to configure the cache node." lightbox="./images/mcc-isp-provision-cache-node-numbered.png":::  
 -->
 1. After a few moments, you'll see a "Validation successful" message, indicating you can move onto the next step and select Create.
 
-1. The creation of the resource may take a few minutes. After a successful creation, you'll see a Deployment complete page as below. Select Go to resource to create cache nodes.
+1. The creation of the resource might take a few minutes. After a successful creation, you'll see a Deployment complete page as below. Select Go to resource to create cache nodes.
 
 
 # [Azure CLI](#tab/cli)
@@ -61,7 +59,7 @@ For more information on sizing and OS requirements, please visit [Host OS Requir
 
     * 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.
 
-#### Create MCC resource
+#### Create MCCE Azure resource
 Replace the following placeholders with your own information:
 * *\<resource-group>*: An existing resource group in your subscription.
 * *\<mcc-resource-name>*: A name for your Microsoft Connected Cache for Enterprise resource.
@@ -73,26 +71,26 @@ az mcc ent resource create --mcc-resource-name <mymccresource> --resource-group
 
 ---
 
-## Create cache node
+## Create MCCE cache node
 
 # [Azure portal](#tab/portal)
 
   1. Open Azure portal and navigate to the Microsoft Connected Cache for Enterprise resource that you created.
-  1. Under Cache Node Management, click on Cache Nodes and then on + Create Cache Node.
+  1. Under Cache Node Management, select on Cache Nodes and then on + Create Cache Node.
   <!--
     :::image type="content" source="images/mcc-isp-provision-cache-node-numbered.png" alt-text="Screenshot of the Azure portal depicting the cache node configuration page of a cache node. This screenshot shows all of the fields you can choose to configure the cache node." lightbox="./images/mcc-isp-provision-cache-node-numbered.png":::  
     -->
-  1. Provide a name for your cache node and select the host OS you plan to deploy the cache node on and click create. Please note, cache node names have to be unique under the Microsoft Connected Cache resource.
+  1. Provide a name for your cache node and select the host OS you plan to deploy the cache node on and select create. Note, cache node names have to be unique under the Microsoft Connected Cache resource.
   <!--
     :::image type="content" source="images/mcc-isp-provision-cache-node-numbered.png" alt-text="Screenshot of the Azure portal depicting the cache node configuration page of a cache node. This screenshot shows all of the fields you can choose to configure the cache node." lightbox="./images/mcc-isp-provision-cache-node-numbered.png":::  
     -->
-  The creation of cache node may take a few minutes. Please click Refresh to see your recently created cache node.
+  The creation of cache node might take a few minutes. Select Refresh to see your recently created cache node.
 Once the status changes to **Not Configured**, you can now configure your cache node.
 
 
 # [Azure CLI](#tab/cli)
 
-Use the command below to create a new cache node if you don't already have one.
+Use the following command to create a new cache node if you don't already have one.
 
 Replace the following placeholders with your own information:
 * *\<resource-group>*: An existing resource group in your subscription.
@@ -123,22 +121,22 @@ az mcc ent node create --cache-node-name <mycachenode> --mcc-resource-name <mymc
 
 ---
 
-## Configure cache node
+## Configure MCCE cache node
 
 # [Azure portal](#tab/portal)
-Please enter required values to configure your cache node. To learn more about the definitions of each field, review the Configuration fields at the bottom of this article.
+Enter required values to configure your cache node. To learn more about the definitions of each field, review the Configuration fields at the bottom of this article.
-Don't forget to click save after adding configuration information.
+Don't forget to select save after adding configuration information.
 
 
 # [Azure CLI](#tab/cli)
 
-Use the command below to configure cache node for **Linux** host OS
+Use the following command to configure cache node for deployment to a **Linux** host machine.
 
 Replace the following placeholders with your own information:
 * *\<resource-group>*: An existing resource group in your subscription.
 * *\<mcc-resource-name>*: A name for your Microsoft Connected Cache for Enterprise resource.
 * *\<cache-node-name>*: The Azure region where your Microsoft Connected Cache will be located.
-* *\<physical-path>*: The cache drive path. You can add upto 9 cache drives.
+* *\<physical-path>*: The cache drive path. You can add upto nine cache drives.
 * *\<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
@@ -162,7 +160,7 @@ az mcc ent node update --cache-node-name <mycachenode> --mcc-resource-name <mymc
 <br>
 <br>
 
-Use the command below to configure cache node for **Windows** host OS
+Use the following command to configure cache node for deployment to a **Windows** host machine.
 
 Replace the following placeholders with your own information:
 * *\<resource-group>*: An existing resource group in your subscription.
@@ -190,22 +188,17 @@ az mcc ent node update --cache-node-name <mycachenode> --mcc-resource-name <mymc
 --cache-drive "[{physical-path:/var/mcc,size-in-gb:<size of cache drive>}]" --proxy <enabled> --proxy-host <"proxy host name"> --proxy-port <proxy port>  --auto-update-day <day of week> --auto-update-time <time of day> --auto-update-week <week of month> --auto-update-ring <update ring>
 ```
 
-
-
 ---
 
 ## Next step
-The next step is to provision the cache node on the server.
 
-# [Azure portal](#tab/portal)
+### [Azure portal](#tab/portal)
-To provision MCC on **Windows** host machine, see [Provision Windows cache node](mcc-ent-configure-provision-windows.md)
+To deploy the cache node to a **Windows** host machine, see [Deploy cache node to Windows](mcc-ent-deploy-to-windows.md)
 
-<br>
+To deploy the cache node to a **Linux** host machine, see [Deploy cache node to Linux](mcc-ent-deploy-to-linux.md)
 
-To provision MCC on **Linux** host machine, see [Provision Linux cache node](mcc-ent-configure-provision-linux.md)
+### [Azure CLI](#tab/cli/)
-
+To deploy cache nodes using Azure CLI, see [Bulk management of cache nodes](mcc-ent-manage-cache-using-CLI.md)
-# [Azure CLI](#tab/cli/)
-To provision cache node using Azure CLI, see [Bulk management of cache nodes](mcc-ent-manage-cache-using-CLI.md)
 
 ---
 <br>
@@ -214,33 +207,30 @@ To provision cache node using Azure CLI, see [Bulk management of cache nodes](mc
 
 ### General configuration fields
 
-| Field Name	|Expected Value	 |Description|
+| Field Name |Expected Value |Description|
 |---|---|---|
-|**Cache node name** |	Alphanumeric string that contains no spaces|	The name of the cache node. You may choose names based on location like Seattle-1. This name must be unique and can't be changed later|
+|**Cache node name** | Alphanumeric string that contains no spaces| The name of the cache node. You may choose names based on location such as "Seattle-1". This name must be unique and can't be changed later |
-|**Host OS** |	Linux or Windows| This is the host operating system that the cache node will be deployed on.|
+|**Host OS** | Linux or Windows| This is the operating system of the host machine that the cache node will be deployed to.|
 
 ### Storage fields
 
-
 ##### Cache node for Linux
 
 >[!Important]
 >All cache drives must have full read/write permissions set or the cache node will not function. For example, in a terminal you can run: sudo chmod 777 /path/to/cachedrivefolder
 <br>
 
-| Field Name	|Expected Value	 |Description|
+| Field Name |Expected Value |Description|
 |---|---|---|
-|**Cache drive folder**|	File path string	|Up to 9 drive folders accessible by the cache node can be configured for each cache node to configure cache storage. Enter the location of the folder in Ubuntu where the external physical drive is mounted. For example: /dev/sda3/. Each cache drive should have read/write permissions configured. Ensure your disks are mounted and visit Attach a data disk to a Linux VM for more information.|
+|**Cache drive folder**| File path string |Up to nine drive folders accessible by the cache node can be configured for each cache node to configure cache storage. Enter the location of the folder in Ubuntu where the external physical drive is mounted. For example: /dev/sda3/. Each cache drive should have read/write permissions configured. Ensure your disks are mounted and visit Attach a data disk to a Linux VM for more information.|
-|**Cache drive size in gigabytes**|	Integer in GB| 	Set the size of each drive configured for the cache node. Minimum cache drive size is 50 GB.|
+|**Cache drive size in gigabytes**| Integer in GB| Set the size of each drive configured for the cache node. Minimum cache drive size is 50 GB.|
-
 
 ##### Cache node for Windows
 
-| Field Name	|Expected Value	 |Description|
+| Field Name |Expected Value |Description|
 |---|---|---|
-|**Cache drive folder**|	File path string /var/mcc|	This is the folder path where content will be cached. You cannot change the folder path.|
+|**Cache drive folder**| File path string /var/mcc| This is the folder path where content is cached. You can't change the folder path.|
-|**Cache drive size in gigabytes**|	Integer in GB|	Set the size of each drive configured for the cache node. Minimum cache drive size is 50 GB. |
+|**Cache drive size in gigabytes**| Integer in GB| Set the size of each drive configured for the cache node. Minimum cache drive size is 50 GB. |
-
 
 #### Proxy settings
 <br>
@@ -255,4 +245,3 @@ You can choose to enable or disable proxy settings on your cache node.
 |---|---|---|
 |**Proxy host name**|	String or number|	Proxy host name or address|
 |**Proxy port**|	Integer|	Proxy port
-

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

@@ -0,0 +1,38 @@
+---
+title: Deploy MCCE cache software to a Linux host machine
+description: Details on how to deploy Microsoft Connected Cache for Enterprise and Education (MCCE) cache software to a Linux host machine.
+author: chrisjlin
+ms.author: lichris
+manager: naengler
+ms.service: windows-client
+ms.subservice: itpro-updates
+ms.topic: how-to
+ms.date: 09/27/2024
+appliesto: 
+- ✅ Supported Linux distributions
+- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>	
+---
+
+# Deploy MCCE cache node to a Linux host machine
+
+This article describes how to deploy Microsoft Connected Cache for Enterprise and Education (MCCE) caching software to a Linux host machine.
+
+Before deploying MCCE 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](https://aka.ms/mccent-create-resources).
+
+## Steps to deploy MCCE cache node to Linux
+
+1. Within the Azure portal, navigate to the "Provisioning" tab of your cache node and copy the provisioning command.
+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 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. Run the provisioning command on the host machine.
+
+## Next step
+
+> [!div class="nextstepaction"]
+> [Verify cache node functionality](mcc-ent-verify-cache-node.md)
+
+## Related content
+
+- [Deploy to a Windows host machine](mcc-ent-deploy-to-windows.md)
+- [Uninstall MCCE](mcc-ent-uninstall-cache-node.md)

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

@@ -0,0 +1,44 @@
+---
+title: Deploy MCCE cache software to a Windows host machine
+description: Details on how to deploy Microsoft Connected Cache for Enterprise and Education (MCCE) cache software to a Windows host machine.
+author: chrisjlin
+ms.author: lichris
+manager: naengler
+ms.service: windows-client
+ms.subservice: itpro-updates
+ms.topic: how-to
+ms.date: 09/27/2024
+appliesto: 
+- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
+- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>	
+---
+
+# Deploy MCCE cache node to a Windows host machine
+
+This article describes how to deploy Microsoft Connected Cache for Enterprise and Education (MCCE) caching software to a Windows host machine.
+
+Deploying MCCE 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 MCCE runtime account. This prevents tampering with the MCC container and the cached content on the host machine.
+
+Before deploying MCCE 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](https://aka.ms/mccent-create-resources).
+
+## Steps to deploy MCCE cache node to Windows
+
+1. Within the Azure portal, navigate to the "Provisioning" tab of your cache node and copy the provisioning command.
+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 windows *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"`.
+    - If you're using a Local User account as the MCCE 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.
+
+## Next step
+
+> [!div class="nextstepaction"]
+> [Verify cache node functionality](mcc-ent-verify-cache-node.md)
+
+<!-- OR -->
+
+## Related content
+
+- [Deploy to a Linux host machine](mcc-ent-deploy-to-linux.md)
+- [Uninstall MCCE](mcc-ent-uninstall-cache-node.md)

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

@@ -1,6 +1,6 @@
 ---
-title: MCC for Enterprise and Education Overview
+title: MCCE Overview
-description: Overview, supported scenarios, and content types for Microsoft Connected Cache (MCC) for Enterprise and Education.
+description: Overview, supported scenarios, and content types for Microsoft Connected Cache for Enterprise and Education (MCCE).
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: conceptual

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

@@ -1,7 +1,7 @@
 ### YamlMime:FAQ
 metadata:
-  title: Microsoft Connected Cache for Enterprise Frequently Asked Questions
+  title: MCCE Frequently Asked Questions
-  description: The following article is a list of frequently asked questions for Microsoft Connected Cache for Enterprise.
+  description: The following article is a list of frequently asked questions for Microsoft Connected Cache for Enterprise (MCCE).
   ms.service: windows-client
   ms.subservice: itpro-updates
   ms.topic: faq

windows/deployment/do/mcc-ent-manage-cache-using-CLI.md

@@ -1,6 +1,6 @@
 ---
-title: MCC for Enterprise manage cache nodes using CLI
+title: Manage MCCE cache nodes using CLI
-description: Microsoft Connected Cache for Enterprise. Learn about managing cache nodes using CLI
+description: Details on how to manage Microsoft Connected Cache for Enterprise (MCCE) cache nodes via Azure CLI commands.
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: how-to
@@ -20,7 +20,7 @@ ms.date: 06/03/2024
 
 <br>
 
-This article outlines how to create, configure and provision your Microsoft Connected Cache for Enterprise cache nodes using Azure CLI.
+This article outlines how to create, configure, and deploy Microsoft Connected Cache for Enterprise (MCCE) cache nodes using Azure CLI.
 
  
 ## Prerequisites:
@@ -34,20 +34,20 @@ This article outlines how to create, configure and provision your Microsoft Conn
 The first step is to create a resource group if you don't already have one.
 An Azure resource group is a logical container into which Azure resources are deployed and managed.
 
-To create a resource group, use [az group create](/cli/azure/group#az-group-create).
+To create a resource group, use `az group create`. You can find more details on this CLI command [here](/cli/azure/group#az-group-create).
 <br>
 
 ```azurecli-interactive
 az group create --name myrg --location westus
 ```
 
-Once the resource group is created, you will need to create a Microsoft Connected Cache for Enterprise resource.
+Once the resource group is created, you'll need to create a Microsoft Connected Cache for Enterprise resource.
 
 
-### 2. Create a MCC resource
+### 2. Create an MCCE Azure resource
-A MCC resource is a resource under which cache nodes can be created.
+An MCCE Azure resource is a top-level Azure resource under which cache nodes can be created.
 
-To create a mcc resource, use az mcc ent resource create
+To create an MCCE Azure resource, use `az mcc ent resource create`
 
 ```azurecli-interactive
 az mcc ent resource create --mcc-resource-name mymccresource --resource-group myrg
@@ -64,7 +64,7 @@ The next step is to create a cache node under this resource.
 
 
 ### 3. Create a cache node
-To create a cache node, use az mcc ent node create
+To create a cache node, use `az mcc ent node create`
 
 ```azurecli-interactive
 az mcc ent node create --cache-node-name mycachenode --mcc-resource-name mymccresource --resource-group myrg --host-os linux
@@ -78,8 +78,9 @@ az mcc ent node create --cache-node-name mycachenode --mcc-resource-name mymccre
 <br>
 
 ### 4. Confirm cache node creation
-Before you can start configuring your cache node, you need to confirm that cache node creation has been successful. 
+Before you can start configuring your cache node, you need to confirm that the cache node was successfully created.
-To confirm cache node creation, use az mcc ent node show
+
+To confirm cache node creation, use `az mcc ent node show`
 
 <br>
 
@@ -93,11 +94,11 @@ az mcc ent node show --cache-node-name mycachenode --mcc-resource-name mymccreso
 
 <br>
 
-Once the cache node has been created successfully, you can now configure the cache node.
+Once successful cache node creation is confirmed, you can proceed to configure the cache node.
 
 
 ### 5. Configure cache node
-To configure your cache node, use az mcc ent node update
+To configure your cache node, use `az mcc ent node update`
 
 The below example configures a Linux cache node with proxy enabled:
 
@@ -125,68 +126,59 @@ az mcc ent node update --cache-node-name <mycachenode> --mcc-resource-name <mymc
 <br>
 
 ### 6. Get provisioning details for the cache node
-Now that you have configured the cache node, the next step is to provision the cache node on the server. To provision the cache node, you will need to create a provisioning script with relevant information.
+After successfully configuring the cache node, the next step is to deploy the cache node to a host machine. To deploy the cache node, you'll need to create a provisioning script with relevant information.
-To get the relevant information for provisioning script, use az mcc ent node get-provisioning-details
+
+To get the relevant information for provisioning script, use `az mcc ent node get-provisioning-details`
 
 ```azurecli-interactive
 az mcc ent node get-provisioning-details --cache-node-name mycachenode --mcc-resource-name mymccresource --resource-group myrg
 ```
 
-In the output, please save the values for cacheNodeId, customerKey, mccResourceId, registrationKey. These values are needed to create the provisioning script.
+Save the resulting values for cacheNodeId, customerKey, mccResourceId, registrationKey. These GUIDs are needed to create the provisioning script.
 
-### 7. Provisioning cache node
+### 7. Deploy cache node
 <br>
 
-#### Provisioning cache node on Linux host OS:
+#### Deploy cache node to Linux host machine
-Before you provision your cache node on Linux machine, please make sure you have completed the requisites listed here: Host machine requirements
+Before you deploy your cache node to a Linux host machine, make sure you have met the prerequisites listed here: [Host machine requirements](mcc-ent-prerequisites.md)
 
-Use the link below to download and unzip the provisioning package on the server and run the below script to provision your cache node. 
+Use the following link to download and extract the Linux-compatible MCCE provisioning package onto the host machine.
 
-[Download MCC package for Linux host OS](https://aka.ms/MCC-Ent-InstallScript-Linux)
+[Download MCCE provisioning package for Linux host machine](https://aka.ms/MCC-Ent-InstallScript-Linux)
 
 <br>
 
 >[!IMPORTANT]
->Note: before you execute the script,  please make sure you change access permissions by running the command below <br>
+>Before you execute the provisioning command, make sure you change directory to the extracted provisioning package and set the script execution permissions by running the command below.
->```azurepowershell-interactive
+```azurepowershell-interactive
->sudo chmod +x provisionmcc.sh
+sudo chmod +x provisionmcc.sh
->```
+```
 
-<br>
+Replace the values in the following provisioning command before running it.<br>
 
->[!NOTE]
+```azurepowershell-interactive
->Please replace the sample values in the script below with the values that you saved in the step 5 and 6.
-
-<br>
-
->[!IMPORTANT]
->'shoulduseproxy' parameter is required, whether or not your network uses proxy to access internet.
-
-<br>
-
-Provisioning script:<br>
-`powershell-interactive
 sudo ./provisionmcc.sh customerid="enter mccResourceId here" cachenodeid=" enter cacheNodeId here " customerkey=" enter customerKey here " registrationkey="enter registrationKey here" drivepathandsizeingb="enter physicalPath value,enter sizeInGb value here" shoulduseproxy="true" proxyurl=http://enter proxy hostname:enter port
-`
+```
 <br>
 
-#### Provisioning cache node on Windows host OS:
-
-Before you provision your cache node on Windows, make sure you have completed the requisites listed here: [Host machine requirements](mcc-ent-prerequisites.md)
-
-Please download and unzip the provisioning package on the server and run the below script to provision your cache node.
-Note: Please replace the sample values with the values that you saved in the above steps.
-
 >[!IMPORTANT]
 >'shoulduseproxy' parameter is required, whether or not your network uses proxy to access internet.
 
+#### Deploy cache node to Windows host machine
+
+Before you deploy your cache node to a Windows host machine, make sure you have met the prerequisites listed here: [Host machine requirements](mcc-ent-prerequisites.md)
+
+Use the following link to download and extract the Windows-compatible MCCE provisioning package onto the host machine.
+[Download MCCE provisioning package for Windows host machine](https://aka.ms/MCC-Ent-InstallScript-WSL)
 <br>
 
-[Download MCC package for Windows host OS](https://aka.ms/MCC-Ent-InstallScript-WSL)
+>[!IMPORTANT]
-<br>
+>Before you execute the provisioning command, make sure you change directory to the extracted provisioning package and set the script execution permissions by running the command below.
+```azurepowershell-interactive
+Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process
+```
 
-
+If you're using a **Group Managed Service Account**, replace the values in the following provisioning command before running it.<br>
-If you are using a **gmsa** account:<br>
 
 ```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 $true -proxyurl " http://enter proxy host name:enter port"  -mccRunTimeAccount $User
@@ -194,7 +186,10 @@ If you are using a **gmsa** account:<br>
 
 <br>
 
-If you are using **local user account** or **domain user account**:<br>
+>[!IMPORTANT]
+>'shoulduseproxy' parameter is required, whether or not your network uses proxy to access internet.
+
+If you're using **Local User account** or **Domain User account**, replace the values in the following provisioning command before running it.<br>
 
 ```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 $true -proxyurl " http://enter proxy host name:enter port"  -mccRunTimeAccount $User -mccLocalAccountCredential $myLocalAccountCredential 
@@ -202,10 +197,13 @@ If you are using **local user account** or **domain user account**:<br>
 
 <br>
 
+>[!IMPORTANT]
+>'shoulduseproxy' parameter is required, whether or not your network uses proxy to access internet.
+
 
 ## Next step
 
-To verify cache node functionality, visit, [Verify cache node functionality](mcc-ent-verify-cache-node.md)
+To verify cache node functionality, see [Verify cache node functionality](mcc-ent-verify-cache-node.md)
 
 
 <br>

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

@@ -0,0 +1,61 @@
+---
+title: Monitor usage of MCCE cache nodes
+description: Details on how to monitor the usage of Microsoft Connected Cache for Enterprise (MCCE) cache nodes.
+ms.service: windows-client
+ms.subservice: itpro-updates
+ms.topic: how-to
+manager: naengler
+ms.author: lichris
+author: chrisjlin
+appliesto: 
+- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
+- ✅ Supported Linux distributions
+- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise</a>	
+ms.date: 09/04/2024
+---
+
+# Monitor MCCE cache node usage
+
+Tracking the status and performance of your MCCE cache node is essential to making sure that you're getting the most out of the service.
+
+<!-- Add standard metrics
+
+      Add scenarios for creating custom metrics -->
+
+## Cache node summary
+
+The Cache Node Summary box on your Azure portal 
+
+| Metric | Description |
+| --- | --- |
+| Healthy nodes | The MCCE service will periodically request heartbeat messages from your MCC node to determine if it's functioning as expected. |
+| Unhealthy nodes | If the cache node doesn't respond, it is labeled as unhealthy. |
+| Max in | The maximum egress (in Mb/sec.) that your node has pulled in at any given time. This statistic isn't dependent on the time filter near the charts. |
+| Max out | The minimum egress (in Mb/sec.) that your node has pushed out at any given time. |
+| Average in | The average ingress (in Mb/sec.) that your node has pulled in over its lifetime. This statistic isn't dependent on the time filter near the charts. |
+| Average out | The average egress (in Mb/sec.) that your node has pushed out over its lifetime. |
+| Cache efficiency | The percentage of all requests that your MCC node receives that are ultimately delivered by your MCC node. An effective node is generally expected to have an efficiency >95%. |
+
+## Charts
+
+### Filters
+
+- Will only filter the data shown in the two charts, scalable from 1 hour to 30 days
+- Can view data by individual cache nodes or the average of all your active MCC nodes.
+
+### Outbound traffic
+
+- The egress (in Mb/sec) that your MCC node is pushing out at specific time intervals
+
+### Volume by Content Type
+
+- The volume of content that your MCCE cache node is distributing, broken down by the hostname used to download said content
+
+## Additional metrics
+
+### Custom metrics
+
+- Navigate to the "Metrics" tab in the left-hand toolbar
+- Configure chart as desired using the provided metrics
+
+<!-- ### Windows Update for Business (WUfB) reports -->

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

@@ -1,60 +1,71 @@
 ---
-title: Requirements for MCC for Enterprise and Education
+title: MCCE prerequisites
-description: Overview of prerequisites and recommendations for using Microsoft Connected Cache (MCC) for Enterprise and Education.
+description: Details of prerequisites and recommendations for using Microsoft Connected Cache for Enterprise and Education (MCCE).
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: conceptual
-ms.author: carmenf
+ms.author: lichris
-author: cmknox
+author: chrisjlin
-manager: aaroncz
+manager: naengler
-ms.reviewer: mstewart
-ms.collection: tier3
 appliesto: 
 - ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
-- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
+- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
-- - ✅ <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
-ms.date: 05/23/2024
 ---
 
-# Requirements of Microsoft Connected Cache for Enterprise and Education (early preview)
+# Microsoft Connected Cache for Enterprise and Education Requirements (Public Preview)
 
-> [!NOTE]
+This article details the requirements and recommendations for using Microsoft Connected Cache for Enterprise and Education (MCCE).
-> 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).
 
-## Enterprise requirements for MCC
+## Licensing requirements
 
-1. **Azure subscription**: MCC management portal is hosted within Azure and is used to create the Connected Cache [Azure resource](/azure/cloud-adoption-framework/govern/resource-consistency/resource-access-management) and IoT Hub resource. Both are free services.
+- **Valid Azure subscription**: To use the Microsoft Connected Cache for Enterprise and Education (MCCE) 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).
 
-    Your Azure subscription ID is first used to provision MCC services, and enable access to the preview. The MCC server requirement for an Azure subscription costs you nothing. 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/).
+    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 resources used for the preview and in the future when this product is ready for production will be free to you, like other caching solutions.
+    The Azure resources used for MCCE will be free to you during this public preview.
-1. **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.
-  
-   > [!NOTE]
-   > Azure VMs are not currently supported. If you'd like to install your cache node on VMWare, see the [Appendix](mcc-enterprise-appendix.md) for a few additional configurations.
 
-    **EFLOW requires Hyper-V support**
+- **E3/E5 or A3/A5 license**: Your organization must have one of the following license subscriptions for each device that downloads content from an MCCE cache node.
-    - On Windows client, enable the Hyper-V feature.
-    - On Windows Server, install the Hyper-V role and create a default network switch.
-    - For more requirements, see [EFLOW requirements](/azure/iot-edge/iot-edge-for-linux-on-windows#prerequisites).
 
-    Disk recommendations:
+    - [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)
-    - Using an SSD is recommended as cache read speed of SSD is superior to HDD
+    - Windows Education A3 or A5, included in [Microsoft 365 A3 or A5](https://www.microsoft.com/education/products/microsoft-365?msockid=32c407b43d5968050f2b13443c746916#Education-plans)
 
-    NIC requirements:
+## Cache node host machine requirements
-    - Multiple NICs on a single MCC instance aren't supported.
-    - 1 Gbps NIC is the minimum speed recommended but any NIC is supported.
-    - For best performance, NIC and BIOS should support SR-IOV.
 
-    VM networking:
+### General requirements
-    -  An external virtual switch to support outbound and inbound network communication (created during the installation process)
-1. **Content endpoints**: If you're using a proxy or firewall, certain endpoints must be allowed through in order for your MCC to cache and serve content. See [Delivery Optimization and Microsoft Connected Cache content type endpoints](delivery-optimization-endpoints.md) for the list of required endpoints. 
 
-## Sizing recommendations
+- Any previous installations of MCC must be [uninstalled](mcc-ent-uninstall-cache-node.md) before installing the latest version of MCC.
+- [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.
+
+### Additional requirements for Windows host machines
+
+- The Windows host machine must be using Windows 11 or Windows Server 2022 with the Latest Cumulative Update (LCU) applied.
+    - Windows 11 must have [OS Build 22631.3296](https://support.microsoft.com/topic/march-12-2024-kb5035853-os-builds-22621-3296-and-22631-3296-a69ac07f-e893-4d16-bbe1-554b7d9dd39b) or later
+    - Windows Server 2022 must have [OS Build 20348.2227](https://support.microsoft.com/topic/january-9-2024-kb5034129-os-build-20348-2227-6958a36f-efaf-4ef5-a576-c5931072a89a) or later
+- The Windows host machine must support nested virtualization.
+- The Windows host machine must have [WSL2 installed](/windows/wsl/install#install-wsl-command).
+
+### Additional requirements for Linux host machines
+
+- The Linux host machine must be using one of the following Operating Systems:
+
+    - Ubuntu 20.04
+    - 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
+
+- Multiple network interface cards (NICs) on a single MCC instance aren'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
 
 | Component  | Branch Office / Small Enterprise | Large Enterprise |
-| -- | --- | --- |
+| --- | --- | --- |
-| OS|  Windows Server 2019*/2022 <br> Windows 10*/11 (Pro or Enterprise) with Hyper-V Support <br><br>* Windows 10 and Windows Server 2019 build 17763 or later | Same |
+| OS|  Windows Server 2022 <br> Windows 11 (Pro or Enterprise) | Same |
 |NIC | 1 Gbps | 5 Gbps |
 |Disk | SSD <br>1 drive <br>50 GB each  |SSD <br>1 drive <br>200 GB each  |
 |Memory | 4 GB | 8 GB |

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

@@ -1,115 +1,26 @@
 ---
-title: MCC for Enterprise early preview
+title: MCCE Private Preview
-description: Microsoft Connected Cache for Enterprise early preview.
+description: Details on Microsoft Connected Cache for Enterprise (MCCE) Private Preview
 ms.service: windows-client
 ms.subservice: itpro-updates
-ms.topic: how-to
+ms.topic: conceptual
-manager: aaroncz
+manager: naengler
-ms.author: nidos
+ms.author: lichris
-author: doshnid
+author: chrisjlin
-ms.reviewer: mstewart
-ms.collection: tier3
 appliesto: 
-- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
-- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
 - ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise</a>	
 ms.date: 06/03/2024
 ---
 
-<!--
+# Microsoft Connected Cache for Enterprise and Education (MCCE) Private Preview
-Remove all the comments in this template before you sign-off or merge to the 
-main branch.
 
-This template provides the basic structure of a Overview article pattern. See the [instructions - Overview](../level4/article-overview.md) in the pattern library.
+If you participated in the MCCE early preview, thank you for your collaboration and feedback.
 
-You can provide feedback about this template at: https://aka.ms/patterns-feedback
+To continue using MCCE, 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 MCCE Azure service.
 
-Overview is an article pattern that covers two aspects of a product or service:
+As such, we strongly recommend you [recreate your existing cache nodes in Azure](mcc-ent-create-resource-and-cache.md) and then [redeploy the MCCE caching software to your host machines](mcc-ent-deploy-to-windows.md) using the latest OS-specific installer. You don't need to re-create your MCC Azure resource.
-
-* What is it?
-* What is it used for?
-
-An Overview article talks about the product or service from a technical point of view. It's not intended to define the benefits or value proposition. That just duplicates marketing.
-
-<!-- 1. H1 -----------------------------------------------------------------------------
-
-Required: This is the primary heading at the top of the article.
-
-Use the format "What is <service>?" 
-
-You can also use this in the TOC if your service name doesn’t cause the phrase to wrap.
-
--->
-
-# What is <product/service>? 
-TODO: Add your heading
-
-<!-- 2. Introductory paragraph ----------------------------------------------------------
-
-Required: Lead with a light intro that describes what the article covers. Answer the fundamental “why would I want to know this?” question. Keep it short.
-
-Many services add artwork or videos below the Introduction.
-
--->
-
-[Introductory paragraph]
-TODO: Add your introductory paragraph
-
-<!---Avoid notes, tips, and important boxes. Readers tend to skip over them. Better to put that info
-directly into the article text.
-
---->
-
-<!-- 3. H2s (Article body)------------------------------------------------------------ 
-
-Required: The article body should discuss the features that answer the "Why should I care?" question with a bit more depth.
-
-Give each H2 a heading that sets expectations for the content that follows. 
-Follow the H2 headings with a sentence about how the section contributes to the whole.
-Add images, code blocks, or other graphical elements after the information it illustrates.
-
-* Call out any basic requirements and dependencies.
-* Call out limitations or overhead.
-* Don't catalog every feature. Some might only need to be mentioned as available, without any discussion.
-* Give each H2 a heading that sets expectations for the content that follows.
-* Follow the H2 headings with a sentence about how the section contributes to the whole.
-* Images, code blocks, or other graphical elements come after the text block it illustrates.
-Don't number H2s.
-
--->
-
-## [Section 1 heading]
-TODO: add your content
-
-## [Section 2 heading]
-TODO: add your content
-
-## [Section n heading]
-TODO: add your content
-
-<!-- 4. Next step/Related content ------------------------------------------------------------------------ 
-
-Optional: You have two options for manually curated links in this pattern: Next step and Related content. You don't have to use either, but don't use both.
-  - For Next step, provide one link to the next step in a sequence. Use the blue box format
-  - For Related content provide 1-3 links. Include some context so the customer can determine why they would click the link. Add a context sentence for the following links.
-
--->
 
 ## Next step
 
-TODO: Add your next step link(s)
-
 > [!div class="nextstepaction"]
-> [Write concepts](article-concept.md)
+> [View documentation for MCCE Public Preview](mcc-ent-edu-overview.md)
-
-<!-- OR -->
-
-## Related content
-
-TODO: Add your next step link(s)
-
-- [Write concepts](article-concept.md)
-
-<!--
-Remove all the comments in this template before you sign-off or merge to the main branch.
--->

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

@@ -1,161 +1,40 @@
 ---
-title: MCC for Enterprise and Education Release Notes
+title: MCCE Release Notes
-description: Release Notes for Microsoft Connected Cache (MCC) for Enterprise and Education.
+description: Release Notes for Microsoft Connected Cache for Enterprise and Education (MCCE).
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: conceptual
-ms.author: nidos
+ms.author: lichris
-author: cmknox
+author: chrisjlin
-manager: aaroncz
+manager: naengler
-ms.reviewer: mstewart
-ms.collection: tier3
 appliesto: 
 - ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
-- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
+- ✅ Supported Linux distributions
 - ✅ <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/04/2024
+ms.date: 09/27/2024
 ---
 
-<!--
+# Release Notes for Microsoft Connected Cache for Enterprise and Education (MCCE)
-Remove all the comments in this template before you sign-off or merge to the  main branch.
 
-This template provides the basic structure of a Concept article pattern. See the [instructions - Concept](../level4/article-concept.md) in the pattern library.
+This article contains details about the latest releases of MCCE. Since MCCE is a Preview service, some releases may contain breaking changes that will be highlighted as such.
 
-You can provide feedback about this template at: https://aka.ms/patterns-feedback
+## Release v0.1.0 (Public Preview launch)
 
-Concept is an article pattern that defines what something is or explains an abstract idea.
+- Released on **10/17/2024**
+- Contains breaking changes
+- Contains service changes
+- Contains client changes
+- Affects Linux, Windows host machines
 
-There are several situations that might call for writing a Concept article, including:
+### Changenotes
 
-* If there's a new idea that's central to a service or product, that idea must be explained so that customers understand the value of the service or product as it relates to their circumstances. A good recent example is the concept of containerization or the concept of scalability.
+- Added new "Outbound egress" and "Volume by Content type" monitoring charts to Azure portal user interface
-* If there's optional information or explanations that are common to several Tutorials or How-to guides, this information can be consolidated and single-sourced in a full-bodied Concept article for you to reference.
+- Added ability to create custom monitoring charts under the Metrics tab in the Azure portal user interface
-* If a service or product is extensible, advanced users might modify it to better suit their application. It's better that advanced users fully understand the reasoning behind the design choices and everything else "under the hood" so that their variants are more robust, thereby improving their experience.
+- Added support for creating both Windows-hosted and Linux-hosted cache nodes under the same MCC Azure resource
-
+- Added Azure CLI support for programmatic creation and management of MCC 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 MCCE container updates
-<!-- 1. H1
------------------------------------------------------------------------------
-
-Required. Set expectations for what the content covers, so customers know the content meets their needs. The H1 should NOT begin with a verb.
-
-Reflect the concept that undergirds an action, not the action itself. The H1 must start with:
-
-* "\<noun phrase\> concept(s)", or
-* "What is \<noun\>?", or
-* "\<noun\> overview"
-
-Concept articles are primarily distinguished by what they aren't:
-
-* They aren't procedural articles. They don't show how to complete a task.
-* They don't have specific end states, other than conveying an underlying idea, and don't have concrete, sequential actions for the user to take.
-
-One clear sign of a procedural article would be the use of a numbered list. With rare exception, numbered lists shouldn't appear in Concept articles.
-
--->
-
-# [\<noun phrase\> concept(s)]
-TODO: Add your heading
-
-<!-- 2. Introductory paragraph
-----------------------------------------------------------
-
-Required. Lead with a light intro that describes what the article covers. Answer the fundamental “why would I want to know this?” question. Keep it short.
-
-* Answer the fundamental "Why do I want this knowledge?" question.
-* Don't start the article with a bunch of notes or caveats.
-* Don’t link away from the article in the introduction.
-* For definitive concepts, it's better to lead with a sentence in the form, "X is a (type of) Y that does Z."
-
--->
-
-[Introductory paragraph]
-TODO: Add your introductory paragraph
-
-<!-- 3. Prerequisites --------------------------------------------------------------------
-
-Optional: Make **Prerequisites** your first H2 in the article. Use clear and unambiguous
-language and use a unordered list format. 
-
--->
-
-## Prerequisites
-TODO: [List the prerequisites if appropriate]
-
-<!-- 4. H2s (Article body)
---------------------------------------------------------------------
-
-Required: In a series of H2 sections, the article body should discuss the ideas that explain how "X is a (type of) Y that does Z":
-
-* Give each H2 a heading that sets expectations for the content that follows.
-* Follow the H2 headings with a sentence about how the section contributes to the whole.
-* Describe the concept's critical features in the context of defining what it is.
-* Provide an example of how it's used where, how it fits into the context, or what it does. If it's complex and new to the user, show at least two examples.
-* Provide a non-example if contrasting it will make it clearer to the user what the concept is.
-* Images, code blocks, or other graphical elements come after the text block it illustrates.
-* Don't number H2s.
-
--->
-
-## [Section 1 heading]
-TODO: add your content
-
-## [Section 2 heading]
-TODO: add your content
-
-## [Section n heading]
-TODO: add your content
-
-<!-- 5. Next step/Related content ------------------------------------------------------------------------ 
-
-Optional: You have two options for manually curated links in this pattern: Next step and Related content. You don't have to use either, but don't use both.
-  - For Next step, provide one link to the next step in a sequence. Use the blue box format
-  - For Related content provide 1-3 links. Include some context so the customer can determine why they would click the link. Add a context sentence for the following links.
-
--->
-
-## Next step
-
-TODO: Add your next step link(s)
-
-> [!div class="nextstepaction"]
-> [Write concepts](article-concept.md)
-
-<!-- OR -->
 
 ## Related content
 
-TODO: Add your next step link(s)
+- [Overview of MCCE](mcc-ent-edu-overview.md)
-
-- [Write concepts](article-concept.md)
-
-<!--
-Remove all the comments in this template before you sign-off or merge to the main branch.
--->
-
-
-<!-- 6. Next step/Related content ------------------------------------------------------------------------
-
-Optional: You have two options for manually curated links in this pattern: Next step and Related
-content. You don't have to use either, but don't use both. For Next step, provide one link to the
-next step in a sequence. Use the blue box format For Related content provide 1-3 links. Include some
-context so the customer can determine why they would click the link. Add a context sentence for the
-following links.
-
--->
-
-## Next step
-TODO: Add your next step link(s)
-> [!div class="nextstepaction"]
-> [Write concepts](article-concept.md)
-
-<!-- OR -->
-
-## Related content
-TODO: Add your next step link(s)
-- [Write concepts](article-concept.md)
-
-<!--
-Remove all the comments in this template before you sign-off or merge to the 
-main branch.
-
--->

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

@@ -1,19 +1,17 @@
 ---
-title: MCC for Enterprise support and troubleshooting
+title: MCCE support and troubleshooting
-description: Microsoft Connected Cache for Enterprise. Learn about support and troubleshooting
+description: Details on how to troubleshoot and seek support for Microsoft Connected Cache for Enterprise (MCCE).
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: how-to
-manager: aaroncz
+manager: naengler
-ms.author: nidos
+ms.author: lichris
-author: doshnid
+author: chrisjlin
-ms.reviewer: mstewart
-ms.collection: tier3
 appliesto: 
 - ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
-- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
+- ✅ Supported Linux distributions
 - ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise</a>	
-ms.date: 06/03/2024
+ms.date: 09/27/2024
 ---
 
 <!--
@@ -40,8 +38,7 @@ For example: "Migrate data from regular tables to ledger tables" or "Create a ne
 
 -->
 
-# "<verb> * <noun>"
+# Troubleshoot Microsoft Connected Cache for Enterprise and Education (MCCE)
-TODO: Add your heading
 
 <!-- 2. Introductory paragraph ----------------------------------------------------------
 
@@ -57,65 +54,35 @@ Example: In this article, you will migrate your user databases from IBM Db2 to S
 
 -->
 
-TODO: Add your introductory paragraph
+This article contains instructions on how to troubleshoot different issues you may encounter while using MCCE. 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).
 
-<!---Avoid notes, tips, and important boxes. Readers tend to skip over them. Better to put that info directly into the article text.
+## 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.
 
-<!-- 3. Prerequisites --------------------------------------------------------------------
+## Troubleshooting cache node creation
-
-Required: Make Prerequisites the first H2 after the H1. 
-
-* Provide a bulleted list of items that the user needs.
-* Omit any preliminary text to the list.
-* If there aren't any prerequisites, list "None" in plain text, not as a bulleted item.
-
--->
-
-## Prerequisites
-
-TODO: List the prerequisites
-
-<!-- 4. Task H2s ------------------------------------------------------------------------------
-
-Required: Multiple procedures should be organized in H2 level sections. A section contains a major grouping of steps that help users complete a task. Each section is represented as an H2 in the article.
-
-For portal-based procedures, minimize bullets and numbering.
-
-* Each H2 should be a major step in the task.
-* Phrase each H2 title as "<verb> * <noun>" to describe what they'll do in the step.
-* Don't start with a gerund.
-* Don't number the H2s.
-* Begin each H2 with a brief explanation for context.
-* Provide a ordered list of procedural steps.
-* Provide a code block, diagram, or screenshot if appropriate
-* An image, code block, or other graphical element comes after numbered step it illustrates.
-* If necessary, optional groups of steps can be added into a section.
-* If necessary, alternative groups of steps can be added into a section.
-
--->
-
-## "\<verb\> * \<noun\>"
 TODO: Add introduction sentence(s)
 [Include a sentence or two to explain only what is needed to complete the procedure.]
 TODO: Add ordered list of procedure steps
+
 1. Step 1
 1. Step 2
 1. Step 3
 
-## "\<verb\> * \<noun\>"
+## Troubleshooting cache node deployment
 TODO: Add introduction sentence(s)
 [Include a sentence or two to explain only what is needed to complete the procedure.]
 TODO: Add ordered list of procedure steps
+
 1. Step 1
 1. Step 2
 1. Step 3
 
-## "\<verb\> * \<noun\>"
+## Troubleshooting cache node monitoring
 TODO: Add introduction sentence(s)
 [Include a sentence or two to explain only what is needed to complete the procedure.]
 TODO: Add ordered list of procedure steps
+
 1. Step 1
 1. Step 2
 1. Step 3
@@ -128,22 +95,6 @@ Optional: You have two options for manually curated links in this pattern: Next
 
 -->
 
-## Next step
+## Filing a support request
-
-TODO: Add your next step link(s)
-
-> [!div class="nextstepaction"]
-> [Write concepts](article-concept.md)
-
-<!-- OR -->
-
-## Related content
-
-TODO: Add your next step link(s)
-
-- [Write concepts](article-concept.md)
-
-<!--
-Remove all the comments in this template before you sign-off or merge to the main branch.
--->
 
+TODO: Add steps for filling out a CSS ticket.

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

@@ -1,149 +1,35 @@
 ---
-title: MCC for Enterprise uninstall
+title: Uninstall MCCE cache nodes
-description: Microsoft Connected Cache for Enterprise. Learn about uninstall
+description: Details on how to uninstall Microsoft Connected Cache for Enterprise and Education (MCCE) from a host machine.
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: how-to
-manager: aaroncz
+ms.author: lichris
-ms.author: nidos
+author: chrisjlin
-author: doshnid
+manager: naengler
-ms.reviewer: mstewart
-ms.collection: tier3
 appliesto: 
 - ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
-- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
+- ✅ Supported Linux distributions
-- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise</a>	
+- ✅ <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: 06/03/2024
+ms.date: 09/27/2024
 ---
 
-<!--
+# Uninstall MCCE caching software from a host machine
-Remove all the comments in this template before you sign-off or merge to the main branch.
 
-This template provides the basic structure of a How-to article pattern. See the
+This article describes how to uninstall Microsoft Connected Cache for Enterprise and Education (MCCE) caching software from a host machine. These steps should be taken after deleting the cache node in the Azure portal.
-[instructions - How-to](../level4/article-how-to-guide.md) in the pattern library.
 
-You can provide feedback about this template at: https://aka.ms/patterns-feedback
+## Steps to uninstall MCCE from a Windows host machine
 
-How-to is a procedure-based article pattern that show the user how to complete a task in their own environment. A task is a work activity that has a definite beginning and ending, is observable, consist of two or more definite steps, and leads to a product, service, or decision.
+1. Launch a PowerShell window *as administrator* and navigate to the MCC installation directory (C:\mcconwsl01 by default)
+1. Run the `uninstallmcconwsl.ps1` script
 
--->
+## Steps to uninstall MCCE from a Linux host machine
 
-<!-- 1. H1 -----------------------------------------------------------------------------
+The `uninstallmcc.sh` script within the provisioning package uninstalls the MCCE caching software and all related components, including:
-
-Required: Use a "<verb> * <noun>" format for your H1. Pick an H1 that clearly conveys the task the user will complete.
-
-For example: "Migrate data from regular tables to ledger tables" or "Create a new Azure SQL Database".
-
-* Include only a single H1 in the article.
-* Don't start with a gerund.
-* Don't include "Tutorial" in the H1.
-
--->
-
-# "<verb> * <noun>"
-TODO: Add your heading
-
-<!-- 2. Introductory paragraph ----------------------------------------------------------
-
-Required: Lead with a light intro that describes, in customer-friendly language, what the customer will do. Answer the fundamental “why would I want to do this?” question. Keep it short.
-
-Readers should have a clear idea of what they will do in this article after reading the introduction.
-
-* Introduction immediately follows the H1 text.
-* Introduction section should be between 1-3 paragraphs.
-* Don't use a bulleted list of article H2 sections.
-
-Example: In this article, you will migrate your user databases from IBM Db2 to SQL Server by using SQL Server Migration Assistant (SSMA) for Db2.
-
--->
-
-TODO: Add your introductory paragraph
-
-<!---Avoid notes, tips, and important boxes. Readers tend to skip over them. Better to put that info directly into the article text.
-
--->
-
-<!-- 3. Prerequisites --------------------------------------------------------------------
-
-Required: Make Prerequisites the first H2 after the H1. 
-
-* Provide a bulleted list of items that the user needs.
-* Omit any preliminary text to the list.
-* If there aren't any prerequisites, list "None" in plain text, not as a bulleted item.
-
--->
-
-## Prerequisites
-
-TODO: List the prerequisites
-
-<!-- 4. Task H2s ------------------------------------------------------------------------------
-
-Required: Multiple procedures should be organized in H2 level sections. A section contains a major grouping of steps that help users complete a task. Each section is represented as an H2 in the article.
-
-For portal-based procedures, minimize bullets and numbering.
-
-* Each H2 should be a major step in the task.
-* Phrase each H2 title as "<verb> * <noun>" to describe what they'll do in the step.
-* Don't start with a gerund.
-* Don't number the H2s.
-* Begin each H2 with a brief explanation for context.
-* Provide a ordered list of procedural steps.
-* Provide a code block, diagram, or screenshot if appropriate
-* An image, code block, or other graphical element comes after numbered step it illustrates.
-* If necessary, optional groups of steps can be added into a section.
-* If necessary, alternative groups of steps can be added into a section.
-
--->
-
-## "\<verb\> * \<noun\>"
-TODO: Add introduction sentence(s)
-[Include a sentence or two to explain only what is needed to complete the procedure.]
-TODO: Add ordered list of procedure steps
-1. Step 1
-1. Step 2
-1. Step 3
-
-## "\<verb\> * \<noun\>"
-TODO: Add introduction sentence(s)
-[Include a sentence or two to explain only what is needed to complete the procedure.]
-TODO: Add ordered list of procedure steps
-1. Step 1
-1. Step 2
-1. Step 3
-
-## "\<verb\> * \<noun\>"
-TODO: Add introduction sentence(s)
-[Include a sentence or two to explain only what is needed to complete the procedure.]
-TODO: Add ordered list of procedure steps
-1. Step 1
-1. Step 2
-1. Step 3
-
-<!-- 5. Next step/Related content------------------------------------------------------------------------
-
-Optional: You have two options for manually curated links in this pattern: Next step and Related content. You don't have to use either, but don't use both.
-  - For Next step, provide one link to the next step in a sequence. Use the blue box format
-  - For Related content provide 1-3 links. Include some context so the customer can determine why they would click the link. Add a context sentence for the following links.
-
--->
-
-## Next step
-
-TODO: Add your next step link(s)
-
-> [!div class="nextstepaction"]
-> [Write concepts](article-concept.md)
-
-<!-- OR -->
-
-## Related content
-
-TODO: Add your next step link(s)
-
-- [Write concepts](article-concept.md)
-
-<!--
-Remove all the comments in this template before you sign-off or merge to the main branch.
--->
 
+- IoT Edge
+- IoT Edge Agent
+- IoT Edge Hub
+- MCC
+- Moby CLI
+- Moby engine

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

@@ -0,0 +1,55 @@
+---
+title: Update MCCE cache nodes
+description: Details on how Microsoft Connected Cache for Enterprise and Education (MCCE) cache nodes are updated by Microsoft.
+ms.service: windows-client
+ms.subservice: itpro-updates
+ms.topic: how-to
+ms.author: andyriv
+author: chrisjlin
+manager: naengler
+appliesto: 
+- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
+- ✅ Supported Linux distributions
+- ✅ <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 (MCCE)
+
+Microsoft Connected Cache for Enterprise and Education (MCCE) caching software is deployed to host machines as a container. The container OS and any software component within the container will need to be updated for security vulnerabilities or quality issues, or performance improvements required to successfully operate the caching software. These Microsoft-published container updates are called "MCCE updates" in this article.
+
+Microsoft silently deploys MCCE updates to your cache nodes based on the Update Ring setting you configure for each cache node.
+
+## Update rings
+
+MCCE 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 MCCE 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 MCCE 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
+
+#### Fast Ring
+All MCCE cache nodes are configured to update as part of the Fast ring by default. MCCE 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 MCCE cache node to update as part of the Slow ring provides users with the option to delay MCCE software updates until the update can be validated. There are three settings that control when MCCE updates will be applied to MCCE cache nodes. All update ring settings can be managed from the Azure portal or through Azure CLI.
+
+| Setting | Description |
+| --- | --- |
+| Week of the month | 1st to 4th week can be selected. There are three to four months in a year that could have a 5th week. If there's a 5th week, the update could be applied during that 5th week if the day of the week falls near the last day of the month.|
+| Day of the week | Monday through Sunday can be selected. |
+| Time of day | Time of day is based on UTC and a 24 hour clock. |
+
+## Update process
+
+When Microsoft publishes an MCCE update, the MCCE service attempts to update all MCCE cache nodes based on their Update Ring membership. If a cache node can't complete the silent MCCE update within 6 hours of starting, an error message is surfaced in the Azure portal.
+
+## Update terminology, criteria, and SLA
+
+MCCE 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 will be 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 [MCCE release notes](mcc-ent-release-notes.md).

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

@@ -1,149 +1,46 @@
 ---
-title: MCC for Enterprise verify cache node
+title: Verify MCCE cache node functionality
-description: Microsoft Connected Cache for Enterprise. Learn about verifying cache node
+description: Details on how to verify functionality of Microsoft Connected Cache for Enterprise and Education (MCCE) cache nodes.
+author: chrisjlin
+ms.author: lichris
+manager: naengler
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: how-to
-manager: aaroncz
+ms.date: 09/27/2024
-ms.author: nidos
-author: doshnid
-ms.reviewer: mstewart
-ms.collection: tier3
 appliesto: 
-- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
+- ✅ Windows-hosted MCCE cache nodes
-- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
+- ✅ Linux-hosted MCCE cache nodes
-- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise</a>	
+- ✅ <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: 06/03/2024
 ---
 
-<!--
+# Verify MCCE cache node functionality
-Remove all the comments in this template before you sign-off or merge to the main branch.
 
-This template provides the basic structure of a How-to article pattern. See the
+This article describes how to verify that a Microsoft Connected Cache for Enterprise and Education (MCCE) cache node is functioning correctly.
-[instructions - How-to](../level4/article-how-to-guide.md) in the pattern library.
 
-You can provide feedback about this template at: https://aka.ms/patterns-feedback
+These steps should be taken after deploying MCCE caching software to a [Windows](mcc-ent-deploy-to-windows.md) or [Linux](mcc-ent-deploy-to-linux.md) host machine.
 
-How-to is a procedure-based article pattern that show the user how to complete a task in their own environment. A task is a work activity that has a definite beginning and ending, is observable, consist of two or more definite steps, and leads to a product, service, or decision.
+## Steps to verify functionality of MCCE cache node
 
--->
+1. To verify that the MCCE container on the host machine is running and reachable, run the following command from the host machine:
 
-<!-- 1. H1 -----------------------------------------------------------------------------
+    ```powershell
+    wget http://localhost/filestreamingservice/files/7bc846e0-af9c-49be-a03d-bb04428c9bb5/Microsoft.png?cacheHostOrigin=dl.delivery.mp.microsoft.com
+    ```
 
-Required: Use a "<verb> * <noun>" format for your H1. Pick an H1 that clearly conveys the task the user will complete.
+    If successful, there should be an HTTP response with StatusCode 200.
 
-For example: "Migrate data from regular tables to ledger tables" or "Create a new Azure SQL Database".
+1. To verify that Windows clients in your network can reach the MCCE cache node, visit the following address from a web browser on a Windows client device:
 
-* Include only a single H1 in the article.
+    `http://[HostMachine-IP-address]/filestreamingservice/files/7bc846e0-af9c-49be-a03d-bb04428c9bb5/Microsoft.png?cacheHostOrigin=dl.delivery.mp.microsoft.com`
-* Don't start with a gerund.
-* Don't include "Tutorial" in the H1.
 
--->
+    If successful, the Windows client device should begin to download a small image file from the MCCE cache node.
 
-# "<verb> * <noun>"
+1. To check how much content an individual Windows client has pulled from an MCCE 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.
-TODO: Add your heading
 
-<!-- 2. Introductory paragraph ----------------------------------------------------------
+    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".
-
-Required: Lead with a light intro that describes, in customer-friendly language, what the customer will do. Answer the fundamental “why would I want to do this?” question. Keep it short.
-
-Readers should have a clear idea of what they will do in this article after reading the introduction.
-
-* Introduction immediately follows the H1 text.
-* Introduction section should be between 1-3 paragraphs.
-* Don't use a bulleted list of article H2 sections.
-
-Example: In this article, you will migrate your user databases from IBM Db2 to SQL Server by using SQL Server Migration Assistant (SSMA) for Db2.
-
--->
-
-TODO: Add your introductory paragraph
-
-<!---Avoid notes, tips, and important boxes. Readers tend to skip over them. Better to put that info directly into the article text.
-
--->
-
-<!-- 3. Prerequisites --------------------------------------------------------------------
-
-Required: Make Prerequisites the first H2 after the H1. 
-
-* Provide a bulleted list of items that the user needs.
-* Omit any preliminary text to the list.
-* If there aren't any prerequisites, list "None" in plain text, not as a bulleted item.
-
--->
-
-## Prerequisites
-
-TODO: List the prerequisites
-
-<!-- 4. Task H2s ------------------------------------------------------------------------------
-
-Required: Multiple procedures should be organized in H2 level sections. A section contains a major grouping of steps that help users complete a task. Each section is represented as an H2 in the article.
-
-For portal-based procedures, minimize bullets and numbering.
-
-* Each H2 should be a major step in the task.
-* Phrase each H2 title as "<verb> * <noun>" to describe what they'll do in the step.
-* Don't start with a gerund.
-* Don't number the H2s.
-* Begin each H2 with a brief explanation for context.
-* Provide a ordered list of procedural steps.
-* Provide a code block, diagram, or screenshot if appropriate
-* An image, code block, or other graphical element comes after numbered step it illustrates.
-* If necessary, optional groups of steps can be added into a section.
-* If necessary, alternative groups of steps can be added into a section.
-
--->
-
-## "\<verb\> * \<noun\>"
-TODO: Add introduction sentence(s)
-[Include a sentence or two to explain only what is needed to complete the procedure.]
-TODO: Add ordered list of procedure steps
-1. Step 1
-1. Step 2
-1. Step 3
-
-## "\<verb\> * \<noun\>"
-TODO: Add introduction sentence(s)
-[Include a sentence or two to explain only what is needed to complete the procedure.]
-TODO: Add ordered list of procedure steps
-1. Step 1
-1. Step 2
-1. Step 3
-
-## "\<verb\> * \<noun\>"
-TODO: Add introduction sentence(s)
-[Include a sentence or two to explain only what is needed to complete the procedure.]
-TODO: Add ordered list of procedure steps
-1. Step 1
-1. Step 2
-1. Step 3
-
-<!-- 5. Next step/Related content------------------------------------------------------------------------
-
-Optional: You have two options for manually curated links in this pattern: Next step and Related content. You don't have to use either, but don't use both.
-  - For Next step, provide one link to the next step in a sequence. Use the blue box format
-  - For Related content provide 1-3 links. Include some context so the customer can determine why they would click the link. Add a context sentence for the following links.
-
--->
-
-## Next step
-
-TODO: Add your next step link(s)
-
-> [!div class="nextstepaction"]
-> [Write concepts](article-concept.md)
-
-<!-- OR -->
 
 ## Related content
 
-TODO: Add your next step link(s)
+- [Monitor cache node usage](mcc-ent-monitoring.md)
-
+- [Troubleshoot cache node](mcc-ent-support-and-troubleshooting.md)
-- [Write concepts](article-concept.md)
-
-<!--
-Remove all the comments in this template before you sign-off or merge to the main branch.
--->
-