Starting on June 16 th , 2026, or soon after, Intune will enforce HTTPS content delivery for customers using Microsoft Connected Cache for Enterprise and Education. To continue using Microsoft Connec...
Updated Feb 20, 2026
Version 2.0
Blog Post
15 MIN READ
How to enable HTTPS support for Microsoft Connected Cache for Enterprise and Education
While we understand the security intent in HTTPS enforcement, this adds huge administrative overhead in large environments. With 100's of MCC deployments we would have to manually manage that many additional certificates for a simple caching service.
Please delay HTTPS enforcement until "bring your own certificate" is fully implemented and supports all certificate formats and types. Alternatively, provide automatic certificate management with Cloud PKI or provide an Intune policy to allow clients to continue trusting HTTP sources.
- adityamiddha
Microsoft
Thanks for raising this. Large environments with hundreds of cache nodes are exactly the scenarios we’re thinking about, so we recognize the administrative overhead the current certificate workflow can create at that scale.
As mentioned in the earlier response, the HTTPS enforcement timeline can’t be delayed further. That said, we intentionally provided significant lead time, and our priority is to reduce the operational burden customers face before the enforcement date.
Enabling “Bring Your Own Certificate” is a key part of that effort. We’re also actively looking at ways to make renewal and lifecycle management easier over time, including how this could better align with existing enterprise PKI and automated certificate management solutions.
We appreciate the feedback and it’s directly influencing how we’re prioritizing improvements ahead of enforcement. I urge you to utilize our MCC Tech Community blog space for other feedback you may have: Microsoft Connected Cache for Enterprise and Education | Microsoft Community Hub
