Active Directory policies define the properties of a machine record, for example, domain, as well as the organizational unit in which the record is created using a vRealize Automation blueprint.
If you apply a policy to a business group, all the machine requests from the business group members are added to the specified organizational unit. You can create different policies for different organizational units, and then apply the different policies to different business groups.
Active Directory policies are a tech preview feature in vRealize Automation 7.1 and should not be used in a production environment.
Using Custom Properties to Override an Active Directory Policy
Using the provided Active Directory custom properties, you can override the Active Directory policy, domain, organizational unit, and other values on a particular blueprint when it is deployed.
The list of the provided Active Directory custom properties is included in the Custom Properties E Table. The custom property prefix is ext.policy.activedirectory.
In addition to the provided properties, you can create your own custom properties. You must prefix you custom properties with ext.policy.activedirectory. For example, ext.policy.activedirectory.domain.extension or ext.policy.activedirectory.yourproperty. The properties are passed to your custom vRealize Orchestrator Active Directory workflows.
For more information about custom properties, see Using Custom Properties. For the values that you are overriding, you might need to create a property definition. For example, you might create a property definition that retrieves the available Active Directory policies from vRealize Automation. Alternatively, you might create definition that allows the requesting user to select from two or more alternative organizational units. See Using Property Definitions.