Tutorial: Azure Active Directory integration with Greenhouse
In this tutorial, you'll learn how to integrate Greenhouse with Azure Active Directory (Azure AD). When you integrate Greenhouse with Azure AD, you can:
- Control in Azure AD who has access to Greenhouse.
- Enable your users to be automatically signed-in to Greenhouse with their Azure AD accounts.
- Manage your accounts in one central location - the Azure portal.
To get started, you need the following items:
- An Azure AD subscription. If you don't have a subscription, you can get a free account.
- Greenhouse single sign-on (SSO) enabled subscription.
This integration is also available to use from Azure AD US Government Cloud environment. You can find this application in the Azure AD US Government Cloud Application Gallery and configure it in the same way as you do from public cloud.
In this tutorial, you configure and test Azure AD SSO in a test environment.
- Greenhouse supports SP and IDP initiated SSO.
Adding Greenhouse from the gallery
To configure the integration of Greenhouse into Azure AD, you need to add Greenhouse from the gallery to your list of managed SaaS apps.
- Sign in to the Azure portal using either a work or school account, or a personal Microsoft account.
- On the left navigation pane, select the Azure Active Directory service.
- Navigate to Enterprise Applications and then select All Applications.
- To add new application, select New application.
- In the Add from the gallery section, type Greenhouse in the search box.
- Select Greenhouse from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
Alternatively, you can also use the Enterprise App Configuration Wizard. In this wizard, you can add an application to your tenant, add users/groups to the app, assign roles, as well as walk through the SSO configuration as well. Learn more about Microsoft 365 wizards.
Configure and test Azure AD SSO for Greenhouse
Configure and test Azure AD SSO with Greenhouse using a test user called B.Simon. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in Greenhouse.
To configure and test Azure AD SSO with Greenhouse, perform the following steps:
- Configure Azure AD SSO - to enable your users to use this feature.
- Create an Azure AD test user - to test Azure AD single sign-on with Britta Simon.
- Assign the Azure AD test user - to enable Britta Simon to use Azure AD single sign-on.
- Configure Greenhouse SSO - to configure the Single Sign-On settings on application side.
- Create Greenhouse test user - to have a counterpart of Britta Simon in Greenhouse that is linked to the Azure AD representation of user.
- Test SSO - to verify whether the configuration works.
Configure Azure AD SSO
Follow these steps to enable Azure AD SSO in the Azure portal.
In the Azure portal, on the Greenhouse application integration page, find the Manage section and select single sign-on.
On the Select a single sign-on method page, select SAML.
On the Set up single sign-on with SAML page, click the pencil icon for Basic SAML Configuration to edit the settings.
On the Basic SAML Configuration section, if you wish to configure the application in IDP initiated mode, enter the values for the following fields:
a. In the Identifier text box, type the value:
b. In the Reply URL text box, type a URL using the following pattern:
Click Set additional URLs and perform the following step if you wish to configure the application in SP initiated mode:
In the Sign-on URL text box, type the URL:
The value is not real. Update the value with the actual Reply URL. Contact Greenhouse Client support team to get the value. You can also refer to the patterns shown in the Basic SAML Configuration section in the Azure portal.
On the Set up Single Sign-On with SAML page, in the SAML Signing Certificate section, click Download to download the Federation Metadata XML from the given options as per your requirement and save it on your computer.
On the Set up Greenhouse section, copy the appropriate URL(s) as per your requirement.
Create an Azure AD test user
In this section, you'll create a test user in the Azure portal called B.Simon.
- From the left pane in the Azure portal, select Azure Active Directory, select Users, and then select All users.
- Select New user at the top of the screen.
- In the User properties, follow these steps:
- In the Name field, enter
- In the User name field, enter the email@example.com. For example,
- Select the Show password check box, and then write down the value that's displayed in the Password box.
- Click Create.
- In the Name field, enter
Assign the Azure AD test user
In this section, you'll enable B.Simon to use Azure single sign-on by granting access to Greenhouse.
- In the Azure portal, select Enterprise Applications, and then select All applications.
- In the applications list, select Greenhouse.
- In the app's overview page, find the Manage section and select Users and groups.
- Select Add user, then select Users and groups in the Add Assignment dialog.
- In the Users and groups dialog, select B.Simon from the Users list, then click the Select button at the bottom of the screen.
- If you are expecting a role to be assigned to the users, you can select it from the Select a role dropdown. If no role has been set up for this app, you see "Default Access" role selected.
- In the Add Assignment dialog, click the Assign button.
Configure Greenhouse SSO
In a different web browser window, sign into Greenhouse website as an administrator.
Go to the Configure > Dev Center > Single Sign-On.
Perform the following steps in the Single Sign-On page.
a. Copy SSO Assertion Consumer URL value, paste this value into the Reply URL text box in the Basic SAML Configuration section in the Azure portal.
b. In the Entity ID/Issuer textbox, paste the Azure AD Identifier value which you have copied from the Azure portal.
c. In the Single Sign-On URL textbox, paste the Login URL value which you have copied from the Azure portal.
d. Open the downloaded Federation Metadata XML from the Azure portal into Notepad and paste the content into the IdP Certificate Fingerprint textbox.
e. Select the Name Identifier Format value from the dropdown.
f. Click Begin Testing.
Alternatively you can also upload the Federation Metadata XML file by clicking on the Choose File option.
Create Greenhouse test user
In order to enable Azure AD users to log into Greenhouse, they must be provisioned into Greenhouse. In the case of Greenhouse, provisioning is a manual task.
You can use any other Greenhouse user account creation tools or APIs provided by Greenhouse to provision Azure AD user accounts.
To provision a user accounts, perform the following steps:
Log in to your Greenhouse company site as an administrator.
Go to the Configure > Users > New Users
In the Add New Users section, perform the following steps:
a. In the Enter user emails textbox, type the email address of a valid Azure Active Directory account you want to provision.
b. Click Save.
The Azure Active Directory account holders will receive an email including a link to confirm the account before it becomes active.
In this section, you test your Azure AD single sign-on configuration with following options.
Click on Test this application in Azure portal. This will redirect to Greenhouse Sign on URL where you can initiate the login flow.
Go to Greenhouse Sign-on URL directly and initiate the login flow from there.
- Click on Test this application in Azure portal and you should be automatically signed in to the Greenhouse for which you set up the SSO
You can also use Microsoft My Apps to test the application in any mode. When you click the Greenhouse tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Greenhouse for which you set up the SSO. For more information about the My Apps, see Introduction to the My Apps.
Once you configure Greenhouse you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. Learn how to enforce session control with Microsoft Defender for Cloud Apps.
Submit and view feedback for