Pass Your Microsoft Identity SC-300 Exam Easy!

Microsoft SC-300 Microsoft Identity and Access Administrator exam dumps vce, practice test questions, study guide & video training course to study and pass quickly and easily. Microsoft SC-300 Microsoft Identity and Access Administrator exam dumps & practice test questions and answers. You need avanset vce exam simulator in order to study the Microsoft Identity SC-300 certification exam dumps & Microsoft Identity SC-300 practice test questions in vce format.

Initial Configuration of Azure Active Directory

6. Set a Custom Domain

You. So you'll remember when we created this tenant that we basically had to choose a tenant name, and that tenant name goes as part of the fully qualified domain name for the tenant. And you might think, "Go, what's the implication of this?" Where does this domain come into play? Well, yeah, there's going to be some internal code when you need to access your active directory in a programme in order to do authentication of users. Nobody's going to see the domain that's being connected to. But what does happen is when you go to try to add a user to your domain and you want to say, "Okay, let's start adding native users as part of my organization." So I want to add Joe Smith as a user. In my case, the only available domain is this default domain, mydevtenancesc 300 dotMicrosoft.com, and there are no other domains and I cannot specify one. So if your company is example.com and your user is Josemith@example.com, you can't set this up without configuring Active Directory for the domain. And so in this video, we're going to add your company's domain as a custom domain to your tenant. We're going to get out of the user space and go back up here. Now, right under Manage, we see a custom domainnames option, and the default domain is here. But let's say we want to add our company domain. In my case, it's getcloudskills.com. Now I'm using a domain that I have control of because then we're going to have to validate that we own the domain, and we'll go through that process. So you're going to add your company's domain name to this custom domain and say "add." But in order to prove that we own it, we do need to add either a TXT domain record or an MX record. A TXT record is pretty straightforward. Now, if you don't have control of this domain—let's say you are an employee of GetCloudSkills.com and you don't know where the domain registration happens—then you're going to have to work with whoever does have that. So this record needs to be added to the domain registrar. Now I use a company called Namecheap, and so I'm going to have to go into my domain registrar under Get Cloud Skills. I can say Manage under the DNS section, and I'm going to have to add a TXT record to that section. So it says here TXT record hostname is at sign TL. So go back to namecheap and I'm goingto see add new record TXT host. Is that paste in that value? They wanted 3600. I'm going to leave it as automatic. It doesn't really matter. and so that's been added. Now there is a thing with domains that is called "propagation," where you update your registrar, but that doesn't get pushed into the global name registry for between twelve and twenty-four hours, and then it takes a while from there to propagate to other caches. Now it's possible that Microsoft doesn't have this domain cached anywhere, and it needs to end up going directly to my domain register to get that. So let's say verifying is successful, even though the status is unverified. So I was able to in those fewminutes, verify this domain, go back here andwe can see Get Cloudskills.com is now verified. Now the one thing you might want to do at this point is to set your new custom domain as a primary. So if you click on it, you can say "make primary," and then the old Microsoft.com domain goes away. And anytime you refer to this, you can refer to it using your custom domain name. I'm not going to do that right now. But if you wanted to make it primary, if youdidn't like this setup, you wanted to go away, youcan certainly make this your primary domain and it wouldbe what's shown everywhere, including the overview page. So that means I can go back to Users and add a user, and I can add in Joe Smith and choose the Get Cloud Skills domain and start to fill in some information. So in this way, we haven't gotten into talking about adding users, but we can see that we can customise the domain name through this. And now we've got an Azure Active Directory that will allow us to work with this domain name because we verified ourselves. So that's how you add a custom domain.

7. Manage Devices

