markdown and image edits

.openpublishing.redirection.json

@@ -19654,6 +19654,11 @@
      "source_path": "windows/configuration/windows-10-accessibility-for-ITPros.md",
      "redirect_url": "/windows/configuration/windows-accessibility-for-ITPros",
      "redirect_document_id": false
+     },
+     {
+      "source_path": "windows/deployment/do/mcc-enterprise.md",
+      "redirect_url": "/windows/deployment/do/mcc-enterprise-overview",
+      "redirect_document_id": false
       }     
   ]
 }

windows/deployment/do/TOC.yml

@@ -36,7 +36,7 @@
       - name: Deploy Microsoft Connected Cache
         href: mcc-enterprise-deploy.md
       - name: Update and uninstall cache node
-        href: mcc-enterprise-update-uninstall.md
+        href: mcc-enterprise-update.md
       - name: Appendix
         href: mcc-enterprise-appendix.md
     - name: MCC for ISPs

windows/deployment/do/index.yml

@@ -69,8 +69,8 @@ landingContent:
     linkLists:
       - linkListType: deploy
         links:
-          - text: MCC for Enterprise and Education (Private Preview)
-            url: mcc-enterprise.md
+          - text: MCC for Enterprise and Education (Early Preview)
+            url: mcc-enterprise-overview.md
           - text: Sign up
             url: https://aka.ms/MSConnectedCacheSignup 
 

windows/deployment/do/mcc-enterprise-appendix.md

@@ -36,11 +36,11 @@ To run this script:
 ## Steps to obtain an Azure Subscription ID
 
 1. Sign in to https://portal.azure.com/ and navigate to the Azure services section.
-2. Click on **Subscriptions**. If you do not see **Subscriptions**, click on the **More Services** arrow and search for **Subscriptions**. 
-3. If you already have an Azure Subscription, skip to step 5. If you do not have an Azure Subscription, select **+ Add** on the top left. 
-4. Select the **Pay-As-You-Go** subscription. You'll be asked to enter credit card information, but you'll not be charged for using the MCC service. 
-5. On the **Subscriptions** blade, you'll find details about your current subscription. Click on the subscription name. 
-6. After you select the subscription name, you'll find the subscription ID in the **Overview** tab. Click on the **Copy to clipboard** icon next to your Subscription ID to copy the value. 
+1. Click on **Subscriptions**. If you do not see **Subscriptions**, click on the **More Services** arrow and search for **Subscriptions**. 
+1. If you already have an Azure Subscription, skip to step 5. If you do not have an Azure Subscription, select **+ Add** on the top left. 
+1. Select the **Pay-As-You-Go** subscription. You'll be asked to enter credit card information, but you'll not be charged for using the MCC service. 
+1. On the **Subscriptions** blade, you'll find details about your current subscription. Click on the subscription name. 
+1. After you select the subscription name, you'll find the subscription ID in the **Overview** tab. Click on the **Copy to clipboard** icon next to your Subscription ID to copy the value. 
 
 ## Troubleshooting
 

windows/deployment/do/mcc-enterprise-overview.md

@@ -14,7 +14,7 @@ ms.topic: article
 
 **Applies to**
 
-- Windows 10
+- Windows 10
 - Windows 11
 
 ## Overview
@@ -24,14 +24,14 @@ ms.topic: article
 
 Microsoft Connected Cache (MCC) preview is a software-only caching solution that delivers Microsoft content within Enterprise networks. MCC can be deployed to as many physical servers or VMs as needed, and is managed from a cloud portal. Cache nodes are created in the cloud portal and are configured by applying a client policy using your management tool, such as [Intune](/mem/intune/).
 
-MCC is a hybrid (a mix of on-premises and cloud resources) SaaS solution built as an Azure IoT Edge module; it's a Docker compatible Linux container that is deployed to your Windows devices. IoT Edge for Linux on Windows (EFLOW) was chosen because it's a secure, reliable container management infrastructure. EFLOW is a Linux virtual machine, based on Microsoft's first party CBL-Mariner operating system. It’s built with the IoT Edge runtime and validated as a tier 1 supported environment for IoT Edge workloads. MCC will be a Linux IoT Edge module running on the Windows Host OS.
+MCC is a hybrid (a mix of on-premises and cloud resources) SaaS solution built as an Azure IoT Edge module; it's a Docker compatible Linux container that is deployed to your Windows devices. IoT Edge for Linux on Windows (EFLOW) was chosen because it's a secure, reliable container management infrastructure. EFLOW is a Linux virtual machine, based on Microsoft's first party CBL-Mariner operating system. It's built with the IoT Edge runtime and validated as a tier 1 supported environment for IoT Edge workloads. MCC will be a Linux IoT Edge module running on the Windows Host OS.
 
 Even though your MCC scenario isn't related to IoT, Azure IoT Edge is used as a more generic Linux container, deployment, and management infrastructure. The Azure IoT Edge runtime sits on your designated MCC device and performs management and communication operations. The runtime performs the following important functions to manage MCC on your edge device: 
 
 1. Installs and updates MCC on your edge device. 
