Del via

Release Notes for Microsoft Connected Cache for Enterprise and Education

This article contains details about the latest releases of Connected Cache.

Latest release: Windows deployment application, Linux deployment package

Released on 3/3/2026

This release consists of a new Windows deployment application version and a new Linux deployment package version that can be downloaded. Customers who wish to take advantage of the improvements in this release must redeploy their cache nodes using the new versions of the deployment application or package.

New Windows-hosted deployment application version

This version of the Windows deployment application contains fixes for known bugs and improvements to enhance the installation and TLS-configuration experience of Connected Cache on Windows-hosted cache nodes.

Bug fixes and improvements

  • Fixed Windows permissions for HTTPS configuration: Fixed a bug that could cause TLS certificate import to fail due to insufficient permissions on Windows 11, Windows Server 2022, and Windows Server 2025 host machines.
  • Resolved TLS-inspecting proxies causing HTTPS configuration issues: Fixed a bug that could cause HTTPS configuration to fail when a TLS-inspecting proxy is present.
  • Added port mapping for port 443: Deployment script now creates the necessary port mapping for port 443, streamlining the HTTPS configuration process.
  • Expanded deployment prerequisite checks: Added new prerequisite checks to identify potential issues that could cause deployment failure.
    • Check if the provided MccRuntimeAccount is the same as the account being used to run the deployment command.
    • Moved the disk space check earlier in the deployment sequence to catch blocking issues earlier.
    • Check if the deployment script is being run using PowerShell 7, which isn't currently supported for Connected Cache deployment.
    • Check if the IP helper service is running, which is required for Connected Cache compatibility with proxy.
  • Added connectivity checks within WSL distribution: Added new connectivity checks within the WSL distribution on Windows-hosted cache nodes to identify potential network issues that could cause deployment failure, such as DNS resolution issues or inability to reach required endpoints.
  • Updated log file format: Updated the file format of log files to .log to be more compatible with common third-party log analysis tools, making it easier for users to analyze logs and identify issues.
  • Standardized runtime account parameter names: Standardized the parameter names related to the Connected Cache runtime account across all deployment, TLS configuration, and uninstall scripts to improve consistency and reduce confusion for users. The runtime account parameters are now consistently named -mccRunTimeAccount and -mccLocalAccountCredential across all scripts.
  • Added optional deployment command parameters for firewall rule creation: Added three new optional parameters to the deployment command that allow users to specify whether the deployment script should configure firewall rules for HTTP, HTTPS, and remote access to the cache node's terse summary page.
    • -IsHttpsFirewallEnabled: Instructs the deployment script to create a firewall rule for port 443, which is necessary for the cache node to download content over HTTPS. This parameter is optional and defaults to true.
    • -IsHttpFirewallEnabled: Instructs the deployment script to create a firewall rule for port 80, which is necessary for the cache node to download content over HTTP. This parameter is optional and defaults to true.
    • -IsSummaryPublic: Instructs the deployment script to create a firewall rule and add port forwarding for port 5000, allowing remote access to the cache node's terse summary page. This parameter is optional and defaults to false.
  • Improved uninstall script: Updated the uninstall script to provide more detailed error messages when required credentials are missing or invalid. Additionally, the uninstall script will now attempt removal of any Connected Cache VHDX file present in installation directory, resulting in a more comprehensive cleanup of cache node resources during uninstallation.

New Linux-hosted deployment package version

This version of the Linux deployment package contains fixes for known bugs and improvements to enhance the installation and TLS-configuration experience of Connected Cache on Linux-hosted cache nodes.

Bug fixes and improvements

  • Fixed hanging HTTPS configuration: Fixed a known bug that caused the certificate import step of HTTPS configuration to run indefinitely, preventing successful HTTPS configuration. With this fix, cache nodes should now be able to successfully complete HTTPS configuration.
  • Improved permissions for certificate folder: Added permissions for the /certs folder during the generateCsr.sh script, allowing non-Adminsitrator accounts the ability to drop their signed certificates before running importCert.sh.
  • Added ShowCertDetails script: Added a new script ShowCertDetails.sh that displays details of the TLS certificate currently imported to the cache node, allowing users to verify that the correct certificate has been imported and identify potential issues with the certificate.

Latest release: GA container release v2.0.0.2124_e

Released on 3/3/2026

This release consists of a new Connected Cache container version that will begin rolling out to all GA cache nodes on the fast ring starting on 3/2/2026. For GA cache nodes configured to be on the slow ring, this container version will be rolled out starting on 4/6/2026. No action is required on GA cache nodes to receive this update.

New Connected Cache container version

  • v2.0.0.2124_e

This container version contains fixes for known bugs that were causing TLS configuration to fail.

Bug fixes and improvements

  • Certificate import fix: Fixed a known bug that caused the certificate import step of TLS configuration to run indefinitely, preventing successful TLS configuration. With this fix, cache nodes should now be able to successfully complete TLS configuration.
  • TLS support when unauthenticated proxy is present: Fixed a known bug that caused TLS content requests to fail when an unauthenticated proxy is present. With this fix, cache nodes should now be able to successfully retrieve TLS content even when an unauthenticated proxy is present.

