Pass-through Authentication (PTA)
๐ What is Pass-through Authentication (PTA)?
Pass-through Authentication (PTA) is a method of authenticating users in Azure Active Directory (Azure AD) where the authentication process happens on-premises instead of in the cloud.
With PTA, users login to Azure AD, but instead of Azure validating their credentials directly, the request is passed through to your on-premises Active Directory (AD) for validation.
๐ง How Does Pass-through Authentication Work?
A user tries to log in to a cloud application (e.g., Office 365).
Azure AD passes the authentication request to the on-prem AD via a secure agent.
The on-prem AD validates the credentials.
If valid, a token is sent back to Azure AD, and the user gains access.
This means Azure AD doesn’t store or validate the actual passwords; it's simply a proxy for passing the authentication request.
๐งฐ Key Features of PTA:
Feature | Description |
---|---|
On-Prem Authentication | Passwords are authenticated by the on-premises AD, not in the cloud. |
No Password Syncing | Passwords are not stored in Azure AD, so there's no risk of cloud storage of plain-text passwords. |
Single Sign-On (SSO) | Provides SSO to cloud apps using the same credentials as your on-premises AD. |
High Security | No need to sync password hashes to the cloud; users’ passwords are verified on-premises. |
Requires Azure AD Connect | You need Azure AD Connect to set up PTA and the necessary agents on-premises. |
๐ ️ How to Set It Up:
Install the Azure AD Connect Tool on your on-prem server.
Choose the Pass-through Authentication option during the setup process.
Install the PTA agents on one or more on-prem servers.
Configure your Azure AD Connect to sync and pass requests between your on-premises AD and Azure AD.
Users can now log in to cloud apps using their on-prem credentials.
๐ PTA vs. Password Hash Synchronization (PHS)
Feature | Pass-through Authentication (PTA) | Password Hash Synchronization (PHS) |
---|---|---|
Authentication Location | On-premises (via Azure AD Connect) | Azure AD Cloud (using password hash) |
Cloud Storage of Password | No password stored in the cloud | Password hashes are stored in the cloud |
Need for On-Prem Server | Yes (PTA agents required) | No (only requires Azure AD Connect) |
Backup Authentication | Works as long as the on-prem server is available | Works even if the on-prem server is down (as passwords are cached in Azure AD) |
User Experience (SSO) | Yes, SSO for cloud apps | Yes, SSO for cloud apps |
Best For | Organizations with strict password control or those with existing on-prem systems | Simpler for cloud-first environments or those preferring a cloud-based approach |
✅ Benefits of PTA:
No need for password synchronization.
Better control over on-premises credentials (since they never leave your on-prem AD).
Single sign-on (SSO) experience for users, without needing to manage separate credentials for cloud services.
Allows for hybrid authentication for organizations still dependent on on-prem AD.
๐จ Considerations:
Dependency on on-prem server availability: If your PTA agent or on-prem AD is down, users can't authenticate to cloud apps.
Requires more infrastructure (agents) compared to Password Hash Sync.
Not as resilient as Password Hash Sync (in case of on-prem failures).
๐งช Real-Life Scenario:
A company with a highly secure on-premises Active Directory setup prefers to keep password validation on-prem for added security and compliance, but also wants its users to access cloud-based Microsoft 365 apps without needing separate credentials. They set up Pass-through Authentication.