Saturday, February 4, 2023

Create a new Office 365 Tenant – Part 2

So you have a new tenant, albeit a bit empty. Let’s get into some of the configuration of it all. The first setup is to verify the domain that you want to use. We can’t be stuck with just lightbluefrog.onmicrosoft.com even though that is an important item. Let’s now configure the domain into the tenant. We are now going to add lightbluefrog.com into Office 365. Firstly then, on your navigation pane on the left click on Setup, then Domains. Your screen will look like this.

Click on the ‘Add domain’ button and lets get started.

As you can see I have put lightbluefrog.com in there as that is the domain for this tutorial. Click on Next and we can start the verification process. This is just to prove that you own the domain. There are various ways to verify the domain, either by logging in to your GoDaddy account (if it was purchased by them), or placing a TXT record in DNS, maybe a piece of code in an HTML page on your website. Either way you choose it will confirm that the domain is yours.

I opted for the GoDaddy option as my domain is registered there and it is quick and easy. Once the validation is complete then the following screen will show. Following this you need to setup up the DNS records. For the setup of a new domain in Office 365 where there is an on-premise server you DO NOT want Office 365 to mess with your DNS. Choose the items you want to add and do it yourself. You don’t want external mail flow going into Office 365. You don’t have any users there yet at least. So click on the ‘I’ll add the DNS records myself’ and you will be presented with what to do. You do need to select if you are using Exchange, Skype for Business and Mobile Device Management. I will tick all of those for now so you can see all the DNS entries. Even if you choose not to use them then you can still edit them later or just leave them in place.


Here is what the DNS records should end up like.

In my case, like I mentioned, I was letting them go in to GoDaddy and make the changes itself. Here is the final list of what it added.

The final screen will look like this and you are all done. The next part is to link the Azure AD to your local Active Directory.

Mark Rochester
Mark Rochesterhttps://thecloudgeezer.com
Mark currently works in the cloud space assisting large companies to migrate from either on premises to the cloud, or cloud to cloud. His experience with Enterprise migrations spans more than 25 years which basically makes him old. However, with all the oldness creeping up he still finds technology massively exciting. Please reach out for a chat anytime you would like. :-)

Related Articles

Migrate Microsoft Teams using MigrationWiz

As there is no native way to migrate the content from Tenant to Tenant for Microsoft Teams we need to use a paid toolset...

Migrate Microsoft 365 Tenant to Tenant with Free Native Tools

An interesting topic again, debating whether the free native tools that are available to migrate the Exchange Online workload in Microsoft 365 are good...

Create ‘Dummy Test’ Users in Local Active Directory

The need for this comes along when you are testing things like Azure AD Connect Sync, or an AD to AD migration. Maybe an...

Stay Connected

82FansLike
37,255FollowersFollow
685SubscribersSubscribe
- Advertisement -

Latest Articles