Practice Exams:

Microsoft AZ-104: Hybrid Identity Decisions

Cloud & Architecture

Hybrid identity is a decision about where account attributes originate, how sign-ins are verified and which synchronization or provisioning service owns each object. Reliable Azure administration requires distinguishing identity sources and authentication paths before choosing a synchronization agent. An on-premises account can synchronize to Microsoft Entra without using the same authentication path for every application. Clarify the authoritative attribute source, provisioning method, sign-in flow, and exception process before deploying a connector.

On this page
  1. Separate directory ownership from user sign-in
  2. Decide which synchronization engine meets actual requirements
  3. Make the authentication choice explicit
  4. Treat device identity as its own design stream
  5. Prevent accidental duplication and conflicting identities
  6. Secure the identity control plane and its recovery paths
  7. Choose a test that proves the entire identity journey

Separate directory ownership from user sign-in

An employee might have an account maintained in an on-premises Active Directory forest and a corresponding Microsoft Entra identity used for Microsoft 365, Azure and other cloud applications. Synchronization can make attributes and lifecycle events flow between systems, but it does not make the directories identical. The cloud identity has its own object ID, tenant context, roles, policies and application access assignments. Hybrid identity in Microsoft AZ-104 separates synchronized identity attributes from the authorization decisions made by the destination tenant or application.

Document the authoritative source for each population and attribute: user names, unique identifiers, group membership, password status, department details, license assignment and privileged roles. On-premises HR or Active Directory workflows may remain authoritative for some data; cloud-only accounts and emergency administrative identities need different governance. If two systems can both rewrite the same attribute without coordination, a conflict is an architecture defect rather than an ordinary sync delay.

The cloud tenant and Azure subscription are different scopes. A person can authenticate through Microsoft Entra ID while still lacking Azure RBAC permissions on a resource group. Conversely, a directory administrator does not automatically own every subscription. Keep directory-role operations separate from resource-management authorization when assigning incident duties and privileges.

Decide which synchronization engine meets actual requirements

Microsoft Entra Connect Sync and Microsoft Entra Cloud Sync have different execution models, feature coverage and migration paths. Cloud Sync uses a lightweight provisioning agent and cloud-controlled configuration, while Connect Sync uses an on-premises synchronization engine. The product names alone do not establish which one supports your forest topology, custom transformations or provisioning scenarios.

Hybrid identity planning begins with the supported Microsoft Entra synchronization tools and the particular hybrid identity scenarios the organization requires. Complex forests, device registration and attribute customizations may affect the right synchronization approach. Validate the current capability matrix for that environment before reusing settings from an older deployment.

A design record should list required source forests and domains, total object count, authoritative attributes, filtering rules, group scenarios, password management expectations, provisioning latency and recovery responsibilities. If Cloud Sync supports all the validated requirements, its agent model may simplify operation. If an important scenario requires Connect Sync, selecting the newer-sounding tool would create an unsupported migration path.

Make the authentication choice explicit

An illustrative decision helps separate the tools. Suppose a company has one conventional Active Directory forest for office workers, another recently acquired forest with different identity rules and a hybrid-joined fleet. A synchronization design should prove account creation and changes work in both forests, that each identity joins the intended cloud account rather than creating a duplicate, and that the chosen approach supports the specific device enrollment scenario. Those are three distinct acceptance tests. If one tested requirement remains unavailable in the selected service, keep the supported existing path for that population while recording a migration plan instead of hiding the exception under a single “sync complete” metric.

Directory synchronization and authentication are related but different. Password Hash Synchronization, Pass-through Authentication and federation each affect how a user’s cloud sign-in is validated and which infrastructure the sign-in depends upon. Password Hash Synchronization can allow supported cloud authentication without a real-time on-premises password verification call; Pass-through Authentication uses on-premises agents; federation sends authentication to a configured identity provider.

Choose based on supported security controls, business continuity, legacy protocol requirements and the organization’s ability to operate the dependencies. A federated deployment may satisfy a specialized policy but also adds service availability, certificate and configuration dependencies. A PTA arrangement must account for agent capacity and outages. Avoid assuming any one choice is inherently the most secure without examining conditional access and supported authentication protections.

Map multifactor authentication and Conditional Access to application entry points and users. These are not automatic substitutes for privileged access review. Password synchronization success does not prove that a user can access a particular resource or that an application has the right tenant configuration.

Treat device identity as its own design stream

Windows devices may be Microsoft Entra joined, hybrid joined or registered under different circumstances. Device identity affects conditional access, management and the user sign-in experience; it should not be inferred from the presence of a synchronized user account. An organization’s Windows device strategy needs an explicit plan for enrollment, policy, certificates and handling devices that cannot contact on-premises services.

Tool capability statements for device synchronization have evolved. Some current Microsoft documentation discusses device sync with Cloud Sync under defined settings, while scenario matrices retain topology-specific distinctions. The safe approach is to verify the exact feature and platform version needed for hybrid join before planning migration. Do not claim every hybrid join configuration automatically moves to Cloud Sync or that all device scenarios are categorically unsupported.

