Skip to main content

How to set up Microsoft SSO for Emergency Button users?

Simplify user management and strengthen security

Montr can be integrated with your organisation's Microsoft Entra ID (Azure Active Directory), allowing users to sign in using their existing Microsoft work account.

The application never sees passwords and cannot change anything in your Microsoft 365 environment.

How is it set up?

Before you start make sure:

  • Your organization uses Microsoft Entra ID (Azure AD), e.g. through Microsoft 365.

  • Staff sign in with accounts that are members of your own organization (guest accounts invited from other organizations are not supported).

  • Your email domain (e.g. `@yourcompany.com`) is a verified domain in your Microsoft environment - if you use Microsoft 365 with your own domain, this is already the case.

  • You have access to one of the Cloud App Admin roles for one approval step:

    • Global Administrator

    • Privileged Role Administrator

    • Cloud Application Administrator

    • Application Administrator

To enable SSO, you will need:

  • Send Montr your Microsoft Tenant ID

    We link your Emergency Button organization to your Microsoft environment using your Tenant ID (also called Directory ID) - a value that looks like aaaabbbb-1111-2222-3333-ccccddddeeee

    1. Go to entra.microsoft.com (or portal.azure.com → Microsoft Entra ID).

    2. On the Overview page, copy the value shown as Tenant ID.

    3. Send it to Montr, as SSO will not work until we have registered this value for you.


    ​At this point users can access the "Sign in with Microsoft" button and they can sign-in using SSO, but they need to consent for SSO (not the Calendar), pending organization-wide permissions.

  • OPTION A - if as a Cloud App Admin you have access to our Emergency Button Backoffice.

    Approve the Montr application and grant permissions on behalf of everyone during first sign-in (recommended).
    ​

    1. Open the Emergency Button panel login page and click Sign in with Microsoft.

    2. Microsoft shows a consent screen listing the requested permissions for SSO (not the calendar permission):

      1. Sign you in and read your basic profile, to identify the user and match them to their Emergency Button account.

      2. Maintain access to data you have given it access to, to keep the calendar link below working without repeated sign-ins.

    3. Click Accept


    ​At this point users can access the "Sign in with Microsoft" button and they can sign-in using SSO, without a need to consent again since you already granted permissions globally, no Calendar permission yet.

  • OPTION B - if as a Cloud App Admin you DON'T HAVE access to our Emergency Button Backoffice
    ​

    Do nothing - permission to Single-Sign on will be accepted per user, upon his first log in.
    Optionally you can Approve the Montr application and grant permissions on behalf of everyone on your Cloud App panel.
    ​
    ​At this point users can access the "Sign in with Microsoft" button and they can sign-in using SSO, but they need to consent for SSO (not the Calendar), pending organization-wide permissions.
    ​

If you would like to integrate Microsoft Calendar allowing the control room to view a user's recent, current and upcoming calendar appointments during an emergency, check this article:

How to set up Microsoft Calendar integration

Did this answer your question?