The easiest way to explain declarative provisioning is as follows: objects are processed from the source connected directory to the target source by evaluating how the objects and the associated attributes should be transformed. This is controlled by inbound rules from the connector space to the metaverse and outbound rules from the metaverse to the connector space. The following diagram gives you an overview of all of the components:
Declarative provisioning options and components overview
Declarative provisioning provides the following capabilities:
- The only way to configure the sync engine
- Functions to configure attribute flows
- Precedence is on SRs (not on Connectors)
MV—deletion rules now use declarative provisioning- Introduces parameters, such as
%Domain.Netbios% - Configured through PowerShell
The attribute-flow expression language can be explained as follows:
- Written in Visual Basic for Applications (VBA)
- Stricter syntax:
- Useful errors for...