Merge pull request #10326 from doshnid/nidos-ent

changes to faq,overview,create pages

windows/deployment/do/mcc-ent-create-resource-and-cache.md

@@ -63,7 +63,7 @@ For more information on sizing and OS requirements, see [the prerequisites for u
 #### Create MCC Azure resource
 
 Replace the following placeholders with your own information:
-* *\<resource-group>*: An existing resource group in your subscription.
+* *\<resource-group>*: Name of an existing resource group in your subscription.
 * *\<mcc-resource-name>*: A name for your Microsoft Connected Cache for Enterprise resource.
 * *\<location>*: The Azure region where your Microsoft Connected Cache will be located.
 
@@ -94,9 +94,9 @@ To know more about different cache node state, see [Cache node states](#cache-no
 Use the following command to create a new cache node if you don't already have one.
 
 Replace the following placeholders with your own information:
-* *\<resource-group>*: An existing resource group in your subscription.
-* *\<mcc-resource-name>*: A name for your Microsoft Connected Cache for Enterprise resource.
-* *\<cache-node-name>*: The Azure region where your Microsoft Connected Cache will be located.
+* *\<resource-group>*: Name of existing resource group in your subscription.
+* *\<mcc-resource-name>*: Name of the Microsoft Connected Cache for Enterprise resource.
+* *\<cache-node-name>*: A name for your Microsoft Connected Cache node.
 * *\<host-os>*: The OS on which cache node will be provisioned.
   Accepted values: windows, linux
 
@@ -131,9 +131,9 @@ Use the following command to configure cache node for deployment to a **Linux**
 
 Replace the following placeholders with your own information:
 
-* *\<resource-group>*: An existing resource group in your subscription.
-* *\<mcc-resource-name>*: A name for your Microsoft Connected Cache for Enterprise resource.
-* *\<cache-node-name>*: The Azure region where your Microsoft Connected Cache will be located.
+* *\<resource-group>*: Name of the resource group in your subscription.
+* *\<mcc-resource-name>*: Name of your Microsoft Connected Cache for Enterprise resource.
+* *\<cache-node-name>*: Name for your Microsoft Connected Cache node.
 * *\<physical-path>*: The cache drive path. You can add upto nine cache drives.
 * *\<size-in-gb>*: The size of cache drive. Must be at least 50 Gb.
 * *\<proxy>*: If proxy needs to be enabled or not.<br>
@@ -163,9 +163,9 @@ Use the following command to configure cache node for deployment to a **Windows*
 
 Replace the following placeholders with your own information:
   
-* *\<resource-group>*: An existing resource group in your subscription.
-* *\<mcc-resource-name>*: A name for your Microsoft Connected Cache for Enterprise resource.
-* *\<cache-node-name>*: The Azure region where your Microsoft Connected Cache will be located.
+* *\<resource-group>*: Name of the resource group in your subscription.
+* *\<mcc-resource-name>*: Name of your Microsoft Connected Cache for Enterprise resource.
+* *\<cache-node-name>*: Name for your Microsoft Connected Cache node.
 * *\<physical-path>*: The cache drive path.<br>
   Accepted value: /var/mcc
 * *\<size-in-gb>*: The size of cache drive. Must be at least 50 Gb.
@@ -252,12 +252,94 @@ You can choose to enable or disable proxy settings on your cache node. Proxy sho
 |**Proxy host name**|	String or number|	Proxy host name or address|
 |**Proxy port**|	Integer|	Proxy port
 
+<br>
+<br>
+
+## Other operations on resource and cache nodes
+<br>
+
+### List all MCC resource
+
+# [Azure portal](#tab/portal)
+Navigate to the resource group under which you would like to see the MCC resources.
+
+
+# [Azure CLI](#tab/cli)
+Use the following command to list all the MCC resources under the resource group. 
+
+Replace the following placeholders with your own information:
+* *\<resource-group>*: An existing resource group in your subscription.
+
+
+```azurecli-interactive
+az mcc ent resource list  --resource-group <myrg>
+```
+---
+
+### List all cache nodes
+
+# [Azure portal](#tab/portal)
+On the left pane, click on 'Cache Nodes' under 'Cache Node Management' to see all the cache nodes under the MCC resource.
+
+
+# [Azure CLI](#tab/cli)
+Use the following command to list all the cache nodes under the resource. 
+
+Replace the following placeholders with your own information:
+* *\<resource-group>*: Name of the resource group in your subscription.
+* *\<mcc-resource-name>*: Name of your Microsoft Connected Cache for Enterprise resource.
+
+```azurecli-interactive
+az mcc ent node list --mcc-resource-name <mymccresource> --resource-group <myrg>
+```
+
+---
+<br>
+
+### Delete MCC resource
+
+# [Azure portal](#tab/portal)
+Navigate to the MCC resource to delete and click on the delete button on top.
+
+
+# [Azure CLI](#tab/cli)
+Use the following command to delete the MCC resource. 
+
+Replace the following placeholders with your own information:
+* *\<resource-group>*: Name of the resource group in your subscription.
+* *\<mcc-resource-name>*: Name of your Microsoft Connected Cache for Enterprise resource.
+* *\<cache-node-name>*: The name for your Microsoft Connected Cache node.
+
+
+```azurecli-interactive
+az mcc ent node delete --cache-node-name <mycachenode> --mcc-resource-name <mymccresource> --resource-group <myrg> 
+```
+---
+
+### Delete cache node
+
+# [Azure portal](#tab/portal)
+On the left pane, click on 'Cache Nodes' under 'Cache Node Management' to see all the cache nodes under the MCC resource. Select the cache node you wish to delete and click delete button on top of the page.
+
+
+# [Azure CLI](#tab/cli)
+Use the following command to delete the cache node under the resource. 
+
+Replace the following placeholders with your own information:
+* *\<resource-group>*: Name of the resource group in your subscription.
+* *\<mcc-resource-name>*: Name of your Microsoft Connected Cache for Enterprise resource.
+
+```azurecli-interactive
+az mcc ent node delete --mcc-resource-name <mymccresource> --resource-group <myrg>
+```
+
+---
 <br>
 
 ##### Cache node states
 | Cache node state |Description|
 |---|---|
-|Creation in progress| Cache node is being created|
+|Operation in progress| An operation is being done on the cache node|
 |Registration in progress| Cache node is being registered|
 |Not configured| Cache node is ready to be configured|
 |Not provisioned| Cache node is ready to be provisioned on host machine|

windows/deployment/do/mcc-ent-edu-overview.md

@@ -25,7 +25,7 @@ Microsoft Connected Cache (MCC) for Enterprise and Education (preview) is a soft
 
 Microsoft Connected Cache (MCC) for Enterprise and Education (preview) is a standalone cache for customers moving towards modern management and away from Configuration Manager distribution points. For information about Microsoft Connected Cache in Configuration Manager (generally available, starting Configuration Manager version 2111), see [Microsoft Connected Cache in Configuration Manager](/configmgr/core/plan-design/hierarchy/microsoft-connected-cache).
 
-Microsoft Connected Cache deployed directly to Windows relies on [Windows Subsystem for Linux] (windows/wsl/about) and either a [Group Managed Service Account](/windows-server/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/getting-started-with-group-managed-service-accounts), local user account, or domain user account are required to run WSL. WSL needs to run in a user context and any user, even if the currently logged-in user, could be used to run WSL and Microsoft Connected Cache.<br>
+Microsoft Connected Cache deployed directly to Windows relies on [Windows Subsystem for Linux](/windows/wsl/about) and either a [Group Managed Service Account](/windows-server/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/getting-started-with-group-managed-service-accounts), local user account, or domain user account are required to run WSL. WSL needs to run in a user context and any user, even if the currently logged-in user, could be used to run WSL and Microsoft Connected Cache.<br>
 
 ### Supported scenarios and deployments
 

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

@@ -23,10 +23,18 @@ summary: |
 sections:
   - name: Ignored
     questions:
-      - question: Is this product a free service?
-        answer: Yes. Microsoft Connected Cache is a free service.  
+      - question: What are the licesning requirement?
+        answer: Microsoft Connected Cache for Enterprise and Education is available to all Windows E3, E5 and F3 and Education A3 and A5 customers.
+      - question: Is there a charge to create MCC resources and cache node on Azure?
+        answer: No. You won't be charged to create MCC resource and cache nodes on Azure. However, you need an Azure pay-as-you-go subscription to create the resources but there is no charge for the resource itself.
       - question: Is there a nondisclosure agreement to sign?
         answer: No, a nondisclosure agreement isn't required.
+      - question: What will Microsoft Connected Cache for Enterprise and Education do for me? 
+        answer: "[Delivery Optimization](waas-delivery-optimization-reference.md) and Microsoft Connected Cache are Microsoft’s comprehensive solutions for minimizing enterprises’ internet bandwidth consumption, with Delivery Optimization acting as the distributed content source and Connected Cache as a dedicated content source. Microsoft customers have benefited from these solutions, seeing savings of more than 90% of bandwidth when managing Windows 11 upgrades, Autopilot device provisioning, Intune application installations, and monthly update deployments."
+      - question: Can I deploy Connected Cache to a production environment?
+        answer: The core caching engine of Microsoft Connected Cache is deployed to hundreds of ISPs globally and has been reliably delivering Microsoft content to customers. Connected Cache relies on production Azure services for the deployment and management of Connected Cache nodes and for Windows installations Windows Subsystem for Linux. Microsoft support is fully onboarded to support your organization whether you deploy Connected Cache in a lab for testing or in production.
+      - question: When will Microsoft Connected Cache for Enterprise and Education be made generally available (GA)?
+        answer: "[Delivery Optimization](waas-delivery-optimization-reference.md) and Microsoft Connected Cache are Microsoft’s comprehensive solutions for minimizing enterprises’ internet bandwidth consumption. Microsoft is committed to making Connected Cache generally available soon. Additionally, Microsoft support is fully onboarded to support your organization in whatever capacity you deploy Connected Cache."
       - question: What are the prerequisites and hardware requirements?
         answer:  | 
          - [Azure pay-as-you-go subscription](https://azure.microsoft.com/offers/ms-azr-0003p/).
@@ -48,25 +56,23 @@ sections:
         answer: For more information, see [Learn how to provision a Local User Account](https://support.microsoft.com/topic/104dc19f-6430-4b49-6a2b-e4dbd1dcdf32). Make sure that your gMSA has been granted permissions to "Log on as batch job" within the host machine's [local security policies](/previous-versions/windows/it-pro/windows-10/security/threat-protection/security-policy-settings/how-to-configure-security-policy-settings).
       - question: Where can I monitor cache node usage?
         answer: You can monitor your cache node usage on Azure portal. For more information, see [Monitor cache node usage Info on Reporting Capabilities](mcc-ent-monitoring.md).
-      - question: Does Microsoft Connected Cache support Xbox or Microsoft Teams content?
-        answer: Currently, Microsoft Connected Cache doesn't support Xbox or Microsoft Teams content. However, supporting Xbox content is of high priority, and we expect this feature soon. We'll let you know as soon as it becomes available!
       - question: How does Microsoft Connected Cache populate its content? Can I precache content?
         answer: Microsoft Connected Cache is a cold cache warmed by client requests at the byte range level so your clients only request the content they need. The client requests content and that is what fills the cache which means there's no cache fill necessary. "Preseeding" can be achieved but use of update rings. A test ring or early adopter ring can be used to fill the cache and all subsequent requests by other clients will come from cache.
       - question: How long would a piece of content live within the Microsoft Connected Cache? Is content purged from the cache?
-        answer: Once a request for said content is made, NGINX looks at the cache control headers from the original acquisition. If that content is expired, NGINX continues to serve the stale content while it's downloading the new content. We cache the content for 30 days. The content is 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 starts to delete content based on its own algorithm, probably some combination of least recently used.
+        answer: Once a request for said content is made, NGINX looks at the cache control headers from the original acquisition. If that content is expired, NGINX continues to serve the stale content while it's downloading the new content. We cache the content for 30 days. The content is in the hot cache path (open handles and such) for 24 hrs, but resides on disk for 30 days. The drive fills up and nginx starts to delete content based on its own algorithm, probably some combination of least recently used.
       - question: Is it possible to not update the Microsoft Connected Cache software or delay update longer than the timeline provided in the updates configuration?
-        answer: No. It's important to keep the Microsoft Connected Cache software up to date, especially when it comes to security issues. Microsoft validates updates prior to releasing Enterprises Connected Cache updates and will only release updates when it's necessary to keep customers secure or to ensure the continued successful operation of Connected Cache nodes for customers.  
+        answer: No. It's important to keep the Microsoft Connected Cache software up to date, especially when it comes to security issues. Microsoft validates updates prior to releasing Enterprises Connected Cache updates and only releases updates when it's necessary to keep customers secure or to ensure the continued successful operation of Connected Cache nodes for customers.  
       - question: How do I set up CLI?
         answer: For more information, see [How to install the Azure CLI](/cli/azure/install-azure-cli).
       - question: How do I install MCC extension?
-        answer: For more information, see [Install the Microsoft Connected Cache extension](mcc-ent-install-extension.md).
+        answer: For more information, see [Install the Microsoft Connected Cache extension](mcc-ent-manage-cache-using-cli.md#prerequisites).
       - question: What do I do if I have to set up or change existing proxy?
-        answer: You can enable proxy and provide proxy information on Azure portal or use the CLI. Don't forget to rerun the provisioning script after making any proxy changes. For more information, see [Set up or change existing proxy](mcc-ent-proxy.md).
+        answer: You can enable proxy and provide proxy information on Azure portal or use the CLI. Don't forget to rerun the provisioning script after making any proxy changes. For more information, see [Set up or change existing proxy](mcc-ent-create-resource-and-cache.md#proxy-settings).
       - question: How do we set up Microsoft Connected Cache if we support multiple countries or regions?
         answer: Microsoft Connected Cache isn't a service that has dependency on a specific Azure region, and there isn't personal or organizational identifiable information stored in the resource that necessitates data residency. The three regions that the Connected Cache resource can be deployed to are (Europe) North Europe, (Asia Pacific) Korea Central, and (US) West US.
       - question: Should I use a gMSA, local user, or domain account to deploy Microsoft Connected Cache to Windows?
         answer: There are pros and cons to the account options available to customers. We anticipate that security and manageability are top priories for customers. Microsoft provides guidance on both Active Directory and Microsoft Entra-based service accounts ([Introduction to Active Directory service accounts - Choose the right type of service account](/entra/architecture/service-accounts-on-premises#types-of-on-premises-service-accounts)) and user-based service accounts ([Secure user-based service accounts in Active Directory)](/entra/architecture/service-accounts-user-on-premises#assess-on-premises-user-account-security)).
       - question: Does the user have to be logged using the account that installed Microsoft Connected Cache on Windows or Linux?
-        answer: No. As part of the installation on Windows a scheduled task is created using the account used to install Connected Cache. Regardless of which user is logged in or not logged in, the schedule task remains running. On Linux Connected Cache is installed by the user and remains running regardless of which user is logged in to the OS.
+        answer: No. As part of the installation on Windows a scheduled task is created using the account used to install Connected Cache. Regardless of which user is logged in or not logged in, the scheduled task remains running. On Linux, Connected Cache is installed by the user and remains running regardless of which user is logged in to the OS.
       - question: What do I do if I need more support and have more questions even after reading this FAQ page?
-        answer: For further support for Microsoft Connected Cache, see [Troubleshooting issues for Microsoft Connected Cache for Enterprise and Education](mcc-ent-support-and-troubleshooting.md). If you still need more support, you can contact customer support.
+        answer: For further support for Microsoft Connected Cache, see [Troubleshooting issues for Microsoft Connected Cache for Enterprise and Education](mcc-ent-support-and-troubleshooting.md). If you still need more support, you can contact customer support.