Using Microsoft Entra ID for Single Sign-on (SSO)
Noah ES uses Single Sign-On (SSO) implemented as Federated Logins. This means:
Federated Login allows users to authenticate through an identity provider (IdP) such as Entra ID, Okta, or similar, using industry-standard OpenID Connect.
Once authenticated via the IdP, users can access Noah ES without needing separate credentials for the application.
What this is NOT
Noah ES does not implement “True Seamless Sign-On,” which is sometimes defined as:
Zero extra logins after the user has authenticated on their PC (e.g., Windows Integrated Authentication).
Automatic sign-in without any interaction when already logged into the workstation.
Instead, Noah ES follows the Federated SSO model, which requires the user to authenticate through the configured IdP when accessing Noah ES.
We are aware of a known issue that may prevent users from receiving the initial account confirmation email.
The most common cause for this scenario occurs when a new Entra ID user is created it may take up to an hour or so for the user's email address to become fully functional. If the user is added to Noah ES before the email is functional it is very likely that required emails being sent to the email address will fail and the email system that Noah ES uses will note failures and stop trying to process email further.
We are currently working on possible solutions.
Current workarounds:
If possible, before adding a user to Noah ES test that the email address can process emails.
If a user does not receive the initial confirmation email, they can generate a new one by attempting to log in to the Noah ES Portal:
The login attempt will detect that the email address has not yet been confirmed and will trigger a new email requesting that they confirm their email address. Once the email is received, the user should click the confirmation link to verify their account. After completing the verification process, they should be able to log in successfully.
If the user still does not receive the confirmation email, please submit a support ticket through the Noah ES Online Help Desk:
Submit an issue or Question - Noah ES Online Help Desk
It is possible that our mailing system has placed the user's email address on a bounce list, preventing delivery of the confirmation email.
Noah ES provides its own authentication system (local system) but also provides the ability to integrate with other authentication systems. At present, Noah ES Supports integration with:
Microsoft Entra ID
HIMSA also supports OpenID Connect
Configure NoahES for OpenID Connect single sign-on
This document is split into two main sections:
Set up for Entra ID
Onboarding new Noah ES users and switching current Noah ES users from the local system to Entra ID
Set up for Entra ID
Preconditions:
Your company has an Entra ID account set up and you have administrative privileges
Your company has a Noah ES account and you have been set up in Noah ES as either a “Business Decision Maker” or “Technical Administration” user. At this point, your Noah ES user account will be using the local system.
These two user types are chargeable uses. If you will not be involved with Noah ES on a regular basis for patient care then it is possible to assign your user to the role of “Administrative Support” after this setup. This user type is able manage users (more in the onboarding section below) and is a free account. This user type is also not able to use patient related Noah ES features.
HIMSA does not make an immediate accounting of chargeable uses but rather over longer periods of time. Once Entra ID is set up you can switch user types within a day or two you will be fine.
Step 1 - Log in to the Noah ES portal
Navigate to Settings > Single Sign-on and select the + icon in the upper right-hand area of the screen, Select Entra ID0.
Step 2 - Enter the necessary data
Enter data for the 2 fields:
Name - text of your choice. This is just a label that will be visible on the user management screen (e.g. Always Listening Inc. Entra ID)
Tenant ID - This is your Entra ID tenant ID, if you do not know it then the screen provides a link for assistance in looking it up.
Logon Domain Hint - the name of your domain. This is not strictly necessary and can be skipped.
Click on Create
Step 3 - Change your user to use Entra ID
Via the Noah ES portal go to Manage Users and select to edit your Noah ES user account.
Under the “Login Method” select Entra ID selection that was just created.
Save
Step 4 - Log out and Log back into Noah ES
Log back into the portal and enter your email address. You will now be directed to Entra ID for authentication.
At this point, you will be requested to provide consent that Noah ES may integrate.
Once this has been accepted you may continue with onboarding Noah ES users.
Q: Is it possible to remove this integration at some point in the future?
A: Yes, you may delete the application from within Entra ID. Make sure to switch your users back to the local system or another authentication system first.
After accepting, an Enterprise App will be created in Entra ID called Noah ES SSO. By default, all users in your Entra ID directory can authenticate with Noah ES. However, this is only possible if the user also has an established user account in Noah ES with a matching email address. See the next section dealing with onboarding new users.
You can control this via the Enterprise App Properties menu. By default, “Assignment required” is set to “No”. If you select “Yes” then it will be necessary to assign users/groups to the Enterprise App in Entra iD.
Related Topics
- Using Microsoft Entra ID for Single Sign-on (SSO)
- Managing User Levels and Permissions
- Inactive user accounts in Noah ES
- How to use Groups and Locations
- How to Deactivate and Re-Activate Users
- Enabling MFA (Multi Factor Authentication)
- Configure NoahES for OpenID Connect single sign-on
- Adding Users to Noah ES
Onboarding new Noah ES users so that Entra ID is used
Step 1 - Adding a new Noah ES User
When adding a new user select the Entra ID entry that is now available under the “Login Method”
The Noah ES User Experience
Now the user can start the Noah ES Client software, and select Noah ES US or Noah ES EU. The browser will open for authentication and ask for their email address
Once they click on Next the process will then continue with Entra ID and any rules and feature set up will continue as you have configured.
Switching current Noah ES users from the local system
If you have users that have used the local system it is possible to switch them to use Entra ID. To do so just edit the user to use the Entra ID login selection.
The next time the user logs into Noah ES they will use Entra ID.
If you wish to enforce this change right away you can first set the user to save Entra ID, Save. Then, deactivate the user, reselect the user and activate. This will force the user to authenticate again and Entra ID will now be used.
Q: If I do integrate Entra ID with Noah ES do all of my users have to make use of Entra ID
A: No