The Joint Commission

Multi-Factor Authentication (MFA): Microsoft Authenticator

As of August 15, 2022: Multi-Factor Authentication (MFA) is required to access the DDSP.

MFA is a separate third-party application “add on” managed by you as the end-user. Your organization may already have an MFA application they prefer to use, or you may need to download an MFA application to use specifically for the DDSP.

The Joint Commission can offer limited guidance on the MFA applications listed below.

  1. Google Authenticator for Android and iOS

  2. Microsoft Authenticator for Android and iOS

However, please note: Whichever MFA add-on an organization elects to use is at their discretion and should be installed and supported by their own internal IT support. Joint Commission is not able to provide individual/site specific IT support on this topic.

This Help topic will cover Microsoft Authenticator for Android and iOS and uses the Android option as the example.

As with most/all other MFA solutions, Microsoft Authenticator is a third-party application. Additional information about Microsoft Authenticator is available via https://www.microsoft.com/en-us/security/mobile-authenticator-app

TIP: Your IT department may limit your ability to download from third-party websites; contact your internal IT for assistance.

If you have not previously installed Microsoft Authenticator, follow steps 1-4 below. Skip to step 5 If you have already set up Microsoft Authenticator for other applications.

  1. To download/install, select the MS Authenticator app from your App Store.

    Screenshot image of Microsoft Authenticator
  2. Once the app is installed there should be a MS Authenticator icon on your phone. Click on the MS Authenticator icon to begin.

  3. Follow the prompts to create an account. Select “Add work or school account”

  4. Screenshot of MFA account setup, indicating options to use the QR Code to set up account.

    Select “Scan a QR code”. Proceed to step #5 to login to DDSP using your laptop or desktop computer where a QR code will be provided to continue the MFA process.

    Set up MFA for the DDSP

  5. To enable MFA, log in to the DDSP and navigate to “User Settings” > “Manage Multi-Factor Authentication”:

  6. If no MFA has been previously enabled, you will see a message stating, “You do not have Multi-Factor Authentication enabled” and a prompt to “Register Device.”

  7. The platform provides a list of three Authenticators (Google, Microsoft, Authy) but your organization may have additional options, preferences, or MFAs already in place that may be used for the DDSP. Contact your internal IT department for assistance. Click “Continue” to begin registration.

  8. On the DDSP, you will be prompted with a scan code and a text code. Open the Microsoft Authenticator app on your mobile device. In the Microsoft Authenticator click on the kebab (three-dot vertical) menu and select “+ Add Account”; select “Work or School Account” and select “Scan a QR Code” A scanner will open within the app.

  9. Hold your device (e.g., phone) camera up to the QR code on the DDSP and scan the code. The Authenticator will update, saying “Account added,” and will display six-digit verification codes. It produces a new code every 30 seconds. Unlike a password, only someone with access to your phone knows the current code.

  10. Enter the six-digit code displayed in Microsoft Authenticator into the “Verification Code” field in the DDSP.

     

  11. Select “Verify”; you should see “You have successfully activated Multi-Factor Authentication” message:

  12. You will be prompted to enter MFA when logging in to the DDSP. When this occurs, click to open Microsoft Authenticator application on your device, select the DDSP account, then enter the token (code provided from Microsoft Authenticator software) into the MFA field in the DDSP.

MFA is specific and applied to each individual user and device, not the HCO or DDSP workspace. If a user has access to multiple workspaces, the MFA applies to all.

TIP:  If the clock shows less than 15 seconds, we suggest waiting for a new code to generate.

 

©The Joint Commission, All Rights Reserved
The Joint Commission is a registered trademark of The Joint Commission.