Login through Microsoft Office 365

SigningHub gives you an option to use your Microsoft Office 365 credentials to log into SigningHub. In this case, you don't even need to have a SigningHub ID, as your Microsoft Office 365 account will be used for SigningHub authentication. Currently, Office 365 uses Azure Active Directory (Azure AD) to manage identities and authentication. However, logging in through your Microsoft Office 365 credentials for the first time, will take you to the registration screen and display your Microsoft Office 365 ID (email address) for new registration. After registration, you can easily login through your Microsoft Office 365 credentials.

---

Login through your Microsoft Office 365 account

1. Go to the SigningHub login screen.

2. Click the "More Login Options" link available at the bottom of the login screen. A dialogue box will appear listing all the supported authentication methods.

3. Click the "Microsoft Office 365" option. The Microsoft Office 365 app will appear in a popup.

4. Specify your Microsoft Office 365 ID and password in the app.

5. Click the "Login" button. SigningHub permissions screen will appear.

6. Click the "Accept" option. You will be authenticated into SigningHub.

1. As a part of GDPR compliance, the "Service Agreement" dialogue box will appear after successful user authentication. This dialogue box contains the links to the "Terms of Service" and "Privacy Policy" pages. SigningHub will ensure that you agree to them before letting you use your account.

2. The "Service Agreement" dialogue box will not appear after successful user authentication if no Service Agreement is marked active.

3. When using an on-premises installation of SigningHub and this is the only configured authentication for the end-users, then you won't need to click the "More Login Options" link to choose it. In that case, this authentication method will be invoked by default on the Login screen.

4. Users cannot log in to SigningHub if their account is disabled, marked as dormant, or temporarily locked due to multiple invalid login attempts.