HAADJ is great for existing AD Joined PCs, but in some ways, it can perpetuate a backwards-facing ‘on-premises centric’ model and reduce (or complicate) some key benefits that the cloud offers.
Hybrid AAD Join (HAADJ) extends the existing AD model and registers AD joined PCs into AAD to allow for cloud capabilities such as device-based Conditional Access for Domain-Joined PCs.There are two major directions for this “join” question as we go into the future:
#News rover 22 registration key Pc
Organizations generally have a well-developed on-prem PC deployment/management solution that includes AD-Join as a cornerstone of that process.
“Should we do Hybrid Azure AD Join or Azure AD Join?” are all mainstream now.Īs I chat with enterprise customers in cloud strategy discussions, a few topics always come up once we get to the PC deployment and management aspects of that convo. Cloud services, SaaS, PaaS, anywhere/always-on connectivity, etc. Inbound Internet traffic was mostly remote users coming back into the corporate LAN – via VPN or modem (where are my Shiva LAN Rover fans?).Ī lot has changed. Outbound Internet access was used to look at wedding photos or research TechNet about recovering from an accidental AD deletion. Active Directory, GPOs and WINS were all the rage. When I worked in corporate IT - heck, when I started blogging out here - on-prem was really all there was. As we all know, the cloud paradigm shifts in IT continue.
0 kommentar(er)
