An Azure service that provides secure managed services and access control for partners and customers.
Hello RobE
Thank you for posting your query on Microsoft Q&A platform.
Service incidents for Microsoft 365 Lighthouse and its dependencies (Microsoft Intune, Microsoft Entra identity services, and MDM cloud services) are surfaced in the Service health page inside Lighthouse itself, not always in the main Microsoft 365 admin center view. From there you can open the Issue history to see past incidents and the Tenants affected tab to see exactly which of your managed tenants were impacted.
To verify Friday's incident, please do this:
- Sign in to https://lighthouse.microsoft.com/ with an account that has the
microsoft.office365.serviceHealth/allEntities/allTaskspermission (any Entra role that includes this, such as Service Support Administrator, will work). - In the left navigation, select Service health.
- Open the All issues tab → switch to Issue history and filter to Friday's date.
- Click the issue to view the Overview (status, user impact, history) and the Tenants affected tab. You can export the affected tenant list to**.csv** to share with your team.
If you can't sign in to Lighthouse at all, check the public Microsoft service health status page for known sign-in issues affecting partner tenants.
About the "it will take 24 hours" message: That message is not an incident ETA, it's the standard Lighthouse data sync window. Lighthouse aggregates data from Intune, Entra, and MDM services, and certain views (OneDrive data, threat details, tenant onboarding state, DAP/GDAP role changes) take time to refresh:
- OneDrive data in the user details pane can show a "may take up to 24 hours" message until the underlying service catches up.
- Threat name missing scenarios self-resolve within 48 hours with no action needed.
- DAP role permission changes can take up to 30 minutes to reflect in Lighthouse.
So, if the "24 hrs" notice you saw is on a data tab (Users, OneDrive, Threats, Tenants), that's expected behavior wait out the documented window before treating it as an incident. The full list is in the Known issues article: Known issues with Microsoft 365 Lighthouse.
If the issue isn't listed anywhere and persists past the documented window:
Open a support request from inside Lighthouse so the engineering team can pull backend logs scoped to your partner tenant:
- In Lighthouse, click the ? (Help & support) icon in the top-right.
- Describe the issue and include the full product name Microsoft 365 Lighthouse.
- On the affected page, select Show diagnostics, save the JSON, and attach it to the ticket.
Reference:
- View tenant service health in Microsoft 365 Lighthouse — learn.microsoft.com [learn.microsoft.com]
- Known issues with Microsoft 365 Lighthouse — learn.microsoft.com [learn.microsoft.com]
- Microsoft service health status (public page) — status.cloud.microsoft [status.clo....microsoft]
Thanks,
Suchitra.