Active Roles currently does not include the ability to create new remote mailboxes.
Active Roles 7.0.4 introduced new functionality for managing existing remote mailboxes. This functionality is also included in later versions and can be enabled by using the EnableRemoteMail registry key.
Enhancement ID 675080 includes the ability to manage existing remote mailboxes only. For more information on this configuration, please consult the release notes of the relevant Active Roles version for the above Enhancement ID.
Active Roles 7.4 includes functionality out-of-the-box to automatically create remote mailboxes when a user account is licensed for Exchange Online.
Earlier versions of Active Roles can implement the Workflow noted below to integrate this functionality into the product.
It is possible to create a custom Change Workflow which allows for the creation of Remote Mailboxes. This Change Workflow can be implemented without the use of a Script Module.
The workflow template would need to be adjusted to a different Virtual Attribute if changed. See attached template to download.
1) In the Active Roles Console, create a new Virtual Attribute called edsvaRemoteMailboxCreation with a Boolean syntax which is linked to User objects and which is not stored in the Active Roles configuration database. Reconnect to the Active Roles Console in order to be able to see the new Virtual Attribute. Link on How to: Create virtual attributes (149978).
2) Create a new Change Workflow which is triggered by a modification to this new Virtual Attribute. Specify a filter so that the Changed Value of the Workflow Target Object's Virtual Attribute equals TRUE.
3) The Workflow should contain an Update Activity. The Update Activity targets the Workflow Target and sets the following attribute values:
As mentioned above the targetAddress, mailNickname, and mail attributes in step 3 are unique to each environment. The template provided has these values blank and will need to be configured to each specific environment that uses the template.
4) The Workflow is now complete and can be activating by writing a TRUE value to the new custom Virtual Attribute which was created in Step 1 above.