deskbird supports a variety of secure Single Sign-On (SSO) options to make access seamless and safe for your organization. Whether you're using Microsoft, Google, or a third-party identity provider like Okta or Keycloak, this guide gives you an overview of all supported SSO configurations.
💡 If you want to restrict sign-in to a specific method, such as Microsoft only, our support team can disable other options (e.g., Google SSO) for your account. Just reach out to support@deskbird.com.
- Single Sign-On with Microsoft
- Single Sign-On with Google
- Single Sign-On with Okta
- Single Sign-On with Keycloak
- Single Sign-On with SAML 2.0
1. Single Sign-On with Microsoft
Use Microsoft Entra ID (formerly Azure AD) to enable seamless login via your corporate Microsoft account. An IT admin with Global Admin rights must consent to the required permissions to activate the integration.
2. Single Sign-On with Google
SSO with Google is available by default—no setup required! If your organization uses Google Workspace, users can log in instantly by selecting the Google option during sign-in.
3. Single Sign-On with Okta
deskbird integrates with Okta via SAML 2.0 to allow secure authentication through your existing Okta environment. This is ideal for companies using Okta as their identity provider (IdP).
4. Single Sign-On with Keycloak
If your company uses Keycloak for identity management, you can configure SSO with deskbird using SAML. This ensures secure access control across systems.
5. Single Sign-On with SAML 2.0
Already using a different SAML 2.0-compliant identity provider? No problem. deskbird supports custom SAML 2.0 configurations for enterprise-level flexibility.