Managed Active Directory® (AD)

Managed Active Directory (AD)

With the advent of SaaS and managed services, a number of IT management tool categories are making the leap to be delivered as outsourced services. Data centers, applications, and file storage are some of the services that have taken advantage of the SaaS model. One of the last categories to make the transition to the cloud has been identity management / directory services. With all of the benefits of moving to the cloud, including lower upfront costs and maintenance, IT admins are wondering whether a managed Active Directory® solution is available to them.

But is a managed Active Directory solution really what IT is looking for? To answer that question we need to take a look at Active Directory’s start and how AD works.

Active Directory’s Launch in IAM Market

The Journey behind Managed Active Directory

The identity management space has been long dominated by Active Directory (AD). Introduced in 1999, Microsoft leveraged their dominance with Windows devices and applications to achieve dominance in enterprise-grade user and system management. Windows systems had already started appearing on every employee’s desk and those systems, along with their access to applications and networks, needed to be managed. When Active Directory was released, for a period of time IT admins had the user and system management they wanted.

Not only have IT resources dramatically changed in the last two decades, but how IT wants to manage those resources has also evolved. Today, the Microsoft ecosystem is just one drop in an ocean of well developed system platforms, web-based applications, cloud resources, and file storage. Additionally, IT doesn’t want to have to deal with the costs and time it takes to manage Active Directory hardware. So is a managed Active Directory even feasible?

Breaking Down the Idea of a Managed Active Directory

The Idea of a Managed Active Directory

Well in the past, the way Active Directory worked was an organization would have AD located on-prem, and an internal IT team was responsible for managing the identity provider. AD worked on a direct connect model, so any IT resources needed to be close to the AD server. This meant that hosting AD at a third party location (Read more...)

*** This is a Security Bloggers Network syndicated blog from JumpCloud authored by Natalie Bluhm. Read the original post at:

Natalie Bluhm

Natalie is a writer for JumpCloud, an Identity and Access Management solution designed for the cloud era. Natalie graduated with a degree in professional and technical writing, and she loves learning about cloud infrastructure, identity security, and IT protocols.

natalie-bluhm has 149 posts and counting.See all posts by natalie-bluhm