Logging in when Microsoft Single sign-on is enabled

Using two-factor authentication, you can only use one device to authenticate to log in to your Arbor account. Make sure you are not using a publicly shared device.

Logging in when two-factor authentication is enabled

Logging in for the first time

When you log in for the first time, you will need to set up a link between your authentication app and your MIS.

Go to the login page of your MIS and click the Log in with Microsoft button.

log_in_with_microsoft_sso.png

 

If you are already logged in to your Microsoft account in your Google Chrome browser, you will be automatically redirected to the next step. Remember - We advise using Google Chrome to use Arbor as this is the most secure and reliable browser.

If you are not logged in to your Microsoft account, you will be redirected to log in to your Microsoft account. You will be asked to either select the Microsoft account you want to use to log in to Arbor or log in to your Microsoft Account. You must use your default work Microsoft email address.

sign_into_microsoft.pngadd_microsoft_password.png

 

You may then also be asked to accept permissions for Arbor. Click Accept.

accept_microsoft_permissions.png

 

Once you successfully log in, you will be asked to set up a link to your authentication app.

2fac_setup_1.png

2fac_setup_2.png

Step 1 - Install the authenticator app

The example below shows the process for Google Authenticator, but the process will be similar for other authentication apps such as Microsoft Authenticator, Authy etc. Your screen may look different from what is shown here depending on your device and software version.

For Android, open the Google Play store and search for ‘Google Authenticator'. Select the Google Authenticator app and click Install.

search_for_authenticator.jpeg

 

For iOS, open the App Store and search for ‘Google Authenticator’. Select the Google Authenticator app and click Get.   

ios_authenticator.png

Step 2 - Connect your authenticator to your MIS account

Open your authenticator app and begin a setup. We recommend choosing the option of scanning the QR code (barcode), but you can do a manual setup instead using your 16-digit code.

Open your authenticator app and click Begin setup to connect the app with Arbor MIS (this button may be called something else on Android devices or for other authentication apps).

Top Tip: Make a note of the 16-digit code you will see in Step 2. You’ll need to tell us this code if your phone ever gets lost, damaged or stolen to verify your account.

use_code_for_authentication.png

Step 3 - Log in

Once the setup of your authenticator is complete, enter your Arbor password and the verification code into Arbor, and click Log in.

log_in_with_authentication.png

 

 

Logging in again

Go to the login page of your MIS and click the Log in with Microsoft button.

log_in_with_microsoft_sso.png

 

If you are already logged in to your Microsoft account in your Google Chrome browser, you’ll be automatically redirected to the next step.

If you are not logged in to your Microsoft account, you will be redirected to log in to your Microsoft account. You will be asked to either select the Microsoft account you want to use to log in to Arbor or log in to your Microsoft Account. You must use your default work Microsoft email address.

sign_into_microsoft.pngadd_microsoft_password.png

 

If you are logging in under a whitelisted IP address, you will be immediately logged in. If you log in using an IP address which is not whitelisted, you will need to complete second-factor authentication by entering the code generated in your app.

To get the verification code open the authenticator app. Enter the code (with no spaces) into the ‘Verification code’ field and click Verify access. If the code is correct, you will be logged in to the MIS.

verify_access.png

 

If you can no longer generate a code (e.g. you no longer have your phone or have uninstalled the app), click the orange button.

This will send an email request to your admin to revoke your original setup. Once your old access has been revoked, you will need to set up your authentication app again to be able to log in.

request_revoke.png

 

Logging in when two-factor authentication is not enabled

Logging in for the first time

Go to the login page of your MIS and click the Log in with Microsoft button.

log_in_with_microsoft_sso.png

 

If you are already logged in to your Microsoft account in your Google Chrome browser, you will be automatically redirected to the next step. Remember - We advise using Google Chrome to use Arbor as this is the most secure and reliable browser.

If you are not logged in to your Microsoft account, you will be redirected to log in to your Microsoft account. You will be asked to either select the Microsoft account you want to use to log in to Arbor or log in to your Microsoft Account. You must use your default work Microsoft email address.

sign_into_microsoft.pngadd_microsoft_password.png

 

You may then also be asked to accept permissions for Arbor. Click Accept.

accept_microsoft_permissions.png

 

Logging in again

Go to the login page of your MIS and click the Log in with Microsoft button.

log_in_with_microsoft_sso.png

 

If you are already logged in to your Microsoft account in your Google Chrome browser, you’ll be automatically redirected to the next step.

If you are not logged in to your Microsoft account, you will be redirected to log in to your Microsoft account. You will be asked to either select the Microsoft account you want to use to log in to Arbor or log in to your Microsoft Account. You must use your default work Microsoft email address.

sign_into_microsoft.pngadd_microsoft_password.png

 

I can't log in

You can help troubleshoot and fix login issues here: Troubleshooting Two-factor authentication and Google authenticator App issues

If you receive an error when trying to log in, follow these instructions: Troubleshooting Single sign-on login errors

Was this article helpful?
1 out of 1 found this helpful
I'm still stuck!

Comments

0 comments

Article is closed for comments.