Skip to main content
Regentra integrates with the tools MSPs already use. Each integration runs at the organization level with credentials encrypted using AES-256-GCM before storage.

Available integrations

Microsoft Entra ID

SSO authentication, user and device sync, and compliance evidence collection from Azure AD.

Level.io RMM

Device and asset sync from RMM agent data with real-time webhook updates.

Stripe

Payment collection for PSA invoicing and platform subscription management.

AWS

Cloud infrastructure evidence collection for compliance frameworks.

Google Cloud

GCP resource inventory and configuration evidence for compliance.

How integrations work

Each integration stores encrypted credentials at the organization level. Regentra uses AES-256-GCM encryption for all stored secrets (API keys, OAuth tokens, client secrets). Credentials are decrypted only at the moment of use and never logged. Integrations sync data on a schedule (typically every 6 hours) and can also be triggered manually. Some integrations support real-time updates via webhooks.

Connecting an integration

1

Navigate to integrations

Go to Settings → Integrations to see all available integrations.
2

Select the integration

Click on the integration you want to connect. Each one has its own setup flow.
3

Enter credentials

Provide the required credentials — API keys, OAuth consent, or connection details depending on the integration.
4

Test the connection

Click Test Connection to verify that Regentra can communicate with the external service.
5

Save and enable

Save the configuration. The integration begins syncing data on its next scheduled run, or you can trigger an immediate sync.

Connection status

Each integration shows its current status on the integrations page:
StatusMeaning
ConnectedCredentials are valid and the last sync succeeded
ErrorThe last sync failed — check credentials or service availability
Not configuredThe integration has not been set up yet
If an integration shows an error, click into it to see the error details. Common issues include expired OAuth tokens (re-authorize) and revoked API keys (regenerate).