Merge pull request #5 from amymzhou/nidos_working

Sign up, create, and support docs

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

@@ -0,0 +1,37 @@
+---
+title: Create Microsoft Connected Cache for ISP
+manager: dougeby
+description: Creating Microsoft Connected Cache for ISP on Azure portal
+keywords: updates, downloads, network, bandwidth
+ms.prod: w10
+ms.mktglfcycl: deploy
+audience: itpro
+author: nidos
+ms.localizationpriority: medium
+ms.author: nidos
+ms.collection: M365-modern-desktop
+ms.topic: article
+---
+
+
+# Create Microsoft Connected Cache for ISP
+
+**Applies to**
+
+- Windows 10
+- Windows 11
+
+<br/>
+
+> [!IMPORTANT]  
+> Before you can create your Microsoft Connected Cache, you will need to complete the sign up process here.
+
+<br/>
+<br/>
+
+## Create Cache Node
+<br/>
+
+
+
+

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

@@ -39,7 +39,14 @@ As an ISP, your network can benefit from reduced load on your backbone and impro
 
 **4. What are the prerequisites and hardware requirements?**  
 - Azure subscription  
-- Hardware to host MCC - The recommended configuration below will serve approximately 35,000 consumer devices downloading a 2GB payload in 24-hour timeframe at a sustained rate of 6.5 Gbps.
+- Hardware to host Microsoft Connected Cache - The recommended configuration below will serve approximately 35,000 consumer devices downloading a 2GB payload in 24-hour timeframe at a sustained rate of 6.5 Gbps.  
+We have 1 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.40GHz , total 32core  
+	- 48GB, Micron Technology 18ASF1G72PDZ-2G1A1, Speed: 2133 MT/s  
+	- 4 - Transcend SSD230s 1TB SATA Drives  
+Intel Corporation Ethernet 10G 2P X520 Adapter (Link Aggregated)
+
 <br/>
 
 | Taffic Estimate | Hardware/VM Recommendation |  
@@ -52,48 +59,48 @@ As an ISP, your network can benefit from reduced load on your backbone and impro
 <br/>
 	
 **5. Will I need to provide hardware BareMetal server or VM?**  
-	Microsoft Connected Cache (MCC) preview is a software-only caching solution and will require you to provide your own server to host the software.
+	Microsoft Connected Cache is a software-only caching solution and will require you to provide your own server to host the software.
 	
 <br/>
 
 **6. Can we use hard drives instead of SSDs?**  
-We highly recommend using SSDs as MCC is a read intensive application. We also recommend using multiple drives to improve performance.
+We highly recommend using SSDs as Microsoft Connected Cache is a read intensive application. We also recommend using multiple drives to improve performance.
 
 <br/>
 
-**7. Will I need to manually enter the CIDR blocks? If I have multiple MCCs, should I configure a subset of CIDR blocks to each MCC?**  
+**7. Will I need to manually enter the CIDR blocks? If I have multiple cache nodes, should I configure a subset of CIDR blocks to each cache node?**  
-You have the option to route your traffic using manual CIDR blocks or BGP. If you have multiple MCCs, you can allocate subsets of CIDR blocks to each MCC if you wish. However, since MCC has automatic load balancing, we recommend adding all of your traffic to all of your MCCs.
+You have the option to route your traffic using manual CIDR blocks or BGP. If you have multiple Microsoft Connected Cache(s), you can allocate subsets of CIDR blocks to each cache node if you wish. However, since Microsoft Connected Cache has automatic load balancing, we recommend adding all of your traffic to all of your cache nodes.
 	
 <br/>
 
 **8. Should I add any load balancing mechanism?**  
-You need not add any load balancing. Our service will take care of routing traffic if you have multiple MCCs serving the same CIDR blocks based on the reported health of the cache node.
+You do not need to add any load balancing. Our service will take care of routing traffic if you have multiple cache nodes serving the same CIDR blocks based on the reported health of the cache node.
 
 <br/>
 
