You can authorize users or groups to view run history of all automation workflows held in a certain container by applying the Automation Workflow - View Access Template to that container. This enables the users or groups to view run history of the automation workflow without giving them the right to modify or run the workflow.
To delegate the task of viewing run history of all automation workflows held in a certain container
- In the console tree, right-click the desired container under Configuration | Policies | Workflow, and then click Delegate Control.
- In the Active Roles Security dialog box, click Add to start the Delegation of Control Wizard.
- On the Users or Groups page in the wizard, click Add, and then use the Select Objects dialog box to select the desired users or groups.
- On the Access Templates page in the wizard, under Access Templates | Configuration, select the Automation Workflow - View check box.
- Follow the instructions in the wizard and accept the default settings.
- Click OK in the Active Roles Security dialog box.
It is also possible to authorize users or groups to view run history of a single automation workflow by applying the Access Template to the workflow definition object.
To delegate the task of viewing run history of a single automation workflow
- On the View menu, select Advanced Details Pane.
- In the console tree, under Configuration | Policies | Workflow, select the container that holds the desired workflow definition object.
- In the upper part of the details pane, select the workflow definition object.
- In the lower part of the details pane, on the Active Roles Security tab, right-click a blank area and click Add to start the Delegation of Control Wizard.
- On the Users or Groups page in the wizard, click Add, and then use the Select Objects dialog box to select the desired users or groups.
- On the Access Templates page in the wizard, under Access Templates | Configuration, select the Automation Workflow - View check box.
- Follow the instructions in the wizard and accept the default settings.
To create a remote mailbox for an existing user, you can convert the on-premises user to a hybrid Azure user with an Office 365 automation workflow and a hybrid migration script, based on the built-in Sample Azure Hybrid Migration script.
The Sample Azure Hybrid Migration script is available at the following location in the Active Roles Console:
Configuration > Script Modules > Builtin > Sample Azure Hybrid Migration
The remote mailbox workflow, on the other hand, is available at the following location in the Active Roles Console:
Configuration > Policies > Workflow > Builtin > Sample Azure Hybrid Migration
Prerequisites
To create remote mailboxes via hybrid migration with the Sample Azure Hybrid Migration script, your organization must meet the following requirements:
-
To enable remote mailboxes, the Exchange management tools of an on-premises Exchange installation must be available. For the list of Exchange Server versions supported by Active Roles, see System requirements in the Active Roles Release Notes.
-
The Active Roles service account must be a part of the Recipient Management management role group to run Exchange hybrid commands.
To configure and run the Sample Azure Hybrid Migration script
-
Depending on whether you want to enable or disable remote mailboxes, use one of the following functions:
-
EnableRemoteMailBox: Use this function to enable remote mailboxes for the users in the workflow scope. Select EnterExchangeCreds_params as the function to declare parameters in the script, then provide the Exchange user name and password to run the EnableRemoteMailBox function in workflow.
-
DisableRemoteMailBox: Use this function to disable remote mailboxes for the users in the workflow scope. Select EnterExchangeCreds_params as the function to declare parameters in the script, then provide the Exchange user name, password and Exchange recipient type details to run the DisableRemoteMailBox function in workflow.
-
Make sure to specify the Fully Qualified Domain Name (FQDN) of the Exchange Server in the script, and that you modify the required code blocks. For more information on declaring script parameters, see Script activity.
-
After the script is modified, enable or copy the default Sample Azure Hybrid Migration workflow and run it.
By default, a remote mailbox is created for users with a valid Exchange Online license and who have no on-premises Exchange mailbox. For more information on creating a remote mailbox for new users, see Creating a new hybrid Azure user with the Active Roles Web Interface.
NOTE: One Identity provides the Remote mailbox migration (RemoteMailbox.ps1) script as a sample script to illustrate the required steps of creating remote mailboxes.
Do not use the script in a production environment without the required modifications and enhancements. Using security credentials within a script in clear text is never secure. When testing the script, consider the appropriate authentication and use of credentials. After testing, do not leave any credentials in clear text in the script.
For more information, see Knowledge Base Article 310525.
After creating the Remote Mailbox, you can manage it through the console and the Web Interface. The supported operations are mentioned below:
- Exchange General
-
View or change the alias
-
View or change the option to use MAPI rich text format
-
Hide the user or contact from Exchange address lists
-
View or change custom attributes
- Exchange Advanced
-
View or change the simple display name
-
Downgrade high priority mail bound for X.400.
-
View or change the Internet Locator Service (ILS) settings
- Email Address
-
View, add, edit or remove e-mail addresses
-
View or change the default reply address for each address type
-
View or change the external e-mail address
-
Set the option to update e-mail addresses based on e-mail address policy
- Mail flow Settings
For more information on Exchange Online Properties, see View or modify the Exchange Online properties on the Active Roles Administration Guide.
To import Azure or M365 Windows PowerShell modules, and run their corresponding M365 services within existing Active Roles workflows, configure M365 automation workflows. These workflows support running scripts from the following Windows PowerShell modules:
Creating a new M365 automation workflow has the following steps:
-
In the Configuration > Script Modules node of the Active Roles Console (also known as the MMC Interface), create the new M365 script that you want to run with the new M365 automation workflow.
-
In the New Workflow wizard, configure the new M365 automation workflow.
-
With the O365 script execution configuration activity of the Workflow Designer, specify the Azure tenant to which the configured workflow will apply.
-
Import the new M365 script into the workflow created in the first step.
NOTE: By default, Active Roles does not select any Azure tenants automatically after you configured a new workflow with the New Workflow wizard. After the workflow is created, configure one in the Workflow Editor, otherwise the workflow will fail with the following error message:
Select a configured Azure tenant from the Select a Tenant to configure O365 Services drop-down list. Alternatively, under Parameter values, provide a valid Tenant ID, Tenant Name, Application (Client) ID and Application (Client) Certificate Thumbprint to override Azure tenant details from the workflow.
For more information on how to configure an M365 automation workflow, see Creating a Microsoft 365 automation workflow. For a list of sample M365 workflow scripts, see Sample Microsoft 365 workflow scripts.