Question 610
Two on-premises forests contain linked user and resource objects and the migration team expects simple one-directory Cloud Sync to resolve them without mapping. The team believes no other action is necessary. Why is the current tenant configuration inadequate for this requirement?
Explanation
Correct Answer
The actual failure mechanism is Identity matching across complex forests requires explicit supported topology and join rules. Its relevance follows from the stated tenant facts, not just a generic security recommendation. Correct it by design a supported multi-forest object matching and synchronization approach for the documented identity topology. Then verify: A pilot joins the appropriate linked objects into one authorized cloud user without duplicate accounts.
Incorrect Answers
An unverified or invalid sign-in suffix can prevent desired cloud UPN alignment. The stated symptoms instead indicate that identity matching across complex forests requires explicit supported topology and join rules.
A running local service is not proof that scheduled sync and identity exports succeed. The stated symptoms instead indicate that identity matching across complex forests requires explicit supported topology and join rules.
Directory synchronization can fail or create duplicate identities when legacy attributes violate cloud requirements. The stated symptoms instead indicate that identity matching across complex forests requires explicit supported topology and join rules.