Study guide

4.3 Cross-Tenant Sync & External Identity Providers

Exam SC-300: Microsoft Identity and Access Administrator Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts & Logistics 1.2 Audience Profile, Zero Trust & Role Scope 1.3 Skills Measured & Study Map

2 Entra Tenant Administration

2.1 Tenant Properties, Domains & Company Branding 2.2 Built-in & Custom Roles, Effective Permissions 2.3 Administrative Units

3 Users, Groups, Licenses & Devices

3.1 Create, Configure & Manage Users 3.2 Groups & Custom Security Attributes 3.3 Licenses, Bulk Operations & Device Join

4 External Identities & Cross-Tenant Access

4.1 External Collaboration & Guest Lifecycle 4.2 Cross-Tenant Access Settings 4.3 Cross-Tenant Sync & External Identity Providers

5 Hybrid Identity

5.1 Entra Connect Sync vs Cloud Sync 5.2 PHS, PTA & Seamless SSO 5.3 AD FS Migration & Connect Health

6 Authentication Methods & MFA

6.1 Authentication Methods Portfolio 6.2 MFA, SSPR & Password Protection 6.3 Passwordless, Session Control & Entra Kerberos

7 Conditional Access

7.1 Planning, Assignments & Controls 7.2 Session Management, Device Restrictions & CAE 7.3 Auth Context, Protected Actions, Templates & Troubleshooting

8 Identity Protection & Global Secure Access

8.1 User Risk & Sign-in Risk 8.2 MFA Registration Campaigns & Risky Workloads 8.3 Global Secure Access

9 Workload & Managed Identities

9.1 Selecting Identities for Apps & Azure Workloads 9.2 Create, Assign & Use Managed Identities 9.3 Service Principals Fundamentals

10 Enterprise Apps & App Registrations

10.1 Enterprise Applications Integration 10.2 App Registrations, API Permissions & App Roles 10.3 Application Proxy & Consent

11 Microsoft Defender for Cloud Apps

11.1 Cloud Discovery & Connected Apps 11.2 CA App Control & Session Policies 11.3 OAuth App Policies & Catalog Management

12 Entitlement Management

12.1 Catalogs & Access Packages 12.2 Access Requests & Terms of Use 12.3 Connected Organizations & External User Lifecycle

13 Access Reviews

13.1 Plan & Create Access Reviews 13.2 Monitor & Respond to Access Reviews

14 Privileged Identity Management

14.1 PIM for Entra Roles & Azure Resources 14.2 PIM for Groups, Approval & Audit 14.3 Break-Glass (Emergency Access) Accounts

15 Monitoring, Logs & Secure Score

15.1 Sign-in, Audit & Provisioning Logs 15.2 Diagnostics, KQL & Workbooks 15.3 Identity Secure Score

4.3 Cross-Tenant Sync & External Identity Providers

Key Takeaways Explain This Topic AI

Cross-tenant synchronization provisions users from a source Microsoft Entra tenant into a target tenant for multi-tenant organization scenarios, reducing manual invite sprawl for internal multi-tenant workforces.

Cross-tenant sync is not a replacement for every B2B partner relationship; it is aimed at tightly related tenants (for example corporate subsidiaries or MTO designs) with governed scope and attribute flow.

External identity providers let users authenticate with federated SAML or WS-Fed partner IdPs (and other External Identities options such as social/OTP where configured) when redeeming or signing in for collaboration.

SAML 2.0 and WS-Federation configurations require correct metadata, entity IDs, claim mappings, and certificates; misconfiguration breaks redemption and sign-in for those domains.

SC-300 expects you to pick the right tool: B2B invite, cross-tenant access trust, cross-tenant sync, or external IdP federation based on whether the problem is partner collaboration, multi-tenant org identity continuity, or authentication source integration.

Last updated: July 2026

Beyond one-off guest invites

Large enterprises often operate multiple Microsoft Entra tenants (by acquisition, geography, regulatory boundary, or historical IT). They also collaborate with partners whose identities live in non-Entra IdPs. SC-300 therefore tests two related skills:

Cross-tenant synchronization — automatically provision identities across related Entra tenants.

External identity providers — federate authentication with SAML or WS-Federation (and understand other External Identities auth options at a conceptual level).

Together with B2B collaboration and cross-tenant access settings, these tools complete the external identity toolkit for Domain 1.

Cross-tenant synchronization overview

