Azure Authentication

The Azure Authentication functionality introduces an alternative authentication method that enables you to configure People Planner or MyPlan to allow users to log in using their credentials from the Azure Active Directory.

Attention: This Azure configuration is only needed if you are using Azure Authentication for People Planner without a Maconomy System. If you have configured Maconomy to use Azure you can configure People Planner to use UPN for authentication.
By default, People Planner's and MyPlan's method of authentication relies on Windows Authentication for user login. Windows handles the user login, and People Planner and MyPlan compare the username of the currently logged-in Windows user to the list of users in the database. If it finds that username, it loads the People Planner Windows application or MyPlan using the privileges and settings that are defined for that user. To switch to a different user in People Planner or MyPlan, the current Windows user must log out of Windows and then log in using a different user account.

You can use Azure Authentication instead of Windows Authentication, if preferred.

Note: Typically, MyPlan is configured to use Window Authentication in the IIS. When using Azure Authentication, you must enable Anonymous Authentication, and disable Windows Authentication.
When People Planner or MyPlan starts, it displays a login screen instead of retrieving the username of the current Windows user. From that login screen, a user can enter their credentials in Azure, which People Planner or MyPlan then matches against the list of users in the database. People Planner or MyPlan then loads with the privileges and settings of the logged-in user with those Azure credentials. When you use this authentication method, users do not need to log out of Windows to switch to a different user account.
Note: When you set up an application-such as People Planner or MyPlan-in Azure, you provide a name for that application. That name appears as the heading in the login dialog. For example, if you give People Planner the name People Planner Client when you set it up, the dialog heading becomes People Planner Client, although the dialog is actually an Azure login dialog.