diff --git a/windows/deployment/do/images/mcc-isp-migration.png b/windows/deployment/do/images/mcc-isp-migration.png
new file mode 100644
index 0000000000..50990a8466
Binary files /dev/null and b/windows/deployment/do/images/mcc-isp-migration.png differ
diff --git a/windows/deployment/do/mcc-enterprise-deploy.md b/windows/deployment/do/mcc-enterprise-deploy.md
index b549733da5..4c015f9471 100644
--- a/windows/deployment/do/mcc-enterprise-deploy.md
+++ b/windows/deployment/do/mcc-enterprise-deploy.md
@@ -158,9 +158,7 @@ Installing MCC on your Windows device is a simple process. A PowerShell script p
    >
    > Don't use PowerShell ISE, PowerShell 6.x, or PowerShell 7.x. Only Windows PowerShell version 5.x is supported.
 
-#### If you're installing MCC on a local virtual machine
-
-1. Turn the virtual machine **off** while you enable nested virtualization and MAC spoofing.
+1. **If you're installing MCC on a local virtual machine**, turn the virtual machine **off** while you enable nested virtualization and MAC spoofing.
    1. Enable nested virtualization:
 
       ```powershell
@@ -230,7 +228,7 @@ Installing MCC on your Windows device is a simple process. A PowerShell script p
 
 1. Your MCC deployment is now complete.
 
-    1. If you don't see any errors, continue to the next section to validate your MCC deployment.
+    1. If you don't see any errors, continue to the next section to validate your MCC deployment. Your VM will not appear in Hyper-V Manager as it is an EFLOW VM.
     1. After validating your MCC is properly functional, review your management solution documentation, such as [Intune](/mem/intune/configuration/delivery-optimization-windows), to set the cache host policy to the IP address of your MCC.
     1. If you had errors during your deployment, see the [Common Issues](#common-issues) section in this article.
 
diff --git a/windows/deployment/do/mcc-isp-create-provision-deploy.md b/windows/deployment/do/mcc-isp-create-provision-deploy.md
index 7eecb4983c..ecc4cf8379 100644
--- a/windows/deployment/do/mcc-isp-create-provision-deploy.md
+++ b/windows/deployment/do/mcc-isp-create-provision-deploy.md
@@ -99,6 +99,8 @@ There are five IDs that the device provisioning script takes as input in order t
 | Customer key | The unique alphanumeric ID that provides secure authentication of the cache node to Delivery Optimization services. |
 | Registration key | Single use device registration key used by Microsoft Delivery Optimization services. |
 
+#### Provision your server
+
 :::image type="content" source="images/mcc-isp-deploy-cache-node-numbered.png" alt-text="Screenshot of the server provisioning tab within cache node configuration in Azure portal.":::
 
 1. After completing cache node provisioning, navigate to the **Server provisioning** tab. Select **Download provisioning package** to download the installation package to your server.  
diff --git a/windows/deployment/do/mcc-isp.md b/windows/deployment/do/mcc-isp.md
index 27de31c9b1..c7186e2d85 100644
--- a/windows/deployment/do/mcc-isp.md
+++ b/windows/deployment/do/mcc-isp.md
@@ -23,7 +23,7 @@ ms.collection: tier3
 ## Overview
 
 > [!IMPORTANT]
-> 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/).
+> This document is for Microsoft Connected Cache (early preview). Microsoft Connected Cache for ISPs is now in Public Preview - for our early preview customers, we highly encourage you to migrate your cache nodes to our public preview. See [instructions on how to migrate](#migrating-your-mcc-to-public-preview) below.
 
 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.
 
@@ -62,7 +62,9 @@ The following steps describe how MCC is provisioned and used:
 
 ## ISP requirements for MCC
 
-### Azure subscription
+Microsoft Connected Cache for Internet Service Providers is now in Public Preview! To get started, visit  [Azure portal](https://www.portal.azure.com) to sign up for Microsoft Connected Cache for Internet Service Providers. Please see [Operator sign up and service onboarding for Microsoft Connected Cache](mcc-isp-signup.md) for more information on the requirements for sign up and onboarding.
+
+<!-- ### Azure subscription
 
 The MCC management portal is hosted within Azure. It's used to create the Connected Cache Azure resource and IoT Hub resource. Both are *free* services.
 
@@ -73,9 +75,6 @@ Your Azure subscription ID is first used to provision MCC services and enable ac
 
 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.
 
-> [!IMPORTANT]
-> To join the Microsoft Connected Cache early preview, provide your Azure subscription ID by filling out [this survey](https://aka.ms/MCCForISPSurvey).
-
 ### Hardware to host the MCC
 
 This recommended configuration can egress at a rate of 9 Gbps with a 10 Gbps NIC.
@@ -102,9 +101,9 @@ The MCC module is optimized for Ubuntu 20.04 LTS. Install Ubuntu 20.04 LTS on a
 | NIC | 10 Gbps| at least 10 Gbps |
 | Disk | SSD </br>1 drive </br>2 TB each  |SSD </br>2-4 drives </br>at least 2 TB each  |
 | Memory | 8 GB | 32 GB or greater |
-| Cores | 4 | 8 or more  |
+| Cores | 4 | 8 or more  | -->
 
-## Steps to deploy MCC
+<!-- ## Steps to deploy MCC
 
 To deploy MCC:
 
@@ -116,16 +115,13 @@ To deploy MCC:
 6. [Verify properly functioning MCC server](#verify-properly-functioning-mcc-server)
 7. [Review common issues if needed](#common-issues)
 
-For questions regarding these instructions, contact [msconnectedcache@microsoft.com](mailto:msconnectedcache@microsoft.com).
 
 ## Provide Microsoft with your Azure subscription ID
 
 As part of the MCC preview onboarding process, an Azure subscription ID must be provided to Microsoft.
 
 > [!IMPORTANT]
-> If you haven't already, provide your Azure subscription ID by filling out [this survey](https://aka.ms/MCCForISPSurvey). You can't continue if you skip this step.
-
-For information about creating or locating your subscription ID, see [Steps to obtain an Azure subscription ID](#steps-to-obtain-an-azure-subscription-id).
+> For information about creating or locating your subscription ID, see [Steps to obtain an Azure subscription ID](#steps-to-obtain-an-azure-subscription-id).
 
 ### Create the MCC resource in Azure
 
@@ -265,9 +261,9 @@ To modify the configuration for existing MCC nodes in the portal, select the cac
 
 :::image type="content" source="./images/mcc-isp-node-configuration.png" alt-text="Screenshot of the Cache Node Configuration page, highlighting editable fields.":::
 
-To delete a cache node, select it in the cache nodes list, and then select **Delete** in the toolbar. If you delete a cache node, there's no way to recover it or any of the information related to the cache node.
+To delete a cache node, select it in the cache nodes list, and then select **Delete** in the toolbar. If you delete a cache node, there's no way to recover it or any of the information related to the cache node. -->
 
-## Install MCC
+<!-- ## Install MCC
 
 To install MCC on your physical server or VM, you use a Bash script installer, which runs the following tasks:
 
@@ -400,7 +396,7 @@ Before you start, make sure that you have a data drive configured on your server
 
     - Inspect the installer logs, which are in the following path: `/etc/mccresourcecreation/`
 
-    - For more information, see [Troubleshoot your IoT Edge device](/azure/iot-edge/troubleshoot).
+    - For more information, see [Troubleshoot your IoT Edge device](/azure/iot-edge/troubleshoot). -->
 
 ## Verify properly functioning MCC server
 
@@ -509,9 +505,9 @@ To configure the device to work with your DNS, use the following steps:
     sudo restart IoTEdge
     ```
 
