Setting up Microsoft and Azure Active Directory SSO
You can configure your ChartHop organization with Microsoft Azure Active Directory SSO.
Generate your XML metadata file
Before configuring the Microsoft/Azure SSO client to ChartHop, you will need to provide your Federation metadata XML file which can be downloaded here.
Set up SSO in Azure
To set up SSO for Active Directory in ChartHop, you must configure several settings in your Azure account:
- In the Azure portal, on the left navigation panel, select Azure Active Directory.
- Select Enterprise Applications.
- Select + New application.
- Name the application ChartHop SSO and select Create.
- Under Getting Started,Β select Option 2, Set up Single Sign-On.
- Under Manage, select Single Sign-On.
- Set the following inΒ Basic SAML Configuration:
- Identifier (Entity ID) - ChartHop
- Reply URL - https://api.charthop.com/saml/sso/{org-slug}
- Sign on URL - Leave this field blank.
- Relay StateΒ - https://app.charthop.com
- Under Manage, select Users and Groups.
- Select Granted to use this application.
Set up Azure SSO in ChartHop
After you have configured your Azure portal settings, enable the SSO option and upload your generated metadata file to ChartHop:
- From the left sidebar, select Access.
- From the sub-menu, select Settings.
- Scroll to the SSO section on the page.
- Toggle both Enable Azure Active Directory SSOΒ andΒ Enable Microsoft SSO.
- Upload your Federation Metadata XML file under Azure Active Directory IDP metadata file content.
- Select Save Settings.
Test the new login with Azure Active Directory to ChartHop
To test your Azure Active Directory and Microsoft SSO configurations with ChartHop:
- Log out of ChartHop.
- Visit https://app.charthop.com/{org-slug}/account/login where {org-slug} is your ChartHop organization's unique slug.
- Confirm that your Microsoft sign-in displays on the login screen.
If you encounter any issues during or after testing your SSO setup, please reach out to [email protected].
Issues with alternative user emails
In some cases, such as during an acquisition, you may have users in your company with alternative email domains than the ones used by the main company. In general, a user's Active Directory email should be the same as the one used in their ChartHop accounts. Having different email domains may result in SSO login issues.
Microsoft suggests using a workaround in cases where users want to keep an original email domain.
Modules: HRIS | Engagement | Goals | Performance | Compensation Reviews | Headcount Planning
Use the same Azure app for your sandbox and production orgs
ChartHop uses one Entity ID, ChartHop, for every org. Azure only lets one enterprise app use an Entity ID, so you can't create a second Azure app for your sandbox.
To use SSO in both orgs:
- Set up the Azure app once and point it at your production org.
- Upload the same Federation Metadata XML file in both your production and sandbox orgs.
- Sign in to production with SSO, then switch to your sandbox org.
Don't change the Entity ID to something like "ChartHop Prod". ChartHop only supports ChartHop as the Entity ID.
