Shared mailboxes for example do have a corresponding user object in Azure AD, yet we can provision them directly via the Exchange tools, such as the New-Mailbox cmdlet. Well technically this is only true for user mailboxes. You remove the license, the mailbox is gone. You grant the user any of the Exchange Online plans, he gets a mailbox. Instead, you need to provision the user object in Azure AD first, and the process of enabling a mailbox for this user is governed by the licensing workflow. In Office 365 however, user objects are authored in Azure AD and there are no Exchange endpoints that allow you to provision a user. Alternatively, you can first create the user object in AD and “mailbox-enable” it later on. In the on-premises world, this is of course dependent on the underlying AD, but as long as you have the necessary permissions you can provision a new user, along with a mailbox, directly via the EAC or the EMS. One of the differences between on-premises Exchange and Exchange Online is the way user mailbox objects are provisioned, or de-provisioned.
0 kommentar(er)
