User Settings

ezdeploy is transitioning from Azure B2C to Auth0 for the creation of user accounts. This allows for the ability to provide and require MFA (Multi-Factor Authentication).

An additional new feature is the ability to link to your Microsoft Account. This will allow you a more seamless SSO experience as well as enforce MFA via you Microsoft Account if so configured.

All Azure B2C user accounts (users created prior to 5/12/2022) will have the following initial options:

Update profile to enable MFA

Update profile to migrate existing B2C user account to new Auth0 local user account and enable MFA. MFA mandatory for migrated profiles.

Link to Microsoft Account

Update profile to link your Microsoft account and migrate off existing B2C user. If you are enforcing MFA on your Microsoft account - that will be used once link completed.

Dark Mode

Dark Mode is available on a per user basis by navigating to Settings>User Settings and clicking checkbox for Enable Dark Mode.

No save is required - it will convert to dark mode upon selection such as this example.

To revert to Light Mode - uncheck the Enable Dark Mode option.

Clear User Page Layout Settings

Clicking the Clear button will clear any filter row selections, text you have entered as well as any groupings on grids across all pages.

 

New users completing signup for the first time will be choosing to create the Auth0 local account or link to their Microsoft account right from the start. So if you start out with Auth0 local account - you will still show the option Link to Microsoft account as available - but not the Update profile to enable MFA option.

Update profile to enable MFA

  1. Navigate to Settings>User Settings and click the Enroll button next to Update profile to enable MFA.

     

  2. The next page you will input your same credentials as currently logged in. If your passwords match, you will be directed to confirm you want to Enroll in MFA.

     

  3. Enter your email address and current password to enroll.

     

  4. You will be prompted to secure your account. Use Microsoft Authenticator or whatever MFA app you like, and scan the QR code, and input the MFA code then continue.

  5. When this process is successful, you will be Logged Out, and you should now login with the same credentials. This time the Password box will NOT disappear. This is how you know at this point that the B2C user has been migrated.

  6. It may ask for MFA code, so enter that and proceed.

  7. You will be logged back into ezdeploy and should land directly on the Settings page. If all is successful, there should be Green text reading Enrolled in MFA.

     

  8. That is the completion of the MFA activation flow. You will be required to enter MFA code at login unless you check the Remember for 30 Days checkbox on the MFA one-time code dialog.

 

Link to Microsoft Account

To switch from current local user account to SSO controlled by Microsoft Azure Active Directory.

  1. Navigate to Settings>User Settings and click the Link button next to Link to Microsoft Account.

     

  2. After confirming the dialog, you will be redirected to the Microsoft Sign In prompt.

  3. You may have multiple Microsoft accounts listed to choose from - normally you would be selecting Work or school account - select the primary account you use to access your organizations resources for Active Directory/Office 365 etc.

  4. If your existing Microsoft account already has MFA enforcement you may see prompt like this from Microsoft or another MFA provider like DUO.

     

  5. If you are the first person in your organization to attempt link - Microsoft will prompt you to allow ezdeploy Authentication to read your profile - click Accept. If you do not have administrative rights for your organization you will need to have an administrator grant permission to the ezdeploy app.

     

  6. Then you will be logged in. If you go to your Settings>User Settings you will see Connected with Microsoft Azure AD noted.

     

 

 

The content of this site is proprietary and confidential information of Stack Advisors, LLC. It is not intended to be distributed to any third party without the written consent of Stack Advisors, LLC.