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, user/device sync, conditional access + MFA evidence.

Microsoft 365 SSO

Staff and portal login through your Microsoft tenant.

Level.io RMM

Device and asset sync with real-time webhook updates.

Okta

User provisioning, MFA enrollment, sign-in event poll.

Cisco Duo

MFA enrollment, global policy, admin inventory, auth-log aggregate.

Google Workspace

User directory sync via service-account delegation.

Proofpoint SAT

Training-completion and phishing-simulation results.

Huntress Managed SAT

Workforce coverage and phishing-simulation evidence.

GitHub

Change-management evidence from repository activity.

Jira

Issue tracking integration for change management.

Stripe

Per-org PSA invoicing and platform subscription billing.

QuickBooks Online

Customer + invoice push with Stripe-paid bridging.

Microsoft Teams — Chat Bridge

Bidirectional bridge between Teams chats and PSA tickets.

Regentra Bot — Teams

Compliance + ticket commands inside Teams.
AWS and GCP evidence collection runs on a separate code path from the Settings → Integrations card list — it’s configured under Compliance → Settings → Evidence Collection. The cards above are the ones surfaced on the per-org Integrations page.

​
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).