Study guide

3.4 Authorization for On-Premises Resources

Exam AZ-305: Designing Microsoft Azure Infrastructure Solutions Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Orientation

1.1 AZ-305 Current Exam Facts & Format 1.2 Candidate Profile, Prerequisites & the AZ-104 Requirement 1.3 Skills Outline, Domain Weights & How to Use This Guide

2 Chapter 2: Logging, Monitoring & Diagnostics Design

2.1 Logging Solution Design 2.2 Log Routing Design 2.3 Azure Monitor Metrics & Alerting Design 2.4 Application Insights & Diagnostic Monitoring Design

3 Chapter 3: Authentication & Authorization Design

3.1 Authentication Solution Design 3.2 Identity Management Design 3.3 Authorization for Azure Resources 3.4 Authorization for On-Premises Resources 3.5 Secrets, Certificates & Key Management Design

4 Chapter 4: Governance, Compliance & Identity Governance Design

4.1 Management Group & Subscription Hierarchy Design 4.2 Resource Group Organization & Tagging Strategy Design 4.3 Compliance Management Design 4.4 Identity Governance Design

5 Chapter 5: Relational Data Storage Design

5.1 Relational Data Storage Selection 5.2 Database Service & Compute Tier Design 5.3 Database Scalability Design 5.4 Relational Data Protection Design

6 Chapter 6: Semi-Structured & Unstructured Data Storage Design

6.1 Semi-Structured Data Storage Design 6.2 Unstructured Data Storage Design 6.3 Storage Tier & Cost-Performance Trade-off Design 6.4 Unstructured Data Protection & Durability Design

7 Chapter 7: Data Integration & Analytics Design

7.1 Data Integration Pipeline Design 7.2 Event-Based & Real-Time Data Integration Design 7.3 Data Analytics Platform Design

8 Chapter 8: Backup & Disaster Recovery Design

8.1 Recovery Objectives Design: Calculating and Meeting RTO/RPO 8.2 Azure Site Recovery Architecture for Hybrid Workloads 8.3 Compute Backup & Recovery Design 8.4 Database Backup & Recovery Design 8.5 Unstructured Data Backup & Recovery Design

9 Chapter 9: High Availability Design

9.1 Compute High Availability: Availability Sets & Availability Zones 9.2 Compute High Availability: Load Balancing & VM Scale Set Design 9.3 Relational Data High Availability Design 9.4 Semi-Structured & Unstructured Data High Availability Design

10 Chapter 10: Compute Solution Design

10.1 Compute Requirements Analysis & Virtual Machine-Based Solution Design 10.2 Container-Based Solution Design (AKS, Container Apps, Azure Container Instances) 10.3 Serverless-Based Solution Design (Azure Functions, Logic Apps) 10.4 Batch Processing Solution Design (Azure Batch, HPC Workloads)

11 Chapter 11: Application Architecture Design

11.1 Messaging Architecture Design (Service Bus, Queue Storage) 11.2 Event-Driven Architecture Design (Event Grid, Event Hub) 11.3 API Integration & Application Caching Design (API Management, Azure Cache for Redis, CDN) 11.4 Application Configuration Management & Automated Deployment Design (App Configuration, DevOps Pipelines, Deployment Slots)

12 Chapter 12: Migration Design

12.1 Migration Assessment: Cloud Adoption Framework & On-Premises Evaluation 12.2 IaaS & PaaS Workload Migration Design 12.3 Database Migration Design (Data Migration Service, Database Migration Assistant) 12.4 Unstructured Data Migration Design (AzCopy, Data Box, Storage Migration Service)

13 Chapter 13: Network Solution Design

13.1 Internet Connectivity Design 13.2 Hybrid Connectivity Design 13.3 Network Security Optimization Design 13.4 Network Performance Optimization & Load-Balancing/Routing Design

14 Chapter 14: Final Review, Exam Strategy & Career Path

14.1 Cross-Domain Scenario Practice: Combining Identity, Data, Continuity & Infrastructure Decisions 14.2 Common AZ-305 Decision Traps 14.3 Final Study Plan & Practice Assessment Strategy 14.4 After AZ-305: Retake Policy, Renewal & Career Path

3.4 Authorization for On-Premises Resources

Key Takeaways Explain This Topic AI

Hybrid identity keeps one user object consistent across on-premises AD DS and Entra ID so authorization decisions stay correct in both environments.

Microsoft Entra Cloud Sync (cloud-managed, lightweight agents) is Microsoft's forward-looking direction as of 2026; Entra Connect Sync (on-premises engine) remains correct for complex multi-forest or advanced-feature needs, and the two can coexist during migration.

Password Hash Synchronization tolerates on-premises outages; Pass-through Authentication requires AD DS to be reachable at sign-in time; Federation (AD FS) is the highest-complexity option, used only when PHS/PTA cannot meet a specific requirement.

Microsoft Entra Domain Services gives a managed, LDAP/Kerberos/NTLM-compatible domain with one-way sync from Entra ID and no domain-controller patching, but no write-back and no forest trusts to on-premises.

