Hello, Siberians. Welcome to this demonstration on a giant E identity protection.
This lesson is part of the second model off the Is that 500 Microsoft Azure security that largest costs. Quick information on the tax that will complete in this demo will start by reviewing as your 80 licensing for identity protection. Well, then, configure the user risk
on the sine inverse policies in identity protection.
We'll conclude by validating the policies are applied by simulating a risk event. Let's get into this.
So the first thing that I do is to review Mijo, 80 tenant to ensure that I have to require addition for identity protection.
I also review where to configure as your area identity protection policies in the azure Pato. So here I am in the azure Pato. If I click on the Potter menu icon on the left inside, and if I click on as your a D
now India view section, I can see that I have the azure 80 premium Peter Addition.
However, I can also go on the licenses
and I can click on life since features.
If I search for identity,
I can see the identity protection feature listed here and I can see that Yes, I am licensed for this feature.
If I go back to the men as your a d window
and if I scored Ammen, click on Security
under Security. I have identity protection here on this is where we'll be completing the next pass off, configuring our identity protection policies.
So in the nest, Ask will configure the use of this policy in identity protection.
Yes, official representation off what I'll be doing
Our configure. The use of this policy now include all users but excludes my designated break. Let's account
the policy will apply to all users that have Avis level off low and above. On the control of their apply is to require a passwords change. Let's get into this.
So here I am back in the azure Pato
on the left hand side, fatally con identity protection.
If I go ahead and click on user this policy
on on the assignment I click and that on I select all users. However, I want to exclude my break less account on my designated break. Let's account
if I click on exclude on, I go to select excluded uses,
I'll select David with the designated account. Click on Select
on our click on Done
Now. I want this to apply toe any either waas a risk level off low and above on our click on conditions to configure this, so that's already selected. But if I click on the option to show you what are the options are available, you can see that I can change. That's a medium and above all, to high. Only I'll just leave that aslo and above and click on select
and actually come down here
on the control that they want to apply is to require passwords. Change. However, our click on each tours to show you other options that are available. You can see that I can block access. I can allow access and require passwords. Change, which is what I want in this case, are just great and click on select.
I'll click on on to make sure that the policies and fast on our click on Safe
and that successful So we're good
in the next task are configure the sign Invest Policy in identity protection.
On is a visual representation off what are between our configures sign in this policy that includes all uses for excludes my designated breathless account.
The policy will apply to all sign in events that have a risk level off medium and above.
On the Controlled I'll be applying is to require MFP. Let's get into this.
So here I am back in the Azure portal if I go ahead and click on Sign in Risk Policy on the left Inside.
If I click on assignment on the users
and I leave that selected as all users about why don't exclude my designated breathless account,
which is David on, I'll click on Select and I'll click on Done.
The condition that I want to apply is for medium and above risk levels,
but you can see the other options that are available day. I'll just leave that take on, select and click on down
the controller. They want to apply, used to require M f A.
I'll click on. That's to show you the other options. I can block access, allow access or allow access, which MF required, which is what our configure in this case.
Go ahead and click on select. If I click on Save How enforced a policy and I'll click on Save Now that successful which means we're good.
And the final task off this demonstration Hobby validating that the policies that have configured I indeed being applied. How do this by simulating a risk event?
Yes, Official representation off. What are between how access and a 80 application is in a top browser, which will Anonima Mayes, the I P address,
however redirected to Azure 80 on our authenticates to heat
identity protection wouldn't have always the signing event Onda tacked on anonymous I p address which, as a medium risk level
because of signing this policy, is configured of acquire Maffei. For this levels medium and above the usable requires to complete m f A.
However, the user that I will be using in this case as no, you actually start for MF A which means that their access we actually be blocked.
So here I am on my test machine on my test mission as the top browser installed.
If I go ahead and open the top policy,
I was gonna connect. So the tor network, which we anonymized the i p address
how great on access and as your 80 application my half start, Microsoft does come
and I'm actually what indicates, Tries i 80
if I quiet on, put in the user name,
and if I click on next,
I'm actually enter the password for my user
quiet and puts that in and I click on signing.
Now I get an error message that says my signing was blocked on again. The reason why it gets this is because this user issues to register for Emma Fee as human. This user has registered for an iffy, though actually be required to complete MFK.
Now if I go back to the azure Pato, and if I click back on the security and click on identity protection,
we need to give it a few minutes for the risk information to be displayed in the azure portal. So there's a bit of a lock day.
So what are do is out positively cutting to you. The event has been detected,
and now it took a few minutes for the events to be displayed.
But if you go ahead and click on viscous signing on the left hand side, you can see the authentication failure for Brenda on. We can go ahead and review the reports down here
so we can see that's that failed, and we can see the user that signed in. We can go ahead and see the device information, the risk information being anonymous, i p address detected.
And we can quiet and view the information they the other things that we can do it. You can configure notifications. So notifications to be sent based on the lots on. We can specify the user risk level that wants notifications to be sent hat.
We can also configure notifications 2% on a weekly basis. No, that was Just get getting a weekly report based on the detection that have happened.
So here's a somebody off the tax that were completed in this demonstration.
We started by reviewing as your 80. Licensing for identity protection
wouldn't configure the user risk and Sinan vis policies in identity protection so fast it pass what we said for any user with this level of low and above on also to require Emma free for any sign in activity with a risk level off medium and above.
In both cases, we excluded at designated bricklayers account according to best practices,
we concluded by validating the policies are applied by simulating a risk event.
This brings us to the hand of this lesson. Thanks very much for watching on. I'll see you in the next lesson.