An Azure service that provides global content delivery and acceleration.
The published Microsoft Connected Cache documentation does not establish a supported in-place resize procedure for an already provisioned Windows Server/WSL2 node, so obtain confirmation from Microsoft Support before deleting, uninstalling, or redeploying the healthy node.
What the documentation confirms
For a Windows-hosted node:
- The cache path must remain
/var/mcc. - The requested allocation is represented as
/var/mcc,400. - The deployment parameter is
-cacheDrives "/var/mcc,400". ^1^ - Azure CLI exposes
az mcc ent node update --cache-drivefor configuring a node. A successful configuration reportsoperationStatus = Succeededand places the node inNot Provisionedstate. However, the documented sequence applies before initial deployment; it does not say that this command can resize an already provisioned Windows node in place. ^2^
Consequently, do not run az mcc ent node update against the production node on the assumption that it is a live resize operation.
Information to give Microsoft Support
Request confirmation of whether the existing node can be transitioned back to Not Provisioned and redeployed with a larger cacheDrives value, or whether a replacement node is required. Include:
- Windows Server 2025 with WSL2
- Current allocation: 200 GB
- Requested allocation: 400 GB
- Current cache-node state and deployment application version
- Whether the node was created before or after GA
- Existing HTTPS/TLS and proxy configuration
- The MCC resource and cache-node names, but do not post keys or GUIDs publicly
Check the installed deployment application version with:
Get-AppxPackage Microsoft.DeliveryOptimization |
Select-Object Name, Version
deliveryoptimization-cli mcc-get-scripts-path
The Windows deployment documentation notes that parameters can differ by application version. Deployment must use Windows PowerShell 5.1 rather than PowerShell 7.x. ^1^ ^3^
If Microsoft confirms reconfiguration and redeployment of the same node
The documented configuration shape would be:
az mcc ent node update \
--cache-node-name <node> \
--mcc-resource-name <resource> \
--resource-group <resource-group> \
--cache-drive "[{physical-path:/var/mcc,size-in-gb:400}]"
After operationStatus becomes Succeeded and the node reports Not Provisioned, retrieve fresh deployment details:
az mcc ent node get-deployment-details \
--cache-node-name <node> \
--mcc-resource-name <resource> \
--resource-group <resource-group>
The deployment command would then contain:
-cacheDrives "/var/mcc,400"
Use the values returned by get-deployment-details; the registration key is refreshed after a successful deployment attempt. Preserve and reapply the existing TLS/proxy parameters. ^1^ ^2^
Before proceeding, ensure the host volume has enough capacity for the requested allocation and plan for service interruption. The documentation does not specify whether existing cached content is retained during this operation.
If Microsoft requires node replacement
Treat this as destructive and plan downtime. The documented uninstall workflow says to delete the cache node in Azure first, then run uninstallmcconwsl.ps1 as administrator using the original runtime-account credentials. The script removes the container and related components and unregisters the Connected Cache application from further updates. ^4^
For a current deployment, locate the scripts with:
Set-Location (deliveryoptimization-cli mcc-get-scripts-path)
If Azure Portal → Cache Nodes shows Migrated = No, it is a Public Preview deployment; use the original <installationFolder>\MccScripts directory instead. The uninstall documentation provides a separate Public Preview procedure. ^4^
Do not remove the Appx package separately unless instructed as part of the replacement process; that additional command removes the application and installation scripts for all users.
References