The 404 (Not Found) error when POSTing to /api/data/v9.0/CheckSharePointOBOFailure in your Dynamics 365 (GCC) environment with SharePoint Online integration is interesting and could potentially be related to the auto-refresh issue you're seeing on the Documents tab.
Here's a breakdown of what might be happening and how to investigate:
Understanding CheckSharePointOBOFailure:
The endpoint CheckSharePointOBOFailure likely relates to Server-Based SharePoint Integration and specifically the "On Behalf Of" (OBO) authentication flow. OBO is used when Dynamics 365 needs to interact with SharePoint Online on behalf of a user. This often involves passing user context and permissions.
The purpose of this specific API call seems to be a check for failures or issues within this OBO authentication or authorization process between Dynamics 365 and SharePoint.
Possible Causes for the 404 Error:
- Incorrect Endpoint or Typo: While seemingly straightforward, double-check if there might be a slight variation in the endpoint URL for your specific Dynamics 365 GCC environment. However, since it's being generated by the application, this is less likely.
- Feature Disablement or Configuration Issue: It's possible that the specific feature or configuration related to this OBO failure check is either disabled or not correctly set up in your Dynamics 365 environment. This could be due to a misconfiguration during the SharePoint integration setup or a subsequent change.
- Version Mismatch or Bug: While v9.0 is a mature version, there's a slim possibility of a bug within that specific version, particularly in the context of GCC and SharePoint Online integration. Check if there are any known issues or hotfixes related to SharePoint integration and GCC for your Dynamics 365 version.
- Permissions Issue: Although it's a 404 (Not Found) and not a 401 (Unauthorized), there might be an underlying permissions issue preventing Dynamics 365 from accessing or finding this specific API endpoint. This could be related to service principal permissions or how the integration is configured.
- GCC Specific Behavior: Given that you are in a GCC environment, there might be specific configurations or limitations related to SharePoint integration compared to commercial environments. It's worth checking Microsoft's documentation specifically for Dynamics 365 GCC and SharePoint integration.
Is it Anything to be Concerned About?
A 404 (Not Found) error generally indicates that the requested resource (in this case, the API endpoint) does not exist on the server. This suggests that the functionality trying to call this endpoint might not be working as intended or that there's a configuration issue.
It could be related to the auto-refresh issue you are observing. If the system is failing to properly check the status of the OBO authentication or any related SharePoint interaction, it might not be receiving the necessary signals to trigger an auto-refresh of the Documents tab when changes occur in SharePoint.
Troubleshooting Steps:
- Review SharePoint Integration Configuration:
- Go to Settings > Document Management > SharePoint Site. Verify that your SharePoint Online site is correctly configured and validated.
- Check Settings > Document Management > Document Management Settings. Ensure the entities you expect to see documents for (like the current record you're on) are selected.
- Review the Server-Based SharePoint Integration settings to ensure it's enabled and configured correctly for your GCC environment.
- Check Dynamics 365 Audit Logs: Examine the audit logs in Dynamics 365 for any errors related to SharePoint integration or document management. This might provide more context around when this error started appearing.
- Inspect Browser Network Tab: Open your browser's Developer Tools (usually F12) and go to the Network tab. Reproduce the action of navigating to the Documents tab on a record. Look for the failing POST request to
CheckSharePointOBOFailure. Examine the request and response headers for any additional clues.
- Test SharePoint Integration Functionality: Thoroughly test the basic SharePoint integration functionality:
- Can you successfully create new folders for records in SharePoint from Dynamics 365?
- Can you upload documents from Dynamics 365 to SharePoint?
- Can you view documents embedded in Dynamics 365?
If these basic functionalities are working, it might indicate that the core integration is fine, and the error is related to a specific background check or feature.
- Compare with a Working GCC Environment (If Possible): If you have access to another Dynamics 365 GCC environment with SharePoint integration that is working correctly, compare the configuration settings.
- Review Microsoft Documentation for GCC: Carefully review the official Microsoft documentation specifically for setting up and troubleshooting SharePoint Online integration with Dynamics 365 in GCC environments. There might be specific steps or considerations that differ from commercial environments.
- Consider Raising a Support Ticket with Microsoft: Given that this seems like an internal API endpoint related to the integration, and it's returning a 404, it's quite possible that there's an underlying issue within the Dynamics 365 service in the GCC environment. Raising a support ticket with Microsoft is highly recommended. Provide them with:
- Your Dynamics 365 version (including any updates).
- That you are in a GCC environment.
- The exact error message from the browser console.
- Details of your SharePoint integration setup.
- The fact that the Documents tab is not auto-refreshing.
Potential Relationship to Auto-Refresh Issue:
It's plausible that the CheckSharePointOBOFailure endpoint is part of a mechanism to ensure the user's session and permissions for interacting with SharePoint are still valid. If this check is failing (due to the 404), the system might not be able to reliably monitor for changes in SharePoint on behalf of the user, thus preventing the auto-refresh of the Documents tab.
In conclusion, the 404 error for CheckSharePointOBOFailure is likely a symptom of an underlying issue with the SharePoint integration in your Dynamics 365 GCC environment and could very well be related to the auto-refresh problem you are experiencing. Thorough investigation of your configuration and potentially raising a support ticket with Microsoft are the best steps forward.
