サポートと今すぐチャット
サポートとのチャット

Active Roles 8.1.1 - Administration Guide

Introduction Getting started Rule-based administrative views Role-based administration
Access Templates as administrative roles Access Template management tasks Examples of use Deployment considerations Windows claims-based access rules
Rule-based autoprovisioning and deprovisioning
Provisioning Policy Objects Deprovisioning Policy Objects How Policy Objects work Policy Object management tasks Policy configuration tasks
Property Generation and Validation User Logon Name Generation Group Membership AutoProvisioning Exchange Mailbox AutoProvisioning AutoProvisioning in SaaS products OneDrive Provisioning Home Folder AutoProvisioning Script Execution Microsoft 365 and Azure Tenant Selection E-mail Alias Generation User Account Deprovisioning Office 365 Licenses Retention Group Membership Removal Exchange Mailbox Deprovisioning Home Folder Deprovisioning User Account Relocation User Account Permanent Deletion Group Object Deprovisioning Group Object Relocation Group Object Permanent Deletion Notification Distribution Report Distribution
Deployment considerations Checking for policy compliance Deprovisioning users or groups Restoring deprovisioned users or groups Container Deletion Prevention policy Picture management rules Policy extensions
Using rule-based and role-based tools for granular administration Workflows
Key workflow features and definitions About workflow processes Workflow processing overview Workflow activities overview Configuring a workflow
Creating a workflow definition for a workflow Configuring workflow start conditions Configuring workflow parameters Adding activities to a workflow Configure an Approval activity Configuring a Notification activity Configuring a Script activity Configuring an If-Else activity Configuring a Stop/Break activity Configuring an Add Report Section activity Configuring a Search activity Configuring CRUD activities Configuring a Save Object Properties activity Configuring a Modify Requested Changes activity Enabling or disabling an activity Enabling or disabling a workflow Using the initialization script
Approval workflow Email-based approval Automation workflow Activity extensions
Temporal Group Memberships Group Family Dynamic groups Active Roles Reporting Management History Entitlement profile Recycle Bin AD LDS data management One Identity Starling Join and configuration through Active Roles Managing One Identity Starling Connect Configuring linked mailboxes with Exchange Resource Forest Management Configuring remote mailboxes for on-premises users Azure AD, Microsoft 365, and Exchange Online Management
Configuring Active Roles to manage Hybrid AD objects Managing Hybrid AD users
Creating a new Azure AD user with the Web Interface Viewing or updating the Azure AD user properties with the Web Interface Viewing or modifying the manager of a hybrid Azure user Disabling an Azure AD user Enabling an Azure AD user Deprovisioning of an Azure AD user Undo deprovisioning of an Azure AD user Adding an Azure AD user to a group Removing an Azure AD user from a group View the change history and user activity for an Azure AD user Deleting an Azure AD user with the Web Interface Creating a new hybrid Azure user with the Active Roles Web Interface Converting an on-premises user with an Exchange mailbox to a hybrid Azure user Licensing a hybrid Azure user for an Exchange Online mailbox Viewing or modifying the Exchange Online properties of a hybrid Azure user Creating a new Azure AD user with Management Shell Updating the Azure AD user properties with the Management Shell Viewing the Azure AD user properties with the Management Shell Delete an Azure AD user with the Management Shell Assigning Microsoft 365 licenses to new hybrid users Assigning Microsoft 365 licenses to existing hybrid users Modifying or removing Microsoft 365 licenses assigned to hybrid users Updating Microsoft 365 licenses display names
Unified provisioning policy for Azure M365 Tenant Selection, Microsoft 365 License Selection, Microsoft 365 Roles Selection, and OneDrive provisioning Microsoft 365 roles management for hybrid environment users Managing Microsoft 365 contacts Managing Hybrid AD groups Managing Microsoft 365 Groups Managing cloud-only distribution groups Managing cloud-only dynamic distribution groups Managing Azure security groups Managing cloud-only Azure users Managing cloud-only Azure guest users Managing cloud-only Azure contacts Changes to Active Roles policies for cloud-only Azure objects Managing room mailboxes Managing cloud-only shared mailboxes
Modern Authentication Managing the configuration of Active Roles
Connecting to the Administration Service Managed domains Using unmanaged domains Evaluating product usage Creating and using virtual attributes Examining client sessions Monitoring performance Customizing the Console Using Configuration Center Changing the Active Roles Admin account Enabling or disabling diagnostic logs Active Roles Log Viewer
SQL Server replication Using regular expressions Administrative Template Communication ports Active Roles and supported Azure environments Integrating Active Roles with other products and services Active Roles Language Pack Active Roles Diagnostic Tools Active Roles Add-on Manager

