Authentication is the process of verifying the identity of a user. Typically, this requires the user to make a claim about their identity by entering their username and password.
You are required to enroll with Specops Authentication prior to accessing O365. The enrollment process will vary for each type of identity service. To enroll with an external identity service, such as Google, you will need to follow the link from the Specops Authentication web to the Google web page, and login with the email address and password associated with your Google account.
Identity services enable users to securely identify themselves when signing in. Identity services fall into multiple categories, including: username and password, social (Facebook, LinkedIn, Tumblr), and higher trust (Google Authenticator, Microsoft authentic, Duo Security).
The following identity services can be used to authenticate users in Specops Authentication for O365:
- Specops Fingerprint: Specops Fingerprint enables users to enroll and authenticate using devices with fingerprint scanners, such as smart phones and tablets. Users can press their finger to the fingerprint scanner on their device to instantly identify themselves. Users can also use Face ID to authenticate, if they own an iPhone X and above. In order to use this identity service, users must have the app installed on their mobile device.
- Specops Authenticator: Users can authenticate using the Specops Authenticator app. Users scan a QR code or enter a secret. Specops Authenticator then provides users with a six-digit one-time password, which must be entered in order to successfully authenticate.
- Mobile Code (SMS): Users will receive a one-time six-digit password via an SMS message, which must be entered in order to successfully authenticate.
- Email: the user’s email is used as an identity service by sending a code to the registered email address that the user then has to input in the field on screen. Email does not require enrollment, since it references the email address in the email attribute in AD (or any other attribute if it is overridden); it can only be used with domains associated with Specops Authentication.
- Personal Email: the user’s email is used as an identity service by sending a code to the registered email address that the user then has to input in the field on screen. Personal Email has to be registered at enrollment by the user and they may use any email address of their choosing.
- Trusted Network Locations: Trusted Network Locations is an identity service that allows administrators to designate certain IP ranges as trusted network locations.
- Manager Identification: When a user authenticates using Manager Identification, an email or SMS message is sent to their manager. Their manager must then approve the authentication request. Administrators can customize the notification that is sent, by adding custom information to the request notification. To make use of Manager Identification, each user must have a manager assigned to them in Active Directory, and manager accounts must have an email address/mobile phone number associated with their profile in order to receive authentication requests from users.
- Secret Questions: Users can select questions from a predetermined list and specify the answers to them. They must then answer these questions in order to authenticate successfully.
- Duo Security: With Duo Security, users can authenticate using the Duo Security mobile app.
- Okta/Okta Verify: Users can enroll and authenticate using their Okta account credentials.
- Symantec VIP: Users can authenticate using the Symantec VIP mobile app.
- Google Authenticator: Google Authenticator is an app that generates one-time passwords. A secret is generated and presented in the form of a QR code that the user scans. Google Authenticator then provides users with a six-to-eight-digit one-time password, which must be entered in order to successfully authenticate.
- Microsoft Authenticator: Microsoft Authenticator is an app that generates one-time passwords. A secret is generated and presented in the form of a QR code that the user scans. Microsoft Authenticator then provides users with a six-to-eight-digit one-time password, which must be entered in order to successfully authenticate.
- EFOS/SITHS (Sweden): EFOS/SITHS is a smart card-based authentication service, which enables employees (such as medical professionals) of authorities, municipalities, and county councils in Sweden to electronically identify themselves.
- Mobile BankID (Sweden): If users have the Mobile BankID app, they can use this to verify their identity.
- Google: Users can enroll and authenticate using their Google account credentials.
- Facebook: Users can enroll and authenticate using their Facebook account credentials.
- Microsoft Live: Users can enroll and authenticate using their Microsoft Live account credentials. Microsoft Live credentials are used to sign in to the Microsoft Cloud, including: Outlook, Office Online, OneDrive, Skype, Xbox Live, and the Microsoft store.
- Tumblr: Users can enroll and authenticate using their Tumblr account credentials.
- Twitter: Users can enroll and authenticate using their Twitter account credentials.
- Flickr: Users can enroll and authenticate using their Flickr account credentials.
- LinkedIn: Users can enroll and authenticate using their LinkedIn credentials.
Multi-factor authentication requires more than one method of authentication from independent categories of credentials: something you know (i.e. password), something you have (i.e. Mobile device), and something you are (i.e. Fingerprint).
The Specops multi-factor authentication model is dynamic. Users can choose which identity services they want to combine for enrollment and authentication, as long as they meet the requirements of the policy. Users enrolled with more identity services than required for their authentication will have authentication choice. This guarantees that end-users will always have the ability to satisfy the authentication policy, even if an identity service is unavailable (e.g. not having their mobile phone nearby).
A policy contains the rules required for enrollment and multi-factor authentication when accessing O365. A policy controls what identity services can be used, and how many must be used to verify the identity of end-users. The system administrator is responsible for configuring the rules in the policies.