Local AD Connector pull the information from the local AD.

with help of Azure AD connector same informations are export to Azure AD

Data is import from AD to AD connector space As well as in Azure AD connector space.

The sync process happen in three phase.

Import

Sync

Export

1. Data is imported from local ad and make replica in Connector Space AD.

2. Data is imported from Azure AD. There is not found differece between your azure ad and azure AD
connector space. resaon behind this all changes are pushed from Metaverse to AAD connecor space.

3. once import process is completed from on prem ad as AAD. After that sync process happen
between AD connector space and Metaverse data space and create a replica in metaverse with ADD
flag. that mean new user has been created.

4. the next process sync happen from AAD Connectre space to metaverse. After that no information
found in AAD connector space about new user created/update etc.

4. After that export process occure from meneaver to AAD Connector space.

5. once sucssfully exported user object in AAD conneter space. it show flag confimation is pending. it
remain untill run import cycle from AAD Connetor space to AAD.

5. Once data successfully imported in AAD that flag is removed from AAD connector space and user
show in Azure AD.

1. Create new users

2. once create user run import on local AD connector to make import user and make a replica.
Click on search and not find any new created objects in connector space.

So we run the delta import to import user in AD connector space.

Right click on AD connector  run  select delta import and click ok.

Once completed delta import cycle you can see one object is add

You can check it by click on ADD. Now you can search object in AD connector space

Now we will run import on azure ad

Right click on AAD connector  run  import delta

Now we will run delta sync on local AD connector right click on connector  run  click delta sync .

After sync cycle complete user object will be show in metaverse space. You can seach in metavers
space

Next process we will delta sync on AAD connector same steps

After competed sync you will not find any difference between metaverse space and AAD space
Now will go to run final steps on AAD Connector as export so that this information to send to cloud

Once export is completed on AAD connector. We will check new object AAD connector space. There
object but not show display name because there is flag of export confirmation.
When you click on this object you will see object is awainting export confirmation. Which object
need to sent AAD but need to verify

So verify this object we run full import on AAD connector to verify this new object and successfully
created on AAD.

Once full run successfully completed, verfification. Export tag will be remove from new object.