Pass Microsoft 365 Certified: Teams Administrator Associate Certification Exams in First Attempt Easily

Microsoft 365 Certified: Teams Administrator Associate Certification Practice Test Questions, Microsoft 365 Certified: Teams Administrator Associate Exam Practice Test Questions

Want to prepare by using Microsoft 365 Certified: Teams Administrator Associate certification exam practice test questions efficiently. 100% actual Microsoft 365 Certified: Teams Administrator Associate practice test questions and answers, study guide and training course from Exam-Labs provide a complete solution to pass. Microsoft 365 Certified: Teams Administrator Associate exam practice test questions and answers in VCE Format make it convenient to experience the actual test before you take the real exam. Pass with Microsoft 365 Certified: Teams Administrator Associate certification practice test questions and answers with Exam-Labs VCE files.

Introduction

6. Introduction to Teams

Let's do an introduction to teams. Now, if you actually just look at Microsoft's website on Teams, they walk you through what the point of Teams is, with Microsoft Teams being their main messaging platform. Now they tell you it's the hub of teamwork in Microsoft 365. Chat from anywhere, meet from anywhere, call from anywhere, and collaborate from anywhere. They've got some nice little videos on there that walk through things with you. Of course, that's what we're learning in this course. Now, I'd like to show you that you can download the team application directly from their website. You can click "download teams." You can also open it up through the Web portal. In fact, let's go to Portal office.com.All right. And at that point, let me just sign in with my credentials here, and it's going to allow us to see the different apps that are available. And the one we're interested in right now is Teams. So we're going to go right here into Teams, and that's going to pop up the team's Web-based application. It also gives you an opportunity to download the app here as well. For the most part, you'll have the same experience, though I'll go over the different browser support, apps, and so on with you in the course. Again, I'm just kind of introducing you. So here I am in Teams, and at that point, I can set up what are called Teams and Teamschannels, and I can see all the activity that's happened. I can see chat messages directly with other users and the different teams and calendar options. Here, we're scheduling meetings. I got calls that had been set up. That's everything we'll cover in the course, the different calls. Another thing is file sharing. We're going to talk about all of that. I've got all these apps available. So if I want to set up an app, I can click on, for example, "Stream." I can pin that That's called pinning. So the app is available to me there. You can even set up bots that allow you to chat and get support and help.Okay, you have all of these apps available to you, but you can also go down here, where it says "Apps," and your company can purchase additional apps and make them available to you and Teams. Okay, so this is all just right here in the main team application itself. Now another thing we're going to spend a lot of time on is the administration side of things. In other words, Teams' "behind the scenes"—or "under the hood," as it were. And we're going to be spending a lot of time on Portal Microsoft.com.If we go there in our web browser, we can get to the Teams Admin Center by clicking on the left over here where it says Teams or clicking Shaw. You're going to hear me say that a lot in this course. I may sound like a broken record between videos because I like to always give a sort of starting point because I've seen instructors in other courses go through and show you how to get somewhere one time and then hours later they revisit somewhere and you don't remember how you got there. So I kind of repeat myself a lot and say, "Okay, you're going to start here on portal.microsoft.com and then you're going to click Teams." Keep in mind if Teams does not show up, and you'll also hear me say this a lot, click "Show all" because that's going to show all of your admin centres at that point. So that brings us into the team's admin center. Again, this is going to be one of the main under-the-hood areas that we'll be discussing as we move forward with all of these different options. Okay? So hopefully that gives you just a quick introduction to what we're looking at. And again, as we go along in the course, we are going to dig deep into all of this stuff.

Administration in Microsoft 365 for Teams

1. Administration with the Azure Portal

