@DebugPrivilege
DebugPrivilege
3 years
Ok, wow! - "This first post in the series was designed to inform you that SSO is possible, to domain resources, from an Azure AD joined device WITHOUT requiring Hybrid Azure AD Join."
7
81
250

Replies

@NathanMcNulty
Nathan McNulty
3 years
@DebugPrivilege HAAJD adds so much unnecessary complexity in most cases I really wish folks understood when it is actually needed and when it isn't :(
2
0
7
@DebugPrivilege
DebugPrivilege
3 years
@NathanMcNulty It can be confusing though. šŸ˜¬
1
0
5
@kaidja
Kaido JƤrvemets
3 years
@DebugPrivilege Why are we focusing so much on the domain-joined state? Your identity is still coming from on-premises AD and much more. We should look bigger picture and not only stuck with the domain-joined state.
2
0
4
@DebugPrivilege
DebugPrivilege
3 years
@kaidja Agreed.
0
0
2
@SteveSyfuhs
Steve Syfuhs
3 years
@DebugPrivilege Definitely one of my favorite features
1
0
6
@SSLWorldwide
SMS
3 years
@DebugPrivilege I blogged about this just yesterday. MFAs or SSOs can be extended to ANY resources on the hybrid IT infrastructures,
0
0
1
@MEM_MVP
John Marcum
3 years
@DebugPrivilege ā€œthe main reason customers are considering Hybrid Azure AD joined devices is if an application requires machine authentication in Active Directory.ā€ā€¦..itā€™s more likely they donā€™t know if they have apps that need this and they are too lazy to figure it out.
2
0
4
@Mister_MDM
Rudy Ooms | MVP šŸ‡³šŸ‡±
3 years
@DebugPrivilege Great blog indeed, Its indeed something most forgottenā€¦i try to explain it how and why to as much people as possibleā€¦ My deliver us from hybrid blog tells you exactly what the title tells :)
0
0
3
@SencerDMR
SnCr
3 years
0
0
0