{"id":45847,"date":"2020-04-20T11:10:59","date_gmt":"2020-04-20T17:10:59","guid":{"rendered":"https:\/\/jumpcloud.com\/?post_type=resource&p=45847"},"modified":"2022-10-20T18:21:23","modified_gmt":"2022-10-20T22:21:23","slug":"domainless-enterprise-roadmap","status":"publish","type":"resource","link":"https:\/\/jumpcloud.com\/resources\/domainless-enterprise-roadmap","title":{"rendered":"Roadmap to the Domainless Enterprise"},"content":{"rendered":"\n
Most IT organizations use Active Directory\u00ae<\/sup>, and they\u2019ve navigated seismic technological developments with it. As new technologies have emerged and cloud services have boomed, IT admins have augmented their AD instances with new add-ons and identity bridges to incorporate each new resource and centrally authenticate users to it.<\/p>\n\n\n\n What this means in practice is that the total cost of ownership of AD is much higher than its up front server and licensing costs, though. The TCO increases with each new add-on and identity bridge. As admins now must navigate a swift transition out of their offices, they need additional add-ons to accommodate and secure users working remotely.<\/p>\n\n\n\n Active Directory enables admins to establish an internal network \u2014 the domain \u2014 to secure on-premises resources and data. However, admins now need new and more efficient ways to expand the domain to users, devices, and resources located outside the traditional office.<\/p>\n\n\n\n An emerging cloud-based architecture integrates with AD to securely extend AD identities to virtually all resources beyond the traditional domain and centrally authenticate users and systems. This architecture can also serve as a stepping stone toward the domainless enterprise<\/em><\/a>. In the domainless enterprise model, admins\u2019 operations are as seamless off-premises as they are on, and users and devices are secured entirely from the cloud.<\/p>\n\n\n\n Armed with this innovative cloud directory architecture, organizations can realize faster time to market, reduce labor-intensive deployment, and achieve flexibility and fluidity in responding to external pressures and market forces.<\/p>\n\n\n\n Organizations primed for use of this architecture include those with: <\/p>\n\n\n\n You can take the following steps now to implement this architecture, ease your transition to remote work, and position your organization for a more significant IT transformation in the future \u2014 without disrupting your current directory environment.<\/p>\n\n\n\n First, we\u2019ll run through the steps an organization can take to move toward the domainless enterprise model, and then we\u2019ll cover considerations for selecting the right cloud directory service provider, training end users for secure mobile work, and preparing for the future. <\/p>\n\n\n\n With AD in place, you might use largely Windows\u00ae<\/sup> systems, Azure\u00ae<\/sup> or AWS\u00ae<\/sup> for cloud infrastructure, and Office 365TM<\/sup> as your productivity suite. You might combine these solutions with a vendor to enable web application single sign-on (SSO)<\/a>, other vendors to manage a smattering of Mac and Linux systems, and a VPN solution to connect users to the internal network when they work remotely.<\/p>\n\n\n\n Although this approach works, you might find there are more economical and cloud-forward ways to do so. These questions can help you assess your existing stack:<\/p>\n\n\n\nDomainless Enterprise Model: Step By Step<\/h2>\n\n\n\n
1. Take Stock of Your Existing Environment <\/h3>\n\n\n\n