and more in a single search tool across platforms. Read the announcement here. |
09/12/2022 01:27 PM
Hi All,
What is the best way to to create mailboxes in Office 365 from Saviynt? Which connector supports this feature?
Thanks,
Shibin
Solved! Go to Solution.
09/12/2022 01:40 PM
09/13/2022 05:25 AM
Thanks @rushikeshvartak . So only option is to use Win-PS connector to create mailboxes in Exchange Server right? Wanted to see if there are any options to create mailboxes in Office 365 directly.
09/13/2022 07:40 AM
Yes
09/13/2022 05:36 AM
If you only want to create a basic mailbox with no special settings (enabling archiving, disabling OWA, additional proxy addresses etc.) you may not need to do anything except assign the Exchange license.
These days assigning the license automatically creates the mailbox in most situations, as long as the correct attributes are set in Azure AD - either by Saviynt or synced from on-prem AD by Azure AD Connect).
09/13/2022 06:58 AM
Thanks @MarkHancock
If you only want to create a basic mailbox with no special settings (enabling archiving, disabling OWA, additional proxy addresses etc.) you may not need to do anything except assign the Exchange license. -- So you are talking about assigning the license directly in Azure AD using REST connector right? just confirming.
These days assigning the license automatically creates the mailbox in most situations, as long as the correct attributes are set in Azure AD - either by Saviynt or synced from on-prem AD by Azure AD Connect) -- I assume you are talking about UPN, Immutable ID etc. correct?
If the customer has a hybrid environment, that the remote mailboxes are created in Exchange Server and actual mailboxes are created in office 365 using AADConnect then only option is to use Win-PS connector to invoke Exchange PowerShell scripts right?
09/13/2022 08:05 AM
If all the mailboxes are in Office 365, and e-mail to users isn't going to be routed through any remaining on-prem Exchange servers then you don't need to run any PowerShell commands.
(Creating a remote mailbox on the on-prem AD/Exchange just sets up routing to Exchange Online.)