-### Diagnostics script
+<!-- ### Diagnostics script
 
-If you're having issues with your MCC, the installer file includes a diagnostics script. The script collects all logs and zips them into a single file. You can then email these logs to Microsoft.
+If you're having issues with your MCC, the installer file includes a diagnostics script. The script collects all logs and zips them into a single file. 
 
 To run the script:
 
@@ -528,9 +524,9 @@ To run the script:
 
 1. The script stores all the debug files into a folder and creates a tar file. After the script is finished running, it displays the path of the tar file that you can share with the MCC team. The file should be `/etc/mccdiagnostics/support_bundle_\$timestamp.tar.gz`
 
-1. [Email the MCC team](mailto:msconnectedcache@microsoft.com?subject=Debugging%20Support%20Request%20for%20MCC) and attach this tar file, asking for debugging support. Screenshots of the error along with any other warnings you saw will be helpful during the debugging process.
+1. [Email the MCC team](mailto:msconnectedcache@microsoft.com?subject=Debugging%20Support%20Request%20for%20MCC) and attach this tar file, asking for debugging support. Screenshots of the error along with any other warnings you saw will be helpful during the debugging process. -->
 
-## Updating your MCC
+<!-- ## Updating your MCC
 
 Throughout the early preview phase, Microsoft will release security and feature updates for MCC. Follow these steps to update your MCC.
 
@@ -546,7 +542,7 @@ For example:
 
 ```bash
 sudo ./updatemcc.sh version="msconnectedcacheprod.azurecr.io/mcc/linux/iot/mcc-ubuntu-iot-amd64:1.2.1.981" tenantid="799a999aa-99a1-99aa-99aa-9a9aa099db99" customerid="99a999aa-99a1-99aa-99aa-9aaa9aaa0saa" cachenodeid=" aa99aaaa-999a-9aas-99aa99daaa99 " customerkey="a99d999a-aaaa-aa99-0999aaaa99aa"
-```
+``` -->
 
 ### Configure BGP on an Existing MCC
 
@@ -558,6 +554,22 @@ If you have an MCC that's already active and running, follow the steps below to
 
 1. To finish configuring your MCC with BGP routing, continue from Step 10 of [Steps to Install MCC](#steps-to-install-mcc).
 
+## Migrating your MCC to Public Preview
+
+Please note, if you reboot your server, the version that you are currently on will no longer function, after which you will be required to migrate to the new version.
+
+We recommend migrating now to the new version to access these benefits and ensure no downtime.
+
+To migrate, use the following steps:
+
+1. Navigate to the cache node that you would like to migrate and select **Download Migration Package** using the button at the top of the page
+1. Follow the instructions under the "Connected Cache Migrate Scripts" section
+1. Go to https://portal.azure.com and navigate to your resource to check your migrated cache nodes
+
+Here is a screenshot from the Azure portal to help:
+
+:::image type="content" source="images/mcc-isp-migration.png" alt-text="A screenshot of Azure portal showing the migration instructions for migrating a cache node from the private preview to the public preview.":::
+
 ## Uninstalling MCC
 
 In the installer zip file, you'll find the file **uninstallmcc.sh**. This script uninstalls MCC and all the related components. Before you run this script, contact the MCC team. Only run it if you're facing issues with MCC installation.