Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The following common errors are observed while configuring the connector, or during crawling and their possible reasons.
Step | Error message | Possible reason(s) |
---|---|---|
Connection settings | Invalid credentials detected. Try signing in with a different account or check the permissions for your account |
Third-party application access via OAuth may be disabled. Follow steps to manage security policies to enable OAuth. |
Connection settings | Bad state message in OAuth pop-up window with URL stating error=InvalidScope |
Wrong scopes provided to the registered app. |
Connection settings | 400 - Bad request message in OAuth pop-up window |
Incorrect App ID. |
Connection settings | BadRequest: Bad Request on API request message in OAuth pop-up window |
Incorrect client secret. |
Crawl time (post connector configuration) | The account associated with the connector doesn't have permission to access the item. |
The registered app does not have any of the required OAuth scopes. (Note - A new OAuth scope requirement 'Analytics:read' was introduced on 8/31/2021). |
Crawl time (post connector configuration) | You don't have permission to access this data source. You can contact the owner of this data source to request permission. |
Third-party application access via OAuth is disabled. Follow steps to manage security policies to enable OAuth. |
Crawl time (post connector configuration) | Credentials associated with this data source have expired. Renew the credentials and then update the connection |
The registered app may have been deleted or expired. |
Crawl time (post connector configuration) | Item listed but no longer accessible or no longer exists |
The crawling account may be missing 'basic' access level. Crawls fail with 'stakeholder' access. |
Crawl time (post connector configuration) | 2011: Bad data source API |
The crawling account may be missing 'basic' access level. Crawls fail with 'stakeholder' access. |
If you have issues or want to provide feedback, contact Microsoft Graph | Support.