Azure Authentication
Azure Authentication is used as an alternative to Windows Authentication.
When you want to log into People Planner, you are first presented with an Azure login screen. When you fill this in correctly, you are logged into People Planner. This type of authentication can be used in situations where the user is not on the same domain as the People Planner application.
Azure Authentication relies on the following fields in the User table:
- AzureUPN
When running a People Planner application using Azure Authentication, the user-"the user" being the UPN returned by Azure-is validated against the Email and AzureUPN properties. If People Planner can find the user in its database, the user is logged in.
In the following sections, the authentication process for each of the People Planner components is described.
People Planner Azure AD authentication is only needed if you are running MyPlan as a standalone web application and the end user is authenticating via Microsoft Azure AD.
Azure AD authentication can also be used in certain security service scenarios.
If you have configured Maconomy to use Azure AD authentication and the end user is authenticating via Microsoft Azure AD when running the People Planner Windows application, you can configure People Planner to use UPN for authentication in .
See Azure Authentication for more information on how to set this up.