diff --git a/windows/deployment/do/mcc-enterprise-appendix.md b/windows/deployment/do/mcc-enterprise-appendix.md
index 0da8b56b15..87e7346429 100644
--- a/windows/deployment/do/mcc-enterprise-appendix.md
+++ b/windows/deployment/do/mcc-enterprise-appendix.md
@@ -5,7 +5,7 @@ description: Appendix on Microsoft Connected Cache (MCC) for Enterprise and Educ
ms.prod: w10
author: amymzhou
ms.localizationpriority: medium
-ms.author: amymzhou
+ms.author: amyzhou
ms.collection: M365-modern-desktop
ms.topic: article
---
diff --git a/windows/deployment/do/mcc-enterprise-overview.md b/windows/deployment/do/mcc-enterprise-overview.md
index a1d3102da1..8493fd2586 100644
--- a/windows/deployment/do/mcc-enterprise-overview.md
+++ b/windows/deployment/do/mcc-enterprise-overview.md
@@ -5,7 +5,7 @@ description: Overview and requirements of Microsoft Connected Cache (MCC) for En
ms.prod: w10
author: amymzhou
ms.localizationpriority: medium
-ms.author: amymzhou
+ms.author: amyzhou
ms.collection: M365-modern-desktop
ms.topic: article
---
diff --git a/windows/deployment/do/mcc-enterprise-update-uninstall.md b/windows/deployment/do/mcc-enterprise-update-uninstall.md
index 8fcaea70c5..69762a115d 100644
--- a/windows/deployment/do/mcc-enterprise-update-uninstall.md
+++ b/windows/deployment/do/mcc-enterprise-update-uninstall.md
@@ -5,7 +5,7 @@ description: Details on updating or uninstalling Microsoft Connected Cache (MCC)
ms.prod: w10
author: amymzhou
ms.localizationpriority: medium
-ms.author: amymzhou
+ms.author: amyzhou
ms.collection: M365-modern-desktop
ms.topic: article
---
@@ -14,7 +14,7 @@ ms.topic: article
## Update MCC
-Throughout the private preview phase, we will send you security and feature updates for MCC. Please follow these steps to perform the update.
+Throughout the preview phase, we'll send you security and feature updates for MCC. Follow these steps to perform the update.
Run the following command with the **arguments** we provided in the email to update your MCC:
@@ -34,12 +34,12 @@ issues.
This script will remove the following:
1. EFLOW + Linux VM
-2. IoT Edge
-3. Edge Agent
-4. Edge Hub
-5. MCC
-6. Moby CLI
-7. Moby Engine
+1. IoT Edge
+1. Edge Agent
+1. Edge Hub
+1. MCC
+1. Moby CLI
+1. Moby Engine
To delete MCC, go to Control Panel \> Uninstall a program \> Select Azure IoT
Edge LTS \> Uninstall
\ No newline at end of file
diff --git a/windows/deployment/do/mcc-isp-monitor.md b/windows/deployment/do/mcc-isp-monitor.md
index e1b2b8c121..b44178b622 100644
--- a/windows/deployment/do/mcc-isp-monitor.md
+++ b/windows/deployment/do/mcc-isp-monitor.md
@@ -36,9 +36,9 @@ To learn more about how to build your custom charts and graphs, visit [Azure Mon
### Monitoring your metrics
-To view the metrics associated with your cache nodes, navigate to the Overview >> Monitoring tab within Azure portal.
+To view the metrics associated with your cache nodes, navigate to the **Overview** > **Monitoring** tab within Azure portal.
-:::image type="content" source="images/mcc-isp-metrics.png" alt-text="Screenshot of the Azure portal displaying the metrics view in the Overview tab":::
+:::image type="content" source="./images/mcc-img-metrics.png" alt-text="Screenshot of the Azure portal displaying the metrics view in the Overview tab":::
You can choose to monitor the health and performance of all cache nodes or one at a time by using the dropdown menu. The Egress bits per second graph shows your inbound and outbound traffic of your cache nodes over time. You can change the time range (1 hour, 12 hours, 1 day, 7 days, 14 days, and 30 days) by selecting the time range of choice on the top bar.
diff --git a/windows/deployment/do/mcc-isp-provision-deploy.md b/windows/deployment/do/mcc-isp-provision-deploy.md
index 31d181efc1..4df4cf6e4b 100644
--- a/windows/deployment/do/mcc-isp-provision-deploy.md
+++ b/windows/deployment/do/mcc-isp-provision-deploy.md
@@ -18,83 +18,53 @@ ms.topic: article
**Applies to**
-- Windows 10
+- Windows 10
- Windows 11
-
-
-
> [!IMPORTANT]
-> Before you can create your Microsoft Connected Cache, you will need to complete the sign up process [here](windows\deployment\do\mcc-isp-signup.md).
+> Before you can create your Microsoft Connected Cache, you will need to complete the [sign up process](mcc-isp-signup.md).
-
-
+# Create a cache node
+1. Navigating to **Cache nodes** under **Settings**.
+1. Select **Create Cache Node**.
+1. Provide a name for your cache node
+1. Select **Create** to create your cache node.
+## Provision your cache node
-Create your cache node by navigating to 'Cache nodes' under Settings and click 'Create Cache Node'. Provide a name for your cache node and click 'Create' to create your cache node.
+1. Select the cache node you want to provision and deploy.
-
+ :::image type="content" source="./images/numberedprovmcc.png" alt-text="Screenshot of the Settings tab in the Cache nodes page.":::
-
+1. Enter the max allowable egress that your hardware can support.
-### Provision your cache node:
-
+1. Under Cache storage, specify the location of the cache drives to store content along with the size of the cache drives in Gigabytes.
+ > [!NOTE]
+ > You can add up to nine cache drives.
-1. Click on the cache node you want to provision and deploy.
-
+1. Under Routing information, select the routing source you would like to use. For more information, see [client routing](mcc-isp-client-routing.md).
-
-:::image type="content" source="images/numberedprovmcc.png" alt-text="numberedprovmcc":::
+ - If you choose **Manual** routing, enter Address range/CIDR blocks and the number of IP space.
+ - If you choose **BGP** routing, enter the ASN and IP addresses of the neighborship.
+ > [!Note]
+ > **Prefix count** and **IP Space** will stop showing 0 when BGP is successfully established.
-
-
-2. Enter the max allowable egress that your hardware can support.
-
-
-
-3. Under Cache storage, specify the location of the cache drives to store content along with the size of the cache drives in Gigabytes.
-Note: You can add upto nine cache drives.
-
-
-
-4. Under Routing information, select the routing source you would like to use. For more information see client routing [here](windows\deployment\do\mcc-isp-client-routing.md).
-
-
-- If you choose Manual routing, enter Address range/CIDR blocks and the number of IP space.
-
-- If you choose BGP routing, enter the ASN and IP addresses of the neighborship.
-Note: 'Prefix count' and 'IP Space' will stop showing 0 when BGP is successfuly established.
-
-
-
-
-### Deploy your cache node:
+## Deploy your cache node
-:::image type="content" source="images/numbereddeploymcc.png" alt-text="numbereddeploymcc":::
+:::image type="content" source="./images/numbereddeploymcc.png" alt-text="Screenshot of the Azure portal showing the Server provisioning tab.":::
-
-5. Under Server provisioning, download the provisioning package to your server.
+1. Under **Server provisioning**, download the provisioning package to your server.
Open a terminal window and run the following command to change the access permission to the Bash script.
-
```bash
sudo chmod +x installmcc.sh
```
-
-
-6. Run the provisioning script that is shown for your cache node.
+1. Run the provisioning script that is shown in the Azure portal for your cache node.
-
-
+1. If there were no errors, you've set up your cache node. To verify the server is set up correctly, follow the [verification steps](mcc-isp-verify-cache-node.md).
-<<<<<<< HEAD
-If there were no errors, you have set up your cache node. To verify the server is set up correctly, follow the steps verification steps [here](windows\deployment\do\mcc-isp-verify-cache-node.md).
-=======
-8. If there were no errors, you have set up your cache node. To verify the server is set up correctly, follow the steps verification steps [here](windows\deployment\do\mcc-isp-verify-cache-node.md).
-
->>>>>>> c023d7d15cf06494a2799bdfb23d7674fa5fbb05
diff --git a/windows/deployment/do/mcc-isp-signup.md b/windows/deployment/do/mcc-isp-signup.md
index c92fad64da..5e2906b282 100644
--- a/windows/deployment/do/mcc-isp-signup.md
+++ b/windows/deployment/do/mcc-isp-signup.md
@@ -17,43 +17,44 @@ ms.topic: article
**Applies to**
-- Windows 10
+- Windows 10
- Windows 11
This article details the process of signing up for Microsoft Connected Cache for Internet Service Providers (Public Preview).
## Resource creation and sign up process
-1. Navigate to your [Azure portal](https://www.portal.azure.com). In the top search bar, search for **Microsoft Connected Cache**.
+1. Navigate to the [Azure portal](https://www.portal.azure.com). In the top search bar, search for **Microsoft Connected Cache**.
-:::image type="content" source="images/searchmcc.png" alt-text="Screenshot of the Azure portal which shows the Microsoft Connected Cache resource in Azure marketplace.":::
+:::image type="content" source="./images/searchmcc.png" alt-text="Screenshot of the Azure portal that shows the Microsoft Connected Cache resource in Azure marketplace.":::
1. Select **Create** to create a **Microsoft Connected Cache**. When prompted, enter a name for your cache resource.
-> [!IMPORTANT]
-> After your resource has been created, we need some information to verify your network operator status and approve you to host Microsoft Connected Cache nodes. Please ensure that your [Peering DB](https://www.peeringdb.com/) organization information is up to date as this information will be used for verification. The NOC contact email will be used to send verification information.
+ > [!IMPORTANT]
+ > After your resource has been created, we need some information to verify your network operator status and approve you to host Microsoft Connected Cache nodes. Please ensure that your [Peering DB](https://www.peeringdb.com/) organization information is up to date as this information will be used for verification. The NOC contact email will be used to send verification information.
-1. Navigate to **Settings** > **Sign up**. Enter your organization ASN. Indicate whether you are a transit provider. If so, additionally, please include any ASN(s) for downstream network operators that you may transit traffic for.
+1. Navigate to **Settings** > **Sign up**. Enter your organization ASN. Indicate whether you're a transit provider. If so, additionally, include any ASN(s) for downstream network operators that you may transit traffic for.
-:::image type="content" source="images/signup1.png" alt-text="Screenshot of the sign up page in the Microsoft Connected Cache resource page in Azure portal.":::
+ :::image type="content" source="./images/signup1.png" alt-text="Screenshot of the sign up page in the Microsoft Connected Cache resource page in Azure portal.":::
1. Once we verify the information entered, a verification code will be sent to the NOC email address provided on [Peering DB](https://www.peeringdb.com/). Once you receive the email, navigate to your Azure portal > **Microsoft Connected Cache** > **Settings** > **Verify operator**, and enter the verification code sent to the NOC email address.
-**Note:** Verification codes expire in 24 hours. You will need to generate a new code if it expires.
+ > [!NOTE]
+ > Verification codes expire in 24 hours. You will need to generate a new code if it expires.
-:::image type="content" source="images/verification.png" alt-text="Screenshot of the signup verification page on Azure portal for Microsoft Connected Cache.":::
+ :::image type="content" source="images/verification.png" alt-text="Screenshot of the sign up verification page on Azure portal for Microsoft Connected Cache.":::
-Once verified, follow the instructions on [Create, provision, and deploy cache node](windows\deployment\do\mcc-isp-create-provision-deploy.md) to create your cache node.
+1. Once verified, follow the instructions in [Create, provision, and deploy cache node](mcc-isp-create-provision-deploy.md) to create your cache node.
## Traffic estimation
-During the sign-up process, Microsoft will provide you with a traffic estimation based on your ASN(s). We make estimations based on our predictions on historical data about Microsoft content download volume. We'll use these estimations to recommend hardware or VM configurations. You can view these recommendations within the Azure portal.
+During the sign-up process, Microsoft will provide you with a traffic estimation based on your ASN(s). We make estimations based on our predictions on historical data about Microsoft content download volume. We'll use these estimations to recommend hardware or VM configurations. You can review these recommendations within the Azure portal.
We make these estimations based on the Microsoft content types that Microsoft Connected Cache serves. To learn more about the types of content that are supported, see [Delivery Optimization and Microsoft Connected Cache content type endpoints](delivery-optimization-endpoints.md).
### Cache performance
-To make sure you're maximizing the performance of your cache node, note the following:
+To make sure you're maximizing the performance of your cache node, review the following information:
#### OS requirements
@@ -61,7 +62,7 @@ The Microsoft Connected Cache module is optimized for Ubuntu 20.04 LTS. Install
#### NIC requirements
-- Multiple NICs on a single MCC instance are supported using a _link aggregated_ configuration.
+- Multiple NICs on a single MCC instance are supported using a *link aggregated* configuration.
- 10 Gbps NIC is the minimum speed recommended, but any NIC is supported.
#### Drive performance
@@ -76,7 +77,7 @@ There are many hardware configurations that suit Microsoft Connected Cache. As a
**Dell PowerEdge R330**
-- 2 x Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40 GHz , total 32 core
+- 2 x Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40 GHz, total 32 core
- 48 GB, Micron Technology 18ASF1G72PDZ-2G1A1, Speed: 2133 MT/s
- 4 - Transcend SSD230s 1 TB SATA Drives
- Intel Corporation Ethernet 10G 2P X520 Adapter (Link Aggregated)
diff --git a/windows/deployment/do/mcc-isp-support.md b/windows/deployment/do/mcc-isp-support.md
index 6c99f12c9c..eca0816a9e 100644
--- a/windows/deployment/do/mcc-isp-support.md
+++ b/windows/deployment/do/mcc-isp-support.md
@@ -17,30 +17,30 @@ ms.topic: article
**Applies to**
-- Windows 10
+- Windows 10
- Windows 11
## Sign up errors
-#### Cannot verify account
+### Cannot verify account
During sign-up, we verify the information you provide against what is present in [Peering DB](https://www.peeringdb.com/). Make sure the information for your ISP entry on [Peering DB](https://www.peeringdb.com/) is up to date and matches what you provide during sign-up.
-#### Invalid verification code
+### Invalid verification code
-During sign-up, a verification code is sent to your NOC email address present in [Peering DB](https://www.peeringdb.com/). This code expires in 24 hours. If expired, you'll need to request a new verification code to complete sign up.
+During sign-up, a verification code is sent to your NOC email address present in [Peering DB](https://www.peeringdb.com/). This code expires in 24 hours. If expired, you'll need to request a new verification code to complete the sign-up.
## Cache Node Errors
-#### Cannot find my cache node
-
+### Cannot find my cache node
+
Did you previously had access to your cache nodes but it's now no longer accessible? If so, it may be because you had a trial subscription, and its trial period ended. To resolve this issue, complete the following two steps:
1. Create a new Azure Pay-As-You-Go subscription
1. Recreate the cache nodes using the new subscription
-#### Recommended Documents
+### Recommended Documents
[Steps to obtain Azure subscription](https://aka.ms/MCC-Azure-Subscription)
-[Pay-as-you-go-subscription](https://azure.microsoft.com/en-us/offers/ms-azr-0003p/)
-[Azure free account FAQs](https://azure.microsoft.com/en-us/free/free-account-faq/)
\ No newline at end of file
+[Pay-as-you-go-subscription](https://azure.microsoft.com/offers/ms-azr-0003p/)
+[Azure free account FAQs](https://azure.microsoft.com/free/free-account-faq/)
diff --git a/windows/deployment/do/mcc-isp-uninstall.md b/windows/deployment/do/mcc-isp-uninstall.md
index 889ea153e3..f34b3a6365 100644
--- a/windows/deployment/do/mcc-isp-uninstall.md
+++ b/windows/deployment/do/mcc-isp-uninstall.md
@@ -17,9 +17,8 @@ ms.topic: article
There are two main steps required to uninstall your cache node:
-
-1. Remove your cache node from Azure portal
-1. Run the uninstall script to cleanly remove MCC from your server
+1. Remove your cache node from Azure portal.
+1. Run the uninstall script to cleanly remove MCC from your server.
## Remove your cache node from Azure portal
@@ -27,6 +26,7 @@ There are two main steps required to uninstall your cache node:
Within Azure portal, navigate to **Cache Nodes**, then select the cache node you wish to delete. Once selected, select **Delete** on the top bar to remove this cache node from your account.
## Run the uninstall script to cleanly remove MCC from your server
+
In the installer zip file, you'll find the file **uninstallmcc.sh**. This script uninstalls MCC and all the related components. Only run it if you're facing issues with MCC installation.
The **uninstallmcc.sh** script removes the following components:
diff --git a/windows/deployment/do/mcc-isp-verify-cache-node.md b/windows/deployment/do/mcc-isp-verify-cache-node.md
index e80f816a68..55811c97d3 100644
--- a/windows/deployment/do/mcc-isp-verify-cache-node.md
+++ b/windows/deployment/do/mcc-isp-verify-cache-node.md
@@ -49,7 +49,7 @@ Similarly, enter the following URL into a web browser on any device on the netwo
http:///mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com
```
-If the test fails, for more information, see the [FAQs](#mcc-isp-faq) section.
+If the test fails, for more information, see the [FAQ](mcc-isp-faq.yml) article.
## Monitor cache node health and performance
@@ -69,14 +69,14 @@ Within Azure portal, you're able to build your custom charts and graphs using th
| **Average in**| The average egress (in Gbps) of inbound traffic|
| **Average out**| The average egress (in Gbps) of outbound traffic|
-To learn more about how to build your custom charts and graphs, visit [Azure Monitor](https://docs.microsoft.com/en-us/azure/azure-monitor/essentials/data-platform-metrics) for details.
+For more information about how to build your custom charts and graphs, see [Azure Monitor](/azure/azure-monitor/essentials/data-platform-metrics).
### Monitoring your metrics
-To view the metrics associated with your cache nodes, navigate to the Overview >> Monitoring tab within Azure portal.
+To view the metrics associated with your cache nodes, navigate to the **Overview** > **Monitoring** tab within the Azure portal.
-:::image type="content" source="images/mcc-img-metrics.PNG" alt-text="Screenshot of the Azure portal displaying the metrics view in the Overview tab":::
+:::image type="content" source="./images/mcc-img-metrics.png" alt-text="Screenshot of the Azure portal displaying the metrics view in the Overview tab":::
-You can choose to monitor the health and performance of all cache nodes or one by one by using the dropdown menu. The **Egress bits per second** graph shows your inbound and outbound traffic of your cache nodes over time. You can change the time range (1 hour, 12 hours, 1 day, 7 days, 14 days, and 30 days) by selecting the time range of choice on the top bar.
+You can choose to monitor the health and performance of all cache nodes or one at a time by using the dropdown menu. The **Egress bits per second** graph shows your inbound and outbound traffic of your cache nodes over time. You can change the time range (1 hour, 12 hours, 1 day, 7 days, 14 days, and 30 days) by selecting the time range of choice on the top bar.
If you're unable to view metrics for your cache node, it may be that your cache node is unhealthy, inactive, or hasn't been fully configured.