Introduction
Setup Microsoft 365 Tenancy and Subscription
Manage Domains
Manage Microsoft 365 Subscription and Tenant Health
Conclusion
The course is part of these learning paths
Microsoft 365 represents a combination of Office 365, Windows 10 and Enterprise Mobility offerings – providing the most complete set of SaaS technologies that Microsoft has to offer. With Microsoft 365, organizations can deploy a complete solution encompassing both devices and applications, along with applying security and compliance policies to protect the entire suite.
This course will help you as you plan your deployment of Microsoft 365, along with configuring and managing your tenant once it’s deployed. It also covers setting up and managing a Microsoft 365 subscription for an enterprise – including managing identities, security, compliance and the supporting technologies in the Microsoft 365 stack.
This course focuses mainly on setting up and managing a Microsoft 365 tenant – including the process for setting up a trial tenant, adding your own domains, and converting your tenant beyond the trial to a fully functional production environment. Now, these steps can seem to be very easy – just click a few options, answer a few questions, and you’re done. In fact, it is that easy! However, if you’re not aware of the big picture and asking some important questions along the way, you can end up painting yourself into a corner and causing problems down the road. At best, you might need to redo some things, at worst, you leave yourself with problems on your hands that might be difficult to sort out later.
After you’re set up, we’ll move on to talking about some of the things you need to consider in your day to day monitoring and management of your Microsoft 365 Tenant and the services that make it up. We’re also going to run through a few demos – showing you some of the practical steps involved, along with some tips and tricks we’ve picked up along the way.
Learning Objectives
- Set up a new Microsoft 365 tenant and subscription
- Add domains to the tenant and configure them for the various service offerings
- Perform the day to day management of your users, including managing user accounts and license assignment
- Know how to monitor the various services in your M365 tenant and have a plan in place to respond to service alerts and manage service requests
Intended Audience
This course is intended for people who:
- Want to become a Microsoft 365 administrator
- Are preparing to take the Microsoft’s MS-100 exam
Prerequisites
To get the most from this course, you should have a general understanding of networking & server administration as well as IT fundamentals such as DNS, Active Directory and PowerShell.
Let's go ahead and add these now, and we will check them out.
Since we don't have any special exchange server configuration, we're not in hybrid, we're just ready to go directly to Office 365. We're gonna grab our MX record here, copy it to a clipboard, head over to our DNS provider, click add, choose MX record, host is the at sign, points two, paste it in, priority is zero, and then save. Now we can come back here, and we can go verify, and our first record is complete, which is our MX record.
Now we're just gonna go through and do the rest of them, as well, let's do our SPF record next. We'll complete all of our exchange ones first, so it's gonna be at, this is our SPF, go back here, and just make sure that we don't an existing SPF record. We're gonna add, if you don't have a record type called "SPF," choose text, host is at, text value, paste, and save. And I'm just gonna go ahead and delete this.
Here we go, I like to keep things nice and clean. And we're gonna add our CNAME record for auto discovers, so let's pick that one. Come back here we're gonna add a CNAME record, for auto discover points to "autodiscover.outlook.com" Just matching the settings here, and save. Okay? Obviously, you don't have to come back and verify each record, I just like to do it, since we're going through each one, one at a time. So we can see that auto discover hasn't shown up yet. Our SPF record is looking good it's correct, and let's just go ahead and add the rest of them. We'll do "sip." Goes to "sipdir's." We're gonna go add, CNAME for sip, points to "sipdir," save. We'll take "lyncdiscover." Add, CNAME, "lyncdiscover," points to "webdir.online.lync.com." We'll do our enterprise registration, as well get our MDM records in place. CNAME, "enterpriseregistration," points to "enterpriseregistration.windows.net." And, enterprise enrollment is our last CNAME. "enterpriseenrollment," and save. And let's go back and check these records. Okay?
You can see that all the rest of them, but the last are good, which means that it's just probably taking a few minutes to go ahead and reflect the changes. Let's do our SRV records while we're waiting. We're gonna add an SRV record. Okay? And this is where everything is broken up like I mentioned, so the service is going to be "_sip." Protocol is "_tls." The name is "@." Target is "sipdir.online.lync.com." Priority is one hundred, weight is one, port is four four three. Do one more of these. SRV record, service is "_sipfederationtls," "_tcp." Name again is "@," target is, should've grabbed that one, "sipfed.online.lync.com." Priority is one hundred, weight is one, and port is five zero six one, and save, and let's go ahead and verify.
Okay? Once again we're just waiting for our last one to identify, while we do, let's go ahead and use "nslookup," and see what that looks like, so you can also check from the command line. So what we're gonna do is we're gonna go into normal command line on our computers, and say "nslookup-q." So query equals SRV, and then we're gonna do "_sip._tls.m365jedi.com," and hit enter. Okay? And we can see that it goes to "sip._tls.m365jedi.com," points to "sipdir.online.lync.com." Let's do the same thing, and we're gonna do this time "sipfederationtls_tcp" that's our second one that hasn't verified yet, and we can see that it is pointed correctly to "sipfed.online.lync.com." Really easy way for you to use "nslookup" to just verify the records that you're configuring in your domain services. Let's go back and finish the verification of the portal. Awesome! Setup complete, we're all good. If we go and check DNS now, we should see that everything is showing up correctly. All DNS records are correct, no errors are found. You can see there's our records for exchange online, MX, SPF, and auto discover. Skype for business has both the CNAME and the SRV records configured, and MDM is configured and ready to go.
Jeremy Dahl is a Senior Technology Consultant who has spent the last 8 years focusing on Microsoft 365 technologies and has been an Office 365 MVP for the last 6 years. Jeremy is a self-proclaimed cloud addict who architects technology solutions that combine cloud technologies with on-premises solutions, allowing organizations to make the most of their existing infrastructure while still taking full advantage of the agility and scalability of what the cloud has to offer.
Jeremy can be found blogging about Microsoft 365 technologies on his website, masterandcmdr.com, and evangelizing the Microsoft cloud on Twitter.