This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Is there a defined solution to manage shared Exchange Online mailboxes in One Identity Manager ?

Hello,

I am trying to define a process to manage shared mailboxes in Azure AD/Exchange Online, my process simply creates a O3EMailbox object in One Identity.

It seems that it is not that simple because each shared mailbox is linked to a corresponding AAD user account  in O365.

Is there a defined process or a common customization used to manage Shared Mailboxes in Exchange Online ?

Thank you in advance for your replies !

Best Regards,

Parents
  • Had this question a while ago with an onprem 2010 Exchange system as well. Yes, the problem in creating a shared mailbox / functional mailbox is that you first need an AD user to tie the two together. I ended up in creating all steps manually first. So creating the AD user, then creating the mailbox, associate them, mark the mailbox accordingly etc, setting the smtp address and add owners/users to it. To do it this way gives you an overview what to do in a custom process/script which automates all manual actions. The solution we build (in 6.1.3) never went to production however as the creation of those mailboxes was placed out of the IAM scope and into the (powershell scripted) hands of the Exchange admins as they wanted to have tight control over shared mailboxes.

Reply
  • Had this question a while ago with an onprem 2010 Exchange system as well. Yes, the problem in creating a shared mailbox / functional mailbox is that you first need an AD user to tie the two together. I ended up in creating all steps manually first. So creating the AD user, then creating the mailbox, associate them, mark the mailbox accordingly etc, setting the smtp address and add owners/users to it. To do it this way gives you an overview what to do in a custom process/script which automates all manual actions. The solution we build (in 6.1.3) never went to production however as the creation of those mailboxes was placed out of the IAM scope and into the (powershell scripted) hands of the Exchange admins as they wanted to have tight control over shared mailboxes.

Children
No Data