Hybrid AAD Join with non-routable UPNs on onpremise AD

%3CLINGO-SUB%20id%3D%22lingo-sub-1569294%22%20slang%3D%22en-US%22%3EHybrid%20AAD%20Join%20with%20non-routable%20UPNs%20on%20onpremise%20AD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1569294%22%20slang%3D%22en-US%22%3E%3CP%3E%3CFONT%3EDoes%20Hybrid%20AAD%20Join%20support%20non-routable%20UPNs%20on%20local%20AD%3F%20The%20issue%3A%20all%20requirements%20for%20hybrid%20AAS%20Join%20are%20met%20except%20of%20routable%20UPNs%20on%20on-prem%20AD%20(no%20SF).%20Effect%3A%20device%20state%20is%20changing%20to%20Hybrid%20but%20devices%20don%E2%80%99t%20enroll%20automatically%20to%20Intune%20MDM%20(GPO%20in%20place).%20Are%20routable%20UPNs%20required%20to%20enroll%20to%20MDM%3F%3C%2FFONT%3E%3C%2FP%3E%3CDIV%3E%3CFONT%3EAzureAdJoined%20%3A%20YES%3CBR%20%2F%3EEnterpriseJoined%20%3A%20NO%3CBR%20%2F%3EDomainJoined%20%3A%20YES%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%3EIsDeviceJoined%20%3A%20YES%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%3E%3CBR%20%2F%3EIsUserAzureAD%20%3A%20NO%3CBR%20%2F%3EPolicyEnabled%20%3A%20NO%3CBR%20%2F%3EPostLogonEnabled%20%3A%20YES%3CBR%20%2F%3EDeviceEligible%20%3A%20NO%3CBR%20%2F%3ESessionIsNotRemote%20%3A%20YES%3CBR%20%2F%3ECertEnrollment%20%3A%20none%3CBR%20%2F%3EPreReqResult%20%3A%20WillNotProvision%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F21544%22%20target%3D%22_blank%22%3E%40Michael%20Niehaus%3C%2FA%3E-%20any%20idea%20what's%20wrong%20with%20the%20enrollment%3F%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1569294%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMobile%20Device%20Management%20(MDM)%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1569772%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20AAD%20Join%20with%20non-routable%20UPNs%20on%20onpremise%20AD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1569772%22%20slang%3D%22en-US%22%3EIf%20the%20user%20is%20user%40onmicrosoft.xyz.com%2C%20the%20answer%2C%20You%20can%E2%80%99t%20enroll%20it%20with%20GPO%20because%20it%20needs%20CNAME%20record%20in%20your%20DNS%20registrar%20to%20redirects%20enrollment%20requests%20to%20Intune%20servers.%20Otherwise%2C%20users%20trying%20to%20connect%20to%20Intune%20must%20enter%20the%20Intune%20server%20name%20during%20enrollment.%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20this%20helps!%3CBR%20%2F%3EMoe%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmem%2Fintune%2Fenrollment%2Fwindows-enroll%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmem%2Fintune%2Fenrollment%2Fwindows-enroll%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1570336%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20AAD%20Join%20with%20non-routable%20UPNs%20on%20onpremise%20AD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1570336%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F503735%22%20target%3D%22_blank%22%3E%40Moe_Kinani%3C%2FA%3EHi%20Moe%2C%20thanks%20for%20reply.%3C%2FP%3E%3CP%3EThis%20requirement%20is%20met%2C%20domain%20on%20AAD%20is%20configured%20properly%20(all%20green).%20The%20user%20name%20on%20AAD%20includes%20the%20verified%20domain%20BUT%20on%20AD%20the%20UPN%20doesn't%20include%20a%20routable%20domain.%20The%20AD%20Connect%20synchronizes%20the%20identities.%20All%20this%20works%20well.%20Only%20MDM%20enrollment%20doesn't%20happen.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1570410%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20AAD%20Join%20with%20non-routable%20UPNs%20on%20onpremise%20AD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1570410%22%20slang%3D%22en-US%22%3EAs%20mentioned%2C%20this%20piece%20not%20going%20to%20work%20because%20the%20domain%20in%20not%20routable.%20Primary%20UPN%2F%20ProxyAddress%20attribute%20needs%20to%20match%20the%20verified%20domain%20so%20Intune%20can%20can%20validate%20the%20request.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20xyz.com%20is%20verified%20domain-%26gt%3BThe%20synced%20user%20needs%20to%20be%20user%40xyz.com%2C%20primary%20upn%20NOT%20alias.%3CBR%20%2F%3E%3CBR%20%2F%3EMoe%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1571477%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20AAD%20Join%20with%20non-routable%20UPNs%20on%20onpremise%20AD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1571477%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F503735%22%20target%3D%22_blank%22%3E%40Moe_Kinani%3C%2FA%3E%26nbsp%3Bi%20can%20confirm%20that%20the%20only%20solution%20is%20to%20change%20all%20the%20on%20prem%20AD%20UPN's%20to%20a%20routable%20domain.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1571589%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20AAD%20Join%20with%20non-routable%20UPNs%20on%20onpremise%20AD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1571589%22%20slang%3D%22en-US%22%3EThanks%2C%20Moe%2C%20for%20clarification.%20The%20docs%20are%20not%20clear%20enough%20-%20as%20devices%20are%20going%20to%20the%20hybrid%20state%20but%20MDM%20enrollment%20will%20not%20happen.%20Thanks%20again!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1571615%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20AAD%20Join%20with%20non-routable%20UPNs%20on%20onpremise%20AD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1571615%22%20slang%3D%22en-US%22%3EThanks%2C%20Th%20ms%20Vrhydn%2C%20when%20two%20guys%20are%20saying%20the%20same%20it%20must%20be%20truth!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1708470%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20AAD%20Join%20with%20non-routable%20UPNs%20on%20onpremise%20AD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1708470%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F160979%22%20target%3D%22_blank%22%3E%40Red%20Flag%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3EI%20know%20it%20is%20too%20late%20for%20your%20query%20(approx.%203%20months%20late)%2C%20but%20for%20future%20researchers%3A%3CBR%20%2F%3EIt%20is%20possible%20to%20achieve%20Hybrid%20Join%20with%20non-routable%20UPN%2C%20as%20long%20as%20you%20can%20deploy%20ADFS%20as%20your%20authentiation%20method.%3CBR%20%2F%3E%3CBR%20%2F%3ESource%20(look%20at%20the%20table%20on%20the%20end%20of%20this%20link)%3A%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevices%2Fhybrid-azuread-join-plan%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevices%2Fhybrid-azuread-join-plan%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3ERegards%2C%3CBR%20%2F%3ERodrigo%20Dias%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1708498%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20AAD%20Join%20with%20non-routable%20UPNs%20on%20onpremise%20AD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1708498%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F807487%22%20target%3D%22_blank%22%3E%40Rodrigo30Horas%3C%2FA%3E%20thanks%2C%20you'r%20right.%20However%20ADFS%20in%20my%20case%20is%20not%20on%20option.%20We%20try%20to%20simplify%20and%20modernize%20rather%20than%20go%20an%20opposite%20way%20-%20which%20ADFS%20would%20actually%20mean.%20Thanks%20for%20highlighting%20this%20method.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Does Hybrid AAD Join support non-routable UPNs on local AD? The issue: all requirements for hybrid AAS Join are met except of routable UPNs on on-prem AD (no SF). Effect: device state is changing to Hybrid but devices don’t enroll automatically to Intune MDM (GPO in place). Are routable UPNs required to enroll to MDM?

