Single Sign On: Azure AD

Officebooking supports Single Sign On (SSO) logins through SAML 2.0 when you’re on the Business Plus, Enterprise edition or subscribed to SSO in combination with any other subscription. We support both SAML 2.0 via self hosted Azure AD.

If you’re not familiar with Active Directory and SSO concepts, please start here.


Step 1: Access to OfficeAdmin and AD environment

This guide assumes someone in your organization (or Officebooking Support) has already created an Admin account for you. This account will give you access to the OfficeAdmin portal.

Next, you’ll need administrative access to your company Azure AD environment. Once you’ve gained access to both environments you can start implementing the integration.


Step 2: Set identifier in the OfficeAdmin

  1. Login to the OfficeAdmin portal and go to the ‘Settings’ page in your menu. Open the tab ‘Integrations’ on the top of the page.
  2. Here you choose the ‘Single Sign On’ option.
  3. First select ‘Microsoft’.
  4. Enter an SSO id that resembles your company name.
  5. The SSO id is included in the SSO metadata URL which will be created later in the process.


Step 3: Configure Azure AD

  1. Login to Microsoft Azure Active Directory admin center.
  2. Select the button ‘Enterprise applications’ in the left hand menu.
  3. Select ‘New application’, then select ‘Create your own application’ and enter a name for the application, i.e. ‘Officebooking’.
  4. Start with assigning users and groups. Select which users should get access to the Officebooking app.
  5. After assigning users and groups, go back and select the button ‘Set up single sign on’.
  6. Then select the option ‘SAML’.
  7. Here you have to add the Identifier and Reply URL for the Officebooking app.

For Identifier (Entity ID) you need to enter the following url. Change the ssoID in the url to the id you’ve entered in the OfficeAdmin portal in step 2.[your configured ssoID from step 2]/metadata


For Reply URL (Assertion consumer Service URL) enter the following url.
Again change the ssoID to your own id.[your configured ssoID from step 2]/consume



Step 4: Enter user attributes

Next, enter the attributes. We will need at least the following attributes:

  • givenname (first name) – user.givenname
  • surname – user.surname
  • emailaddress – user.mail


Next to the mandatory attributes, it’s possible to add the following optional attributes:

  • labels – user.extensionattribute1 – This will send through any labels added to the user in AD, for example the label ‘firefighter’. This user label will be visible in all apps, at Who’s at Work.
  • employeeid – user.employeeid – This will send through the user id from AD. This user id will be only visible for an Admin in the OfficeAdmin and can be used for HR purposes.
  • office – user.physicaldeliveryofficename – This sets the default location for the user. Note: you’ll need to match the location ID with the Location UID in OfficeAdmin! The Location UID can be entered in the OfficeAdmin via Location > Select location > Edit > Enter UID > Save location.

Note: in the case you’ve added these attributes, these extra attributes need to be activated in Officebooking. Please contact Officebooking Support, and they will help you activate this.



Step 5: Enter metadata URL in the OfficeAdmin

After following the steps above, you’ve collected the right metadata URL to enter in the OfficeAdmin portal (add to the field you’ve left open in step 2). The metadata URL will be something like:


Copy the ‘App Federation Metadata URL’ and enter it in the OfficeAdmin portal at ‘SSO Metadata URL’.



Step 6: Start testing

  1. Make sure you add your