Mailbox is not visible in Exchange Online

Question

After creating a user, I want to create a mailbox that is visible both on-premises and in Exchange Online (remote mailbox). The presence in on-premises Exchange is required for a specific application being developed. I read that Adaxes handles this automatically. However, after the user is created, the mailbox appears in Exchange on-premises but cannot be found in Exchange Online. When I check the user properties in Office 365, under the mail section, I see the message: ‘This user’s on-premises mailbox hasn’t been migrated to Exchange Online. The Exchange Online mailbox will be available after migration is completed.

The groups the user is being added to are license groups.

Answer 1

Hello,

The behavior you are facing is expected as the Create Exchange mailbox action is not the one to be used. With your current workflow, you will end up with users having two separate mailboxes – one in Exchange Online and the other in Exchange on-premises. To achieve the desired, you need to enable a remote mailbox in the business rule and then wait for the synchronization to complete (this will create a mailbox in Exchange Online based on group membership). To enable a remote mailbox, replace the Create Exchange mailbox action in your business rule with the Regular remote mailbox script from the following article: https://www.adaxes.com/script-repository/create-remote-mailbox-s256.htm.

Comments

Hi,

Thanks for your reply!

I added a business rule but I am now getting the following error when creating a user: Unable to connect to Exchange server ***. The WS-Management service cannot process the request because the XML is invalid. I checked and the WS-Management service is running fine. I can ping the Exchange machine and I am able to establish a remote PowerShell session from the Adaxes machine to the Exchange machine.

---

Hello,

Unfortunately, we cannot be helpful about the error you are facing as it is just returned by your Exchange server. It is not related to Adaxes itself. However, the approach from the following Q&A post might be helpful: https://www.adaxes.com/questions/1778/ws-management-service-error-connecting-to-exchange. Pay attention, that if you are using the script we referenced from our repository, the connection is established with the credentials of the domain service account which can be different from the Adaxes service account. For details on how to check the service account for a managed domain, see https://www.adaxes.com/help/ChangeManagedDomainServiceAccount.

---

Thanks for your reply,

Windows Authentication was disabled in the Powershell web application on the Exchange server. It works now!