Microsoft Connected Cache verification stuck after provisioning (IoT Edge running but portal not moving forward

Hello Al Jazeera Telecom,

Thanks for reaching out—this issue with Microsoft Connected Cache (MCC) verification getting stuck after provisioning is definitely frustrating, especially when everything on the IoT Edge side looks healthy.

Here’s a more targeted troubleshooting checklist to help finalize the verification process:

You can try for these Quick Checks:

1. IoT Edge Modules\ Confirm that edgeAgent, edgeHub, and the MCC module are all running via:

      sudo iotedge list
   

2. If MCC isn’t listed, it may not have been deployed correctly.
3. DNS Resolution\ You mentioned containers can resolve mcr.microsoft.com, which is great. Also ensure outbound connectivity to Azure endpoints used by MCC (like *.blob.core.windows.net, *.azureedge.net, etc.).
4. Logs Review\ Run:

      sudo iotedge system logs -- -f
   

   Look for any errors or warnings related to MCC provisioning or module startup.
5. Restart Edge Runtime\ Sometimes a refresh helps:

      sudo systemctl restart      iotedge
   

For Azure Portal Stuck at Verification

The message:

“Congratulations, you are now verified. Please wait for a few minutes and refresh your page to move onto the next step.”

…is typically shown after successful DNS and module validation. If it persists for more than 24 hours:

• Try a different browser or clear cache to rule out UI issues.
• Check the MCC resource in Azure Resource Explorer to see if credentials were generated but not surfaced in the portal.
• Verify that the MCC module is reporting status back to Azure—this is key for the portal to move forward.

Ref. doc: https://dori-uw-1.kuma-moon.com/en-us/windows/deployment/do/mcc-ent-create-resource-and-cache?tabs=portal

Hope this helps!
Thank you!

Hello Al Jazeera Telecom,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Thank you!

Hello Al Jazeera Telecom,

Following up to see if the above response was helpful. Please let us know if you have any queries.

Thank you!

Hello VSawhney,

Thanks for your follow-up. The MCC node is now provisioned and shows as Healthy in the Azure portal, and the IoT Edge + MCC container are running fine.

However, we are not yet seeing traffic being cached. Do we need to configure any static DNS forwarding rules on our resolver, or should the traffic redirection happen automatically once the node is healthy and verified?

Appreciate your guidance.

Best regards,

Bakr Ahmed