Back

Creating an Office 365 Mailbox in a Hybrid Configuration

When working with customers in Exchange hybrid configurations they often have questions about creating Office 365 mailboxesin Exchange Online Your...

4 min read
Published on Apr 4, 2017
Creating an Office 365 Mailbox in a Hybrid Configuration

When working with customers in Exchange hybrid configurations, they often have questions about creating Office 365 mailboxes in Exchange Online. Your organization might have existing processes for adding new users that will likely need to adapt to Office 365 after the migration.

In this guide, we’ll discuss the different methods of creating Office 365 mailboxes in an Exchange hybrid configuration.

Options to Create Office 365 Mailboxes

There are two ways to properly create an Office 365 mailbox in an Exchange hybrid configuration. One is via a more user-friendly GUI and the other is through Exchange PowerShell (for those of you who love automation).

Here’s how to create Office 365 mailboxes using both methods:

Option 1: Add New Users in the Exchange Admin Center (Exchange 2013 and 2016)

This is the simplest way to create an Office 365 mailbox. The process of creating an AD user and setting up the mailbox can be completed in one place and in one step.

The main disadvantage of the Exchange Admin Center is that it only lets you create a new Active Directory account for the user. To create a mailbox for an existing AD user, you’ll need to use PowerShell. Alternatively, you could give that user an on-premises mailbox and then migrate the mailbox to Office 365.

Here’s how to get started using the Exchange Admin Center:

  1. Log into the Exchange Admin Center here: https://mail.contoso.com/ecp.
  2. In the Exchange Admin Center of your on-premises hybrid server, jump over to Recipients > Mailboxes and hit the plus sign right above the “Display Name” column. You’ll notice one of the options is a new “Office 365 mailbox.” ![Office 365 mailbox hybrid] (/wp-content/uploads/2016/11/hybrid-office365-300x188.png)
  3. Complete the information in the Dialog Box and click Save. Once saved, you can edit the user’s mailbox properties to add information such as title, manager, address and phone number.

If you’re creating an Office 365 mailbox this way, there’s no need to set up an AD account for the user beforehand. As part of this process, Exchange automatically creates the AD object for the user in the OU you specify. Simply fill out the details and click save.

creating an office 365 mailbox

4. Sync the directory using AD Connect.  

On the next synchronization of AD Connect (either automatic or forced), your user will show up in Office 365 and an Exchange Online mailbox provisioned shortly after. Once the user is synced, you’re free to assign the appropriate license to the account.

To force a manual directory sync, log in to the Azure AD Connect server, open an Administrative PowerShell window and execute the following command:

  • Start-ADSyncSyncCycle -PolicyType Delta

5. License the User.

  1. Browse to https://portal.office.com
  2. Click the tiles icon and select the Admin tile
  3. Navigate to Users and select Active users licensing office 365 user accounts
  4. Select the user in question, locate the Product Licenses field and click Edit
  5. Choose a location then click the slider to activate an available license product licenses office 365 business essentials
  6. At the bottom of the Product licenses pane, click Save

Related Content: What to Consider in an Office 365 Hybrid Exchange Deployment

Option 2: Use Exchange PowerShell (Exchange 2010, 2013, and 2016)

You would use the Exchange PowerShell method for one of two reasons: to automate account provisioning or to grant an Office 365 mailbox to an existing AD user. You can also use this method to add Exchange Online mailboxes to the view in the on-premises Exchange Admin Center.

To create an Office 365 mailbox for an existing user, the command we’ll be using is [enable-remotemailbox](https://technet.microsoft.com/en-us/library/ff607313(v=exchg.160).aspx).

A general example would be: [code language=“PowerShell”] enable-remotemailbox -Identity <UserIdParameter> -remoteroutingaddress <ProxyAddress> [/code] proxy address More specifically, for the demo user from the EAC instructions, we would use enable-remotemailbox -identity “Demo User”-remoteroutingaddress [email protected].

The proxy address will always be @tenant.mail.onmicrosoft.com

Why Use These Methods to Create an Office 365 Mailbox?

It’s possible to simply create the Office 365 account in Active Directory, wait for AD Connect to sync the user to Office 365 and license the account. But creating new mailboxes this way never fills in the correct Exchange attributes on the user’s AD account, which causes them to not display in the local EAC.

This could also cause the inventory of your on-premises AD Connect domain and Azure AD domain to show incorrect data and conflicting information.

mailbox properties

We hope you found this guide helpful for creating new mailboxes in your Office 365 hybrid configuration.

Have more questions or need help managing your hybrid Office 365 environment? Agile IT is a proven expert in Office 365 cloud migration. We offer affordable migration plans that get you to the cloud seamlessly, on time and on budget.

Request a Quote

This post has matured and its content may no longer be relevant beyond historical reference. To see the most current information on a given topic, click on the associated category or tag.

Related Posts

Who Needs to Comply with CMMC Regulations?

Who Needs to Follow DoD Cybersecurity Requirements for CMMC Compliance

CMMC regulations apply to defense contractors, subcontractors, and suppliers handling DoD information. Find out who must comply and what certification level is required.

Jun 17, 2025
6 min read
What’s the Real Cost of CMMC Compliance?

The Real Cost of CMMC: Catching Up on What You Were Already Supposed to Be Doing

CMMC isn’t introducing new rules, it’s enforcing what should already be in place. Learn what’s really driving the cost of CMMC compliance.

Jun 16, 2025
4 min read
How to Meet ITAR Compliance Requirements in Office 365

How to Meet ITAR Compliance Requirements in Office 365

Need to meet ITAR compliance in the Microsoft cloud? Learn why GCC High is required for Office 365, what the regulations demand, and how to secure export-controlled data.

Jun 12, 2025
6 min read
Are You Ready? Understanding CMMC Controls Prohibited from POA&Ms

Are You Ready? Understanding CMMC Controls Prohibited from POA&Ms

CMMC Level 2 requires full implementation of specific controls. Learn which ones cannot be deferred in a POA&M and how to prepare for assessment success.

Jun 11, 2025
7 min read
How to Use the Microsoft Product Placemat for CMMC 2.0 Compliance

How to Use the Microsoft Product Placemat for CMMC 2.0 Compliance

Learn how to use Microsoft’s product placemat to map tools like Entra ID, Defender, and Purview to CMMC 2.0 requirements and accelerate your compliance journey.

Jun 11, 2025
8 min read
CMMC and the False Claims Act: Understanding Compliance Risk

CMMC and the False Claims Act: Why Not Getting Compliant Hurts

Learn how failure to meet CMMC 2.0 requirements can lead to False Claims Act liability for DoD contractors. Discover compliance risks and how to protect your business.

Jun 10, 2025
5 min read

Ready to Secure and Defend Your Data
So Your Business Can Thrive?

Fill out the form to see how we can protect your data and help your business grow.

Loading...
Secure. Defend. Thrive.

Let's start a conversation

Discover more about Agile IT's range of services by reaching out.

Don't want to wait for us to get back to you?

Schedule a Free Consultation

Location

Agile IT Headquarters
4660 La Jolla Village Drive #100
San Diego, CA 92122

Secure. Defend. Thrive.

Don't want to wait for us to get back to you?

Discover more about Agile IT's range of services by reaching out

Schedule a Free Consultation