An operations checklist should identify how a new device is provisioned, how its object is created and recognized, when a device becomes compliant, and how access is removed after loss or retirement. Test a user device and a service or shared device separately when their lifecycle requirements differ.

Prevent accidental duplication and conflicting identities

Password and identity-provisioning incidents often have different owners. When a new hire’s account appears in Entra ID but login fails, identify whether the failure is password validation, conditional access, a missing application entitlement or a directory object conflict. For example, a group assigned through a filtered on-premises organizational unit might be absent in the cloud even though the user’s password can be validated. Fixing the authentication agent cannot restore the missing group assignment; first verify authoritative membership and its sync scope. This separation reduces broad, risky changes during a high-pressure account outage.

Moving synchronization engines creates risk if the same on-premises source object is provisioned twice or mapped incorrectly to a cloud object. Plan immutable/source anchors, soft matching, account conversion and scoping before introducing a new active sync path. Compare a sample of cloud and on-premises objects and record how duplicates or mismatches will be detected.

Microsoft’s Cloud Sync migration discusses staging, supported configuration transfer, validation and rollback. It does not authorize switching an entire enterprise without verifying customizations and downstream dependencies. Export the current configuration and document how you will restore the previous state if attribute flow or matching behaves unexpectedly.

Test changes with a selected population and predefined acceptance criteria: new user creation, attribute update, group change, password reset, disablement and an intentional exception. Check the cloud object ID and permissions after migration. A user may still appear in the directory but have lost an application assignment or joined the wrong group.

Secure the identity control plane and its recovery paths

Synchronization agents and their service identities deserve the protections given to core infrastructure: restricted administrative access, patching, monitoring, documented ownership and recoverable configuration. Compromise of an authoritative directory or agent can affect access far beyond one resource group. Separate day-to-day operator roles from highly privileged directory administration.

Provide cloud-only emergency accounts under approved monitoring and use them only for break-glass situations. Test whether critical Azure management tasks can continue when the on-premises directory, VPN, federation provider or synchronization engine is down. A recovery plan based entirely on signing in through the failed component is circular.

Log provisioning failures, object conflicts, stale agents and unusual privileged changes with actionable escalation routes. A monitoring dashboard showing “sync healthy” can still hide a high-impact failure for one organizational unit excluded by a filter. Reconcile actual intended populations to observed cloud objects regularly, especially after directory restructuring.

Choose a test that proves the entire identity journey

For operational handover, store an evidence table with the test object’s source identifier, resulting cloud object ID, observed sync time, group membership, authentication method, effective Azure role scope and incident contact. Include a deliberately disabled test user and confirm downstream cloud access responds according to the organization’s token/session policies rather than claiming instantaneous universal revocation. A help desk runbook should explain which team owns each state and what evidence is safe to collect without exposing credentials. That makes hybrid identity an auditable service instead of a black box maintained by one directory engineer.

A complete hybrid-identity validation is more than triggering synchronization. Choose a representative newly hired test user, create the source account, confirm the correct cloud identity and group state, authenticate through the approved path, and verify application and Azure resource access with appropriately scoped roles. Record timings and failures at each boundary.

Repeat for termination or disablement. Observe how quickly sessions and effective access change, not only when one directory flag updates. Include a credential reset, change of group, device registration and an on-premises connectivity interruption where relevant. These exercises expose assumptions about propagation delay and cached tokens that a happy-path sign-in does not.

Hybrid identity needs separate evidence for account lifecycle, authentication, and resource authorization. During an exercise, verify how a joiner receives access, how a leaver loses it, and what happens when the synchronization or federation component fails. Document which system is authoritative for each attribute so incident responders do not attempt to repair a sign-in outage by granting unrelated Azure permissions.

Continue learning

Related guides

Microsoft Entra Groups, Roles, and Access ReviewsGovern Entra membership, directory roles, and access reviews.Managed Identities in Azure AdministrationReplace embedded workload secrets with scoped managed identities.Azure RBAC Design for Platform TeamsDelegate platform access with scoped roles and least privilege.Windows Server Hybrid ManagementConnect hybrid identity to Windows Server and Azure Arc operations.

Related Posts

• Legacy MCSA Cloud Platform: Azure Architecture Skills and Current Paths

• Microsoft AZ-104: Is Azure Administration the Right Career?

• Azure Mastery Beyond the Basics: Governance, Green Cloud, and Strategic Growth

• Cloud Strategy Unlocked: How AZ-305 Shapes Real Azure Architects

• Microsoft AZ-104: Managed Identities in Azure

• Microsoft AZ-104: Entra Roles and Access

• Microsoft AZ-900: Cloud Economics: CapEx, OpEx, and the Cost of Commitment

• Microsoft AZ-104: Zones and Failure Domains

• Microsoft AZ-104: Load Balancer vs. App Gateway

• Microsoft AZ-104: FSLogix Profiles for Azure Virtual Desktop