Get started

Admin consent to Fortytwo Universe

Consent has to be granted by a Global Administrator, once per tenant. See get started for details, and Administrator permissions for the roles that have to be assigned afterwards.

Setting up IAM Core

Getting from an empty tenant to useful data is four steps, in this order.

1. Add a connector

A connector brings a source system into IAM Core. Start with whichever system is authoritative for people — usually HR.

Install-Module Fortytwo.IAM.Core.Admin -Scope CurrentUser
Connect-IAMCore

Get-IAMCoreConnectorTemplate

If you just want something to look at, the demo data connectors populate a fictional municipality and need no credentials.

2. Look at what arrived

Before writing any rules, see what the source actually produced. Sync rules are written against these exact attribute names, so this step saves a lot of guessing:

Get-IAMCoreConnectorDataStatistics -Id $Connector.id

Find-IAMCoreConnectorDataObject -ConnectorId $Connector.id -ConnectorObjectType "person" |
    Select-Object -First 1

3. Write sync rules

Sync rules decide which connector objects matter and what they become. The usual order is org units first, then identities, then the relationships that tie them together.

Build them up one at a time and preview before committing:

Get-IAMCoreConnectorDataObjectSyncPreview -ConnectorId $Connector.id -ConnectorObjectId $Object.id

4. Synchronize

New-IAMCoreSyncJob | Wait-IAMCoreSyncJob

Then check the result:

Get-IAMCoreIdentity | Select-Object -First 5
Get-IAMCoreOrgUnit | Show-IAMCoreOrgUnitStructure

Adding a second source

Once one system is flowing, additional systems join onto what is already there rather than creating duplicates. The second connector's rules are usually join only — they enrich existing identities instead of provisioning new ones — and priority decides which system wins where both supply the same attribute.