Cross-tenant synchronization (CTS) is a Microsoft Entra capability that synchronizes users from a source tenant into a target tenant . Synchronized users in the target are typically represented for collaboration as B2B-style users so they can be assigned access locally, while identity lifecycle is driven from the source scope you configure.

Problems CTS solves

Pain without CTS CTS-oriented outcome

Manual bulk invite of thousands of sister-company employees Automated provisioning of in-scope source users into the target

Stale guest accounts after HR changes in the home tenant Ongoing sync updates/deprovisioning based on scope rules

Inconsistent attributes for dynamic groups in the target Attribute mappings flow selected properties into the target user objects

Multi-tenant organization (MTO) collaboration friction More seamless identity availability across related tenants

Multi-tenant organization context

A multi-tenant organization scenario involves several Entra tenants that represent one company (or a tightly coupled corporate group). Microsoft has been investing in multi-tenant organization experiences (for example improved collaboration UX across member tenants). Cross-tenant sync is a provisioning engine that supports those designs by making users from Tenant A available in Tenant B without relying solely on people clicking invite emails.

CTS is not the first choice for a short project with five vendor users from an unrelated company — use B2B invite + access packages . CTS shines when identity continuity across related tenants is ongoing and large-scale.

Cross-tenant sync building blocks

Conceptual components you should recognize:

  • Component Role
  • Source tenant Authoritative workforce identities to project outward
  • Target tenant Receives synchronized user objects for local access assignment
  • Configuration / job Defines that source→target relationship and sync behavior
  • Scope Which users/groups are included (not necessarily entire source directory)
  • Attribute mappings Which properties flow and how they transform
  • Provisioning cycle Create/update/disable-or-delete behavior on subsequent runs
  • Cross-tenant access alignment Partner/org settings must allow the collaboration relationship underlying sync
  • Scope design

Never sync “all users” into a target tenant without a business reason. Prefer:

Security groups that represent “needs access to Contoso target resources.”

Attribute-based scoping when supported by your design process.

Separate configurations per target if you have many tenants with different populations.

Over-scoping creates excess guest/sync objects, license questions, and governance noise in the target.

Attributes and identity continuity

Synced attributes support dynamic groups, CA filters, and admin readability in the target (department, display name, manager where mapped, etc.). Understand that source remains authoritative for those projected attributes; fixing a display name only in the target may be overwritten on the next cycle if the attribute is in scope — similar mental model to hybrid directory sync, but tenant-to-tenant rather than AD-to-Entra.

Lifecycle and deprovisioning

When a user leaves scope in the source (disabled, removed from scope group, deleted), CTS should update the target accordingly (block/delete soft-delete patterns depending on configuration and product behavior). Exam scenarios often reward “fix source scope / let sync deprovision” over “manually delete 4,000 guests one by one” for MTO offboarding.

CTS versus related features

  • Capability Primary purpose
  • B2B collaboration invite Ad-hoc or package-based external partners into a resource tenant
  • Cross-tenant access settings Allow/block and trust posture between tenants
  • Cross-tenant sync Auto-provision users across related tenants at scale
  • Entra Connect / Cloud Sync Hybrid on-prem AD → Entra (different problem)
  • Entitlement management Request, approve, expire access packages for users who already can authenticate

Trap: choosing Entra Connect to solve “two cloud tenants in one company need shared user presence.” Connect addresses hybrid AD; cross-tenant sync addresses Entra-to-Entra multi-tenant provisioning.

Planning checklist for CTS (exam-oriented)

Confirm business ownership of source and target tenants and data boundary rules.

Ensure cross-tenant access organizational settings support the relationship.

Define scope groups and attribute mapping minimally.

Pilot a small set; validate sign-in, app assignment, and CA for synced users.

Define who assigns access in the target (groups, packages, apps) — sync alone does not equal authorization to sensitive apps.

Monitor provisioning logs for failures (hard deletes, scoping misses, permission issues).

Establish joiner-mover-leaver process that starts in the source system of record.

External identity providers (External Identities)

Not every collaborator authenticates with a Microsoft Entra workforce tenant. External identity providers integrate alternative authentication sources into your External Identities experience so users can sign in / redeem with those IdPs.

Why add an external IdP?

A partner organization runs a SAML 2.0 or WS-Federation IdP (AD FS, another cloud IdP, custom federation suite).

