AADDS: consider excluding disabled objects from counting towards billing.
AADDS: consider excluding disabled objects from counting towards billing.
A lot of organizations maintain user objects indefinitly for compliance reasons. The ratio commonly is 1:50 or more between active:disabled user accounts. Billing based for ALL objects would prohibit the adoptation/use of AADDS. This is the same historical reason many 3rd party vendors of AD management tools didn't make their adoptation/sales targets. The same discussion also applies to service accounts.
Carl Nakamura
shared this idea
1 comment
-
Mike Stephens
commented
If the object is synced into Azure AD Domain Services, then it is counted toward the directory count. Disabled objects are still synced from Azure AD. But we understand the use case. You can use Group Scoped Synchronization to limit the number of objects synced into Azure AD Domain Services. You can read more about it here (https://docs.microsoft.com/en-us/azure/active-directory-domain-services/scoped-synchronization)
Mike Stephens
Senior Program Manager
Azure Identity
IAM Core | Domain Services