I'd like to start out by taking a look at just some of the administration of working with our Microsoft 365 and Azure services. Now to start with here, I want to look at the Azure Portal, which is where you can manage your users and your groups and some of the security and all that involves Microsoft Azure, okay? This is also where Azure Active Directory sits, which is, of course, your directory services, where user accounts, passwords, and all that stuff is going to be managed. So to get there, we're just going to go to Portal Azure.com.So you're going to type portal.azure.com into your URL bar there, and it's going to bring you into the Azure Portal. Once you get into the Azure Portal, if it's your very first time ever going into it, it's going to ask you to take a little tour. You can close out of that if you want. And then you're looking here at your main Azure objects that you've maybe recently used before. So here are some of the things that I've recently been into. Now what you're going to do is you're going togo up in the upper left hand corner and you'regoing to click this little menu bar here. So you drop that little menu bar down, and you'll see that you'll have different objects here that you can click on. Now these are called blades, okay? They'll call these blades. And you have a home blade, a dashboard blade, on which you can look at some of the objects. You can actually create your own little dashboards here, which is kind of neat. You can click on "new dashboard." You can organise things the way you want it.So every time you log on to Azure, things are organised a certain way. If you want, you can save that. You can go full-screen with it if you want. Now the other thing you'll notice is that you can see all of the Azure services by clicking on the All Services blade. And it kind of organises it all by category, okay? So you can kind of click through and look at some of these different options if you want. You can search for services there, which is handy. Or when you do find something that you want, you can add it as a favorite. Okay? So for example, if I were to search for, let's say, tune, I could see In Tune, I can hover over that with my mouse cursor here. And then I've got this little star here, and that will make it a favorite. Okay? The next thing is, once you've done that, if you click the little menu bar, it shows up as a favourite down here. So these are some of my favorites. Now the thing that I want to focus on right now, though, is Azure Active Directory. So we're going to click on the Azure Active Directory blade. This is where your user accounts, groups, and things like that are all going to be managed. Okay. So I can go right over here, click on User, and if I wanted to create a new user, I could simply click New User. Okay. Create a new user. Or I could invite a user as a guest if I wanted to. This comes in handy. So for example, when working with teams, I might want to invite somebody to be a guest of a team who doesn't even belong to the organization. You could have a Gmail account, for example, and I could invite you to be a guest. Okay. Or if I want, I could create a new user, which is kind of what I'm doing here. So I want to create a new user. Maybe I'm going to add a username, Bob Hyatt. Okay. That's going to be my username. So, username: Bob Hyatt. Okay. And then put in the information from Bob Hyatt here. And then I could set a password, auto generated. Let me choose a password if I want. Select the password, whichever you want. You could add groups here. Okay. You can add roles. All right. I could block the user from logging on right now if I wanted. This is good in a scenario where maybe I am going to say maybe we're hiring this person, but they don't start till next week. I could block them for now, so the account couldn't be used. Or if I wanted to block a user later down the road, maybe you've got a situation; maybe you've got a lady who is pregnant. She's going to go have her baby. She's going to be on maternity leave for the next three months. So I could block that account. I don't want anybody using that account while she's gone. I could do that. It is also possible to do usage location. Now it's important that with Azure and the Microsoft 365 services, you're going to have subscriptions that you can assign the user to. It's very important that you assign a usage location. The funny thing about the Azure Portal for creating user accounts is that it doesn't require you to assign a usage location. The problem is, if you start assigning licences to the user, like to use Office 365 so they can get access to your Microsoft 365, Office 365 Services, Exchange, SharePoint, and Teams, then they've got to have a licence for that. And in order to get a license, they have to have a usage location. So I'll make sure to enter a usage location, and in my case, I'll select United States.

Okay. And then from there, I could specify a job title. Okay. So maybe this person is going to be in our finance department. So I'm going to say this person is the finance manager, and the department is going to be financed. Okay. So you could put that in if you want. And the department attributes are extremely useful because, once you start working with groups and all of that, you can assign someone to a group based on criteria such as department or job title. There's also additional information you can configure once the account has been created. Okay, so there's a lot you can do here, from creating the account to the groups; they're members of roles, which gets into assigning privileges to the user. So then I can just click "Create" and the new user is created. Okay. So from there, I can go back. If I click on the name of my Azure AD domain, which in my case is Examlabpractice, which is associated with Examlabpractice.com, I can click that, and I'm back in Azure Active Directory. Okay? You can also just click the menu bar here and then click Azure Active Directory as well. That will bring you back in here. So I've got my users and my groups. I can go create a group if I want to. All right? And I can click to create a new group here, specifying the kind of group I want to create, all right? And then I can start assigning users to the group.

Okay, so a lot of control here as far as creating my objects, creating groups, and assigning users to groups. With Azure Active Directory, you can set policies. You can set permissions. This can be linked to intune and control your devices and settings. I can control the password reset here if I want. I can even allow what's called "self-service password reset" if I want. Okay, where you have to, it will allow you to prove that you are who you say you are in order to reset your password. Now, by default, when you first setup a new tenant with Azure, you don't have self-service password reset enabled. You'd have to turn that on, for example, if you wanted it. However, at that point, you can allow users to reset their passwords and so on. There are even some additional settings there that I'm not going to talk about right now that you can configure as well if you want to. Okay? And so another thing that you've got that you kind of have to think about too is that in order for users to get access to the different services, applications, and things that they want access to, such as Exchange Online, SharePoint, and Teams, and your Office 365 downloadable apps, they have to have a licence for that. Now back over on the Azure Active Directory side of things, I've got a blade called licences that I can click on, okay? And from there, I can click on all products, and I can see what products I've got available. Okay? Now what we really care about here, if I'm trying to give access to my office apps, is the Office 365 E-5 subscription. There's also an F-three subscription here, but you can see exactly what you get by clicking on the subscription. And you can click on service plan details and see the different things that you get. Okay? So, for example, if I'm wanting users to have access to teams, this Office 365 EFive is going to give them teams, okay? They're going to get all sorts of things here. Yammer, as you can see, has a lot of stuff here that you get from exchangeonline, and version two is planned. Another thing is the Microsoft 365 apps for enterprise.

