{"id":61014,"date":"2023-01-03T11:38:37","date_gmt":"2023-01-03T03:38:37","guid":{"rendered":"https:\/\/version-2.com\/?p=61014"},"modified":"2023-01-06T11:42:05","modified_gmt":"2023-01-06T03:42:05","slug":"total-cost-of-ownership-of-azure-ad","status":"publish","type":"post","link":"https:\/\/version-2.com\/zh\/2023\/01\/total-cost-of-ownership-of-azure-ad\/","title":{"rendered":"Total Cost of Ownership of Azure AD"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Editor\u2019s Note: Given the fast-paced nature of technology, it is possible that some of the information presented in this article is out-of-date, or incomplete, in some fashion. The author periodically reviews and revises this article to ensure information contained within is as accurate as possible.<\/em><\/p>

Microsoft\u00ae<\/sup> Azure\u00ae<\/sup> is an umbrella for a variety of cloud services, including Azure Active Directory (AAD). On its face, Azure AD might seem like a replacement<\/a> for on-prem Active Directory (AD) or a cloud-based solution for organizations in need of a directory service, but more factors come into play for IT admins making purchasing decisions, including complicated SKUs and licensing. This article examines the total cost of ownership (TCO) of AAD for the type of configuration that a small and medium-sized enterprise (SME) would require for its identity management lifecycle.

AAD was created to extend on-prem AD identities to Azure in order to provide user management for Microsoft Office applications, and now single sign-on (SSO) for service providers (SP). It\u2019s available as a standalone product, but is also bundled with Microsoft 365 (M365) subscriptions. Microsoft has positioned AAD as the connective tissue within a broader identity and access management (IAM) ecosystem. That extends from users and devices to its security portfolio. Add-ons and integrations are almost inescapable, because AAD is very interwoven with those products. It\u2019s not even possible to implement Microsoft\u2019s best practices for AAD<\/a> without paying more.<\/p>

A Codependent Approach<\/h2>

Significantly, Microsoft manages endpoints separately from identities even though experts recommend making identity the new perimeter<\/a> in cybersecurity. Device management (outside of AD) is only bundled with some of its premium M365 SKUs, but not AAD. Organizations that aren\u2019t using M365 will have to purchase a separate subscription to manage their devices.<\/p>

Microsoft\u2019s reference architecture suggests an array of Microsoft-based tools to fully leverage AAD, so even Microsoft-heavy IT shops will encounter more IT infrastructure and maintenance costs. You\u2019ll have limited administrative capabilities if you use AAD without on-prem AD, or aren\u2019t subscribed to premium tiers and add-on services. For example, you won\u2019t be able to employ the suite of group policy objects (GPOs) to on-prem Windows devices, and you\u2019ll struggle with authenticating local IT resources such as applications and file servers.\u00a0<\/p>

AAD is also not an open directory, so working with external identities from other identity providers (IP) and connecting users to IT resources (RADIUS, LDAP) requires even more solutions. Some are cloud-based, but others expand its footprint on-premise, and are reliant on AD.<\/p>

Costs of Azure Active Directory<\/h2>

To fully assess the TCO of Azure AD, it\u2019s necessary to account for tangential, but necessary, costs. Fortunately, we\u2019ve developed an equation to help you understand the TCO of AAD:<\/p>

Costs of Azure Active Directory = Azure AD Premium Package + Add-Ons for device management + External Identities + Azure AD DS + Active Directory<\/a> + LDAP Server + RADIUS Server + Integration\/Management Time for your implements<\/p><\/blockquote>

Let\u2019s begin by assessing AAD\u2019s pricing and then branch outward to the other components.<\/p>

Standalone Azure AD and M365<\/h3>

Standalone AAD has three SKUs:<\/p>