My key vault connection won't verify. What should I check?

Why this happens

The form holds a service principal that Cyberlop uses to read scan credentials from a vault. Verify tests the connection and the named secrets, so it can fail for several reasons: a mistyped ID, a wrong or expired client secret, or a principal without read rights on the vault.

How to fix it

1. Go to Integrations and open the key vault tab.
2. Tenant ID and Client ID are long UUIDs, like 00000000-0000-0000-0000-000000000000. Copy them again without spaces.
3. The secret is never shown again after saving. Paste a fresh value, since a blank or expired one will fail.
4. Press Verify before Save and read the result.
5. In your cloud provider, confirm the service principal may read the vault and the secret names you use.

The check is an API call, and it needs the permission to manage credentials. If your role lacks it, you may see a permission error instead of a vault error. Ask an admin to run the check.

Still not working?

Change one thing at a time and verify after each change, so you learn which field was wrong. Nothing about the exact error text was captured, so read the message shown in the app and pass it on. See how to verify a key vault and what a permission error means. If it still fails, send the message to us through the contact page. Never send the client secret itself.

Related questions

• How do I connect my cloud key vault?
• How do I check that my key vault connection works?
• What is the cloud key vault integration used for?
• Why does my API call return a permission error?
• Why can't I see my saved token or key any more?

Full tutorial

How to connect a cloud key vault to Cyberlop

Step-by-step, with annotated screenshots.

Updated 8 October 2026 · Back to the help centre