Troubleshooting errors that occur during monitor addition and data collection in Microsoft 365 monitor (For versions 16310 onwards)
From Applications Manager version 16310 onwards, Microsoft 365 monitor will use Microsoft Graph API as the primary mode of data collection.
We have migrated from PowerShell to Graph API as Microsoft 365 PowerShell commands were taking more time to execute for huge resources and required Administrative user privileges for execution of the commands. Microsoft provides archived data alone in the Graph API. To monitor live data, use the PowerShell mode considering the user privileges and the time taken to fetch huge resources.
Prerequisites:
- Ensure that you have met all the prerequisites for the Microsoft 365 monitor.
If you have enabled the Enable monitoring via PowerShell option, refer the links given below:
The below errors are the possible causes that are mentioned next to the keyword 'Reason' of the UI error messages on the monitor. For example, Unable to collect Service Health data. Reason: Required permission 'ServiceHealth.Read.All' is missing to collect the Service Health Data refer to the Required permission to collect the data troubleshooting steps.
How to fix "Authentication Failed. Please provide a valid Tenant ID / Client ID / Client Secret." error?
Sample error messages:
- Ensure that the given values for Tenant ID, Client ID and Client Secret are correct.
- Ensure that Client Secret is not expired. Refer here to check the client secret expiry.
How to fix "Required permission missing to collect the data." error?
Sample error messages;
- Refer to the prerequisites and ensure you have given the mentioned permissions to the Azure AD application.
- Ensure that you have given admin consent for the APIs as shown below.
How to fix "Unable to connect / Unable to resolve / Unreachable host."?
- Ensure you have an active internet connection.
- Verify the proxy configuration in the Applications Manager.
- Ensure that login.microsoftonline.com & graph.microsoft.com endpoints are accessible.
- If proxy is configured, ensure that the above endpoints are not excluded in the Applications Manager Settings -> Product Settings -> Connectivity -> Proxy server -> 'Do not use proxy for addresses beginning with' field.
Follow the steps given in this KB to invoke API and verify the response from the Applications Manager installed machine.
How to fix "Unable to parse endpoints in CSV."?
To edit/add endpoints in Microsoft365 monitors, one can edit the Microsoft365_Endpoints.csv file which is present under <APM_Home>/working/conf/Microsoft365Configurations/ folder. The maximum number of endpoints allowed per monitor type is 100.
The file follows the below format for Microsoft365, ExchangeOnline, SharePointOnline, and MicrosoftTeams monitors:
- Endpoint,Port
- #<Monitor Type> starts,
- Host,Port
- #Can comment a line with a # symbol at the start of the line if a particular endpoint is not needed for monitoring.
- #<Monitor Type> ends,
Sample file to indicate how to specify endpoints:
- Endpoint,Port
- #Microsoft365 starts,
- api.login.microsoftonline.com,443
- clientconfig.microsoftonline-p.net,443
- #Microsoft365 ends,
- #ExchangeOnline starts,
- smtp.office365.com,587
- outlook.office365.com,443
- #ExchangeOnline ends,
Errors that you might encounter:
- Exception occurred on line number(s): {0}. Please check if the given format is correct.
- Check the Microsoft365_Endpoints.csv file for syntax errors in the reported line number.
- Check the syntax given above reference.
- Reason: Endpoints parsing error. Please check the CSV file for any syntax errors or missing values.
- Check the Microsoft365_Endpoints.csv file for correct values and ensure the starts and ends header are placed correctly.
- Ensure that the endpoints entry are present for the specific monitor type.
- Check the syntax given above reference.
Other common API errors
- Refer this KB.
Reach out to our support team with the text file containing the output and email the same to appmanager-support@manageengine.com along with the latest Support Information File (SIF) from Applications Manager with print all logs enabled for analysis.New to ADSelfService Plus?
Related Articles
Troubleshooting errors during data collection in Microsoft 365 monitor (For versions upto v16300)
Prerequisites: Ensure that you have met all the prerequisites for the Microsoft 365 monitor. From Applications Manager version 16300 onwards, Microsoft 365 monitor will use Microsoft Graph API as the primary mode of data collection. We have migrated ...Troubleshooting errors that occur while adding Microsoft 365 monitor (For versions upto 16300)
Prerequisites: Ensure that you have met all the prerequisites for the Microsoft 365 monitor. From Applications Manager version 16300 onwards, Microsoft 365 monitor will use Microsoft Graph API as the primary mode of data collection. We have migrated ...Troubleshooting errors in Microsoft Teams monitor (For versions upto 16300)
Prerequisites: Ensure that you have met all the prerequisites for the Microsoft 365 monitor. From Applications Manager version 16300 onwards, Microsoft 365 monitor will use Microsoft Graph API as the primary mode of data collection. We have migrated ...Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check prerequisites to be done Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...Best Practices in adding Microsoft 365 monitor
From Applications Manager version 16300 onwards, Microsoft 365 monitor will use Microsoft Graph API as the primary mode of data collection. We have migrated from PowerShell to Graph API as Microsoft 365 PowerShell commands were taking more time to ...