That's the downloadable version of the Office apps. Now I want to clarify. When it comes to licensing, one of the best things you can do is look up that subscription type, and you can see exactly what Microsoft is going to give you, like Office 365 E 5. I can look that up. You can just go out there and search for it. Office three, six, five, and eight, and you can see what you're going to get with that plan. All right? Microsoft has pretty clear information on the things that you're going to get if you go and look up the subscription. I like to do this too. There's Office 365 E5, and there's e three.If you do this, if you type Office 365, e3 versus e5, for example, they give you a nice little list of tables you can look at. See here, it says "compare." You can see that there's e three, there's e five, and there's f three. You can see the different things you're getting with each subscription, okay? And you can also, of course, expand out the little plus signs here, okay? Like, for example, the E-5 is the most powerful subscription you're going to get that's on this list. You also get advanced compliance settings, e-discovery, lockbox, data governance, encryption key management, and data protection. So you do get some great features with that identity management. Okay, I'm not getting in all the depth on all that right now, but I encourage you to check that out, look, and see what you get out of that subscription. And you can even see what the current going rate for a monthly cost is per user. Okay? Finally, with the help of Azure Active Directory, it's fairly simple to get in there and look at your users, groups, and licenses.

2. Administration with the Microsoft 365 Portal

Let's now take a look at administration and basic administration with the Microsoft 365 Portal. So in order to get to Azure, for example, we would go to Portal Azure, but in order to get to the Microsoft 365 Services Portal, we're going to go to Portal Microsoft.com. Now keep in mind that when you administer users and groups and all that through the Microsoft 365 Portal, it's all stored in Azure Active Directory. So whatever you do here involving Azure Active Directory is going to tie into that as well. So if you're using Portal Azure.com and you're using Portal Microsoft.com, you're going to look at the same users. The same users are going to exist in both places.

So if I click on the users drop-down here and I click Active Users, I'm going to see the same users that I have in the Azure Portal as well. Okay? So here are these users that I've got listed. And if I wanted to create a new user, as you can probably guess, I've got an add a user option here, and I can create a user here. So if I wanted to create a new user, and let's say that this new user is going to be called Zack, All right? Zach Jiminez is here. We've got our user display name username, and I'll just say Zach Jiminez here. So my username is [email protected]. auto-generate the password. I can require the user to change their password at their next login. I can send a password upon email completion if I want. And then at that point I can click Next, and I can specify the usage location. Now, one thing that's interesting here that we don't have over on the Portal Azure.com method is I have to choose a usage location here, which is important because, again, I cannot assign a licence to the user unless I have a usage location. It will throw an error. But one thing that's great about adding it to the Microsoft 365 Portal is that I have to do it. I have no choice. It's going to make me select the usage location. So at that point, if I wanted, I could also assign the licence too. I can go ahead and assign a licence through this if I want, right? Simply by selecting "Office 365," I'm going to give this user Office 365, and maybe I'm going to give them Enterprise Mobility Plus Security, but I don't have all the details on that yet. You could obviously look it up, but I'll get more into the security side of things as we go along. But I'm going to assign those two licenses, and then at that point, granted, don't forget that if you wanted to not assign a licence right now, you could do it later if you wanted to. Okay? You can also select which applications the person receives based on their license.

Keep in mind that you can do all this through the Azure Portal as well. It doesn't let you do it when you're creating the user. You have to create the user and then go back and do it. Okay? So at that point I could click "Next." I can assign a role if I want to click Next. It lets me verify everything that I've selected, and then I can click Finishand I've now officially created my user. Okay, so my user is here, and the user will also show up in Azure Active Directory. Keep in mind, sometimes it takes a minute if you jump over to Azure Active Directory for it to show up, but it is there. Okay? And then from there I could go over to groups, and this is where I would go to create groups. Okay? I'll be talking more about groups, but this is where I would add a group, and I can assign users to a group through this and manage my group through the Microsoft 365 Portal. Okay, so another thing you can do as far as licences and all of that stuff is concerned is drop down billing and click on licenses, and you can see the licenses. Just like within the Azure Portal, I can go and see exactly what licences are available to my users. I can do the same thing through the Microsoft 365 Portal. So what you're going to find is that there's a lot of similarity there.

