Tutorial: Azure Active Directory single sign-on (SSO) integration with WhosOffice

In this tutorial, you'll learn how to integrate WhosOffice with Azure Active Directory (Azure AD). When you integrate WhosOffice with Azure AD, you can:

  • Control in Azure AD who has access to WhosOffice.
  • Enable your users to be automatically signed-in to WhosOffice 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.
  • WhosOffice single sign-on (SSO) enabled subscription.

Scenario description

In this tutorial, you configure and test Azure AD SSO in a test environment.

  • WhosOffice supports SP and IDP initiated SSO


Identifier of this application is a fixed string value so only one instance can be configured in one tenant.

To configure the integration of WhosOffice into Azure AD, you need to add WhosOffice from the gallery to your list of managed SaaS apps.

  1. Sign in to the Azure portal using either a work or school account, or a personal Microsoft account.
  2. On the left navigation pane, select the Azure Active Directory service.
  3. Navigate to Enterprise Applications and then select All Applications.
  4. To add new application, select New application.
  5. In the Add from the gallery section, type WhosOffice in the search box.
  6. Select WhosOffice from results panel and then add the app. Wait a few seconds while the app is added to your tenant.

Configure and test Azure AD SSO for WhosOffice

Configure and test Azure AD SSO with WhosOffice 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 WhosOffice.

To configure and test Azure AD SSO with WhosOffice, perform the following steps:

  1. Configure Azure AD SSO - to enable your users to use this feature.
    1. Create an Azure AD test user - to test Azure AD single sign-on with B.Simon.
    2. Assign the Azure AD test user - to enable B.Simon to use Azure AD single sign-on.
  2. Configure WhosOffice SSO - to configure the single sign-on settings on application side.
    1. Create WhosOffice test user - to have a counterpart of B.Simon in WhosOffice that is linked to the Azure AD representation of user.
  3. Test SSO - to verify whether the configuration works.

Configure Azure AD SSO

Follow these steps to enable Azure AD SSO in the Azure portal.

  1. In the Azure portal, on the WhosOffice application integration page, find the Manage section and select single sign-on.

  2. On the Select a single sign-on method page, select SAML.

  3. On the Set up single sign-on with SAML page, click the edit/pencil icon for Basic SAML Configuration to edit the settings.

    Edit Basic SAML Configuration

  4. On the Basic SAML Configuration section, if you wish to configure the application in IDP initiated mode, enter the values for the following fields:

    In the Reply URL text box, type a URL using the following pattern: https://<SUBDOMAIN>.my.whosoffice.com/int/azure/consume.aspx

  5. 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 a URL using the following pattern: https://<SUBDOMAIN>.my.whosoffice.com/int/azure


    These values are not real. Update these values with the actual Reply URL and Sign-on URL. Contact WhosOffice Client support team to get these values. You can also refer to the patterns shown in the Basic SAML Configuration section in the Azure portal.

  6. On the Set up single sign-on with SAML page, in the SAML Signing Certificate section, find Federation Metadata XML and select Download to download the certificate and save it on your computer.

    The Certificate download link

  7. On the Set up WhosOffice section, copy the appropriate URL(s) based on your requirement.

    Copy configuration URLs

Create an Azure AD test user

In this section, you'll create a test user in the Azure portal called B.Simon.

  1. From the left pane in the Azure portal, select Azure Active Directory, select Users, and then select All users.
  2. Select New user at the top of the screen.
  3. In the User properties, follow these steps:
    1. In the Name field, enter B.Simon.
    2. In the User name field, enter the username@companydomain.extension. For example, B.Simon@contoso.com.
    3. Select the Show password check box, and then write down the value that's displayed in the Password box.
    4. Click Create.

Assign the Azure AD test user

In this section, you'll enable B.Simon to use Azure single sign-on by granting access to WhosOffice.

  1. In the Azure portal, select Enterprise Applications, and then select All applications.

  2. In the applications list, select WhosOffice.

  3. In the app's overview page, find the Manage section and select Users and groups.

  4. Select Add user, then select Users and groups in the Add Assignment dialog.

  5. In the Users and groups dialog, select B.Simon from the Users list, then click the Select button at the bottom of the screen.

  6. 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.

  7. In the Add Assignment dialog, click the Assign button.

Configure WhosOffice SSO

  1. To automate the configuration within WhosOffice, you need to install My Apps Secure Sign-in browser extension by clicking Install the extension.

    My apps extension

  2. After adding extension to the browser, click on Set up WhosOffice will direct you to the WhosOffice application. From there, provide the admin credentials to sign into WhosOffice. The browser extension will automatically configure the application for you and automate steps 3-7.

    Setup configuration

  3. If you want to setup WhosOffice manually, in a different web browser window, sign in to your WhosOffice company site as an administrator.

  4. Click on Settings and select Company.

    Screenshot shows Company selected from Settings.

  5. Click on Apps/Integrations.

    Screenshot shows Apps / Integrations selected from Company settings.

  6. Select Microsoft Azure from the provider dropdown and click on Activate Login Provider.

    Screenshot shows Activate Login Provider selected for Microsoft Azure.

  7. Upload the downloaded federation metadata file from Azure portal by clicking on the Upload option.

    Screenshot shows the Upload option for a Meta Data file.

Create WhosOffice test user

  1. In a different web browser window, sign into WhosOffice website as an administrator.

  2. Click on Settings and select Users.

    Screenshot shows Users selected from Settings.

  3. Select Create new User.

    Screenshot shows Create new User selected.

  4. Provide the necessary details of the user as per your organization requirement.

    Screenshot shows the new User dialog box where you can enter user data.

Test SSO

In this section, you test your Azure AD single sign-on configuration with following options.

SP initiated:

  • Click on Test this application in Azure portal. This will redirect to WhosOffice Sign on URL where you can initiate the login flow.

  • Go to WhosOffice Sign-on URL directly and initiate the login flow from there.

IDP initiated:

  • Click on Test this application in Azure portal and you should be automatically signed in to the WhosOffice 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 WhosOffice 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 WhosOffice for which you set up the SSO. For more information about the My Apps, see Introduction to the My Apps.

Next steps

Once you configure WhosOffice 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 Cloud App Security.