LIFECYCLE INSIGHTS

Troubleshooting Microsoft 365 Integrations

Originally published on Lifecycle Insights's help center · View live article ↗

Why this piece is featured

A strict Issue → Cause → Resolution structure repeated across three unrelated problems, including a real licensing nuance most people wouldn't think to check.

This article outlines how to resolve some commonly reported issues with Microsoft 365 data not syncing or displaying correctly in Lifecycle Insights.

De-identified or random data in the user list

Issue. User names and emails appear as random strings or GUIDs in the Lifecycle Insights user list, and may also appear that way in other Microsoft tools using the same usage report data.

Cause. By default, Microsoft reports conceal information such as usernames, groups, and sites. Since Lifecycle Insights uses the same reporting API, this information is obfuscated unless the setting is changed in your Microsoft 365 admin center.

Resolution. Update the reporting privacy setting for each tenant:

  1. Sign in to your Microsoft 365 admin center.
  2. Go to Settings > Org Settings > Services > Reports.
  3. Clear the Display concealed user, group, and site names in all reports checkbox, and click Save.
  4. Run a manual sync in Lifecycle Insights, or wait for the next scheduled sync.

User-level MFA data missing or sync errors appearing

Issue. The Microsoft 365 MFA Status and Authentication Methods columns are missing from the user list, and errors appear in Data Sync Manager or under Administration > Integrations > Microsoft 365 > Log/Sync.

Cause. Microsoft only returns user-level MFA data via API if the tenant has a Microsoft Entra ID P1 or P2 license (formerly Azure AD Premium P1/P2) and Conditional Access Policies are implemented. If either condition isn't met, Microsoft blocks this data from being returned.

Resolution. Confirm the tenant has Azure AD Premium P1 or P2 licensing and has enabled Conditional Access Policies. After meeting these requirements, Microsoft may take up to one week to begin returning MFA data.

Old or stale data showing in the user list

Issue. Data in the User List appears outdated — for example, the report shows a Last Refresh date from several days in the past.

Cause. Microsoft's reporting APIs don't return real-time data; returned data is typically 1-7 days old. This applies across all Microsoft reporting tools.

Resolution. No action is required. Lifecycle Insights displays the most recent data available through Microsoft's API.

← Back to index