AZ-305 ยท Authentication and identity management
Reaching on-premises apps: application proxy, Private Access, Domain Services
Microsoft Entra application proxy and Microsoft Entra Private Access for on-premises apps, Microsoft Entra Domain Services for legacy Kerberos/LDAP apps in Azure.
Key points
- Microsoft Entra application proxy: publishes on-premises web apps externally; pre-authentication, Conditional Access, MFA.
- Private network connector: Windows server inside the network, outbound-only.
- SSO to Windows-auth apps: Kerberos constrained delegation.
- Private Access: replaces VPN for FQDN or IP resources; Global Secure Access client.
- Domain Services: managed domain (domain join, Group Policy, LDAP, Kerberos/NTLM), one-way sync.
Source: https://learn.microsoft.com/en-us/entra/identity/app-proxy/overview-what-is-app-proxy
Practice questions
Which component of Microsoft Entra application proxy runs on a server inside your own network?
- The application proxy service
- The private network connector
- The Global Secure Access client
- The Microsoft Entra provisioning service
Show answer
Answer: B. The private network connector
The private network connector is a lightweight agent on Windows Server inside your network that handles connections to the on-premises app. The application proxy service runs in the cloud as part of Microsoft Entra ID.
Which statements about Microsoft Entra Domain Services are true?
- It offers domain join, Group Policy, LDAP and Kerberos/NTLM
- Changes made in the managed domain sync back to Microsoft Entra ID
- It receives users and groups by one-way sync from Microsoft Entra ID
- You patch and monitor its domain controllers yourself
- The managed domain is standalone, not an extension of on-premises AD
Show answer
Answer: A. It offers domain join, Group Policy, LDAP and Kerberos/NTLM, C. It receives users and groups by one-way sync from Microsoft Entra ID, E. The managed domain is standalone, not an extension of on-premises AD
Domain Services provides domain join, Group Policy, LDAP and Kerberos/NTLM; it synchronizes one way from Microsoft Entra ID; and the managed domain is standalone, not an extension of an on-premises domain (forest trusts are optional). Changes do not flow back to Entra ID, and Microsoft, not you, patches and monitors the domain controllers.
To publish an internal web app with Microsoft Entra application proxy, you must open inbound port 443 on the corporate firewall to the connector server.
Show answer
Answer: False
False. The private network connector makes only outbound connections to the cloud service over ports 80 and 443, so no inbound firewall ports or perimeter network are needed. User traffic ends at the cloud service.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