There are also certain things that you'll find that you can't do through the Azure Portal that you can do through the Microsoft 365 Portal, and vice versa. There are some things you can't do in the Microsoft 365 Portal that you can do in the Azure Portal. Okay? So yeah, believe it or not, all the features are not exactly the same, but there are a lot of similarities there, okay? and they do both tie back to Azure Active Directory. So whatever you do here will still involve Azure advertising, and vice versa. But from here, I've got another thing I can do. I can control some settings here. But here's what I really want to also point out. You have what are called administration centres that you can use. In fact, if I click "Show All," I can see everything. I have a lot of different admin centres, including teams here for team administration. but not just teams. You've got Exchange and SharePoint, and you've got something called Endpoint Manager that gets into managing Intune. Okay? Here's a look at Azure Active Directory. If I click Azure ActiveDirectory, something interesting will happen. It actually redirects me to the Azure Portal. So, I'm back over here on the Azure Portal at that point. So they don't actually let you manage a full-blown Azure Active Directory from the Microsoft 365 Portal. They want you to do that through the Azure Portal. Okay, but anyway, the point being, this is basic administration for your users and groups. Again, I'm not going into too much detail about groups right now, but it shows you the fundamentals of navigating between the Microsoft 365 portal and the various objects that you have here versus doing it through the Azure Active Directory Portal, Portal Azure.com. So those are your two main portals: PortalAzure.com to manage Azure and PortalDotMicrosoft.com to manage the Microsoft 365 side.

3. Powershell Foundations

Now, like most Microsoft environments where we're working with products and trying to manage products, one of the things that Microsoft has really, really put a lot of stock in over the years is PowerShell. And if you're going to do administration with any of the cloud services, whether it be Teams, Exchange, SharePoint, Azure, Ad in Tune, or all the cloud services available now as well as the security and compliance capabilities of the Microsoft cloud services, PowerShell is still a major component of really working with and managing all that. The fact that your Microsoft services are available is an important piece of the puzzle. Okay, I want to spend some time making sure that you guys have the fundamentals because it's really hard to understand the more advanced things that you can do with your command line environment if you don't understand the basics. So I want to make sure that you understand the foundation of PowerShell.

Now, of course, if you already feel like, "Oh, I'm an expert with PowerShell," you can move on. But this is going to help you acquire the fundamentals that are needed for working with PowerShell. The first thing to understand is that you can get into PowerShell in your operating system by clicking Start and searching for PowerShell. You can right-click your Start button in Windows, like Windows 10, and go to Power. So I recommend opening up PowerShell as an admin because you're going to have administrative privileges, and some of the things that you're going to want to do, you're going to need administrative privileges for. Okay, and the other option is to open it if you're in command prompt. If you go to the command prompt, you can just type the word PowerShell, and you can get into the command prompt and work with PowerShell that way. Okay? Now there are two main ways of dealing with PowerShell. One is right here in the PowerShell command line environment, where you can run commands similar to what you're used to with command prompt. Or maybe you had experience with DOS back in the day, or maybe you're a Unix or Linux person. So you're very comfortable with the way that working with the command-line environment goes. This is great for you. Another way is that Microsoft has a scripting environment that is built to help you with writing scripts involving PowerShell. and it's called the Ise. You can type ISE and that will open up the integrated scripting environment, which will help you if you are wanting to run scripts and things like that within PowerShell. This is a great way to do it because it's going to sort of walk you through the process of writing a script. Okay, I'll look more at that here. It's coming up in just a minute. though I'm going to minimise that.

Get back into regular PowerShell. Now. PowerShell really does live up to its name. It's an incredibly powerful commandline environment. If there is such a thing as an intuitive command-line environment that is easier to use, I really do think that you have a good case to argue that PowerShell is one of the easiest command-line environments you can use because it has a lot of tools to help you and make your life a little easier. Okay? For one, it works off of a verb-noun system. Whenever you run a PowerShell command, it's going to start with a word that is a verb, and then there's going to be a dash, and then there's going to be a noun. For example, if I want to see some information about something, I'm going to use the verb get. "Get" means get me some information. However, if I want to change or alter something, I'll use the word set. Okay? Set is going to let me modify. It's going to let me alter something or change something. If I want to delete something, I could use the word "remove." That's going to delete something. Okay? If I want to move something, I'm going to use the word move; if I want to copy something, I'm going to use the word copy. Okay? If I want to start something like a service, I'm going to use the word "start." Then, if I want to put an end to something, I would use the word stop. Okay? So it uses a verb-noun system. Speaking of services, for example, if I wanted to see what services are running on my Windows operating system right now, again, not even talking about the cloud right now, but just right here on Windows, I could type Get and then the word service. Oh, and by the way, PowerShell supports IntelliSense, so if you start typing a noun, you can hit the tab key and it will try to figure out what it is you're typing. Now if I were to just type "get the letter S," I could tab through all these commands that start with the letter S. If you accidentally pass the one you're looking for by hitting tab, you can hold down the shift key and go backwards if you want. There's no reason why you should have to type out a big long command like that because you can use the tab command to help you. I'm going to type "Get Ser. And there it is. I'm going to hit Enter, and it's going to show me the services that are running on this Windows computer right now.

