Forum Discussion

Jerry Meyer's avatar
Jerry Meyer
Iron Contributor
Mar 20, 2017
Solved

The question nobody dares to ask! How do you create a new user in a hybrid environment.

Hi, the last couple fo days the question how to create a new user in a hybrid exchange environment is floating around in my head.   Most of the time when i create a user i create a onpremise accoun...
exchange online
Exchange Server
hybrid
office 365
  • Paul Cunningham's avatar
    Paul Cunningham
    Mar 20, 2017

    The best practice is whatever works for your user management workflows. You can create it either way. In a hybrid you can move mailboxes back and forth whether they were created on-prem or in the cloud.

     

    One caveat with New-RemoteMailbox is that it can't do Shared mailboxes. Those you need to create on-prem and then move, or, create in EXO as a user mailbox and then convert to Shared. Either way, same result.

Joe Stocker's avatar
Joe Stocker
Bronze Contributor
Nov 05, 2019
it's probably best to start a new thread/question, but to answer your question, no that is not the expected experience. If your on-premises users are not seeing the cloud users in the GAL then that means someone missed a step when provisioning those cloud users, because in a Hybrid configuration, those cloud users should be represented as RemoteMailbox recipient types on-premises. Fortunately, there is a fairly quick fix to resolve this which includes using the enable-remotemailbox command, which tells the on-premises AD account that it has a cloud mailbox in O365. That step will cause the remote mailboxes to appear in the on-premises Exchange Online address book. If you need further help email me us here: support AT patriotconsultingtech.com
NodorinaMing's avatar
NodorinaMing
Copper Contributor
Nov 05, 2019

Joe Stocker 

Hi,

- These new mailboxes, they do not has an on prem EX 2010 mailbox.

- and in AD - there the Email field is empty too.

 

- their SMTP is now ....@onmicrosoft.com instead of the 'company" SMTP. 

 

May i know if enable-remotemailbox command can fix all these? 

 

THANK YOU

  • donreak's avatar
    donreak
    Copper Contributor
    Nov 13, 2020

    NodorinaMing 

    That usually only happens from what I've seen is if it did not provision properly.  Maybe you could use PowerShell and the MSOL service

     

    Set-MsolUserPrincipalName -UserPrincipalName “First.Last@companyonline.mail.onmicrosoft.com” –NewUserPrincipalName “First.Last@company.com”

     

     

  • Joe Stocker's avatar
    Joe Stocker
    Bronze Contributor
    Nov 05, 2019
    that is correct, enable-remotemailbox is designed to solve your problem. No on-premises mailbox required. It will glue the on-premises AD account to a remote mailbox that already exists in Office 365, so that the mailbox in the cloud will appear in the on-premises GAL.
    the syntax should be enable-remotemailbox -identity "Josh Smith" -remoteroutingaddress jsmith@Contoso.Mail.Onmicrosoft.com (of course replace Contoso with your tenant name)
    It will also fix mail routing problems that you are having but don't know about yet 😃 (unless you changed your accepted domain to internal relay, which would be a work-around). This article confirms what you are experiencing and shows the fix I am suggesting to you: https://misstech.co.uk/2015/01/30/remote-mailboxes-in-exchange-hybrid-configuration/