Settings
The Settings tab lets you configure how this Connector behaves during provisioning — including whether it is active, how it matches incoming records to existing Identities, and which attributes it uses as a join key.
The Connector Settings tab controls provisioning behavior, display name, and identity matching for this Connector.
What you can do here
Provisioning Enabled toggle
Enables or disables all Sync operations for this Connector. When disabled, no data is written to the Target System during a Sync run.
App Display Name
Sets the human-readable name for this Connector. This is the display name of the Enterprise Application in Entra ID.
Identity Mode selector
Controls how incoming records are matched to existing Identities. The example shown is Delta (ingestion), which uses an incremental matching strategy.
Join Key field
A comma-separated list of canonical attribute names AOH Sync uses — in priority order — to match an incoming record to an existing Identity. The first attribute that produces a match wins.
Telemetry toggle
Enables or disables the collection of provisioning telemetry data for this Connector. When on, AOH Sync sends telemetry data for monitoring and diagnostics.
Connection Info
Read-only reference section showing this Connector's Tenant ID, creation date, last-updated timestamp, and current status.
Understanding the Identity Matching settings
Identity Mode determines the strategy AOH Sync uses when deciding whether an incoming record is a new Identity or an update to an existing one. The mode shown in the demo is Delta (ingestion), which processes only changed records since the last Sync. Select the mode that matches how your Source System delivers data to AOH Sync.
Join Key is the list of canonical attributes AOH Sync evaluates to find an existing Identity for each incoming record. In the demo, the join key is userPrincipalName,email,employeeId — AOH Sync tries userPrincipalName first, then falls back to email, then employeeId. If no match is found on any attribute, AOH Sync creates a new Identity record. Leaving the Join Key empty falls back to default UPN/email/displayName matching.
Telemetry controls whether AOH Sync collects provisioning telemetry data for this Connector. Enabling it sends diagnostic signals that help identify Sync issues. It can be toggled independently of provisioning.
The Connection Info section is read-only and shows reference identifiers for this Connector: its Tenant ID, creation date, last-updated timestamp, and current status. Use these values if you need to identify the Connector in support requests or audit logs.
Disabling the Provisioning Enabled toggle stops all Sync operations for this Connector immediately. No data will be written to or removed from your Target System until you re-enable it.
How to use it
Confirm provisioning is enabled
Check that the Provisioning Enabled toggle is on. If you need to pause all Sync activity for this Connector, turn it off here.
Set the App Display Name
Enter the name you want to appear for this Connector. This becomes the display name of the Enterprise Application in Entra ID. Use a name that clearly identifies the source and target (for example, HR System → AOH Sync).
Choose the Identity Mode
Select the mode that matches how your Source System delivers data to AOH Sync.
Define the Join Key
Enter a comma-separated list of canonical attribute names in the order you want AOH Sync to try them. The first attribute that matches an existing Identity wins. Leave blank to use the default matching behavior.
Configure Telemetry
Turn the Telemetry toggle on to enable provisioning telemetry collection for this Connector, or leave it off to disable it. This setting does not affect Sync operations.
Related
Last updated