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

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

Using unmanaged domains

After you’ve registered an Active Directory domain with Active Roles, you have the option to use the domain as an unmanaged domain. An unmanaged domain is a domain that is registered with Active Roles for read-only access. The use of the unmanaged domain option allows you to reduce licensing costs since the user count that corresponds to the unmanaged domains is not added to product usage statistics. For more information, see Evaluating product usage.

Unmanaged domains are instrumental in the following scenarios:

  • Group membership management: When used to add members to a group, by selecting the new members from a list of objects, Active Roles requires the domain that holds the objects to be registered. If you only use Active Roles for selecting member objects when managing group membership, you can configure the domain that holds the member objects as an unmanaged domain.

  • Exchange resource forest: When used to create Exchange mailboxes in a forest that is different from the forest that holds the accounts of the mailbox users, Active Roles requires the domain of the mailbox users (account domain) to be registered. If you do not use Active Roles for user management in the account domain, you can make that domain an unmanaged domain.

As applied to a registered unmanaged domain, the features and functions of Active Roles are limited to those that do not require write access to the objects held in that domain (including write access to the object data that is stored by Active Roles as virtual attributes). Thus, you can use Active Roles to:

  • Search for, list and select objects from unmanaged domains.

  • Populate groups in regular managed domains with objects from unmanaged domains.

  • Retrieve and view properties of objects held in unmanaged domains.

  • Assign users or groups from unmanaged domains to the role of manager, primary owner, or secondary owner for objects held in regular managed domains.

  • Delegate management tasks and approval tasks to users or groups held in unmanaged domains.

  • Run Active Roles policies against objects held in unmanaged domains, provided that the policies require only read access to those objects.

  • Provision users from unmanaged domains with linked Exchange mailboxes held in a separate managed forest.

  • Populate Managed Units with objects from unmanaged domains.

Since Active Roles has read-only access to unmanaged domains, it cannot:

  • Create, move, or delete objects in unmanaged domains.

  • Change any properties of objects held in unmanaged domains.

  • Run any group membership related policies against the groups in unmanaged domains, including the Group Family and Dynamic Group policies.

  • Run any auto-provisioning or deprovisioning policies against the users or groups held in unmanaged domains.

  • Run any workflow that makes changes to objects in unmanaged domains.

  • Restore objects from Active Directory Recycle Bin in unmanaged domains.

Configuring an unmanaged domain

You can configure an unmanaged domain by applying the Built-in Policy - Exclude from Managed Scope Policy Object in the Active Roles Console.

To configure an unmanaged domain

  1. In the Console tree, under the Active Directory node, right-click the domain you want to configure, and click Enforce Policy.

  2. Click Add in the dialog that appears, and then select the Built-in Policy - Exclude from Managed Scope Policy Object.

  3. Click OK to close the dialogs.

Once applied to a domain, the Built-in Policy - Exclude from Managed Scope Policy Object stops product usage statistics from counting objects in the domain and prevents any changes to the objects held in that domain, making the objects available for read access only. For more information, see Managed scope to control product usage.

Evaluating product usage

Active Roles provides a predefined collection of statistics that helps you understand how many Active Directory domain users, AD LDS, Azure, and SaaS users are managed by this product over time. By analyzing this statistical data, you can establish a baseline of product usage, verify your current Active Roles licensing compliance, and plan for future licensing needs. Since Active Roles’s license fee is calculated based on the number of managed users, product usage statistics enables you to justify and predict your Active Roles licensing expenditures. For instructions on how to examine product usage, see Viewing product usage statistics.

For each Active Directory domain, AD LDS instance, Azure tenants, and SaaS applications registered with Active Roles, product usage data is collected on a scheduled basis by counting the number of enabled users in that domain, instance, registered Azure tenants, and connected SaaS applications with the resulting counts stored in the Active Roles database. For further details, see Scheduled task to count managed objects.

By default, Active Roles counts users in the entire domain or instance. It is possible to have Active Roles count users within a part of a domain or instance by changing managed scope—a tunable collection of containers assumed to hold the managed users. For further details, see Managed scope to control product usage.

Active Roles counts the managed objects on a scheduled basis, and provides a report of managed object statistics. This does not impose any restrictions on the number of objects managed by Active Roles. However, as the number of the managed objects is a key factor in determining the license fee, you may need to ensure that your managed object count does not exceed a certain limit. For this purpose, you can configure Active Roles to check the number of managed objects and send an email notification if the total number of managed objects exceeds a given threshold value. For further details, see Voluntary thresholds for the managed object count.

Viewing product usage statistics

You can view the current total number of managed users on the root page in the Active Roles Console. Select the Console tree root to open the root page in the details pane, and then expand the Product Usage Statistics area on that page. The count of objects under Active Directory Domains, AD LDS Directory Partitions, Azure tenants, and SaaS application represents the current number of managed domain users, managed AD LDS users, Azure hybrid users, Azure cloud only users, Azure guest users, and SaaS users respectively.

NOTE: The count can be derived using the (&(objectCategory=person)(objectClass=user)) LDAP query.

It is possible to view the average or maximum number of managed users in each domain or instance for a certain reporting period. Click Product Usage Statistics to open a page allowing you to:

  • Choose the reporting period.

    The page displays options to export data in HTML format and as raw counters for the period you choose from the Reporting period options, such as past month, past half-year, past year, or a custom date range.

  • Examine the managed user counts for the reporting period you’ve chosen.

    The page displays the current number of managed users per Active Directory domain, AD LDS directory partition, Azure tenant, and SaaS application in the tables under Total accounts. The average and the maximum values along with the total number of managed users can be viewed in the HTML file.

    License type and Total estimated licenses, display the type of license in use and the number of estimated license required, respectively.

  • View the information about the license.

    Click License description to view a detailed information about the license.

  • Save the contents of the page as an HTML file.

    Click Save as HTML at the bottom of the page and specify the desired file name and location.

  • Export the raw statistical data to a file.

    Click Export raw counters at the bottom of the page and specify the desired file name and location. The data is exported in the comma-delimited (CSV) format, representing the daily counts of managed users over the reporting period.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択