Is Azure AD Multi-Tenant?

Is Azure AD Fit for Multi-Tenant purposes (pic of lollipops)

The Microsoft® cloud platform, Azure®, has steadily been growing in popularity over the past few years. As more companies adopt the Microsoft cloud, including the client organizations of managed service providers (MSPs), there are several considerations on the minds of MSP admins and technicians regarding user management in Azure Active Directory (AD). For MSPs, namely, is Azure AD multi-tenant?

Multi-Tenancy and Azure AD

Azure, in and of itself, is a multi-tenant platform, as is the underlying infrastructure of Azure AD. This multi-tenancy means that Microsoft is using the same infrastructure across their multiple clients. What it doesn’t mean, however, is that an MSP can manage multiple clients via their account in the web console.

Replace AD with JumpCloud

The result is that Azure Active Directory is not multi-tenant in the traditional sense of the word. Multi-tenancy implies the ability to manage multiple, different disparate uses of a software, called tenants, from a single instance. From Microsoft’s perspective, Azure is multi-tenant, but not from the perspective of an MSP, where they would need to manage individual accounts for their individual customers.

User Management for MSPs in Azure

MSP Multi Tenant AzureBy the very nature of their services, MSPs are concerned with managing multiple organizations simultaneously. The ideal MSP user management solution offers an identity management functionality that is leverageable from one pane of glass. That way, instead of having to log out and relog into multiple different instance of the same solution, the enterprising MSP can do so instantly, anytime, anywhere. MSPs with multiple clients in the Azure platform are struggling with how to manage them centrally.

The multi-tenant experience that MSPs are looking for is to have one user interface that consolidates all of their customers, enabling easy, efficient remote management. In an industry that feeds on effective, speedy service, the hassle of switching back and forth between individualized Azure AD instances can be overwhelming. Unlike Azure AD, this ideal solution should be one that is also flexible, allowing MSPs the same freedom of choice for solutions that their clients take advantage of regarding their systems, applications, networks, and more rather than being tied (Read more...)

*** This is a Security Bloggers Network syndicated blog from Blog – JumpCloud authored by Zach DeMeyer. Read the original post at:

Zach DeMeyer

Zach DeMeyer

Zach is a writer and researcher for JumpCloud with a degree in Mechanical Engineering from the Colorado School of Mines. He loves being on the cutting edge of new technology, and when he's not working, he enjoys all things outdoors, making music, and soccer.

zach-demeyer has 223 posts and counting.See all posts by zach-demeyer