I never found a solution for storing favorite recipes that wasn't very manual or required signing up for a service. As I explore the world of software development and solutions-as-code, I chose this as a problem statement for a DIY approach. What I really should do is find a cheap printer and have a physical binder full of recipes like they did in the olden days, but that's no fun...

The requirements for this project were simple, or so I thought: Save recipes from the web in a readily accessible and usable format. I didn't realize until later that I had many more requirements I had not discovered. In the end, valuable lessons were learning about knowing your requirements and... just knowing more?

September 2025 Update: This article was written using the preview version of MCC, which has since been updated to global availability. Some features may have changed and issues may have been fixed.

After a long 3 weeks of fumbling around with Microsoft Connected Cache (MCC) and the underlying technologies, I determined that the issue with my deployment ultimately stemmed from the lack of proxy support in the installation scripts. While the root cause of your problem will most likely be different from mine, the steps listed below are a good start to diagnose several possible issues and to aid general understanding the of the application.

I'll be covering the installation of MCC on a Windows 2022 Server with unauthenticated proxy support.

I started exploring Microsoft Connected Cache (MCC) for Enterprise and Education as a potential enabler for transitioning endpoint managment from SCCM on-premise to Microsoft Intune in the cloud. Intune offers many new features and improved off-network reliability when compared with SCCM, but supporting this requires a strong connection to the internet. The Microsoft CDN traffic overwhelms my corporate network's small and heavily utilized WAN links, making local caching and peering essential for reducing network congestion. I thought this couldn't be done until I saw MCC.