Looking for a MessageMedia page? If you are and were redirected here, it's because MessageMedia is rebranding to Sinch Engage. Learn more about our rebrand.
SINGLE SIGN ON
Single Sign On (SSO) lets your team log in once to access connected applications and services. Sinch Engage supports SAML 2.0 Single Sign On with Microsoft Entra ID and Okta.
BUSINESS OUTCOMES
Single Sign On cuts down on the number of passwords your team needs to remember. It speeds up login times across connected applications and services while lowering IT support demand from password reset requests. SSO can also reduce the risk of phishing and password reuse.
HOW SSO WORKS
A user enters their credentials on your identity provider (IdP), such as Microsoft Entra ID or Okta. The IdP verifies the credentials and generates a secure authentication token. Sinch Engage uses SAML 2.0, which lets IdPs pass authorization credentials safely to service providers.
INTEGRATION & SETUP
Sinch Engage integrates with Microsoft Entra ID (Azure AD) and Okta. Setup starts in your IdP, where you create a new SAML application. Then you sign in to the Sinch Engage parent account with admin credentials. You add your email domains and verify ownership with a DNS TXT record.
For trusted locations, the IdP domain must be a subdomain of okta.com or microsoftonline.com.
SECURITY & CONTROL
Turn on Enforce SAML authentication to require SSO for users with matching email domains. When enforcement is on, those users can’t use password login, cutting down the risk of password reuse.
You can also turn on auto-provisioning, so if someone authenticates with SSO and has no profile, Sinch Engage can create one.
WE’RE HERE TO HELP
CAPABILITIES
Sinch Engage supports a focused set of Single Sign On capabilities built on the SAML 2.0 standard. Use these controls to reduce admin effort and tighten access control.
SAML 2.0 authentication standard
Microsoft Entra ID and Okta support
DNS TXT record domain verification
Enforce SAML authentication toggle
Auto-provisioning for new users
Multi-account domain verification
CAPABILITIES
This setup is intended for IT system administrators. Sinch can support Sinch Engage setup steps, but we can’t support configuration inside your SAML identity provider.
FAQ
We answer your most common questions about the Sinch Engage mobile app that lets you manage group chats and mass texts all from your mobile phone.
Single Sign On is an authentication method that lets users log in to multiple applications or services with one set of credentials. Users authenticate once and get access across connected systems.
Sinch Engage uses SAML 2.0 for Single Sign On. SAML 2.0 is an open standard for exchanging authentication and authorization data between an IdP and a service provider.
Sinch Engage supports Microsoft Entra ID (Azure AD) and Okta for Single Sign On. Custom domains and self-hosted identity providers are not supported at this time.
You add a DNS TXT record to your domain’s DNS settings. Use the TXT value shown in the SSO configuration screen. After DNS propagation, save your configuration in Sinch Engage.
If Enforce SAML authentication is on and your IdP is down, contact the Sinch Engage support team. Support can turn off enforcement so administrators and existing users can log in with email again.
No. Active user sessions stay logged in until they expire. The next time a user logs in, they must authenticate through SAML Single Sign On.
When SSO is enforced, users can’t log in with a password, so 2FA is not triggered. When SSO is not enforced, password login triggers 2FA. Users can also choose SSO login, which bypasses 2FA.
Not at this stage. Users must start in the Sinch Engage web portal and use the Login with Single Sign On page. One-tap SSO apps are not supported at this time.
No. Sinch Engage only supports Azure Active Directory (Microsoft Entra ID).
Single Sign On is a request-only feature. Contact the Sinch Engage support team to request that it is activated on your account.