-2. Maintains Azure IoT Edge security standards on your edge device. 
-3. Ensures that MCC is always running. 
-4. Reports MCC health and usage to the cloud for remote monitoring.
+1. Maintains Azure IoT Edge security standards on your edge device. 
+1. Ensures that MCC is always running. 
+1. Reports MCC health and usage to the cloud for remote monitoring.
 
 To deploy a functional MCC to your device, you must obtain the necessary keys that will provision the Connected Cache instance to communicate with Delivery Optimization services and enable the device to cache and deliver content. See [figure 1](#fig1) below for a summary of the architecture of MCC, built using IoT Edge.
 
@@ -42,17 +42,17 @@ For more information about Azure IoT Edge, see [What is Azure IoT Edge](/azure/i
 The following steps describe how MCC is provisioned and used.
 
 1. The Azure Management Portal is used to create MCC nodes.
-2. The MCC container is deployed and provisioned to a server using the installer provided in the portal.
-3. Client policy is configured in your management solution to point to the IP address or FQDN of the cache server.
-4. Microsoft end-user devices make range requests for content from the MCC node.
-5. An MCC node pulls content from the CDN, seeds its local cache stored on disk, and delivers content to the client.
-6. Subsequent requests from end-user devices for content come from the cache.
+1. The MCC container is deployed and provisioned to a server using the installer provided in the portal.
+1. Client policy is configured in your management solution to point to the IP address or FQDN of the cache server.
+1. Microsoft end-user devices make range requests for content from the MCC node.
+1. An MCC node pulls content from the CDN, seeds its local cache stored on disk, and delivers content to the client.
+1. Subsequent requests from end-user devices for content come from the cache.
 
 If an MCC node is unavailable, the client will pull content from CDN to ensure uninterrupted service for your subscribers.
 
 <a id="fig1">
 
-![eMCC img01](images/emcc01.png)
+ :::image type="content" source="./images/ent-mcc-overview.png" alt-text="Diagram of the MCC process." lightbox="./images/ent-mcc-overview.png"::: 
 
 </a>Figure 1: **MCC processes**. Each number in the diagram corresponds to the steps described above.
 

windows/deployment/do/mcc-isp.md

@@ -23,7 +23,7 @@ _Applies to_
 ## Overview
 
 > [!IMPORTANT]
-> Microsoft Connected Cache is currently a private preview feature. During this phase we invite customers to take part in early access for testing purposes. This phase doesn't include formal support. Instead, you'll be working directly with the product team to provide feedback on Microsoft Connected Cache. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
+> Microsoft Connected Cache is currently an early preview feature. During this phase we invite customers to take part in early access for testing purposes. This phase doesn't include formal support. Instead, you'll be working directly with the product team to provide feedback on Microsoft Connected Cache. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
 Microsoft Connected Cache (MCC) preview is a software-only caching solution that delivers Microsoft content within operator networks. MCC can be deployed to as many physical servers or VMs as needed and is managed from a cloud portal. Microsoft cloud services handle routing of consumer devices to the cache server for content downloads.
 
@@ -735,6 +735,6 @@ For more information on Azure IoT Edge, see the [Azure IoT Edge documentation](/
 
 ## Related articles
 
-[Microsoft Connected Cache for enterprise and education](mcc-enterprise.md)
+[Microsoft Connected Cache for enterprise and education](mcc-enterprise-overview.md)
 
 [Introducing Microsoft Connected Cache](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/introducing-microsoft-connected-cache-microsoft-s-cloud-managed/ba-p/963898)

windows/deployment/do/waas-microsoft-connected-cache.md

@@ -31,9 +31,9 @@ MCC is a hybrid (mix of on-prem and cloud resources) SaaS solution built as an A
 Even though your MCC scenario is not related to IoT, Azure IoT Edge is used as a more generic Linux container deployment and management infrastructure. The Azure IoT Edge runtime sits on your designated MCC device and performs management and communication operations. The runtime performs several functions important to manage MCC on your edge device:
 
 1. Installs and updates MCC on your edge device.
-2. Maintains Azure IoT Edge security standards on your edge device.
-3. Ensures that MCC is always running.
-4. Reports MCC health and usage to the cloud for remote monitoring.
+1. Maintains Azure IoT Edge security standards on your edge device.
+1. Ensures that MCC is always running.
+1. Reports MCC health and usage to the cloud for remote monitoring.
   
 To deploy a functional MCC to your device, you must obtain the necessary keys to provision the Connected Cache instance that communicates with Delivery Optimization services, and enable the device to cache and deliver content. The architecture of MCC is described below.
   
@@ -42,20 +42,20 @@ For more details information on Azure IoT Edge, please see the Azure IoT Edge [d
 ## How MCC Works  
 
 1. The Azure Management Portal is used to create MCC nodes.
-2. The MCC container is deployed and provisioned to the server using the installer provided in the portal.
-3. Client policy is set in your management solution to point to the IP address or FQDN of the cache server.
-4. Microsoft end-user devices make range requests for content from the MCC node.
-5. The MCC node pulls content from the CDN, seeds its local cache stored on disk, and delivers the content to the client.
-6. Subsequent requests from end-user devices for content will now come from cache.
-7. If the MCC node is unavailable, the client will pull content from CDN to ensure uninterrupted service for your subscribers.
+1. The MCC container is deployed and provisioned to the server using the installer provided in the portal.
+1. Client policy is set in your management solution to point to the IP address or FQDN of the cache server.
+1. Microsoft end-user devices make range requests for content from the MCC node.
+1. The MCC node pulls content from the CDN, seeds its local cache stored on disk, and delivers the content to the client.
+1. Subsequent requests from end-user devices for content will now come from cache.
+1. If the MCC node is unavailable, the client will pull content from CDN to ensure uninterrupted service for your subscribers.
 
-See the following diagram.
+The following diagram displays and overview of how MCC functions:
 
 ![MCC Overview](images/waas-mcc-diag-overview.png#lightbox)
 
 For more information about MCC, see the following articles:
-- [Microsoft Connected Cache for Enterprise and Education](mcc-enterprise.md)
-- [Microsoft Connected Cache for ISPs](mcc-isp-device-provisioning.md)
+- [Microsoft Connected Cache for Enterprise and Education](mcc-enterprise-overview.md)
+- [Microsoft Connected Cache for ISPs](mcc-isp.md)
 
 ## Also see