On the drop down menu, choose a new integration type to add:
Microsoft 365: Connects OfficeMaps to Microsoft platforms which provide support for authentication and calendars.
Embrava: Connects OfficeMaps to the Embrava Desk sign in system which allows users to confirm that they have entered an office.
PointGrab: Connects OfficeMaps to the PointGrab system which automatically detects users entering an office space.
In the new screen create an Integration Label, a name that can be easily identified within OfficeMaps.
After entering a Integration Label you must save the integration before continuing. The SAVE button is visible at the top right of the card. After this, you can continue to edit the integration details.
Microsoft 365 / Azure AD
Enter the information below to enable OfficeMaps to connect to Microsoft 365 / Azure AD.
Authorise Microsoft Log In:
Authorise OfficeMaps: This setting will allow all users to connect to OfficeMaps through a browser and the mobile application using their Microsoft credentials.
Clicking on this button will redirect to a Microsoft dialog where an Azure AD Administrator will be able to enter their login details to confirm consent.
Authorise Microsoft Sync:
User Groups: The name(s) of existing Windows Group/s to source users from. Organisational Units and Dynamic Distribution Lists cannot be used for this field. If more than one group is required, separate the group names with a semicolon (e.g. Accounts;Management). During a sync, users from the named groups will be added to OfficeMaps with the role User if they do not already exist in OfficeMaps.
To ensure that the AD Sync process is fully configured, you will also need to adjust settings in Administration → People (under the Settings section on the side menu). More information about this process is available in the later section AD Sync Settings in Administration → People.
Make sure that you have saved your integration by clicking the SAVE button before leaving the Integration page.
Clicking the Authorise Access to Microsoft button will redirect to a Microsoft dialog where an Azure AD Administrator will be able to enter their login details to confirm consent.
It is possible to authorise Azure AD Log In permissions without using AD Sync, but all users will need to be created or
imported manually and their email address field must match their Azure AD
credentials.
Tenant Schema Extension App Client ID
DO NOT EDIT OR USE THIS VALUE UNLESS SPECIFICALLY REQUIRED.
OfficeMaps can read information from Azure AD to set OfficeMaps user details. Most fields can be read directly but for some fields in Azure AD (including custom fields), Administrators will need to record their Tenant Schema Extension App Client ID. The Azure AD fields that will require a value in this field are:
Initials
IP Phone (Phone Extension)
WebPage
as well as any custom field.
To get information about how to find your Tenant Schema Extension App Client ID please contact
support@officemaps.com.
Enable Calendar Read Access
Setting this check box will allow OfficeMaps to display a user’s or an asset’s calendar from within the application.
Authorise Calendar Write Access
Setting this check box will allow OfficeMaps to update a user or asset's calendar when a meeting is created from within the application. Clicking the Authorise Access for Calendar button will redirect to a Microsoft dialog where an Azure AD Administrator will be able to enter their login details to confirm consent.
Additional settings are required to finalise configuration of the Azure AD Synchronisation. To view these settings, choose the Main Menu (Company Name) → Administration → People (under the Settings section on the side menu).
If using Azure AD to add people to OfficeMaps, select the second option in the section How Are New People Added? This will ensure that the default Azure AD integration is used to add new users to OfficeMaps.
Additional settings can control the behaviour of the AD Sync process when a user's Azure AD account is disabled or when users are removed from the User Group(s). Choose the options that meet your organisation's requirements:
- Users in OfficeMaps who are members of the named User Group(s) will have their role set to Disabled / Non User if their Azure AD account is disabled.
- Users in OfficeMaps who are removed from the named User Group(s) will have their role set to Disabled / Non User.
It is also possible to control the behaviour of the AD Sync process if an existing OfficeMaps Non-User / Disabled account is re-enabled in Azure AD.
- Non-User or Disabled Users in OfficeMaps can be re-enabled if their membership of the named User Group(s) is restored.