Bobcares

Azure Multi-factor authentication Setup – How we do it

by | Dec 1, 2020

Wondering how to setup Azure multi-factor authentication? We can help you with it.

Here at Bobcares, we have seen several such Azure related queries as part of our Server Management Services for web hosts and online service providers.

Today, we’ll take a look at how to set up Azure multi-factor authentication.

 

Azure multi-factor authentication setup

Multi-factor authentication refers to the system in which more than one system authenticates the user to access an application. This authentication offers better security for Azure clients.

In this process, first, the user signs in with the username and password in a normal way. The credentials are verified and then if the automated call authentication is activated, the user receives a call and is asked to confirm the sign-in attempt.

Now let’s take a look at how our Support Engineers setup the Azure Multi-Factor Authentication.

 

Creating a Multi-Factor Authentication Provider

  1. In Microsoft Azure, we click on ‘New’ at the left bottom corner >> App Services >> Active Directory >> Multi Factor Auth Provider >> Quick Create.
    azure multi factor authentication setup
  2. Next, we enter the name of the provider.
  3. Then we select the Usage model. Here, we are considering ‘Per Authentication’
    Note: It is not possible to change the usage model once a multi-authentication provider is created. So we need to consider the needs before choosing.
  4. Now we get an option about if we wish we can link the existing directory or not. Here, we are linking an existing directory name ‘bobcares’ that we previously created for a multi-factor provider.
  5. After we click on ‘Create’, it will list in our services list. Then we select the multi-factor provider that we just created.
  6. We select ‘Manage’ at the bottom of the screen and we will land on a new page.
  7. Here, we select ‘Configure’ to choose the authentication.
  8. Here, we can set the number of attempts, change the phone number from where the call is made (default number is already there), two-way message timeout (default is 60 seconds), one-time password’s timeout (default is 300 seconds) under general settings. Also, we can provide an email address where we can be notified if a one-time password is bypassed.
  9. When we scroll down the page, we see the fraud settings. Under Fraud Setting, we can choose to allow the users to send fraud alerts, block the user if an alert report, and also set an e-mail address where alerts are sent.

This activates the multi-factor authentication. When users sign in to their account next time, they will need to choose one of the three methods (automated message, text message, or mobile app). Using the chosen method, authentication is made to them each time they sign in to their account.

 

Enabling the Multi-Factor Authentication for Existing Directory

In the previous section, we saw how to link the directory to a multi-factor authentication provider while creating it. However, we can also do it for a particular user in the following way.

First, we go to the directory by choosing it from the left panel and click ‘Manage MultiFactor Auth’ at the bottom of the screen.

In the next screen, we select the user and enable or disable the multi-factor authentication for the user.

[Need any further assistance with Azure queries? – We are here to help you.]

 

Conclusion

Today, we saw how our Support Engineers setup Azure multi-factor authentication.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF