지금 지원 담당자와 채팅
지원 담당자와 채팅

Active Roles 8.1.5 - Administration Guide

Introduction Getting started with Active Roles Configuring rule-based administrative views Configuring role-based administration 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 Configuring 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 Migrating Active Roles configuration with the Configuration Transfer Wizard Managing Skype for Business Server with Active Roles
About Skype for Business Server User Management Active Directory topologies supported by Skype for Business Server User Management User Management policy for Skype for Business Server User Management Master Account Management policy for Skype for Business Server User Management Access Templates for Skype for Business Server Configuring the Skype for Business Server User Management feature Managing Skype for Business Server users
Exchanging provisioning information with Active Roles SPML Provider Monitoring Active Roles with Management Pack for SCOM Configuring Active Roles for AWS Managed Microsoft AD Azure AD, Microsoft 365, and Exchange Online Management
Configuring Active Roles to manage Hybrid AD objects Unified provisioning policy for Azure M365 Tenant Selection, Microsoft 365 License Selection, Microsoft 365 Roles Selection, and OneDrive provisioning Changes to Active Roles policies for cloud-only Azure objects
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 Configuring federated authentication 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

Scenario 1: Using mask to control phone number format

This scenario describes how to configure a policy that forces the user phone number to conform to the format (###) ###-##-##.

To implement this scenario, you must perform the following actions:

  1. Create and configure a Policy Object that defines the appropriate policy.

  2. Apply the Policy Object to a domain, OU, or Managed Unit.

As a result, when creating or modifying a user object in the container you selected in Step 2, Active Roles checks whether the phone number conforms to the stated format. If not, the policy disallows the creation or modification of the user object.

The following two sections elaborate on the steps to implement this scenario.

Creating and configuring the Policy Object

You can create and configure the Policy Object you need by using the New Provisioning Policy Object Wizard. For more information about the wizard, see Creating a Policy Object.

To configure the policy, click Property Generation and Validation on the Policy to Configure page of the wizard. Then, click Next.

On the Controlled Property page, click Select. Then, in the Select Object Type and Property dialog, select User from the Object type list, and click Telephone number in the Object property list, as shown in the following figure.

Figure 37: Select Object type and property

Click OK, then click Next.

On the Configure Policy Rule page, in the upper box, select the following check boxes:

  • ‘Telephone Number’ must be specified: This makes the phone number a required property, that is, requires that a phone number be specified in every user account.

  • ‘Telephone Number’ must be <value>: This allows you configure a mask for the telephone number by adding the appropriate entry to the value for this condition.

At this stage, the Configure Policy Rules page looks like the following figure.

Figure 38: Configure policy rules

The next phase is to configure the value.

Click <click to add value>. In the Add Value dialog, click Configure. In the Configure Value dialog, click Add. In the Add Entry window, under Entry type, click Mask.

Now you can use the Entry properties area in the Add Entry window to configure a mask.

The format consists of four groups of numerals divided by certain characters: spaces, hyphens, and brackets. First, configure a mask that requires the first three characters to be numerals:

  • Select Exactly the specified number of characters.

  • In the Number of characters box, enter 3.

  • Under Allowed characters, select the Numerals check box.

The Add Entry window should look as shown in the following figure.

Figure 39: Add entry

Click OK to close the Add Entry window. Then, click OK to close the Configure Value dialog. As a result, the Add Value dialog looks as shown in the following figure.

Figure 40: Add value dialog

Taking into consideration the mask you have configured, you can guess that the mask for the phone number format you need is as follows:

({3 required [0-9]}) {3 required [0-9]}-{2 required [0-9]}-{2 required [0-9]}

Type this mask in the ‘Telephone Number’ must be box in the Add Value dialog. Pay attention to the round brackets enclosing the first three characters, a space character following the group in the round brackets, and two hyphen characters that separate the groups of characters.

Click OK to close the Add Value dialog. Click Next and follow the instructions in the wizard to create the Policy Object.

Applying the Policy Object

You can apply the Policy Object by using the Enforce Policy page in the New Provisioning Policy Object Wizard, or you can complete the wizard and then use the Enforce Policy command on the domain, OU, or Managed Unit where you want to apply the policy.

For more information on how to apply a Policy Object, see Applying Policy Objects and Managing policy scope.

Scenario 2: Using regular expressions to control phone number format

This scenario describes how to configure a policy that forces the user phone number to conform to the following format:

  • The first character must be “+”.

  • The second character(s) must be the country code.

    (This is 1 in the US and Canada, and 61 in Australia for example.)

  • Use spaces (instead of dashes or braces) to separate area code.

  • Use spaces (instead of dashes) to separate the phone number.

  • Optionally, use a lowercase “x” to indicate an extension.

The following table provides some examples to clarify how the phone number should look in accordance with these formatting requirements.

Table 5: Phone number format

Correct

Incorrect

Comment

+1 949 754 8515

949-754-8515

The incorrect entry does not begin with + and country code, and uses dashes instead of space.

+44 1628 606699 x1199

+44 1628 606699 X1199

The incorrect entry uses the upper-case X.

To implement this scenario, you must perform the following actions:

  1. Configure the Policy Object that defines the appropriate policy.

  2. Apply the Policy Object to a domain, OU, or Managed Unit.

As a result, when creating or modifying a user object in the container you selected in Step 2, Active Roles checks whether the phone number conforms to the stated format. If not, the policy disallows the creation or modification of the user object.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택