diff --git a/windows/deployment/do/mcc-ent-create-resource-and-cache.md b/windows/deployment/do/mcc-ent-create-resource-and-cache.md index 754add9f0c..41d12b7c97 100644 --- a/windows/deployment/do/mcc-ent-create-resource-and-cache.md +++ b/windows/deployment/do/mcc-ent-create-resource-and-cache.md @@ -11,7 +11,7 @@ appliesto: - ✅ Windows 11 - ✅ Supported Linux distributions - ✅ Microsoft Connected Cache for Enterprise -ms.date: 10/30/2024 +ms.date: 03/19/2025 --- # Create Microsoft Connected Cache Azure resource and cache nodes @@ -20,7 +20,7 @@ This article outlines how to create and configure your Microsoft Connected Cache ## Prerequisites -1. **Azure Pay-As-You-Go subscription**: Microsoft Connected Cache is a free-of-charge service hosted in Azure. You'll need a pay-as-you-go Azure subscription in order to onboard to our service. To create a subscription, go to [pay-as-you-go subscription page](https://azure.microsoft.com/offers/ms-azr-0003p/). +1. **Azure Pay-As-You-Go subscription**: Microsoft Connected Cache is a free-of-charge service hosted in Azure. You need a pay-as-you-go Azure subscription in order to onboard to our service. To create a subscription, go to [pay-as-you-go subscription page](https://azure.microsoft.com/offers/ms-azr-0003p/). 2. **Hardware to host Connected Cache**: The recommended configuration serves approximately 35,000 managed devices, downloading a 2-GB payload in 24-hour timeframe at a sustained rate of 6.5 Gbps. For more information on sizing and OS requirements, see [the prerequisites for using Connected Cache](mcc-ent-prerequisites.md). @@ -28,8 +28,8 @@ For more information on sizing and OS requirements, see [the prerequisites for u ## Create Connected Cache Azure resource ->[!Note] - >* Resource move is not currently supported for Connected Cache Azure resources. If you need to move your Connected Cache Azure resource, you can consider deleting the existing resource and creating another one in another location. +> [!Note] +> Resource move isn't currently supported for Connected Cache Azure resources. If you need to move your Connected Cache Azure resource, you can consider deleting the existing resource and creating another one in a different location. # [Azure portal](#tab/portal) @@ -59,7 +59,7 @@ For more information on sizing and OS requirements, see [the prerequisites for u * Run [az version](/cli/azure/reference-index#az-version) to find the version and dependent libraries that are installed. To upgrade to the latest version, run [az upgrade](/cli/azure/reference-index#az-upgrade). - * Install Azure CLI extension **mcc** by following the instructions [here](/cli/azure/azure-cli-extensions-overview#how-to-install-extensions). + * Install Azure CLI extension `mcc` by following the instructions [here](/cli/azure/azure-cli-extensions-overview#how-to-install-extensions). * Resource group under which a Connected Cache resource can be created. Use the [az group create](/cli/azure/group#az-group-create) command to create a new Resource group if you don't already have one. @@ -83,7 +83,7 @@ az mcc ent resource create --mcc-resource-name --resource-group 1. Open Azure portal and navigate to the Microsoft Connected Cache for Enterprise resource that you created.
1. Under Cache Node Management, select **Cache Nodes** then **Create Cache Node**.
- 1. Provide a name for your cache node and select the host OS you plan to deploy the cache node on, then select **Create**. Note, cache node names have to be unique under the Microsoft Connected Cache resource. + 1. Provide a name for your cache node and select the host OS you plan to deploy the cache node on, then select **Create**. Note that cache node names have to be unique under the Microsoft Connected Cache resource. @@ -114,7 +114,7 @@ az mcc ent node create --cache-node-name --mcc-resource-name ```azurecli-interactive >az mcc ent node show --cache-node-name --mcc-resource-name --resource-group >``` ->In the output look for **cacheNodeState**. If ***cacheNodeState = Not Configured***, you can continue with cache node configuration. +>In the output, look for **cacheNodeState**. If ***cacheNodeState = Not Configured***, you can continue with cache node configuration. >If ***cacheNodeState = Registration in Progress***, then the cache node is still in process of being created. Wait a couple of minutes and run the command again. >To know more about different cache node state, see [Cache node states](#cache-node-states). @@ -141,7 +141,7 @@ Replace the following placeholders with your own information: * *\*: The size of cache drive. Must be at least 50 Gb. * *\*: If proxy needs to be enabled or not.
Accepted values: `enabled`, `disabled`
- Proxy should be set to enabled if the cache node will need to pass through a network proxy to download content. The provided proxy will also be used during deployment of the Connected Cache cache node to your host machine. + Proxy should be set to enabled if the cache node needs to pass through a network proxy to download content. The provided proxy will also be used during deployment of the Connected Cache cache node to your host machine. * *\*: The proxy host name or ip address. Required if proxy is set to enabled. * *\*: Proxy port number. Required if proxy is set to enabled. * *\*: Update ring the cache node should have.
@@ -174,7 +174,7 @@ Replace the following placeholders with your own information: * *\*: The size of cache drive. Must be at least 50 Gb. * *\*: If proxy needs to be enabled or not.
Accepted values: `enabled`, `disabled`
- Proxy should be set to enabled if the cache node will need to pass through a network proxy to download content. The provided proxy will also be used during deployment of the Connected Cache cache node to your host machine. + Proxy should be set to enabled if the cache node needs to pass through a network proxy to download content. The provided proxy will also be used during deployment of the Connected Cache cache node to your host machine. * *\*: The proxy host name or ip address. Required if proxy is set to enabled. * *\*: Proxy port number. Required if proxy is set to enabled. * *\*: Update ring the cache node should have.
@@ -218,7 +218,7 @@ To deploy cache nodes using Azure CLI, see | Field Name |Expected Value |Description| |---|---|---| -|**Cache node name** | Alphanumeric string that contains no spaces| The name of the cache node. You may choose names based on location such as "Seattle-1". This name must be unique and can't be changed later | +|**Cache node name** | Alphanumeric string that contains no spaces| The name of the cache node. You can choose names based on location such as "Seattle-1". This name must be unique and can't be changed later. | |**Host OS** | Linux or Windows| This is the operating system of the host machine that the cache node will be deployed to.| ### Storage fields @@ -243,12 +243,12 @@ To deploy cache nodes using Azure CLI, see #### Proxy settings
-You can choose to enable or disable proxy settings on your cache node. Proxy should be set to enabled if the cache node will need to pass through a network proxy to download content. The provided proxy will also be used during deployment of the Connected Cache node to your host machine. +You can choose to enable or disable proxy settings on your cache node. Proxy should be set to enabled if the cache node needs to pass through a network proxy to download content. The provided proxy will also be used during deployment of the Connected Cache node to your host machine.
>[!IMPORTANT] ->Enabling or disabling the proxy settings after your cache node has been deployed will require running the provisioning script on the host machine again. This will ensure that proxy changes are in effect on the cache node. +>Enabling or disabling the proxy settings after your cache node has been deployed will require running the provisioning script on the host machine again. This ensures that proxy changes are in effect on the cache node. | Field Name |Expected Value |Description| |---|---|---|