GA container release v2.0.0.2119_e

Released on 11/17/2025

This release consists of a new Connected Cache container version that will begin rolling out to all GA cache nodes on the fast ring starting on 11/17/2025. For GA cache nodes configured to be on the slow ring, this container version will be rolled out starting on 1/6/2026. No action is required on GA cache nodes to receive this update.

Cache nodes still on the Public Preview release must be migrated to the GA release to receive this new container version.

New Connected Cache container version

  • v2.0.0.2119_e

This container version contains various fixes and improvements to enhance the stability and performance of Connected Cache, especially on host machines with limited resources.

Known issues

  • Certificate import hangs indefinitely: This container version has a known bug where the container's internal buffer isn't cleared during importCert, causing the certificate import process to run indefinitely. The cache node remains functional even if this bug is encountered, but TLS configuration won't complete successfully. This issue will be fixed in an upcoming container update.
  • TLS content requests fail when unauthenticated proxy is present: This container version has a known bug where the cache node's TLS content requests fail if an unauthenticated proxy is present. The cache node is still able to retrieve non-TLS content even if this bug is encountered. This issue will be fixed in an upcoming container update.

Bug fixes and improvements

  • Fixed memory leak in Connected Cache container: Fixed a memory leak in the Connected Cache container that could cause the cache node to shut down, rendering it unhealthy in the Azure portal and unable to serve some content hosts. This fix improves the stability and reliability of cache nodes.
  • Reduced frequency of chart serialization: Reduced the frequency of chart serialization in the Connected Cache container, reducing disk write operations that could compete for I/O resources on less powerful cache node host machines. This change improves the performance of cache nodes, especially on host machines with limited resources.
  • Improved terse summary page: Revised the terse summary page to improve readability and added a new chart showing egress distribution across content hostnames. Added HTTPS certificate details if cache node has completed HTTPS configuration. These enhancements provide better visibility into cache node performance and usage patterns.
  • Added new HTTPS hostnames for Intune content: Added new HTTPS-supporting Intune hostnames to the list of supported content hosts for Connected Cache. This ensures that cache nodes can effectively download and cache Intune content using HTTPS when configured to do so.
  • Added support for HTTPS configuration in TLS-inspecting proxy: Improved the handling of HTTPS configuration when a TLS-inspecting proxy is present. This enhancement ensures that cache nodes can successfully configure HTTPS support even when operating behind a TLS-inspecting proxy.
  • Security improvements: Kept intentionally vague to protect previous versions of Connected Cache.

General Availability Release

Released on 7/23/2025

This release contains improvements that can only be applied by redeploying your cache nodes using the updated Linux-hosted deployment package or the new Connected Cache Windows application.

New Connected Cache container version

  • v2.0.0.2112_e

    This container version contains changes to mitigate a regression caused by an Ubuntu OS change to how user IDs are assigned. This is a breaking change that requires you to migrate your Public Preview cache nodes to the GA release by redeploying them using the updated Linux deployment package or the new Connected Cache Windows application. You can use the Azure portal to check the GA migration status of your Public Preview cache nodes. For more information, see GA migration status.

New Windows-hosted deployment application

  • v1.0.24.0

    This is the first release of the Connected Cache Windows application, which replaces the previous bundle of installation scripts. The new application simplifies the installation of Connected Cache on Windows-hosted cache nodes.

New Linux-hosted deployment package version

  • v1.09

New capabilities

  • Connected Cache Windows application: We're introducing a new Connected Cache Windows application that streamlines the installation of Connected Cache on Windows-hosted cache nodes. This first iteration focuses on providing autoupdate functionality for the files used to keep the Connected Cache operational after installation.
  • Configure cache nodes to support Intune and Teams content via HTTPS: You can now configure your Windows-hosted and Linux-hosted cache nodes to support download of Intune and Teams content via HTTPS. This allows for secure and efficient caching of content needed by these services, improving performance and reducing bandwidth usage.
  • Script to update Scheduled Tasks on Windows-hosted cache nodes: A new PowerShell script is available to update the credentials used by Connected Cache Scheduled Tasks on Windows-hosted cache nodes. This script should be run when the Connected Cache runtime account password is changed. It ensures that the Scheduled Tasks continue to run with the correct credentials, preventing potential issues with scheduled task execution.
  • Terse summary page for Connected Cache: A new terse summary page is available for cache nodes that use the GA container version. This page provides a quick overview of the cache node's status, performance, and configuration, making it easier to monitor and manage your cache nodes. Instructions for accessing the summary page are available in the Connected Cache monitoring documentation.