So the next requirement of the exam is to talk about how Azure Active Directory manages devices. Now it's a bit difficult to show, so we're going to do our best here to demonstrate this. But when you go into your tenant and you go under Devices, there are, by default, no devices listed, and there doesn't seem to be a way to add a device. So what exactly is this? So what it is is that you have your, let's say, on-premises workstation computers, and you want to join them into Azure so that you can do some type of authentication using them in other applications. And so you can basically, through Windows, Mac, Linux,basically register a device into your Azure tenant. It also works with iOS and Android. You can register your Android into your AzureAD tenant using the Microsoft Authenticator app. to start the app store for Apple. also has a Microsoft Authenticator app. Now for Desktops, for Windows for instance, there isthe concept of having a user in Windows. You go under Settings, under Users, and you can say "Connect." And the user, say, a work user, will enter their work email address into this field. And because we've set this up so that Azure Active Directory manages the authentication for this domain, then this user is going to have this device added into the devices section. Now I haven't gone in and created users and thingslike that yet, but this is how you would adda Microsoft Windows Workstation as a device in Microsoft Azure. So just to demonstrate, I'm going to go ahead and create a user. I'm going to name them Test Users and add them under Settings. Under Users, we're going to say "Access Workerschool," "Connect," and we're going to try "Test user@getcloudskills.com." Now somehow the Microsoft Network has alreadyrecognized that Getcloudskills.com is a domain managedby my Azure Active Directory tenant andit's asking for my password. Now this is the first time I'm signing in soI have to change the password, which is great. You can see it now, right? It says it registered this device with your company and applied any policies. Hopefully I don't have any strange policies that are going to affect my home computer. All right. So now my test user, Get CloudSkills, is associated with my computer. And if I go back to my tenant and go under devices, and if I refresh, then I can see my Windows device, which happens to be my desktop, and say, here it says it's registered. So there are two main types of devices that are registered or joined. Registered is like a bring your own device scenario or a mobile device scenario where it just says, "We did. We had a user account, and we logged in, and we basically registered our device with this tenant." A joint device is actually more like a company-owned device. So this is where you have basically total control of the device. It's suitable for users in your organization, but basically you're going to control the device. So that is a joint device. Now, this is going to be difficult to demonstrate, and I do appreciate your patience here, but if you go under Android and you go under Settings and you go under Accounts, go to the bottom, you will see AddAccount, and you'll see Work Account. So you click on that, and now we're into this workplace join screen. So I'm going to enter the test user that we created. Now I have multi-factor authentication turned on for this user. And the Authenticator app is connected to this phone already. So I just have to give my fingerprint there, and it's asking for my password. I entered that; I'm going to save it. And so now it's doing some work. To join this, I do need to download a certificate and an RSA certificate. So that is authenticated. The certificate is installed. I say, "Okay, unlock authenticator again." And now my phone goes into the Authenticator. But what I should have is this phone registered to my Azure tenant. So now I have two devices registered to my tenant. One for my desktop, one for my Pixel. Both of them are registered, not joined, but associated with me. Now, in future videos, we can talk about the types of authentication where we can restrict applications to only these devices, approved devices, etcetera, or to devices that are joined, but not devices that are not joined. We can do device-specific security and other settings in the future video. The final thing I'll show you is that if we go under device settings here, we can basically prevent users from joining devices. We can restrict users based on the registration that we just demonstrated. We can require multi-factor authentication to join devices. We can limit the maximum number of devices per user, like the one you saw me register too.But how many do I realistically need? 510, 2050. So those are the device settings. You can see the relatively few settings that we have in this particular section. So these are the devices associated with my tenant. Let's keep going.

8. Administrative Units

