add elixir photos

windows/deployment/do/images/elixir/readme.md

@@ -0,0 +1,15 @@
+# Read Me
+
+This file contains the images that are included in this GitHub repository for the purpose of Diagnose and Solve. These images below _should not be removed_ from the repository.
+
+:::image type="content" source="checkverbose-1.png" alt-text="A terminal screenshot that show all green checks in the output after the command "iotedge check --verbose"":::
+
+:::image type="content" source="checkverbose-2.png" alt-text="A screenshot that shows 6 out of the 22 checks raising errors":::
+
+:::image type="content" source="connectivitycheck1.png" alt-text="A screenshot of green checkmarks, showing that all of the connectivity checks are successful":::
+
+:::image type="content" source="edgeagentfailed.png" alt-text="A screenshot of the terminal after the command 'iotedge list', which shows three containers and the edgeAgent container failing":::
+
+:::image type="content" source="iotedgelist.png" alt-text="A screenshot of the terminal after the command 'iotedge list', showing all three containers running successfully":::
+
+:::image type="content" source="mccfailed.png" alt-text="A screenshot of the terminal after the command 'iotedge list', showing the MCC container in a failure state":::

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

@@ -0,0 +1,17 @@
+---
+author: amyzhou
+ms.author: amyzhou
+manager: dougeby
+ms.prod: w10
+ms.collection: M365-modern-desktop
+ms.topic: include
+ms.date: 11/09/2022
+ms.localizationpriority: medium
+---
+<!-- This file is included in the mcc-isp-faq.yml file. -->
+
+Peak Egress | Hardware Specifications|
+---|---|
+< 5G Peak | VM with 8 cores, 16 GB memory, 1 SSD Drive 500GB|
+10 - 20G Peak | VM with 16 cores, 32 GB memory, 2 - 3 SSD Drives 1 TB|
+20 - 40G Peak | Hardware (sample hardware spec) with 32 cores, 64 GB memory, 4 - 6 SSDs 1 TB |

windows/deployment/do/index.yml

@@ -79,10 +79,13 @@ landingContent:
     linkLists:
       - linkListType: deploy
         links:
+          - text: MCC for ISPs (Public Preview)
+            url: mcc-isp-signup.md
+          - text: Sign up
+            url: https://aka.ms/MCCForISPSurvey)
           - text: MCC for ISPs (Early Preview)
             url: mcc-isp.md
-          - text: Sign up
-            url: https://aka.ms/MSConnectedCacheSignup 
+          
 
   # Card (optional)
   - title: Resources

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

@@ -35,6 +35,9 @@ sections:
          - Azure subscription  
          - Hardware to host Microsoft Connected Cache - The recommended configuration below will serve approximately 35,000 consumer devices downloading a 2-GB payload in 24-hour timeframe at a sustained rate of 6.5 Gbps.  
           
+          <!--Using include file, mcc-prerequisites.md, for shared content on DO monitoring-->
+          [!INCLUDE [Microsoft Connected Cache Prerequisites](includes/mcc-prerequisites.md)]
+
          We have one customer who is able to achieve 40-Gbps egress rate using the following hardware specification:  
           - Dell PowerEdge R330  
           - 2 x Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40 GHz, total 32 core  

windows/deployment/do/mcc-isp-signup.md

@@ -1,6 +1,6 @@
 ---
 title: Operator sign up and service onboarding
-manager: aaroncz
+manager: dougeby
 description: Service onboarding for Microsoft Connected Cache for ISP
 keywords: updates, downloads, network, bandwidth
 ms.prod: w10
@@ -17,44 +17,46 @@ 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). 
 
+> [!IMPORTANT]
+> Microsoft Connected Cache for ISPs (Public Preview) is currently invite-only. Interested in joining our public preview? Fill out [this survey](https://aka.ms/MCCForISPSurvey) to be notified when it becomes available.
+
 ## Resource creation and sign up process  
 
-1. Navigate to the [Azure portal](https://www.portal.azure.com). In the top search bar, search for **Microsoft Connected Cache**.
+1. Navigate to your [Azure portal](https://www.portal.azure.com). In the top search bar, search for **Microsoft Connected Cache**.
 
-   :::image type="content" source="./images/mcc-isp-search.png" alt-text="Screenshot of the Azure portal that shows the Microsoft Connected Cache resource in Azure marketplace.":::
+:::image type="content" source="images/searchmcc.png" alt-text="Screenshot of the Azure portal which 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're a transit provider. If so, additionally, 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 are a transit provider. If so, additionally, please include any ASN(s) for downstream network operators that you may transit traffic for.
 
-   :::image type="content" source="./images/mcc-isp-sign-up.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/mcc-isp-operator-verification.png" alt-text="Screenshot of the sign up verification page on Azure portal for Microsoft Connected Cache.":::
+:::image type="content" source="images/verification.png" alt-text="Screenshot of the signup verification page on Azure portal for Microsoft Connected Cache.":::
 
-1. Once verified, follow the instructions in [Create, provision, and deploy cache node](mcc-isp-create-provision-deploy.md) to create your cache node.
+Once verified, follow the instructions on [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 review 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 view 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, review the following information:
+To make sure you're maximizing the performance of your cache node, note the following:
 
 #### OS requirements
 
@@ -62,7 +64,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
@@ -73,11 +75,11 @@ RAID disk configurations are discouraged as cache performance will be impacted.
 
 ### Hardware configuration example
 
-There are many hardware configurations that suit Microsoft Connected Cache. As an example, a customer has deployed the following hardware configuration and is able achieve a peak egress of about 35 Gbps:
+There are many hardware configurations that suit Microsoft Connected Cache. As an example, below is the hardware configuration of a customer who is able to egress 40 Gbps of traffic.
 
 **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)

windows/deployment/do/mcc-isp.md

@@ -13,7 +13,7 @@ ms.topic: how-to
 ms.date: 05/20/2022
 ---
 
-# Microsoft Connected Cache for Internet Service Providers (ISPs)
+# Microsoft Connected Cache for Internet Service Providers (Early preview)
 
 *Applies to*
 
@@ -23,7 +23,7 @@ ms.date: 05/20/2022
 ## Overview
 
 > [!IMPORTANT]
-> 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/).
+> This document is for Microsoft Connected Cache (early preview). 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.
 

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

@@ -22,7 +22,7 @@ ms.technology: itpro-updates
 - Windows 11
 
 > [!IMPORTANT]
-> 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 does not include formal support, and should not be used for production workloads. 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 a preview feature. To view our early preview documentation, visit [Microsoft Connected Cache for Internet Service Providers (ISPs)](mcc-isp.md). 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 Enterprise networks. MCC can be deployed to as many bare-metal servers or VMs as needed, and is managed from a cloud portal. Cache nodes are created in the cloud portal and are configured by applying the client policy using management tools such as Intune.
 
@@ -58,4 +58,4 @@ The following diagram displays and overview of how MCC functions:
 ## Next steps
 
 - [Microsoft Connected Cache for Enterprise and Education](mcc-enterprise-overview.md)
-- [Microsoft Connected Cache for ISPs](mcc-isp.md)
+- [Microsoft Connected Cache for ISPs](mcc-isp-signup.md)