Email-based approval

In addition to the Web Interface pages for performing approval tasks, Active Roles provides the facility to approve or reject a pending request by replying to a notification message that informs of the request. An approval workflow can be configured to behave as follows:

  • Upon the receipt of a change request that requires approval, Active Roles sends a notification message to the designated approvers, with the message body containing the option to approve or reject the request.

  • The approver replies to the notification message, choosing the desired option—approve or reject. In the reply message the approver is expected to provide a comment explaining the reason for that choice.

  • Active Roles receives the reply massage from the approver, checks to see if the approver elected to approve or reject the request, and then allows or denies the requested changes accordingly.

This way, the capabilities to work with approval requests are integrated into the e-mail client. The approvers do not need a web browser to view, and respond to, their approval requests. This, for instance, enables Microsoft Office Outlook users to manage approvals even when they are offline. One more opportunity is to manage approvals using an e-mail client on a mobile device.

IMPORTANT: To manage approval requests by replying to notification emails, you must be logged on to the approver’s mailbox as the owner of the mailbox or as an identity that has full access to the mailbox (including the Send As permission). The Send on Behalf permission will not suffice. Active Roles detects the situation where the reply is sent on behalf of the mailbox owner, and disregards the reply message in that case.

Integration with Microsoft Outlook

For organizations that have deployed Microsoft Exchange Server 2013 or later, and use Microsoft Office Outlook 2010 or later as their standard email client, Active Roles provides an approvals management facility integrated in Outlook. This allows Microsoft Office end-users to manage approvals in Active Roles through the email application they use on a day-to-day basis.

The Add-in for Outlook component that is included with Active Roles offers the basic functionality for processing and submitting approvals. Active Roles Add-in for Outlook allows Microsoft Outlook users to approve or reject requests that are sent to them for approval. Requests are delivered through notification email messages, and can be approved or rejected directly from the notification email message, without having to use the Active Roles Web Interface. In every email message from Active Roles that notifies of an approval request, Active Roles Add-in for Outlook adds the Approve and Reject buttons along with Approve and Reject menu commands allowing the approver to respond by selecting the appropriate button or command.

Software and configuration requirements for Microsoft Outlook integration

Integration with Microsoft Office Outlook requires the following software and configuration prerequisites:

  • Microsoft Exchange Server 2013 or later: Integration with Outlook requires at least one server running Exchange 2013 or later that holds the Client Access server role and Mailbox server role, to be deployed in your Exchange organization.

  • Microsoft Office Outlook 2010 or later: The approvers use Outlook 2010 or later as their email client application.

  • Active Roles Add-in for Outlook (32-bit): The Add-in for Outlook component of Active Roles is installed on the computer running Microsoft Office Outlook. The software requirements specific to Active Roles Add-in for Outlook are listed in the Active Roles Quick Start Guide.

    NOTE: The Active Roles Add-in for Outlook does not support the 64-bit version of Microsoft Office Outlook.

  • (Optional) Approver mailboxes: The mailboxes by which requests can be approved or rejected must be located on a mailbox server running Exchange 2013 or later.

    TIP: Although setting up approver mailboxes are not mandatory, One Identity highly recommends configuring them.

  • Active Roles mailbox: A mailbox reserved for the exclusive use of Active Roles. This mailbox must be on a mailbox server running Exchange 2013 or later.

  • Exchange Web Services: The approval workflow has the approval rule notification settings configured so that Active Roles uses Exchange Web Services to communicate with Exchange. These settings include the address (URL) of the Exchange Web Services endpoint on an Exchange server that holds the Client Access server role, along with the credentials that identify the Active Roles mailbox.

Integration with non-Outlook email clients

For organizations that have deployed Microsoft Exchange Server 2013 or later, but use an email client application other than Outlook 2010 or later, Active Roles offers the ability to approve or reject change requests by simply replying to notification messages that inform approvers of approval tasks. In this case, the notification message contains selectable options that, when clicked or tapped, cause the e-mail application to create a new message in reply to the notification message. The reply message contains indication of the approval decision (approve or reject) and prompts the approver to supply a comment on the approval decision (approval or rejection reason). Then, the approver sends the reply message, thereby completing the approval task.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択