With single sign-on (SSO), your practitioners and medical assistants sign in to MeetOne using your organization's existing Microsoft/Azure credentials — without a separate MeetOne password.

What SSO gives you

  • Sign-in with your organization's existing Microsoft/Azure Entra ID credentials.
  • Centralized access control through your Azure Entra ID, instead of separate MeetOne passwords.

SSO is for sign-in only, not sign-up. Each person still needs an existing MeetOne account with the same email address as in Azure Entra ID. Create new accounts as usual, see Invite and manage team members.

Prerequisites

  • SSO is enabled for your organization.
  • You have administrator rights in your Azure Entra ID (Azure Active Directory) to register an application there.

How setup works

Exchanging the technical credentials (client ID, client secret, tenant ID) isn't currently a self-service option in your account — setup happens together with MeetOne:

  1. You register MeetOne as an application in your Azure portal (app registration).
  2. You send us the resulting values (client ID, tenant ID, client secret) through a secure channel.
  3. MeetOne enables SSO for your organization and configures the matching redirect URL.
  4. Once enabled, a Sign-in with SSO button appears on the sign-in page.

The full technical guide for the Azure Entra ID app registration is in the developer documentation.

For setup or later changes (e.g. a new client secret), contact our support at support@meetone.io.

Troubleshooting

  • I don't see a "Sign-in with SSO" button. SSO isn't enabled for your organization yet — contact our support.
  • "No user account found with this email address." The person needs an existing regular MeetOne account with the same email address as in Azure Entra ID first.

Still have questions? Contact us at support@meetone.io.