Bug fixes and improvements

  • Windows-hosted cache nodes no longer grow past their configured disk size: Fixed a bug that caused Windows-hosted cache nodes to grow past their configured disk size, potentially leading to performance issues and storage constraints. This fix necessitates that the minimum disk size for all cache nodes is now 100 GB. If your existing cache nodes have a disk size smaller than 100 GB, you must reconfigure and redeploy them.
  • Added support for non-English locales on Windows: Connected Cache installation on Windows now supports non-English locales, improving accessibility and usability for international customers.
  • Added support for file paths with spaces on Windows: Fixed a bug that caused issues when file paths contained spaces during the installation of Connected Cache on Windows. This change ensures that cache nodes can be installed and configured correctly regardless of file path formatting.
  • Removed X-FF header conflict with ZScaler: Removed the X-Forwarded-For (X-FF) header from the HTTP requests made by the Connected Cache container in order to prevent traffic routing issues in networks using ZScaler.
  • Renamed "Provisioning" to "Deployment": The term "Provisioning" has been replaced with "Deployment" in the Azure portal, public documentation, script names, and Azure CLI commands to better align with industry terminology and improve clarity for users.

February 2025 Release

Released on 3/03/2025

This release contains improvements that can only be applied by redeploying your cache nodes using the updated installation script.

New Connected Cache container version

  • v1.2.1.2083_E

New Linux-hosted installation script version

  • v1.08

New Windows-hosted installation script version

  • v2.0.0.3

Improvements to Windows-hosted cache nodes

  • Connected Cache WSL distribution now uses Ubuntu 24.04: The Windows Subsystem for Linux (WSL) distribution used by Connected Cache has been updated to Ubuntu 24.04 (was 22.04). This change ensures that the WSL distribution is up-to-date with the latest security patches and features.
  • Connected Cache container now uses Ubuntu 24.04 Docker environment: The Connected Cache container now runs using an Ubuntu 24.04 Docker environment (was 22.04). This change ensures that the container environment is up-to-date with the latest security patches and features.
  • TLS-inspecting proxies no longer cause IoT Edge error during Connected Cache installation: Fixed a bug that was causing proxy certificate path string to be improperly handled, leading to IoT Edge errors during Connected Cache installation. Added an intermediate certificate verification step to the installation process on both Windows-hosted and Linux-hosted cache nodes. Direct calls to *.prod.do.dsp must be enabled for installation to succeed.
  • Security improvements: Kept intentionally vague to protect previous versions of Connected Cache.

Improvements to Linux-hosted cache nodes

  • Connected Cache container now uses Ubuntu 24.04 Docker environment: The Connected Cache container now runs using an Ubuntu 24.04 Docker environment (was 22.04). This change ensures that the container environment is up-to-date with the latest security patches and features.
  • TLS-inspecting proxies no longer cause IoT Edge error during Connected Cache installation: Fixed a bug that was causing proxy certificate path string to be improperly handled, leading to IoT Edge errors during Connected Cache installation. Added an intermediate certificate verification step to the installation process on both Windows-hosted and Linux-hosted cache nodes. Calls to *.prod.do.dsp must be enabled for installation to succeed.
  • Security improvements: Kept intentionally vague to protect previous versions of Connected Cache.

Windows-hosted install script v2.0.0.2

Released on 2/7/2025

This release only contains changes to the Windows-hosted installation scripts for Connected Cache. To take advantage of these changes, you need to redeploy your existing cache nodes using the updated installation script.

Improvements

  • Removes dependency on AMQP/MQTT ports: Cache nodes deployed using this updated installation script will no longer use AMQP (5671) or MQTT (8883) ports. This change simplifies the network configuration for cache nodes and reduces the number of ports that need to be opened in your network security group.
  • Improves cleanup during uninstall: Windows-hosted cache nodes will now remove port proxy rules when uninstalled using the uninstallmcconwsl.ps1 script. This change ensures that the host machine's WSL port-forwarding rules are cleaned up properly when uninstalling Connected Cache.
  • Changes install error codes from decimal to hex code: Install error codes for Windows-hosted cache nodes are now displayed in hex code format, improving error code readability.
  • Uses configured proxy to perform install: If a proxy was configured for the Windows-hosted cache node in Azure portal, the cache node uses the specified proxy during installation.

Public Preview Release

Released on 10/30/2024

For customers that installed earlier versions of Connected Cache, this release contains breaking changes that affect both Linux-hosted and Windows-hosted cache nodes. See the early preview documentation page for more details.

New Connected Cache container version

  • v1.2.1.2076_E

Feature updates

  • Metrics and charts in Azure portal: You can now visualize Outbound egress and Volume by Content type charts for your cache node on Azure portal. You can also create custom monitoring charts for your cache nodes. This capability is under the Metrics tab on Azure portal.
  • Cache nodes for Windows or Linux host machines: Cache nodes can now be created and deployed to Windows host machine or Linux host machines by choosing the OS when creating cache nodes.
  • Ubuntu 22.04 LTS: Cache nodes can now be deployed on Ubuntu 22.04 LTS.
  • Azure CLI support: Cache nodes can now be created and managed via Azure CLI.
  • Proxy: We added support for unauthenticated proxy and cloud proxy integration.
  • Updates: Your cache nodes are now updated automatically and we also added the capability to set each cache node's update ring to govern the cadence of Microsoft Connected Cache container updates.

Fixes

  • We fixed various bugs to achieve a smoother installation experience.

Related content

  • Last updated on