Okay? Now if I wanted to stop a service, say, let's say I wanted to stop this search service right here, I could say "Stop service" and then the name of the service. Or maybe I want to start a service like RM when it, for example, is currently stopped. I could say "start services." Notice how I'm just changing the verb from get to start. I typed "Get Service" as a secondary, and I'm typing "Start," and at that point, Get Service." And then I could say her name. Now, keep in mind that some of the commands you run will give you a default output. Like if you type "Get service," it's going to give you a default output. But if you're trying to run certain commands, they need additional parameters. And that's what these dashes right here are. So you'll do a start-dash service, the verb, noun, space, and then a dash, and then you'll be reidentifying a parameter when you do that, all right? That's the purpose of that, so get rid of that message. Now I'm going to specify the service I want to start. So I'm going to say win, RM. That's the service. Hit enter. And with PowerShell, a lot of times, no news is good news. If you don't see a bunch of red text, then whatever you did was right and it started the service. Now, if I type "Get service" and hit Enter, you should notice that the Win RM service is officially going to be running on my machine. Now, see, it's running. Okay, I can clear my screen by typing CLS. I just cleared my screen. Now watch this. I'm going to stop that Win RM service now. I started it. I'm going to stop at Stop Service and then type WinR and hit Enter. And there you go. I've stopped the service if I type "Get service again." And by the way, you can just hit the up arrow and it'll cycle through the commands you've typed, all right? And then it'll show that that service is now officially stopped again. Okay? And by the way, speaking of the Win RM service, that is a command. I'm sorry, a service that lets you remote into your machine allows machines to remote into your machine.

If I wanted to remote into another machine and run commands, that service must be running on the destination computer. Okay, again, we're not talking really about the cloud here, but if I wanted to remote into another machine, I could. So I could actually type "get service." Check this out. Computer name. And then, whatever the name of the other computer is, if the other computer is called client 68, I could hit Enter right now. And if there really was a computer called client68 that's running when RM starts, I could actually get into that machine, run, and see the services that are running on it. Another thing you can do is actually type "Enter PS Session," the name of a computer, "computer name," and then "client 68," for example. And I can remote into that other machine and run commands directly from within it instead of just running one command at a time. Now, I'm not really getting into all that in this course because I'm sort of more focusing on teaching the fundamentals and then getting into the cloud. and how we're getting to the cloud. But I did want to clarify that that's something you can do with your PowerShell. Okay? So that's one of the things that makes PowerShell so powerful: the fact that you can run lots of commands locally, but you can also very easily remote into another machine. I can say "get process," for example, and that's going to show the processes that are running on this computer right here. But I can also, if I wanted to, say, "Get process ComputerName client," which will say "tencomma clientele," my client," twelve commas," whatever. I could see the services on all those machines. Another thing I can do with PowerShell PowerShell supports something called piping. Piping is where you take the output from one command and send it to the input of another command. So, for example, I could pipe-use that little bar symbol. That's the symbol above your inner key with the slash. If you hold down Shift and hit that backslash, it'll create that character. Okay? And then, if I wanted to, I could say "outfile," "this is going to output it to a file," and "clientprocesses," if I wanted text. Right? And that would generate a file on the C drive called Client Processes. Okay. And it would actually generate it from those three computers if those three computers would allow me to remote into them. Okay? So that's the idea of being able to pipe the output from one command and send it over to the input of another command. I'll show another example of this coming up in a minute. All right. But PowerShell makes it very easy for us to do so. The other thing PowerShell does is allow us to get help on things. For example, if I wanted to see, let's say, the Windows event log, I could type "get," okay? But the problem is, maybe I don't know how to use the command correctly. So if I hit Enter, for example, it tells me I'm missing a value. I need to specify a login name. I'm going to hit Control C to escape out of that. Okay? You can type "Get Help." All right, get help on that if you want. And if you type "get help," I could say "get help" and then type "get event log." And then it'll ask me if I want to download the latest help information from Microsoft. I'm going to say no to that, and it's going to show me a little bit about using the syntax of that. Okay, using its syntax of it.But I'm going to tell you, I'm not a huge fan of their help documentation built into PowerShell. What I love to do is look the commands up using the browser. So let me jump into the browser and I'll show you really quickly how you can find the Knowledge Base article on this command. Okay? So just popping over here at Google, if you type that command, get EventLog," and you just search that, you're going to find that there is a KnowledgeBase article on just about every single PowerShell command. So I encourage you, anytime you're working with PowerShell, to just search for the command on Google or something like that. Pop that up and you'll see the very first link there shows you how to use this command. So it even gives examples, which I really love. So like for example, get event log, LOGNAMEshow me the newest five entries or whatever. It even gets in a little bit of scriptinghere, how to declare variables and all that. Great. They have some great examples, though, that will really help you. Okay? In fact, let's say we wanted to create a little script—we'll do this in the ISC—that was going to get the latest five entries of the security log on this Windows machine. And then I want to save it as a file, and I want to reformat it as a list instead of a table.

