Reminder: Intune-managed Win32 app delivery will be HTTPS-only, affecting Connected Cache customers

Starting today, Intune will be enforcing HTTPS-only delivery for managed Win32 app content

Why this matters for Connected Cache customers:

if HTTPS isn't configured on your cache nodes, clients that previously pulled Intune Win32 app content through Connected Cache can still download content, but those requests bypass cache nodes and fall back to CDN. This behavior can increase internet egress and bandwidth usage. 

This enforcement was previously announced in February via Message Center and the Intune Tech Community blog: How to enable HTTPS support for Microsoft Connected Cache for Enterprise and Education.

Get started with the following documentation:

Configure HTTPS on your cache nodes

• HTTPS setup on Windows
• HTTPS setup on Linux

Validate HTTPS functionality

• Validate HTTPS on Windows
• Validate HTTPS on Linux 

Additionally, you can verify Intune Win32 HTTPS enforcement on a client machine 

1. Open C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\AppWorkload.log. 
2. Find log entries that include the app download URL for the app assignment you are validating. 
3. Confirm the URL is HTTPS (for example, starts with https://). 
4. Optionally correlate with Delivery Optimization status to verify whether bytes are being served from cache versus CDN. 

Configuration Manager customers

If you're using Configuration Manager distribution points with Connected Cache, review and apply the published hotfix and prerequisites: Connected Cache update for Microsoft Configuration Manager versions 2409, 2503, and 2509 (KB33247081). 

 

If you'd find it useful, reply in this thread and we can also post a step-by-step TLS setup walkthrough video for the Connected Cache community.