Giving your workforce access to ahead

To access ahead, two conditions need to be met:

• The user needs to have a cloud identity within Azure Active Directory (AAD)
• The user needs to be part of one of the three AD groups that were connected to ahead

If all users in your company already have a cloud identity, please skip to the next paragraph. However, you are likely to have a considerable amount of blue collar workers (non-Desk) without any cloud identity. Currently there is no way around this condition so you will have to create those user profiles.

Some of the more frequently asked questions:

• Do we have to assign any M365 user license? No, to access ahead no M365 license is required.
• How does the user reset their password? Without a license attached, a person from your Service Desk has to reset the password. If you have Azure AD Connect to synchronise your user base, make sure to activate password write-back - otherwise you can't set a one-time password.

After creating the users, you have to give them access to ahead by adding them to either one of the AAD groups created previously. As mentioned in the previous lesson, there are three user roles in ahead:

• User
• Editor
• Administrator

For each of the roles there is an AD group in AAD. The following article describes what each user group can and can't do: What can the different roles in ahead do?

You can also use aD groups that are synchronised from a local (on-premise) Active Directory. We also support groups in groups (a.k.a. nesting).