Multiple searches on the internet and I couldnt find a single site that listed all the information I needed. I did find most of it from 2 sites which I will include the links into the bottom of this post.

I decided to put together a step by step guide for Exchange 2013 multi-tenancy and needing to have distinct, separate organizations on a single server or cluster.

Note Microsoft has no “multi tenant mode” for Exchange 2013 due to limitations and major architectural changes.

Here is how I set up multi-tenancy in Exchange 2013. This is all done via PowerShell Exchange Cmdlets. Powerful and verbose!

We need a container to hold all of our data, created at the root of Active Directory (A/D going forward).

On your A/D server, via PowerShell:

First, create an Organization Unit (OU) to hold the tenant data, I am using the word ‘Tenant’ with a 5 digit sequence number in my examples. In the example you will need to replace ‘hosted’ ‘exchange’ with your local domain.

On your A/D server, via PowerShell:

Now we need to User Principal Name (UPN) suffixes for later.

On your A/D server, via PowerShell:

If you are working remote against the Exchange server then you need to create a connection to EMS as the rest of the configuration is now with Exchange directly instead of A/D.

NOTE: This is not required if you are on the Exchange server itself. You later destroy this session at the end (documented below) but since you are on the A/D server for the above cmdlets then it is just easier to keep going with a single PowerShell connection.

Now, add a new domain for the new tenant.

Create the Global Address List (GAL) for Tenant00001

If needed then create All Rooms Address List

And time to create All Users Address List

The All Contacts Address List

The All Groups Address List

Now for something quite useful: Offline Address Book

You’ll also need to create an Email Address Policy. This example also includes first.last@domain email aliasing, or you can set the primary email address to first.last@domain by using the -EnabledPrimarySMTPAddressTemplate “” attribute and data.

Now we need to create the Address Book Policy

Optional: create a resource for rooms by creating a Room Mailbox. It is vital that we also set a Custom Attribute for the tenant

Almost done, we are getting to the good parts now.

Let’s create some users with their associated mailboxes.

First, we need to get a password for the user, this will prompt you for such. For the ‘username’ field you can type anything you want as it is the password attribute we want for the mailbox being created. As with a room mailbox we need to also set a custom attribute to the tenant.

If you connected to the Exchange server from remote you should close your Session

And you now have created your first tenant organization.

You can now continue to create users and resource mailboxes via the new Exchange Action Center (EAC).


One item that will probably crop up for you is the issues of quotas. By default, the quotas are 2 GiB for a mailbox; here is how you can add/update the quota on a mailbox.

Of course, adjust as needed.

Leave a Reply

Your email address will not be published. Required fields are marked *