So the next topic on the exam is the topic of administrative units. under your Azure ad. Tenant, you manage administrative units. Now, an administrative unit is effectively a logical grouping of users and groups that may be managed administratively together. So let's say you have a really large organization. Maybe you've got tens of thousands of users and groups. Not every single Help Desk member helps every single one of your 10,000 or so users, let's just say. So you've got your business group, your marketing group, and your sales group. That doesn't make sense. So let's say you've got your North American Team, your European Team, and your Asian Team, and those teams all have users that they manage. And you don't want your Asian team doing anything to your users on your European team. You want them to basically have some limits on the amount of control that they have. So what you're going to do is create an administrative unit, and in that unit you're going to assign all of the users from Europe to the European Administrative Unit for North America, to the North American Administrative Unit, to Asia, to the Asian Unit, etc. Here, let's create our units. So I'm going to give this a name. I'll call it the North American unit. And this is going to contain, again, all of the users and groups that are in North America. We're not going to deal with rules right now. We're just going to say "review and create" and say "create." So really, it's almost like a TAG or a piece of metadata. We're going to say these are the users that are part of the North American unit. Now, I could do the same thing for the European unit, and I hope I don't make a typo. and the Asian unit. All right. So now I've created three Administrative Units. If I go back to my users, I've added a bunch more test users. For this example, let's say I'm going to go into this user, student one. "Oh, this student one, I happen to know, is part of the North American unit," I want to say. And so now I'm basically assigning this user to this unit. I can do that for other students and other users within my account here. So let's say we go down our list of users and groups and add them to an administrative unit. On the other end of the spectrum, let's go back to Administrative Units and choose the North American unit. We do have to look at the roles and the administrators who can manage this unit. Now, Microsoft gives us these seven categories of roles: Help Desk, License Password User, etc. Let's go under "Help Desk." Now, as just so happens, this is a brand new tenant. I have not assigned any users to the Help Desk role. So let's add one. I want to create some teacher users. So let's say the teacher user is the Help Desk Administrator for the North American unit. So I assign an administrator or more to each of the administrative units and multiple users as the users of this unit. And in doing so, I'm basically limiting the scope of the help desk administrators to only the users that are in the same administrative unit as them. So to view this, we can go back to the tenant, go under the roles, and go under the user. First, let's go to the teacher that we just assigned this to. We can look at the assigned role, and we can say that they have been assigned the help desk role. But the resource type is administrative unit, and the resource name is the North American unit. So this person has a limited helpdesk administrator assignment to this resource. So, in a sense, we reduced the number of users that this help desk administrator can actually manage. So, administrative units. This is a way of reducing the scope of roles for specific groups within your organization.

9. Manage Azure AD Company Branding

