Sailpoint Identity function failure

Question

Hi Everyone,

We have used the built in Sentinel Data connector for Sailpoint IdentityNow. The Sailpoint team have confirmed they followed the access token steps provided in the data connector.

We have successfully deployed it with the client ID, secret and tenant ID. However we are getting no events and the log stream only shows this error:

The Sailpoint team have confirmed they are getting no api logs from the client ID they have provided us and have used postman to confirm the client ID + secret work.

Any guidance on how to troubleshoot or a possible solution for this would be greatly appreciated!

Answer 1

Hello @Isabella Baker ,
This looks more like a Function App runtime/dependency issue than a SailPoint API permission problem.

The SailPoint IdentityNow connector is a community Azure Functions connector and is intended to run on Python 3.9, not 3.8. There is also a known issue where the function fails during SearchEvent module import/startup, so no logs are ingested even though the credentials are correct.

Also, changing the Python version in the portal alone is usually not enough. For Azure Functions, you need to rebuild and redeploy the app so dependencies are recreated for the new runtime. Using remote build is recommended.

So the practical fix is:

Redeploy the connector as a new Function App using Python 3.9

Use remote build

Verify all required app settings are present and case-sensitive

If it still fails with import/dependency errors, treat it as a connector package issue, not an auth issue

Because this connector is supported by SailPoint, not Microsoft, I would raise it with SailPoint support and reference the known GitHub issue if the built-in Sentinel deployment continues to deploy an incompatible runtime.