SharePoint search shows Error 3 on managed device, is Hexnode blocking it?Solved

If the device does not have Web Content Filtering, VPN, or Global HTTP Proxy configurations applied through Hexnode, Hexnode is unlikely to be blocking SharePoint traffic.

An “Error 3” message in this context usually indicates that the app was able to send the request, but the app’s backend service returned an invalid or broken response. This points more toward an application-side or service-side connectivity issue rather than an MDM restriction.

To isolate whether a Hexnode policy is involved, you can test with one device by temporarily removing the associated policy, saving the policy changes, and then checking SharePoint search again. If the issue continues even without the policy, the next step would be to check with the app vendor or the internal IT team managing SharePoint/Microsoft 365 access.

 Does deploying the SharePoint app through Hexnode affect the app’s in-app search or server communication in any way?

Deploying the app through Hexnode does not, by itself, modify how SharePoint search communicates with Microsoft 365 or the app backend. Hexnode app deployment only installs or manages the app unless additional configurations or restrictions are applied. The areas to review are:

1. Web Content Filtering policies
2. VPN configurations
3. Global HTTP Proxy settings
4. App-specific configuration, if one is being pushed
5. Any external network filtering outside Hexnode.

If none of these are configured through Hexnode, an “Error 3” response from the app should be treated as an app/backend or network service issue rather than a Hexnode block.