-**9. How many MCC instances will I need? How do we setup if we support multiple countries?**  
+**9. How many Microsoft Connected Cache instances will I need? How do we setup if we support multiple countries?**  
-As stated in the table above, the recommended configuration will achieve near the maximum possible egress of 20Gbps with a two-port link aggregated NIC and four cache drives. If you provide us with your ASN numbers, we can give a rough estimate of how many MCC instances may be needed. If your ISP spans multiple countries, you can certainly set up separate MCC instances per country.
+As stated in the table above, the recommended configuration will achieve near the maximum possible egress of 20Gbps with a two-port link aggregated NIC and four cache drives. If you provide us with your ASN numbers, we can give a rough estimate of how many Microsoft Connected Cache instances may be needed. If your ISP spans multiple countries, you can set up separate cache nodes per country.
 
 <br/>
 
-**10. Where should we install MCC?**  
+**10. Where should we install Microsoft Connected Cache?**  
 You are in control of your hardware and you can pick the location based on your traffic and end customers. You can choose the location where you have your routers or where you have dense traffic or any other parameters.
 
 <br/>
 	
-**11. How long would a piece of content live within the MCC? Is content purged from the cache?**  
+**11. How long would a piece of content live within the Microsoft Connected Cache? Is content purged from the cache?**  
 A request for said content is made, and NGINX looks at the cache control headers from the original acquisition, and if that content has expired, NGINX will continue to serve the stale content while it is downloading the new content.  We are caching the content for 30 days.  The content will be in the hot cache path (open handles and such) for 24 hrs, but will reside on disk for 30 days.  
 The drive fills up and nginx will start to delete content based on its own algorithm, probably some combination of least recently used.
 	
 <br/>
 
-**12. What content is cached by MCC?**  
+**12. What content is cached by Microsoft Connected Cache?**  
-MCC supports Windows and Office content.
+See [Delivery Optimization and Microsoft Connected Cache content endpoints - Windows Deployment](delivery-optimization-endpoints.md) for more information.
 
 <br/>
 	
-**13. Does MCC support Xbox or Teams content?**
+**13. Does Microsoft Connected Cache support Xbox or Teams content?**  
-Currently, MCC does not support Xbox or Teams content. However, supporting Xbox content is of high priority, and we expect this feature in the near future. We'll let you know as soon as it becomes available!
+Currently, Microsoft Connected Cache does not support Xbox or Teams content. However, supporting Xbox content is of high priority, and we expect this feature in the near future. We'll let you know as soon as it becomes available!
 
 <br/>
 	
@@ -102,14 +109,14 @@ No, we do not currently support IPV6. We plan to support it in the future.
 		
 <br/>
 
-**15. Is MCC stable and reliable?**  
+**15. Is Microsoft Connected Cache stable and reliable?**  
 We have already successfully onboarded ISPs in many countries around the world and have received positive feedback! However, you can always start off with a portion of your CIDR blocks to test out the performance of MCC before expanding to more customers.
 
 <br/>
 
-**16.How does MCC populate its content?**  
+**16.How does Microsoft Connected Cache populate its content?**  
-MCC is a cold cache warmed by client requests. The client requests content and that is what fills up the cache. There is no off-peak cache fill necessary.  
+Microsoft Connected Cache is a cold cache warmed by client requests. The client requests content and that is what fills up the cache. There is no off-peak cache fill necessary.  
-MCC will reach out to different CDN providers just like a client device would. The traffic flow from MCC will vary depending on how you currently transit to each of these CDN providers. The content can come from 3rd party CDNs or from AFD.
+Microsoft Connected Cache will reach out to different CDN providers just like a client device would. The traffic flow from Microsoft Connected Cache will vary depending on how you currently transit to each of these CDN providers. The content can come from 3rd party CDNs or from AFD.
 	
 <br/>
 	
@@ -117,7 +124,7 @@ MCC will reach out to different CDN providers just like a client device would. T
 You can find more information or post your questions on MCC Community Forum.  
 <link to community forum>  
 
-For further support for your MCC you can find solutions to common problems here. <link to diagnose and solve>
+For further support for your Microsoft Connected Cache you can find solutions to common problems here. <link to common issues>
 
 <br/>
 

