Preface
Many smaller companies do not use an on premise Active Directory, which is the primary authentication and identification system used by Locator. These companies often only use Office 365, and as such, their primary authentication and identification system is Azure Active Directory. This guide is meant to give you the required steps on how to change from Active Directory to Azure Active Directory as the primary authentication and identification system.
Prerequisites
You need to have Locator installed before starting this reconfiguration task.
...
- A service account in Azure AD that has the role Administrator
- Create an Azure AD APP - for instructions on how to create this, follow this guide (scroll down to Setting up the Windows Azure Graph API for Locator)
Step-by-step guide
Follow these steps to reconfigure your system to use Azure AD as primary authentication and identification system.
...
| Info | ||
|---|---|---|
Please note If Multi Factor Authentication is enabled for additional security for the Office 365 tenant, authentication will fail in Locator, as MFA is not currently supported. If MFA is enabled, you need to have your Office 365 tenant administrator whitelist the public IP used by the server Locator is running on. If you are unable to log on after you have followed the above steps and see this in your w3wp.exe.log file:
It is very likely that Multi Factor Authentication is enabled, and a whitelist entry has to be made. |
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...