Office 365 Extension not showing Feature Status data in 25.5.1 EA Build

Products

• DX SaaS

Issue/Introduction

1) Got the EA build and configured it, however it is not giving expected metrics as listed below.

Service and Feature Status Values

For each service and feature, you can view the Status metrics.

The following list indicate the applicable statuses and the corresponding value mappings:

• Investigating - 0
• ServiceDegradation - 1
• ServiceInterruption -2 
• RestoringService - 3
• ExtendedRecovery - 4
• ServiceRestored - 5
• PostIncidentReportPublished - 6
• VerifyingService -7 
• ServiceOperational - 8

2) When we try to access the API, observed few services are not considered to handle in the extension for reporting.

3) Errors reported in the log file, there was an error reported when accessing to groups API.
Error:  [DEBUG] [IntroscopeAgent.RESTMon] [AsyncHttpClient-3-4 ResponseHandler] Finish RestAPICall for URL https://graph.microsoft.com:443/v1.0/groups?$select=<id-string> in 1007ms status code: 403 , response size : 266

Resolution

1) The tenant was not able to access the parent URL: https://graph.microsoft.com:443/v1.0/<number>/admin/serviceAnnouncement/healthOverviews

Observed that the "ServiceHealth.Read" permissions was given under Office365 Management APIs. This permission is not working as we are using new GraphAPI. It requires permission "ServiceHealth.Read.All" under "Microsoft Graph".

Please provide the permission as shown below.

In summary: It requires permission "ServiceHealth.Read.All" and “GroupMember.Read.All”, “Group.Read.All” under "Microsoft Graph". 

2) Provided the new scripts  (DE604178_MS Office365_New Scripts.zip) in this KB.
Please replace two script files provided in the zip file and start the agent.
Directory:

apmia/extensions/office365**/config/
File Names:

office365_services_node.json
office365_services_schema.json

3) Please try providing below permissions and it will solve the error under Graph API
GroupMember.Read.All
Group.Read.All

Additional Information

This same issue happened in 24.5.1 GA.