Forum Discussion
Feature Usage and Adoption Report - No New Data
- 11 months ago
Hi cdfizz17 ,
Thank you for the update, It won’t appear as a normal user in Entra. That service principal should have AuditLog.Read.All and Report.Read.All permissions.Since you already re-ran the setup and the issue persists, the next steps are:
1.Verify in Entra Enterprise Applications if the app/service principal for Feature Usage and Adoption exists and still has the required permissions.
2.Double-check monitoring settings (all needed workspaces/capacities are included).
3.If everything looks correct, this is likely a service-side issue. At that point, the best action is to open a Microsoft support ticket with your tenant ID so the ingestion pipeline can be reviewed and restored if needed.
Best Regards,
Community Support Team
Hi rohit1991
rohit1991 wrote:
Confirm audit logging is enabled in Microsoft 365 Compliance.
Check audit log retention (30–90 days depending on license). If data is older, it won’t load.
I have confirmed that this is enabled.
rohit1991 wrote:
Verify the service account has AuditLog.Read.All and Report.Read.All permissions.
What is the name of the service account? I don't see anything in Entra portal.
I have deleted the workspace and re-run the setup, but this did not help.
Thank you for the detailed reply.
Hi cdfizz17 ,
Thank you for the update, It won’t appear as a normal user in Entra. That service principal should have AuditLog.Read.All and Report.Read.All permissions.
Since you already re-ran the setup and the issue persists, the next steps are:
1.Verify in Entra Enterprise Applications if the app/service principal for Feature Usage and Adoption exists and still has the required permissions.
2.Double-check monitoring settings (all needed workspaces/capacities are included).
3.If everything looks correct, this is likely a service-side issue. At that point, the best action is to open a Microsoft support ticket with your tenant ID so the ingestion pipeline can be reviewed and restored if needed.
Best Regards,
Community Support Team
- cdfizz1710 months agoFrequent Visitor
Hi v-menakakota,
Thanks to your reply, the problem is now solved.
Permissions were not sufficient to read MS 365 audit logs.
When the workspace was deleted and re-initialized, the logged-in user did not have sufficient permissions to view audit logs. So the problem persisted.
This time, the workspace was deleted and re-initialized using a higher-priveleged account. This solved the issue.
Thank you for the assistance.