windows/deployment/do/mcc-isp-provision-deploy.md

@@ -0,0 +1,30 @@
+---
+title: Provision and deploy Microsoft Connected Cache for ISP
+manager: dougeby
+description: Provision and deploy Microsoft Connected Cache for ISP on Azure portal
+keywords: updates, downloads, network, bandwidth
+ms.prod: w10
+ms.mktglfcycl: deploy
+audience: itpro
+author: nidos
+ms.localizationpriority: medium
+ms.author: nidos
+ms.collection: M365-modern-desktop
+ms.topic: article
+---
+
+
+# Provisioning and deploying Microsoft Connected Cache for ISP
+
+**Applies to**
+
+- Windows 10
+- Windows 11
+
+<br/>
+
+## Provision Cache Node
+<br/>
+
+> [!IMPORTANT]  
+> Before you can create your MCC, you will need to complete the sign up process.

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

@@ -0,0 +1,51 @@
+---
+title: Service onboarding for Microsoft Connected Cache for ISP
+manager: dougeby
+description: Service onboarding for Microsoft Connected Cache for ISP
+keywords: updates, downloads, network, bandwidth
+ms.prod: w10
+ms.mktglfcycl: deploy
+audience: itpro
+author: nidos
+ms.localizationpriority: medium
+ms.author: nidos
+ms.collection: M365-modern-desktop
+ms.topic: article
+---
+
+
+# Service Onboarding for Microsoft Connected Cache for ISP
+
+**Applies to**
+
+- Windows 10
+- Windows 11
+
+<br/>
+
+## Resource creation and sign up process  
+
+
+<br/>
+
+1. Search for 'Microsoft Connected Cache' and go through the process of creating a resource by selecting the region and enter a name for your Cache resource name. 
+<pic>
+
+<br/>
+
+> [!IMPORTANT] 
+After your resource has been created, we need some information to verify you network operator status and approve you to host a 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.
+ 
+<br/>
+
+2. Add your organization ASN below. The NOC contact email will be used to send verification information. Additionally, please include any ASN(s) for downstream network operators that you may transit traffic for.
+<pic>
+
+1. Once we verify the information entered, a verification code will be sent to the NOC email address provided on Peering DB. In the Azure portal operator verification blade enter the verification code sent to the NOC email address.  
+**TBD Note:** The verification code will expire in 24 hours. You will need to generate a new code if it expires.
+<pic>
+
+<br/>
+<br/>
+Once verified follow the instruction on [Provisioning and Deploying MCC] to create and install the cache node.

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

@@ -0,0 +1,50 @@
+---
+title: Troubleshooting Issues for Microsoft Connected Cache for ISP
+manager: dougeby
+description: Troubleshooting Issues for Microsoft Connected Cache for ISP
+keywords: updates, downloads, network, bandwidth
+ms.prod: w10
+ms.mktglfcycl: deploy
+audience: itpro
+author: nidos
+ms.localizationpriority: medium
+ms.author: nidos
+ms.collection: M365-modern-desktop
+ms.topic: article
+---
+
+# Troubleshooting Issues for Microsoft Connected Cache for ISP (public preview)
+
+**Applies to**
+
+- Windows 10
+- Windows 11
+
+<br/>
+
+## Sign up Errors
+
+### Could not verify account:  
+During sign up we verify the information you provide against what is present in [Peering DB]. Make sure the information you have provided on Peering DB is up to date and matches what you provide during sign up.
+<br/>
+<br/>
+
+### Invalid verification code: 
+During sign up, a verification code is sent to your NOC email address present in Peering DB. **TBD** This code expires in 24 hours. You will need to request a new verification code and use that to complete sign up.  
+<br/>
+
+<br/>
+
+
+## Cache Node Errors  
+
+### Cannot find my cache node:  
+If you previously had access to your cache nodes but it is now no longer accessible, it may be because you had a trial subscription and its trial period ended. 
+#### Recommended steps:  
+1. Create a new Azure Pay As You Go subscription  
+1. Recreate the cache nodes using the new subscription 
+
+#### 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/)