Drata - Troubleshooting

While configuring your Drata connection, you may encounter several issues. Understanding these common errors can help streamline the setup process and facilitate quick resolutions.

The connection stopped working on its own

The usual cause is the API key's expiration date, which Drata preselects at 12 months. Open Settings → API Keys and check the key's status: Expired and Revoked keys are permanent — create a new key and update the connection with it.

Drata rejects the calls but the key looks fine

Check the key's Allowed IP Addresses. If that field is not empty, it must list the Improvado addresses for the cluster your workspace runs on — see the list in the Drata setup guide.

The key works elsewhere but not here

Confirm its scopes cover reading. A key created with Custom access may carry scopes for other endpoints but not for personnel; All read avoids the question entirely.