AzureAdJoined : YES
EnterpriseJoined : NO
DomainJoined : YES
IsDeviceJoined : YES

IsUserAzureAD : NO
PolicyEnabled : NO
PostLogonEnabled : YES
DeviceEligible : NO
SessionIsNotRemote : YES
CertEnrollment : none
PreReqResult : WillNotProvision
@Michael Niehaus- any idea what's wrong with the enrollment?
8 Replies
Highlighted
If the user is user@onmicrosoft.xyz.com, the answer, You can’t enroll it with GPO because it needs CNAME record in your DNS registrar to redirects enrollment requests to Intune servers. Otherwise, users trying to connect to Intune must enter the Intune server name during enrollment.

Hope this helps!
Moe

https://docs.microsoft.com/en-us/mem/intune/enrollment/windows-enroll
Highlighted

@Moe_KinaniHi Moe, thanks for reply.

This requirement is met, domain on AAD is configured properly (all green). The user name on AAD includes the verified domain BUT on AD the UPN doesn't include a routable domain. The AD Connect synchronizes the identities. All this works well. Only MDM enrollment doesn't happen.

Highlighted
As mentioned, this piece not going to work because the domain in not routable. Primary UPN/ ProxyAddress attribute needs to match the verified domain so Intune can can validate the request.

If xyz.com is verified domain->The synced user needs to be user@xyz.com, primary upn NOT alias.

Moe

@Moe_Kinani i can confirm that the only solution is to change all the on prem AD UPN's to a routable domain. 

Highlighted
Thanks, Moe, for clarification. The docs are not clear enough - as devices are going to the hybrid state but MDM enrollment will not happen. Thanks again!
Highlighted
Thanks, Th ms Vrhydn, when two guys are saying the same it must be truth!
Highlighted

@Red Flag 
I know it is too late for your query (approx. 3 months late), but for future researchers:
It is possible to achieve Hybrid Join with non-routable UPN, as long as you can deploy ADFS as your authentiation method.

Source (look at the table on the end of this link):  https://docs.microsoft.com/en-us/azure/active-directory/devices/hybrid-azuread-join-plan

Regards,
Rodrigo Dias

Highlighted

Hi @Rodrigo30Horas thanks, you'r right. However ADFS in my case is not on option. We try to simplify and modernize rather than go an opposite way - which ADFS would actually mean. Thanks for highlighting this method.