So the last requirement of this section says to modify some tenant-wide settings. Now, most of these blades within the tenant will be talked about elsewhere in this course. We'll talk about users and groups and external identities, app registration and governance, ad connect, et cetera. Perhaps when you get down here is when you start to see some things that are not covered by the course, and maybe we can talk about this here. So one interesting thing is this concept of company branding. Now by default, you don't have any company branding, but I created one here. If I add a new brand, it gives me the option of setting a background image on the sign-in page. I can upload my company logo. I can give the user a hint if they don't know their username. So I can say it's the same as you use on your desktop at work. There are some other texts you can put on the page. You can pick a custom color. This is a nice purple here, along with some logo options. So if I say save, then these options are going to start to show up for end users. And so it takes the boring, drab, white Microsoft stuff and turns it into something a bit more interesting. For example, the end user, in this case testuser at cloudskills.com, has a portal called My Account (Myaccount@microsoft.com.And as soon as I change the branding, I can see my logo show up on this page. So that gives the user a feeling of trust that their account is associated with your company. Now, more prominently, if I sign out here, I'm going to sign out of being a test user. We can see the custom colouring that I chose, the logo that shows up when I go to login with that user, the colour coming back, and it says thanks for stopping by, which is some custom text I put in there. And we can see this sort of customization based on that company branding here. So I'm not going to save this; I'm not going to stay signed in and then go back to My Account. You can create different branding for different locations, so different languages and things like that. We look at user settings; there are only a couple of settings in here, and we can see that users can register applications. We'll talk about registering applications later in this course. We could actually restrict access to the AV portal. Now, what this means is that a testuser@getcloudskills.com can actually log into the Azure portal. Let's say I give it permission to do something, and it can get into the AD Active Directory portal. But I can't do anything unless I grant any sort of permission. So if I was to restrict access to it, only administrators would be able to see the administrative portal at all. There's a LinkedIn setting here and other features. Okay, properties, please allow me to rename the tenant. If my developer tenant turned out to be a bad name, I couldn't change the country even if I wanted to. Because that's what that said. It's sort of permanent. I can put some contact information in here. Privacy Statement I can grant myself the user logged in as management for this, so I can basically ensure that I have access to this tenant this way. Those are pretty much the generic settings for this tenant. The rest of this logging and diagnostics will at that.So, yeah, that's the end of the basic settings for a tenant. Again, as we go through this course, all of the requirements of this exam make sure we're going to go through a lot of these other settings, so don't worry about that.

Configure and Manage Identities

1. Create and Manage Users

So in this section of the course, we're going to be talking about creating, configuring, and managing identities within Azure Active Directory. And specifically, we'll be talking about user groups and assigning and managing Azure Ad licences between them. Now I'm logged into the portal, and I've switched to my Azure Active Directory, which I am the global administrator for. And remember, in the last section, I did upgrade to Premium 2 on a free trial. But that's not too relevant for this section of the course. So we'll be talking about user groups and licences in this section. Now the primary purpose of Azure Active Directory is to manage identity in the cloud. And what that means is you might have some users and you may have an application, and you want to use Azure Active Directory to authenticate these people so they can log in using their user ID and password, optionally. They can have multi-factor authentication. And once Azure Active Directory approves that they are who they say they are, they've passed all of these system checks. They basically pass a token to your application that you can validate and say, "Okay, yes, they are who they say they are." The other thing that is done within Azure ID is the authorization, which is what permissions this user has. So if I go into the users section of AzureAD, I already have some users that I created. I've created a bunch of students and teachers. But basically, you might not have any users in your test Azure ad. Or if you're working within your organization, you may have hundreds or even thousands of users. So the basic concept of a user is that you're basically going to create a login, user ID, and password. And it can have various properties, such as a name and an associated email address and location. And there are other properties that are optional. So let's go into the users section of Azure AD and say "new user." So we're going to create a full-on member of this Azure ad. Now, we remember when we were creating custom domains that we were given this default domain, theonmicrosoft.com, and we were able to add a different domain. Whatever ID you choose is the one they're going to have to use to log in. Let's leave this as the default on Microsoft.com. So you can see the red asterisks here to indicate which are the mandatory fields. Let's call this person Test User Two, and the green check mark indicates that the user is available. And then I can give it a proper name, which is also mandatory. All of the other fields, which the screen doesn't even show, are optional. So first name, last name, and we can have it auto-generate a password or we can create a password for it. We won't talk about groups yet. We'll assign this user to a group in a second. We can basically turn, you canhave them enabled or disabled. We can specify which country they are most likely from and other details. These are all optional fields, so I can say "create." So test user number two has now been created. Now, by default, this user has no permissions or rights. Okay? So if this person tried to log in using the system-assigned password, then they would have pretty much access to nothing, not even your application or anything within Azure. Now, we do have this concept of external users. We do have a section coming up to talk about external users. And so we'll leave this for now. All right, so we're able to click on the user that we created to see more details about that user. We can see that this user was just created and has never signed in to some of the details, including the job info and some contact info that hasn't been filled out yet. So this person has an actual profile, if you will, and you could use this almost like your company directory. And if you were using a synchronisation tool like AdConnect to synchronise with your on-premises Active Directory, some of this stuff could just be pulled over from your on-premises Active Directory. Now, let's say you're not using this as an on-premises Active Directory and this is just for the cloud only.If they called you and said they were notable to access their account, as a customer support person, you can simply click to reset their password. You can edit some of their biographical information, et cetera. You can basically ensure that any of the logged-in sessions that are currently logged in are revoked. We have a few features here on the left. We haven't talked about roles yet, administrative units, groups in the next video, any kind of applications that they're part of, et cetera. So all of the basic stuff is here, but we're going to dig into that later in this course. So that's it for users. I mean, you can create, I'm going to say, as many users as you want, but there are limits to the number of users you can create. quite high limits, but there still are limits. And as you get into the premium plans, you're going to be charged based on users and licensing. So we'll talk about licences in this section as well, because some of these users will be free and some will need a license. And we can deal with that coming up.

Go to testing centre with ease on our mind when you use Microsoft Identity SC-300 vce exam dumps, practice test questions and answers. Microsoft SC-300 Microsoft Identity and Access Administrator certification practice test questions and answers, study guide, exam dumps and video training course in vce format to help you study with ease. Prepare with confidence and study using Microsoft Identity SC-300 exam dumps & practice test questions and answers vce from ExamCollection.