Directory Sync
In this article, learn how the workspace directory sync function works.
Sync Behaviour
New Objects:
| Objects Created through Orchestry | For objects created via Orchestry, these items are automatically added to the directory at the tail end of a provisioning request completing. |
| Objects Created outside Orchestry | For objects created outside Orchestry, these items are picked up from 5 minute to an hour after creation. |
Changed Objects
| Objects Changed via any mechanism | For changes to objects such as their name or description, these changes are picked up as part of the nightly ETL process where changes are detected, and any updates are imported into the Directory. |
Archived/Deleted Objects
Objects Archived/Deleted through Orchestry:
| Archive in Place | An Archive in Place through Orchestry is carried out nightly through the policy execution process, after which the Directory is retained in the Directory but its visibility is set to hidden. |
| Move and Delete | A move/deletion through Orchestry is carried out nightly through the policy execution process, after which the Directory is updated to remove the original item. |
| Delete | A deletion through Orchestry is carried out nightly through the policy execution process, after which the Directory is updated to remove the original item. |
Objects Archived/Deleted outside Orchestry:
|
Teams Admin Archive |
An Archive done via Microsoft Teams will not be reflected into the Workspace Directory. Should you wish to hide it, this will need to be a manual step. |
| Delete | A deletion through M365 is picked up as part of the nightly ETL process where changes are detected, and any deleted items are removed from the Directory. |