Extending AD DS to Azure IaaS VMs gives full on-premises-equivalent control at the cost of owning domain-controller patching and high availability.

Last updated: July 2026

Why Hybrid Authorization Design Matters

Very few enterprises taking AZ-305 are cloud-only from day one. Most have an existing on-premises Active Directory Domain Services (AD DS) forest with years of accumulated groups, group policy, and application authorization logic. The exam's "authorizing access to on-premises resources" bullet tests whether you can design the synchronization and trust relationship that lets a single identity authenticate once and be authorized correctly both in the cloud and on-premises — without maintaining two separate, drifting sets of credentials.

Hybrid Identity: The Core Concept

Hybrid identity means a single user object is represented consistently in both on-premises AD DS and Microsoft Entra ID, synchronized so that a password change, a group membership change, or a disabled account propagates to both environments. This is the foundation that lets an on-premises AD DS group continue to drive file-share NTFS permissions while the same user also signs in to Azure-hosted apps through Entra ID with one identity and one credential.

Choosing a Synchronization Tool

Two Microsoft tools synchronize on-premises AD DS objects into Entra ID, and AZ-305 expects you to recommend the right one for the stated constraints:

Factor Microsoft Entra Connect Sync Microsoft Entra Cloud Sync

Sync engine location On-premises (installed on a domain-joined server, local SQL database) Cloud-managed; lightweight on-premises provisioning agents only

  • Password writeback Yes Supported for common scenarios, expanding over time
  • Device writeback / Exchange hybrid Yes Limited compared to Connect Sync

Multi-forest support Deep, granular OU/domain/attribute filtering Simplified filtering; good for most modern multi-forest cases but less granular

Best fit Complex, large, or legacy environments needing advanced attribute mapping Organizations simplifying, scaling out, or going cloud-first

Microsoft's 2026 direction Being phased out as the default for new deployments Actively invested in as the primary path forward; in April 2026, Microsoft announced a transition plan with tenant notifications beginning July 2026 for organizations whose needs Cloud Sync already meets

For an exam scenario describing a straightforward single-forest company wanting cloud-first simplicity, Cloud Sync is the forward-looking recommendation. For a scenario describing a complex multi-forest environment or one that explicitly needs device writeback or Exchange hybrid features not yet in Cloud Sync, Entra Connect Sync remains the correct choice — and the two can run side by side temporarily during a migration.

Authentication Methods for Hybrid Identity

Once objects are synchronized, three methods determine how the password itself is validated:

Password Hash Synchronization (PHS) — a hash of the password hash is synced to Entra ID; Entra ID validates sign-ins independently. Simplest, most resilient to on-premises outages.

Pass-through Authentication (PTA) — Entra ID forwards the sign-in to a lightweight on-premises agent that validates against AD DS directly, so the password never leaves the premises. Requires on-premises AD DS to be available at sign-in time.

Federation (AD FS) — a separate federation server issues tokens after validating against AD DS. Highest complexity and infrastructure burden; chosen only when a specific requirement (e.g., smart-card sign-in AD FS already supports) cannot be met by PHS or PTA.

Extending Authorization to the Cloud Without Deploying Domain Controllers

Some scenarios need a directory that behaves like on-premises AD DS (LDAP, Kerberos, NTLM) but hosted for cloud workloads, without an architect having to build and patch domain controllers. Two options:

Extend AD DS to Azure IaaS — deploy domain controllers as Azure virtual machines, joined to the existing forest. Full feature parity with on-premises AD DS, but the team owns patching, backup, and high availability of those VMs.

Microsoft Entra Domain Services — a fully managed domain, one-way synchronized from Entra ID, that provides LDAP/Kerberos/NTLM compatibility for legacy or lift-and-shift applications without deploying or patching any domain controllers. It supports a single flat OU structure and cannot write changes back to on-premises AD DS — the sync direction only flows Entra ID → Managed Domain.

Recognize the trade-off: option 1 gives full control at the cost of operational overhead; option 2 removes operational overhead at the cost of flexibility (no forest trusts to on-premises, one-way sync, simplified schema).

Exam Scenario

A company is lifting a legacy, on-premises line-of-business application to Azure VMs. The application authenticates users via Kerberos against AD DS and has no code path to call Entra ID directly, and the team wants to avoid deploying and patching new domain controllers. The correct recommendation is Microsoft Entra Domain Services : it exposes an LDAP/Kerberos/NTLM-compatible managed domain synchronized one-way from Entra ID, letting the legacy app authenticate exactly as it does today without any code change and without the team owning domain-controller infrastructure.

Common Traps

Recommending Entra Domain Services when the scenario needs write-back to on-premises AD DS or a multi-domain forest trust — Managed Domain sync is one-way and supports a flat structure only.

Choosing Federation (AD FS) by default for "extra security" — it is the highest-complexity option and should only be recommended when PHS or PTA cannot satisfy a specific stated requirement.

Assuming Cloud Sync and Entra Connect Sync are mutually exclusive forever — they can coexist during a deliberate migration.

Forgetting that Pass-through Authentication requires on-premises AD DS availability at sign-in time — an outage on-premises blocks sign-in, unlike PHS.