This document describes how to set up multi-factor authentication (MFA) for Microsoft Office 365® with AuthPoint as an identity provider. Office 365 must already be configured and deployed before you set up MFA with AuthPoint.
Office 365 can be configured to support MFA in several modes. For this integration, we set up SAML with AuthPoint.
To undo the changes made to your domain after you complete the steps in this procedure, see the Rollback Instructions section at the end of this integration guide.
AuthPoint communicates with various cloud-based services and service providers with the SAML protocol. This diagram shows the data flow of an MFA transaction for a Office 365.
Before you begin these procedures, make sure that:
To start, you must download the metadata file from the Resources page in the AuthPoint management UI. Once you have the metadata file, you can configure Office 365.
We recommend that you choose the certificate with the latest expiration date.
The AuthPoint metadata provides your resource, in this case Office 365, with information necessary to identify AuthPoint as a trusted identity provider.
The default domain and initial domain in Office 365 cannot be federated. You must register another domain with Office 365 or follow the Microsoft guidelines to connect an existing domain to the Office 365 service. The configured domain can then be used when you configure AuthPoint.
Type Get-msoldomain -domain youroffice365domain.com to return the status of domains and verify that your account is not federated. If your domain is already federated, you must follow the steps in the Rollback Instructions section to change the status of your domain from federated back to managed before you continue.
If your domain is federated, we recommend that you run this command to return your settings: $saml = Get-MsolDomainFederationSettings -DomainName <domain_name>. This information is necessary if you want to undo the changes made to your domain.
To help you format the X.509 value as a string, see https://www.samltool.com/format_x509cert.php.
If you require authentication for desktop applications or other non-browser clients, you must also set this parameter for the AuthPoint ECP endpoint for Office 365 to use Basic Authentication:
Set-MsolDomainAuthentication -DomainName $dom -Authentication Federated -PassiveLogOnUri $url -IssuerUri $uri -LogOffUri $logoutUrl -PreferredAuthenticationProtocol SAMLP -SigningCertificate $cert.
If you need to enable Basic Authentication, the command must include -ActiveLogOnUri $ecpurl.
If you use the Microsoft Partner Center, the command must include -SupportsMfa $true.
Get-msoldomain -domain youroffice365domain.com
Complete these steps to configure Skype for Business:
This command must be used with an Office 365 administrator account on a domain that is not federated, usually the default Office 365 domain (<domain>.onmicrosoft.com)
This change takes about two hours to take effect.
Before AuthPoint can receive authentication requests from Office 365, you must specify the Office 365 client as a resource in AuthPoint. You must also assign the Office 365 resource to the user group that will authenticate through Office 365.
From the AuthPoint management UI:
You must have at least one user group in AuthPoint for authentication with Office 365 and you must assign an access policy for the Office 365 resource to that group. If you already have a group, you do not have to add another group.
Access policies for an Office 365 resource have a Basic Authentication option (also called Enhanced Client or Proxy) that you must enable if you require authentication for desktop applications or other non-browser clients.
In the AuthPoint management UI:
For SAML resources, if you select more than one authentication option, users must choose one of the available options when they authenticate. For example, if you select OTP and Push users can choose whether to type their OTP or approve a push to authenticate, but you cannot require that they do both.
You must sync your local AD users (which you synced to Azure AD earlier) to AuthPoint so that the users have the same attributes and they can be recognized by both Office 365 and AuthPoint.
To sync users to AuthPoint from Active Directory, you must add an external identity in AuthPoint. External identities connect to user databases to get user account information and validate passwords. For detailed instructions, see About External Identities.
If you use ADFS, you must add an ADFS resource in the AuthPoint management UI and install the ADFS agent on your ADFS server. For detailed instructions to configure ADFS, see MFA for ADFS.
If you have not installed and configured a Gateway, you must do so before you configure ADFS or sync users from your LDAP database. For more information, see About Gateways.
To test the integration of AuthPoint and Office 365, you can authenticate with a mobile token on your mobile device. You can choose any method (one-time password, QR code, or push).
In this example, we test the integration with the push authentication method (users receive a push notification in the mobile app that they must approve to authenticate).
If you enable Basic Authentication, we recommend that you also test MFA with an app that uses Basic Authentication.
This section is for users who want to undo the changes made to their domain. The steps in this section describe how to change the status of your domain from federated back to managed and how to reconfigure the settings for a previously federated domain.
Microsoft Office 365 does not support multiple federations on a single domain. Before you begin, confirm the status of your domain in Office 365.
To change the status of your domain from federated back to managed:
To restore the settings for a federated domain:
To restore the settings for your previously federated domain, you must have run the command $saml = Get-MsolDomainFederationSettings -DomainName <domain_name> in the Configure Office 365 section.