And I'll show you the difference here, too. So let's jump over to the ISC again. Okay, so right here in PowerShell, remember to get an ISC. You can just type ISC. It's going to open up the integrated scripting environment. And I want to show you how it kind of helps you when you're doing this sort of thing. So with the ISC, I can type "get event log," for example. And then if I space over and hit dash, notice that it shows me all the parameters. See how much easier this is? If you're trying to write a script or something, you have the parameters right here in front of you. All right, I'm going to do log name, and then here's one of my favourite things about it: space. It's going to show me the logs that are available, okay? So not only does it detect the parameters, it detects the objects that the parameters are associated with. In this case, it's the log. So I'm going to click on security, and then I'll hit space and I'll say "newest," and we'll say "ten entries," okay? So from there, can I hit play? And it's going to show me the ten newest entries. It's going to run the command down here. Problem is the entries are so long, this table viewthat the Get event log tries to show it. It shows it in what's called a table view. It can't show at all. It can't put it in a format where I can see everything. So I'll pipe that in using that little bar symbol. And there's a command called formatlist. Okay? You can see all the format commands here too, if you want. You have a bunch of options here. The format list is the one I want. And then if I hit play, it's going to format it all as a list for me, okay? And then if I wanted to pump this into a text file, I could say, "Pipe out C drive security log text," and it would then put it in a file on my C drive. So now if I go to my C drive, I can say "DIRSTAR text" and there it is right there. So if I want to look at the Notepad security log, it's going to open up in Notepad, and here it is in Notepad, and I can kind of peruse that at my convenience. Okay, so that's very helpful. So the other thing you can do here with PowerShell is declare variables. For example, I could declare a variable called dollar sign computername equals client ten, and then I could throw a variable in here, say dollar sign computername, and declare that now that I've declared the variable up here, I can call on that variable here. This is just a very basic example of using variables in PowerShell. And if I want to run this whole thing, I can hit the play button using ISE. Or if I just want to run one line at a time, I could hit this run selection button here, and it'll run just that one line.

Okay? So declaring variables in PowerShell is really easy. You just use a dollar sign. If I say dollar sign NUM equals one and then say dollar sign, we'll say numb equals two. I could say dollar sign numb plus dollar sign numb plus dollar sign numb plus dollar sign numb plus dollar sign numb plus dollar Hit Enter, and it's going to add those together. It gives you a three. very basic example here of declaring a variable, and then you can utilise those variables, especially when you're doing scripts. One more thing I want to mention about dealing with PowerShell When you save a script, it gets saved with a PS1 extension. The other thing is that on the computer that you're running it on, you need to make sure that the computer supports it and hasn't been restricted from using scripts. So for example, if I type "get," there's a thing called "execution policy," and by default, Windows computers have a restricted execution policy. So, if I run Get Execution on my computer, it will already be set to Unrestricted, allowing me to run scripts. But if you're sitting at a new Windows computer, like a new Windows 10 computer, you'll need to type set execution policy, and then you can set it to execution policy. You could set it to unrestricted. You have different options here. Unrestricted is what I've got. Mine too. So I can run scripts on my machine. Okay. All right. Hopefully, that gives you a quick look and a quick foundation of PowerShell, as well as a basic understanding of how to work with PowerShell and how it can really benefit you. We didn't really look at it from a cloud perspective here; we just looked at it from a local computer perspective. But hopefully, that gives you a little bit of an understanding of utilising PowerShell commands and how they're formatted.

4. Connecting Powershell to the Microsoft Cloud Services for Teams Administration

Let's spend some time now talking about how we can use PowerShell to connect to our cloud services. Now, the first thing you need to understand is that when you have a newly created operating system, you don't have access to cloud-based commands, Microsoft 365 commands, or things like Teams and Exchange Online right out of the gate. You actually have to install the commands. Now you can run the command, you can say "Getcommand," and you can hit "Enter," and it'll show you all the commands that you have right now in memory. Of course, in my case, I have actually installed my cloud-based commands. When I scroll down this list, I'm going to see some Azure commands and some Microsoft 365 commands and all that. There is one way to search to see if you have, for example, if I wanted to see if I had my Microsoft 365 commands. Those commands are called the MSOL commands. So if you actually type the Get command, hit the spacebar and type Noun, meaning I want to search for Noun. And if you were to just type MSOL and hit Enter, nothing's going to happen because there is no command where MSOL is just the only acronym in the noun. But you actually want to search using wildcards. So if I hit the up arrow, watch this. If I put a star before the MSOL, that's a wild card. It's going to show me every command that ends with MSOL. If I was to put the star at the end, it would show me every command where MSOL starts as the noun. But I'm actually going to search and see everything that's got MSOL in it in general. By putting an asterisk at the beginning and end, it will search for every command that contains MsOL anywhere in the now.

