> For the complete documentation index, see [llms.txt](https://docs.strongdm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strongdm.com/admin/deployment/integrations.md).
# Integrations
StrongDM integrates with a variety of service providers. Documentation is provided about each integration. Select one of the following links to learn how to configure that integrated service.
StrongDM has a variety of integrations with each of these clouds, including for cloud management, specific resource types, secrets management tools, and user SSO and provisioning.
### Certificate Authorities
* [Active Directory Certificate Services (RDP)](/admin/access/certificate-authorities/adcs-ca.md)
* [AWS (RDP)](/admin/access/certificate-authorities/aws-ca-rdp.md)
* [GCP (RDP)](/admin/access/certificate-authorities/gcp-ca.md)
* [Hashicorp Vault (RDP)](/admin/access/certificate-authorities/vault-ca-rdp.md)
* [Hashicorp Vault (SSH)](/admin/access/certificate-authorities/vault-ca-ssh.md)
* [Keyfactor EJBCA (RDP)](/admin/access/certificate-authorities/ejbca-ca-rdp.md)
* [Keyfactor EJBCA (SSH)](/admin/access/certificate-authorities/ejbca-ca-ssh.md)
### Logging
* [CloudWatch](/admin/audit/logs/scenarios/export-to-cloudwatch.md)
* [Filebeat](/admin/audit/logs/scenarios/export-to-filebeat.md)
* [Graylog](/admin/audit/logs/scenarios/export-to-graylog.md)
* [Rsyslog](/admin/audit/logs/scenarios/export-via-rsyslog.md)
* [S3](/admin/audit/logs/scenarios/export-to-s3.md)
* [S3 (Log Stream)](/admin/audit/logs/log-stream.md)
* [Splunk](/admin/audit/logs/scenarios/export-to-splunk.md)
### Secret Stores
* [AWS Secrets Manager](/admin/access/secret-stores/aws-secrets-manager.md)
* [Azure Key Vault](/admin/access/secret-stores/azure-key-vault.md)
* [CyberArk Conjur](/admin/access/secret-stores/cyberark-conjur.md)
* [CyberArk PAM](/admin/access/secret-stores/cyberark-pam.md)
* [Delinea Secret Server Vault](/admin/access/secret-stores/delinea-secret-server.md)
* [GCP Secret Manager](/admin/access/secret-stores/gcp-secret-manager.md)
* [HashiCorp Vault](/admin/access/secret-stores/hashicorp-vault.md)
### Security
* [CrowdStrike](/admin/access/policies/device-trust.md)
* [Duo](/admin/principals/mfa/mfa-duo.md)
* [Microsoft Defender](/admin/access/policies/device-trust.md)
* [Okta Verify](/admin/principals/mfa/mfa-okta.md)
* [SentinelOne](/admin/access/policies/device-trust.md)
* [TOTP](/admin/principals/mfa/mfa-totp.md)
### SSO
* [ADFS](/admin/principals/sso/adfs-oidc.md)
* [Auth0](/admin/principals/sso/auth0-oidc.md)
* [Entra ID (formerly Azure AD)](/admin/principals/sso/entra-oidc.md)
* [Google](/admin/principals/sso/google-oidc.md)
* [Jumpcloud](/admin/principals/provisioning/jumpcloud-provisioning.md)
* [Keycloak](/admin/principals/sso/keycloak-oidc.md)
* [Okta (OIDC)](/admin/principals/sso/okta-oidc.md)
* [Okta (SAML)](/admin/principals/sso/okta-saml.md)
* [OneLogin (OIDC)](/admin/principals/sso/onelogin-oidc.md)
* [OneLogin (SAML)](/admin/principals/sso/onelogin-saml.md)
* [Ping Identity (OIDC)](/admin/principals/sso/ping-identity-oidc.md)
* [Ping Identity (SAML)](/admin/principals/sso/ping-identity-saml.md)
* [Rippling](/admin/principals/sso/rippling-saml.md)
* [VMware Workspace ONE](/admin/principals/sso/vmware-oidc.md)
{% hint style="info" %}
To learn how to integrate any OpenID Connect (OIDC)-compliant SSO service, please see the [General SSO Guide](/admin/principals/sso.md).
To set up SSO using SAML with an identity provider that is not explicitly listed, see [SSO With SAML](/admin/principals/sso/saml.md).
{% endhint %}
### User Provisioning
* [Entra ID (formerly Azure AD)](/admin/principals/provisioning/entra-provisioning.md)
* [Google](/admin/principals/provisioning/google-provisioning.md)
* [Okta](/admin/principals/provisioning/okta-provisioning.md)
* [OneLogin](/admin/principals/provisioning/onelogin-provisioning.md)
{% hint style="info" %}
Use [StrongDM SCIM API Specification](/references/scim.md) when leveraging the StrongDM SCIM API to connect to an identity provider that is not explicitly listed.
{% endhint %}
### Workflows
* [Jira](/admin/access/approval-workflows/jira-workflows.md)
* [Microsoft Teams](/admin/access/access-workflows/teams-workflows.md)
* [ServiceNow](/admin/access/approval-workflows/servicenow-workflows.md)
* [Slack](/admin/access/access-workflows/slack-workflows.md)
### Incident Response
* [Incident.io](/admin/deployment/integrations/incidentio.md)
* [PagerDuty](/admin/deployment/integrations/pagerduty.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.strongdm.com/admin/deployment/integrations.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
