Forum Discussion
Microsoft 365 Apps admin center - No Devices Being Managed?
We are an Office 365 E3 customer, and have configured Cloud Update for our devices. However, devices are not updating, and I see the message "0/27 devices are being managed by Cloud". Any idea what I need to do to get updates rolling out?
Thanks!
3 Replies
Usually that "0 devices managed" status means the Office Click-to-Run client isn't successfully checking into config.office.com, or device telemetry is getting blocked before Microsoft can inventory them.
A few quick things I'd look into:
Diagnostic data settings. If your GPO or Intune policy sets Office diagnostic data to Off or Security instead of Optional/Required, the portal won't see those endpoints.
Network rules. Make sure your firewall or proxy isn't dropping traffic to *.config.office.net or *.officeconfig.msocdn.com. The onboarding fails silently if those endpoints are blocked.
Tenant group assignments. Double check under Cloud Update settings to see if your target device groups are properly assigned or if there's an active exclusion policy blocking those 27 machines.
Keep in mind that even after fixing telemetry or network access, it usually takes 24 to 48 hours for devices to report back to the portal once users launch an M365 app.
Usually that "0 devices managed" status means the Office Click-to-Run client isn't successfully checking into config.office.com, or device telemetry is getting blocked before Microsoft can inventory them.
A few quick things I'd look into:
Diagnostic data settings. If your GPO or Intune policy sets Office diagnostic data to Off or Security instead of Optional/Required, the portal won't see those endpoints.
Network rules. Make sure your firewall or proxy isn't dropping traffic to *.config.office.net or *.officeconfig.msocdn.com. The onboarding fails silently if those endpoints are blocked.
Tenant group assignments. Double check under Cloud Update settings to see if your target device groups are properly assigned or if there's an active exclusion policy blocking those 27 machines.
Keep in mind that even after fixing telemetry or network access, it usually takes 24 to 48 hours for devices to report back to the portal once users launch an M365 app.
Wanted to also get insight into this request. I have a handful of devices that refuse to register or show up in config.office.com.
One of the devices I'm troubleshooting has the correct tenant association key in the registry below.
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\cloud\office\16.0\Common\officesvcmanager
It also shows a successful value of 200 for the check in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\C2RSvcMgr