Now in my case, again, I've got these commands. In your case, you may not, though, if this is a newly installed version of Windows. Okay, so what we've got to do is install those commands. We can actually install them over the Internet. using this command. We can type "Install module" and then "MS Online." So if you hit Enter on that, it's going to ask your permission to basically install a Path variable into a PowerShell. You're just going to hit "yes" to that. It'll also ask your permission to install something called Nougat, which is going to be the software that's going to download the commands from the Microsoft PowerShell Gallery. And then it'll tell you that it will ask your permission to install from the Microsoft PowerShell Gallery because it'll say it's an untrusted gallery. Even though it is Microsoft's gallery, it is a community gallery. so it'll ask your permission. You're just going to hit "yes" to that. In my case, I already have the commands for this, okay. Now the other thing we're going to want is, when we want to run these commands, to connect to the cloud. Right now we're not connected. So for example, if I type get MSOL user, this command would display all of my users. The problem is I'm not connected to the cloud service right now. Okay, so to connect to the cloud service, you're going to type connect service and hit enter. It will pop a little box up on the screen, and this is where you're going to put your cloud credentials in. So I'm going to put in [email protected] and then I'm going to put my password in here, and at that point, it should connect. And as I like to say, no news is good news. If you don't get an error message, you're doing good.

Okay, so we're going to type "get MSOL user" and now I'll be able to see my user accounts. Okay, so these are the same user accounts. I have my Azure Active Directory, which is hosted in the cloud rather than on-premises. I checked this out. If, let's say, I wanted to create a user account or something like that, I could actually create a user. I can type. Okay, all I have to do is change the verb to "new MSOL user." And I'm going to do the principal user name. Don't forget that if you don't know how to use these commands, Microsoft's knowledge base articles are excellent. So if I didn't know how to build a user account off the top of my head, I could just go out there and search for this command right out here on my search engine. So if I type new MSOL user and I hit enter, it's going to be the very first article, and I can go and see examples on how to use this command. It tells me all the parameters and shows me how to use it. It's very nice, and I definitely encourage you to check that out to use those PowerShell articles. So if I wanted to create a user, let's say I wanted to create a user named, let's say, "the user's email address." The user principal name is an email address. Type name. I'm going to say, let's say, David. [email protected]. Okay, close quotation mark. And then I'm going to specify his displayname, which is going to be David James. And then I'm going to say that my first name is David and my last name is James. and then let's go ahead and throw him in a department. Let's put him in the marketing department. So we'll say he is going to be in the marketing department. Now the other thing I can do is hit dash here, and I could tab through all these different parameters. even if I wanted to. I could specify a usage location like "us." I could also do it; let's say I wanted to get his license. I could actually assign a license.

If you go to their knowledge base article, You can look up the licence codes for the various Microsoft products and assign them, such as an Office 365, a five-user license, and so on. So I'm just going to hit Enter, and I'm going to create this new user. And now my user David James has been created. So at that point, I should be able to go back over to Portal Azure.com or Portal Microsoft.com. It really doesn't matter. You can pick one, go to Azure Active Directory, click on Users, and my user David James should be showing up in my list here. And there it is, as you can see. So that worked perfectly. Now, as far as creating a group, I want to warn you about this. When you go to create a group, one thing that's a little strange that will not let you create a group is a Microsoft 365 group. If I create a group, it does not give me a choice. Now I do want to clarify. You can create a Microsoft 365 group. I'm going to show you, but you won't use this noun to do it. The MSOL noun is not going to do it. Okay? So if I say "new MSOL group," for example, and I do the display name, and I'm just going to call it, let's just call it "Group Creation Test," that's kind of a crappy name, but this is just a demonstration. So if I use that as my display name, you can add a description. This is a test. When you create a group, it doesn't have a parameter that will let you change the group type from security to Microsoft 365. Okay? You can, for example, go through all of these parameters. It will not let you make it a Microsoft 365 Group. Now in order to do that, you're going to need to access the Exchange commands. The Exchange Online commands are going to let you create a Microsoft 365 group. And again, this is very important. If you're wanting to create a team from a group, you're going to need to make it a Microsoft 365 group. A security group is not going to do it.

