Cross-Tenant Synchronization Identity Types
Short answer
A Only User1 syncs because cross-tenant synchronization only supports user identities, not group objects.
Question
Key Takeaways
The question tests the specific limitation of cross-tenant sync: while you can scope provisioning by group membership, the group object itself does not sync to the target tenant; only the users within it do.
Microsoft Entra cross-tenant synchronization is limited to synchronizing user identities only. This page clarifies that groups are not synced as distinct objects, resolving confusion around scoping filters.
Common mistake: Many candidates choose D because they assume all listed entities (users and groups) will appear in the target tenant, confusing 'scoping' with 'syncing'.
Expert Analysis
Why the Answer Is Correct
Correct answer: A — Only User1 syncs.
Microsoft Entra ID cross-tenant synchronization has a strict limitation: it only supports synchronizing users. While you can configure scoping filters to select which users should be provisioned based on their group membership, the groups themselves are not synchronized to the target tenant. Therefore, even if Group1 and Group2 are used to filter which users get synced, those group objects do not appear in fabrikam.com. Only the individual user accounts (User1) are created in the target tenant.
Why the Other Options Are Wrong
Options B, C, and D incorrectly assume that group objects (Group1 or Group2) are replicated to the target tenant. In reality, groups remain local to the source tenant. If you need group-based access control in the target tenant, you must create equivalent groups there manually or via other automation, but the cross-tenant sync tool does not transfer group definitions.
Community Comment Notes
Community consensus strongly supports Option A. Comments highlight that "only users can be synchronized between tenants" and clarify that while groups are used for scoping, they are not synced. One commenter noted, "the scoping for groups is only to select the users and the group itself is not synchronised." Another cited Microsoft documentation stating, "Only Entra ID users can be synchronized (groups, devices and contacts are not supported)."
Official Reference
This link opens the official vendor documentation in a new tab.
Exam Strategy
Always distinguish between 'scoping' (filtering who gets synced) and 'syncing' (what actually moves). For Cross-Tenant Sync, remember: Users sync, Groups do not. If the question asks what appears in the target tenant, exclude groups.
Frequently Asked Questions
Can I sync security groups with cross-tenant sync?
Why did some think Groups sync too?
Community Votes
81% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 10 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 10
-
sn0rlaxxx 👍 8 Answered AMicrosoft Entra users can be synchronized between tenants. (Groups, devices, and contacts aren't currently supported.) https://learn.microsoft.com/en-us/entra/identity/multi-tenant-organizations/cross-tenant-synchronization-overview?form=MG0AV3#cross-tenant-synchronization-setting:~:text=Microsoft%20Entra%20users%20can%20be%20synchronized%20between%20tenants.%20(Groups%2C%20devices%2C%20and%20contacts%20aren%27t%20currently%20supported.)
-
test123123 👍 2 Answered Dhttps://learn.microsoft.com/en-us/entra/identity/multi-tenant-organizations/cross-tenant-synchronization-configure#step-7-define-who-is-in-scope-for-provisioning You can sync both users and groups.
-
anonymousarpanch 👍 1 Answered AIgnore my previous response. After further studying the user and groups assignments, apparently it is now known that the scoping for groups is only to select the users and the group itself is not synchronised to target tenant. This has been clarified by Microsoft in Multitenant org FAQ. Sometimes, I wonder why don’t they give everything in one place?. Learning one thing in azure takes so much time. And then after 3 months they change the entire setting.
-
Sunth65 👍 1 Answered ACross-tenant synchronization limitations and disadvantages Only one-way sync is supported. ... The target tenant isn't queried for changes in attributes. ... No support for cross-cloud sync. Only Entra ID users can be synchronized (groups, devices and contacts are not supported). Cross-tenant sync starts every 40 minutes.
-
anonymousarpanch 👍 1 Answered BMay sound weird. But now, we Can sync user and groups. M365 groups are not supported. This is as per latest Microsoft documentation. Lookout for ‘what is cross-tenant synchronization’. There is a hyperlink ‘scoping users or groups to be provisioned with scoping filters’. Go through it..which should clarify
Show 5 more comments
-
Frank9020 👍 1 Answered BOnly users and security groups are synchronized. Microsoft 365 groups are not included in cross-tenant synchronization.
-
rvln7 👍 1 Answered Aonly users can be synchronized between tenants!
-
noa808a 👍 1 Answered AAnswer is correct.
-
mert123 👍 1 Answered Acorrect chatgpt
-
PD1 👍 1 Answered DAll can sync.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All SC-300 Questions
Access 80 questions with complete answers and detailed explanations.
View Full SC-300 Practice Test →