I think MCC's should be a critical companion service on literally any customer network for efficient app deployment from Intune. The fact that it can run under Windows 11, and doesn't need a Server OS, means it's available to any appropriately licensed customer willing to assign a device to the purpose. I don't think it should be treated or thought of as not the Intune team's concern. Not every customer is going to have super-fast Internet service. Even if you have fast Internet, an MCC is still more efficient. Why waste bandwidth. It can't be good for energy consumption.

The size of these packages, I appreciate is rare. We have a package that is 28.2GB and another two that are around 18GB. It's for a new self-deploying Windows client going into emergency services vehicles (it's a mapping app and documentation library) and we have around 700 targets for this. Intune delivers them just fine, but we have positioned an MCC on the same switch and VLAN, in our build room and hoped it would help. We've run the deployment many times now since early November last year but it doesn't seem to be retrieved from the MCC. It can literally take an entire day for the Autopilot build to complete because of this. Our current Internet feed isn't up to the job. We need to be building 100/week and had hoped to avoid as much human intervention as possible.

I have posted about this within the Intune Infrastructure discussions in the Management CCP Teams chat, where Jason Sandys replied and said he'd discussed with the MCC PM. He mentioned the requirement for the Intune Win32 content needing to be requested 3+ times before it will be cached. We must be past that by now. 

Metrics don't seem to reflect the cache is supporting this or much else at all. It's almost as though it's not doing any Win32 packages. This was 7 days activity:

HTTPS is enabled on the cache.

On all caches, seeing more realistic figures for Windows Updates/Store, Office, Edge and Teams. Intune figures just seem low. It's similar on our main MCC's feeding our normal corporate clients.

I wondered if content needed to be flagged [by Intune] in any particular way to end up on these caches? Could it be the Intune end that's not doing enough? Are we missing a trick? Could the recent shift to AFD be to blame (at either end)? How can I diagnose what's going wrong further?

Support Request has been logged with the same email address I am posting with here.

I was starting to fear that I'm experiencing another nightmare caused by our decrypting transparent proxy. However, I can see some Intune and Teams content coming through. So, I'm not convinced it's being interfered with at our end. 30 days for the MCC's I've deployed so far:

The Intune content is nowhere near showing the 20 devices built with the massive packages.

Would be useful for anyone else who's not experienced any issues with delivery of Win32 apps that are excessively large [Ideally, 17GB and above] to let me know it does work. This will allow me to prioritise investigating proxy interference here.

AndrewMcN_SFRS​ the panelists raised your question at around 24:36 in the live AMA. They requested you please share more details about this issue so they can help. Thanks!