Okay? So here's how you're going to do that, all right? You've got to connect to Microsoft 365. I'm sorry, Microsoft 365 Exchange Online Services, in order to do it. And we are not connected to that right now. So we need to install the Exchange Online Management Commands. Okay? Now I'm going to tell you, this is really nice. They've made this so much easier than it was, like, a year ago. Even a year ago, connecting to Exchange Online was a big hassle. It's a lot easier now. So to do it, you've got to install the Exchange command. So I'm going to type "install dash module name." And what you're going to do isyou're going to type Exchange Online Management. And then depending on when you redo this and all that, There is a certain version that you need to have at least a certain version of this.The reason I warned you about this is that maybe you've installed an older version of this on your computer. And if you did, you may have out-of-date commands that don't have the commands that can do what we're about to do. So I recommend that you put "requiredversion" and then say "1.0.1," okay? And that way, you're going to have at least that version, and that version is going to have all these Exchange commands in it. But you can also go out there and look to see what the latest version of the Exchange Online Management commands are. You can find that in the PowerShell Gallery. If you go out there and Google PowerShell Gallery,you can look up what the latest ones areand you can install the latest one. However, 1.0.1 is the bare minimum you should install. So if I hit Enter, it's going to install those commands. All right. Now in my case, I've got most of the commands already installed, but it is going to double-check, and eventually it's going to pop back up. All right, so I've already got the commands installed. The next thing you've got to do is connect to the Exchange Online Services. So you're going to type "ConnectExchangeOnline." Same thing. You're going to put your credentials in here. By the way, there is a way to store your credentials in a variable so that you don't have to keep putting this in.

There's a little command that puts in the wrong password. There's a little command called the Get Credential command. You can create a variable and point it to Get Credential, and it'll store it in memory. and that way you don't have to keep putting in your credentials. Okay, so it's loading the Exchange commands here. Now the command that's going to let us do what we want to do has a noun called the "Unified Group." So a Microsoft 365 group in PowerShell is called Unified Group. If I do a search, if I say, "Let me just clear the screen and get command STAR," I'm going to say "Unified." Unified Group star You can see the commands that support Unified Group. So there is a "Get" command there. I can type Get UnifiedGroup, and I will be able to see my groups that are available. There are my Microsoft 365 groups right there. Now if you want to create a Microsoft 365Group so you can associate it with the team, I'm going to type "Unified Group." Okay, let's start with the display name and then call it Consumers Group alias. This is the syntax. By the way, don't forget that you can always look up the syntax in the knowledge base. Okay? same thing I showed you a minute ago. So dash alias, and then I'll say the alias is going to be Consumer Group. Consumers Group. All right. And then we'll say email address because it is going to have an email address in the Microsoft 365 Group. All right. And I'll say it will be consumers' groups. Add examlaboopspractice.com. You kind of have to spell that, right? That does help. All right. and then access type. This is going to be public or private. I'm going to make it private. Oops, let's fix that. Here we go. And I think I typed it. All right, so let's click to create. All right, and it does take a moment to create a unified group. It's a little bit slower than creating a security group, but as you can see, it did create it, and now I can actually type Unified Group and I can see the group. Okay, so that's how you can create yourself a Microsoft 365 group. And instead of going to Azure this time, let's go to portal Microsoft.com and see if the group is visible on our Microsoft 365 services. Okay, so this is loading a little slowly. All right, so we're going to go over here to groups. Now drop this down and we'll see if it appears.

And there it is, as you can see, and it is an Office 365-based group. So our Microsoft 365 service got its own group called the Consumer Group Exam. Now it does not have a team associated with it. We know that because the Little Team symbol is not there. But we'll get into it later with how we would manage teams. Now speaking of which, I want to point out that I'm actually not connected to teams through PowerShell yet either. I've got to connect teams. You've got to have the team's commands in order to do that. You see the pattern here in how you're behaving to install these commands. Okay, there are thousands and thousands of PowerShell commands. Microsoft doesn't want to load them all up in memory, so they make us go get them and install them if we want to use them. So, to get teams, I'll use the following command: So I'm going to say "install module. All right? And then from there, after I got an error, there we go, installing the module. And then I'm going to say dashname. And the module we want is called Microsoft Teams hit Enter. And of course I've already got it installed, so I'm good. But if you're doing this, it will ask you to install it. And then, just like the previous methods of working with these modules, you have to make a connection. Okay? So I'm going to type "Connect Microsoft Teams" and hit Enter. It's going to pop the little box up again, and then I'm going to put those credentials in JC at examlabpractice.com. Okay, I'm going to put my password in now and log on, and I am now connected. So I can now type get command star, noun star, or team star. And you can see all the team commands that are available to us. For instance, if I want to see what teams I have, I can type get team, okay, which is what I'll be elaborating on, along with creation and all that. Right now, I'm not going to get into creating teams and all this. I just wanted to show you how to connect to the team's services online. So now you've seen how you can make connections with PowerShell all the way out in the clouds. And I'm going to be showing you a lot of commands as we move along, creating and managing things using PowerShell.

So when looking for preparing, you need Microsoft 365 Certified: Teams Administrator Associate certification practice test questions and answers, study guide and complete training course to study. Open in Avanset VCE Player & study in real exam environment. However, Microsoft 365 Certified: Teams Administrator Associate exam practice test questions in VCE format are updated and checked by experts so that you can download Microsoft 365 Certified: Teams Administrator Associate certification exam practice test questions and answers files in VCE format.