You want partner users to use their corporate credentials rather than Microsoft account sprawl or only email OTP.

You are aligning federation for a strategic partner domain to a known IdP.

External Identities also includes options such as email one-time passcode and social identity providers where the product and tenant configuration allow — useful when partners lack a formal federation relationship. For SC-300, prioritize understanding SAML and WS-Fed federation admin tasks and when federation is the right design.

SAML and WS-Federation federation concepts

Both protocols establish a trust so the external IdP authenticates the user and issues a security token your Entra External Identities configuration accepts for that identity pathway.

  • Topic SAML 2.0 WS-Federation
  • Common in Broad SaaS/partner federation Many Microsoft-centric / AD FS historical deployments

Metadata Entity IDs, endpoints, certificates often exchanged via metadata XML Federation metadata similarly defines endpoints and signing certs

Claims Attributes in SAML assertions (name identifier, email, etc.) Claims in WS-Fed tokens

Admin goal Correct issuer, ACS/endpoint URLs, cert rollover, claim rules Same trust hygiene with WS-Fed endpoints

Configuration elements you must respect

Regardless of protocol, federation breaks when any of these drift:

Issuer / entity ID mismatches between IdP and Entra configuration.

Reply URL / assertion consumer endpoint incorrect for the cloud environment.

Signing certificate expired or rolled on IdP without updating the trust.

NameID / email claims not matching how users are invited or matched.

Domain association — partner users’ email domains must align with the configured IdP routing for those sign-ins.

Operational lifecycle of an external IdP

Gather partner metadata (or manual endpoints and certs).

Create the external IdP in Microsoft Entra External Identities.

Map claims required for unique user identification (typically email/UPN-style identifiers).

Assign domains or otherwise ensure users with those domains hit this IdP path.

Test with a pilot partner account: redeem invite, complete auth, land on assigned app.

Monitor sign-in failures; coordinate certificate rollover windows with the partner.

Decommission cleanly when the partner relationship ends (do not leave stale trusts).

Choosing the right external identity approach

  • Business need Prefer
  • Occasional vendor needs Teams/SharePoint B2B invite (+ access package), collaboration settings
  • Fine-tune partner tenant allow/trust Cross-tenant access organizational settings
  • Two corporate Entra tenants, continuous workforce sharing Cross-tenant synchronization (+ MTO practices)
  • Partner has own SAML/WS-Fed IdP for staff credentials External IdP federation
  • Partner has no IdP and no Entra tenant Email OTP or other supported External Identities methods
  • On-prem AD users into your single tenant Entra Connect / Cloud Sync (hybrid — later chapter)
  • Security and governance considerations

Federation is trust: a compromised partner IdP can assert identities for domains you accept — limit domains, monitor sign-ins, require CA MFA where appropriate, and review partner security posture.

CTS multiplies presence: users appear in multiple tenants; access reviews and least privilege must run in each tenant that holds access.

Attribute leakage: only map attributes the target needs; avoid syncing sensitive HR fields without purpose.

Admin roles: configuring external IdPs and cross-tenant sync requires privileged identity admin roles — use PIM and change control.

Logging: use Entra sign-in logs (including failed federated attempts) and provisioning logs for CTS troubleshooting.

Exam traps

Using cross-tenant sync for a one-week external agency project (overkill; invite/package instead).

Choosing Entra Connect to link two cloud-only Entra tenants.

Forgetting that CTS provisions identity presence , not automatic access to every app — assignment still required.

Ignoring certificate expiry on SAML/WS-Fed trusts.

Confusing WS-Fed/SAML external IdP (partner auth into External Identities) with app registration SSO for a SaaS app you publish (related skills, different admin blades and purposes).

Enabling broad social IdPs in a high-security tenant without policy alignment.

Putting the chapter together

External identity mastery for SC-300 is a stack:

Guest lifecycle & collaboration settings — invite, redeem, restrict, offboard.

Cross-tenant access settings — default vs organizational, inbound/outbound, direct connect, trust claims.

CTS & external IdPs — scale related-tenant provisioning and federate non-Entra authenticators.

If you can read a scenario and pick the correct layer, you are ready for hybrid identity and authentication deep dives next. Keep drilling items at /practice/azure-sc-300 and review adjacent fundamentals in /study-guides/azure-sc-900 when you need Zero Trust vocabulary refreshers, then return to the SC-300 guide at /study-guides/azure-sc-300 .