{"id":18276,"date":"2026-10-03T06:41:25","date_gmt":"2026-10-03T06:41:25","guid":{"rendered":"https:\/\/www.exam-labs.com\/blog\/?p=18276"},"modified":"2026-10-13T09:14:56","modified_gmt":"2026-10-13T09:14:56","slug":"microsoft-entra-users-groups-and-administrative-units","status":"publish","type":"post","link":"https:\/\/www.exam-labs.com\/blog\/microsoft-entra-users-groups-and-administrative-units","title":{"rendered":"Microsoft AZ-104: Microsoft Entra Users, Groups, and Administrative Units"},"content":{"rendered":"<p>A Microsoft Entra tenant can contain thousands of users, groups, devices, applications, and administrators. The difficult part is not creating those objects. It is understanding what each object changes and, just as importantly, what it does not change. A user object gives the directory an identity to authenticate and manage. A group lets administrators treat multiple identities as a set. An administrative unit narrows the scope of certain directory-management roles. Those mechanisms interact, but they are not interchangeable.<\/p>\n<p>Delegating Entra administration in <a href=\"https:\/\/www.exam-labs.com\/dumps\/AZ-104\">AZ-104<\/a> requires separating directory identity, group membership, resource authorization, and administrative scope. A convenient-looking group or role assignment must not accidentally delegate control over an entire tenant.<\/p>\n<h3>Users are identities, but the user object is only one part of access<\/h3>\n<p>A <a href=\"https:\/\/www.exam-labs.com\/blog\/the-transition-to-microsoft-entra-id-a-new-era-beyond-azure-active-directory\">Microsoft Entra<\/a> user object represents a person or, in some cases, an account used for a specific administrative or operational purpose. The object carries properties such as sign-in identity, group memberships, authentication methods, licensing relationships, and directory attributes. Those properties become inputs to other systems, but the existence of the user alone does not grant access to every Azure resource.<\/p>\n<p>Azure resource access is commonly granted through role assignments, application access can be granted through enterprise-application configuration or groups, and conditional access can apply separate sign-in requirements. The user object is therefore the identity anchor rather than a universal permission list.<\/p>\n<p><a href=\"https:\/\/www.exam-labs.com\/blog\/foundations-of-identity-and-access-management-with-microsoft-entra-id-sc-300\">Microsoft Entra identity and access management<\/a> separates directory accounts from the permissions and sign-in controls applied by connected services. Disabling, deleting, restoring, or changing a user can affect every application and resource that trusts that identity.<\/p>\n<h3>Groups are a scaling mechanism for membership and authorization<\/h3>\n<p>Groups let administrators assign access or configuration to a collection instead of managing every user individually. That is valuable because individual role assignments are hard to review and easy to leave behind when people change jobs. A well-named group can represent a business role, project team, licensing population, application-access set, or administrative function.<\/p>\n<p>The design still needs discipline. Nested groups, dynamic membership, synchronized on-premises groups, and application-specific groups can make effective access difficult to understand. A user may receive permission through several paths, and removing one assignment may not remove the access if another group still grants it.<\/p>\n<p>Group ownership is also a control. If business owners can add members, the organization should know what access that membership implies. If IT is the only owner, the group may become operationally stale because the people closest to the business change cannot maintain it. Periodic membership review is therefore as important as initial creation.<\/p>\n<h3>Administrative units scope administration, not ordinary resource access<\/h3>\n<p>Administrative units solve a different problem. They allow an organization to scope supported Microsoft Entra directory roles to a defined portion of the directory. A global company can, for example, delegate user administration for one region without giving the regional help desk the same role over the entire tenant.<\/p>\n<p>The subtle point is that an administrative unit is not simply another security group. It is a container used to scope management. Microsoft currently allows administrative units to contain users, groups, or devices. If a group is added to an administrative unit, the group object falls within that administrative scope, but the group\u2019s members do not automatically become members of the administrative unit. If administrators must manage the individual users as well, those users need to be in the appropriate administrative scope.<\/p>\n<p>This distinction prevents a common design error: using group membership to imply an administrative-unit boundary that the platform does not actually create.<\/p>\n<h3>Administrative scope is not the same as an isolation boundary<\/h3>\n<p>Another common mistake is assuming that a scoped directory administrator cannot see anything outside the administrative unit. Administrative units primarily restrict the reach of supported role permissions. They do not automatically turn the rest of the tenant invisible, and they do not replace resource-level authorization for Azure subscriptions, applications, or data.<\/p>\n<p>That means a regional help-desk administrator might be permitted to reset passwords for users inside the unit while still being able to browse some directory information outside it through normal user capabilities. If the organization requires stronger separation for especially sensitive identities, the design should evaluate the platform\u2019s restricted-management options and other compensating controls rather than assuming a normal administrative unit provides complete isolation.<\/p>\n<p>The correct question is always: which operation is being delegated, over which object, through which role, and at what scope?<\/p>\n<h3>Directory roles and Azure RBAC belong to different authorization planes<\/h3>\n<p>Microsoft Entra directory roles govern directory and identity administration. Azure role-based access control governs actions on Azure resources such as subscriptions, resource groups, virtual machines, storage accounts, and other Resource Manager resources. A person can have broad rights in one plane and limited rights in the other.<\/p>\n<p>This is why a User Administrator does not automatically become an Azure subscription Owner, and an Azure Contributor does not automatically gain permission to reset users\u2019 authentication methods. The two systems can use the same identity while authorizing different operations.<\/p>\n<p><a href=\"https:\/\/www.exam-labs.com\/blog\/mastering-access-control-in-azure-the-fundamental-role-of-role-based-access-control-rbac\">Azure role-based access control<\/a> provides the resource side of that distinction. Candidates moving deeper into identity administration may also encounter <a href=\"https:\/\/www.exam-labs.com\/dumps\/SC-300\">SC-300<\/a>, where Microsoft Entra identity and access responsibilities are central.<\/p>\n<h3>Dynamic membership reduces manual work but increases rule dependency<\/h3>\n<p>Dynamic groups and dynamic administrative-unit membership can reduce repetitive administration when membership can be derived from reliable attributes. A region, department, device property, or other directory attribute can drive membership without requiring a help-desk ticket for every change.<\/p>\n<p>The trade-off is that the rule becomes a security dependency. If source attributes are inaccurate, delayed, or inconsistently populated, authorization can drift. A user transferred between departments may retain old access until attributes and group evaluation catch up. A badly written rule can expand membership far beyond the intended population.<\/p>\n<p>Teams should therefore treat dynamic rules like production logic: document the source attributes, test edge cases, monitor unexpected membership changes, and understand how quickly membership recalculates after a source change.<\/p>\n<h3>Group-based licensing is an access workflow, not a directory-role assignment<\/h3>\n<p>Group-based licensing can assign supported Microsoft cloud licenses to members of an authorized group instead of managing each user&#8217;s entitlement one by one. Microsoft currently manages those assignments in the Microsoft 365 admin center, not through the older Entra licensing screens that some legacy tutorials still describe. The operator needs an appropriate licensing or group administration role, available subscribed licenses, and valid user usage-location information. A licensed group is not the same thing as an Azure RBAC group: membership that confers a product subscription does not automatically grant rights to manage a resource group.<\/p>\n<p>Group nesting is an important limitation. Microsoft&#8217;s current group-based licensing guidance does not support applying license assignments through nested group membership; membership must be checked against the licensed group itself. When a license assignment fails, inspect available seats, disabled service plans, overlapping direct\/group entitlements, usage location, and reported processing errors before expanding privileges or moving users between groups.<\/p>\n<h3>Inviting external users is not the same as giving them resource access<\/h3>\n<p>For workforce B2B collaboration, an authorized Entra administrator can invite an external user into the directory. An invitation creates a guest-type user object, but the person still needs to redeem the invitation and receive the intended group, application, or resource authorization. A visible guest user is not proof that a third party can sign in successfully, and completed sign-in is not permission to manage subscriptions. Apply tenant collaboration restrictions and the least-privileged group\/application assignments required for the project.<\/p>\n<p>A useful verification records the guest&#8217;s invitation state, accepted identity, governing tenant restrictions, membership, app permission, expiration review, and offboarding owner. Removing a guest from a project group may not delete its directory identity, and deleting an application permission may not remove other access paths. Identity lifecycle work should distinguish these effects before access is declared revoked.<\/p>\n<h3>Self-service password reset requires a supported authentication-method policy<\/h3>\n<p>Self-service password reset (SSPR) is a controlled recovery workflow. Microsoft documents enabling it for selected or all eligible users, choosing allowed methods, requiring the configured number of verifications, and establishing user registration. The combined security-information experience lets users register methods that can serve both multifactor authentication and password recovery where supported. Administrators must review feature licensing, registered methods, affected groups and emergency recovery procedures before promising that every account can reset a password unattended.<\/p>\n<p>Microsoft ended management of authentication methods through the legacy SSPR\/MFA policies on September 30, 2025, directing administrators toward the Authentication methods policy. A modern runbook should therefore validate that the supported method policy, SSPR scope and registration settings agree. Test with an approved nonproduction identity, document what happens when methods are missing, and ensure the help desk has a safe identity-proofing and escalation path without bypassing the intended controls.<\/p>\n<h3>Lifecycle events are where identity designs prove themselves<\/h3>\n<p>Joiner, mover, and leaver events expose whether users, groups, and administrative scope are designed coherently. A new employee should receive only the memberships required for the role. A transfer should remove obsolete access instead of merely adding new groups. A departure should disable sign-in, revoke relevant sessions, transfer ownership where needed, and remove access through groups and resource roles.<\/p>\n<p>Group-based access helps when group membership is authoritative and reviewed. Administrative units help when delegated administrators need a constrained management area. Neither replaces a lifecycle process. If the source system does not signal changes reliably, stale access accumulates regardless of how clean the directory structure looks.<\/p>\n<p>The organization should be able to answer who owns each important group, why a member belongs, who can change membership, and how quickly departures propagate to downstream applications and Azure resources.<\/p>\n<h3>A regional help-desk scenario exposes the differences quickly<\/h3>\n<p>Imagine a company with support teams in North America, Europe, and Asia. The European help desk should reset passwords and manage selected group memberships for European employees, but it should not have the same directory authority over executives or staff in other regions. A normal Microsoft Entra group can collect the European employees, but group membership alone does not scope a directory role. An administrative unit can provide that management scope when the supported role and objects fit the scenario.<\/p>\n<p>The design becomes more subtle if the administrative unit contains a group. The regional administrator may be able to manage that group object and its membership, yet that does not automatically grant the administrator user-management rights over every person inside the group. If password reset or authentication-method management is required for those users, the users themselves need to fall within the appropriate administrative scope. This is a small platform detail with a large operational consequence.<\/p>\n<p>Now add an Azure subscription used by the same regional team. The administrative unit still does not grant management rights to virtual machines or storage accounts. Those permissions belong to Azure RBAC. The same person might therefore have a scoped directory role over European users and a separate Azure role over a resource group. Keeping those assignments separate makes both least privilege and investigation easier.<\/p>\n<p>Licensing and feature support can also constrain the design, so administrators should verify requirements before standardizing on administrative units as the delegation model. Architecture should be based on supported behavior, not merely on the visual similarity between a group and a directory container.<\/p>\n<h3>Design the directory so effective access can be explained<\/h3>\n<p>A strong directory design is understandable under investigation. Administrators should be able to trace why a user can perform an action: direct assignment, group membership, directory role, Azure role assignment, application role, or another explicit path. Administrative units should make delegated responsibilities narrower, not make the model harder to reason about.<\/p>\n<p>Within the <a href=\"https:\/\/www.exam-labs.com\/certification\/Microsoft-Certified-Azure-Administrator-Associate\">Microsoft Certified: Azure Administrator Associate<\/a> path, Entra users and groups are not introductory trivia. They are the identities and collections on which Azure administration depends. Administrative units add a second dimension\u2014who may administer which directory objects. Keeping identity, membership, resource authorization, and administrative scope separate in the mental model makes the platform\u2019s behavior much easier to predict.<\/p>\n<p>Object naming and documentation also affect operational clarity. A group called \u201cProject-Blue-Users\u201d tells a reviewer less than a group name that indicates the application, permission level, environment, and owning team. Administrative units should likewise reflect a delegation model people can recognize. Clean naming does not create security by itself, but it reduces the chance that administrators add members to the wrong collection or retain obsolete structures because nobody understands what they were for. In a large tenant, understandable structure is a control against administrative error.<\/p>\n","protected":false},"excerpt":{"rendered":"<p class=\"post__text\">A Microsoft Entra tenant can contain thousands of users, groups, devices, applications, and administrators. The difficult part is not creating those objects. It is understanding what each object changes and, just as importantly, what it does not change. A user object gives the directory an identity to authenticate and manage. A group lets administrators treat [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1045],"tags":[],"class_list":["post-18276","post","type-post","status-publish","format-standard","hentry","category-microsoft"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"A Microsoft Entra tenant can contain thousands of users, groups, devices, applications, and administrators. The difficult part is not creating those objects. It is understanding what each object changes and, just as importantly, what it does not change. A user object gives the directory an identity to authenticate and manage. A group lets administrators treat\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Allen Rodriguez\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/www.exam-labs.com\/blog\/microsoft-entra-users-groups-and-administrative-units\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\n\t\t<meta property=\"og:site_name\" content=\"Exam-Labs - Pass Your Certification Exam Easily\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"Microsoft AZ-104: Microsoft Entra Users, Groups, and Administrative Units - Exam-Labs\" \/>\n\t\t<meta property=\"og:description\" content=\"A Microsoft Entra tenant can contain thousands of users, groups, devices, applications, and administrators. The difficult part is not creating those objects. It is understanding what each object changes and, just as importantly, what it does not change. A user object gives the directory an identity to authenticate and manage. A group lets administrators treat\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/www.exam-labs.com\/blog\/microsoft-entra-users-groups-and-administrative-units\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2026-10-03T06:41:25+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2026-10-13T09:14:56+00:00\" \/>\n\t\t<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n\t\t<meta name=\"twitter:title\" content=\"Microsoft AZ-104: Microsoft Entra Users, Groups, and Administrative Units - Exam-Labs\" \/>\n\t\t<meta name=\"twitter:description\" content=\"A Microsoft Entra tenant can contain thousands of users, groups, devices, applications, and administrators. The difficult part is not creating those objects. It is understanding what each object changes and, just as importantly, what it does not change. A user object gives the directory an identity to authenticate and manage. A group lets administrators treat\" \/>\n\t\t<script type=\"application\/ld+json\" class=\"aioseo-schema\">\n\t\t\t{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"BlogPosting\",\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/microsoft-entra-users-groups-and-administrative-units#blogposting\",\"name\":\"Microsoft AZ-104: Microsoft Entra Users, Groups, and Administrative Units - Exam-Labs\",\"headline\":\"Microsoft AZ-104: Microsoft Entra Users, Groups, and Administrative Units\",\"author\":{\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/author\\\/admin#author\"},\"publisher\":{\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/#organization\"},\"datePublished\":\"2026-10-03T06:41:25+00:00\",\"dateModified\":\"2026-10-13T09:14:56+00:00\",\"inLanguage\":\"en-US\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/microsoft-entra-users-groups-and-administrative-units#webpage\"},\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/microsoft-entra-users-groups-and-administrative-units#webpage\"},\"articleSection\":\"Microsoft\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/microsoft-entra-users-groups-and-administrative-units#breadcrumblist\",\"itemListElement\":[{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/#listItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/category\\\/certifications#listItem\",\"name\":\"Certifications\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/category\\\/certifications#listItem\",\"position\":2,\"name\":\"Certifications\",\"item\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/category\\\/certifications\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/category\\\/certifications\\\/microsoft#listItem\",\"name\":\"Microsoft\"},\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/#listItem\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/category\\\/certifications\\\/microsoft#listItem\",\"position\":3,\"name\":\"Microsoft\",\"item\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/category\\\/certifications\\\/microsoft\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/microsoft-entra-users-groups-and-administrative-units#listItem\",\"name\":\"Microsoft AZ-104: Microsoft Entra Users, Groups, and Administrative Units\"},\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/category\\\/certifications#listItem\",\"name\":\"Certifications\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/microsoft-entra-users-groups-and-administrative-units#listItem\",\"position\":4,\"name\":\"Microsoft AZ-104: Microsoft Entra Users, Groups, and Administrative Units\",\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/category\\\/certifications\\\/microsoft#listItem\",\"name\":\"Microsoft\"}}]},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/#organization\",\"name\":\"Exam Labs Blog - IT Certifications in Easy Way\",\"description\":\"Pass Your Certification Exam Easily\",\"url\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/author\\\/admin#author\",\"url\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/author\\\/admin\",\"name\":\"Allen Rodriguez\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/microsoft-entra-users-groups-and-administrative-units#authorImage\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/c3fe64bebd9f43850f9d0596b6003fdf570626ed3ea459dd1696b69cc880ef83?s=96&d=mm&r=g\",\"width\":96,\"height\":96,\"caption\":\"Allen Rodriguez\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/microsoft-entra-users-groups-and-administrative-units#webpage\",\"url\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/microsoft-entra-users-groups-and-administrative-units\",\"name\":\"Microsoft AZ-104: Microsoft Entra Users, Groups, and Administrative Units - Exam-Labs\",\"description\":\"A Microsoft Entra tenant can contain thousands of users, groups, devices, applications, and administrators. The difficult part is not creating those objects. It is understanding what each object changes and, just as importantly, what it does not change. A user object gives the directory an identity to authenticate and manage. A group lets administrators treat\",\"inLanguage\":\"en-US\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/#website\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/microsoft-entra-users-groups-and-administrative-units#breadcrumblist\"},\"author\":{\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/author\\\/admin#author\"},\"creator\":{\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/author\\\/admin#author\"},\"datePublished\":\"2026-10-03T06:41:25+00:00\",\"dateModified\":\"2026-10-13T09:14:56+00:00\"},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/\",\"name\":\"Exam Labs Blog - IT Certifications in Easy Way\",\"description\":\"Pass Your Certification Exam Easily\",\"inLanguage\":\"en-US\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.exam-labs.com\\\/blog\\\/#organization\"}}]}\n\t\t<\/script>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"Microsoft AZ-104: Microsoft Entra Users, Groups, and Administrative Units - Exam-Labs","description":"A Microsoft Entra tenant can contain thousands of users, groups, devices, applications, and administrators. The difficult part is not creating those objects. It is understanding what each object changes and, just as importantly, what it does not change. A user object gives the directory an identity to authenticate and manage. A group lets administrators treat","canonical_url":"https:\/\/www.exam-labs.com\/blog\/microsoft-entra-users-groups-and-administrative-units","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"BlogPosting","@id":"https:\/\/www.exam-labs.com\/blog\/microsoft-entra-users-groups-and-administrative-units#blogposting","name":"Microsoft AZ-104: Microsoft Entra Users, Groups, and Administrative Units - Exam-Labs","headline":"Microsoft AZ-104: Microsoft Entra Users, Groups, and Administrative Units","author":{"@id":"https:\/\/www.exam-labs.com\/blog\/author\/admin#author"},"publisher":{"@id":"https:\/\/www.exam-labs.com\/blog\/#organization"},"datePublished":"2026-10-03T06:41:25+00:00","dateModified":"2026-10-13T09:14:56+00:00","inLanguage":"en-US","mainEntityOfPage":{"@id":"https:\/\/www.exam-labs.com\/blog\/microsoft-entra-users-groups-and-administrative-units#webpage"},"isPartOf":{"@id":"https:\/\/www.exam-labs.com\/blog\/microsoft-entra-users-groups-and-administrative-units#webpage"},"articleSection":"Microsoft"},{"@type":"BreadcrumbList","@id":"https:\/\/www.exam-labs.com\/blog\/microsoft-entra-users-groups-and-administrative-units#breadcrumblist","itemListElement":[{"@type":"ListItem","@id":"https:\/\/www.exam-labs.com\/blog\/#listItem","position":1,"name":"Home","item":"https:\/\/www.exam-labs.com\/blog\/","nextItem":{"@type":"ListItem","@id":"https:\/\/www.exam-labs.com\/blog\/category\/certifications#listItem","name":"Certifications"}},{"@type":"ListItem","@id":"https:\/\/www.exam-labs.com\/blog\/category\/certifications#listItem","position":2,"name":"Certifications","item":"https:\/\/www.exam-labs.com\/blog\/category\/certifications","nextItem":{"@type":"ListItem","@id":"https:\/\/www.exam-labs.com\/blog\/category\/certifications\/microsoft#listItem","name":"Microsoft"},"previousItem":{"@type":"ListItem","@id":"https:\/\/www.exam-labs.com\/blog\/#listItem","name":"Home"}},{"@type":"ListItem","@id":"https:\/\/www.exam-labs.com\/blog\/category\/certifications\/microsoft#listItem","position":3,"name":"Microsoft","item":"https:\/\/www.exam-labs.com\/blog\/category\/certifications\/microsoft","nextItem":{"@type":"ListItem","@id":"https:\/\/www.exam-labs.com\/blog\/microsoft-entra-users-groups-and-administrative-units#listItem","name":"Microsoft AZ-104: Microsoft Entra Users, Groups, and Administrative Units"},"previousItem":{"@type":"ListItem","@id":"https:\/\/www.exam-labs.com\/blog\/category\/certifications#listItem","name":"Certifications"}},{"@type":"ListItem","@id":"https:\/\/www.exam-labs.com\/blog\/microsoft-entra-users-groups-and-administrative-units#listItem","position":4,"name":"Microsoft AZ-104: Microsoft Entra Users, Groups, and Administrative Units","previousItem":{"@type":"ListItem","@id":"https:\/\/www.exam-labs.com\/blog\/category\/certifications\/microsoft#listItem","name":"Microsoft"}}]},{"@type":"Organization","@id":"https:\/\/www.exam-labs.com\/blog\/#organization","name":"Exam Labs Blog - IT Certifications in Easy Way","description":"Pass Your Certification Exam Easily","url":"https:\/\/www.exam-labs.com\/blog\/"},{"@type":"Person","@id":"https:\/\/www.exam-labs.com\/blog\/author\/admin#author","url":"https:\/\/www.exam-labs.com\/blog\/author\/admin","name":"Allen Rodriguez","image":{"@type":"ImageObject","@id":"https:\/\/www.exam-labs.com\/blog\/microsoft-entra-users-groups-and-administrative-units#authorImage","url":"https:\/\/secure.gravatar.com\/avatar\/c3fe64bebd9f43850f9d0596b6003fdf570626ed3ea459dd1696b69cc880ef83?s=96&d=mm&r=g","width":96,"height":96,"caption":"Allen Rodriguez"}},{"@type":"WebPage","@id":"https:\/\/www.exam-labs.com\/blog\/microsoft-entra-users-groups-and-administrative-units#webpage","url":"https:\/\/www.exam-labs.com\/blog\/microsoft-entra-users-groups-and-administrative-units","name":"Microsoft AZ-104: Microsoft Entra Users, Groups, and Administrative Units - Exam-Labs","description":"A Microsoft Entra tenant can contain thousands of users, groups, devices, applications, and administrators. The difficult part is not creating those objects. It is understanding what each object changes and, just as importantly, what it does not change. A user object gives the directory an identity to authenticate and manage. A group lets administrators treat","inLanguage":"en-US","isPartOf":{"@id":"https:\/\/www.exam-labs.com\/blog\/#website"},"breadcrumb":{"@id":"https:\/\/www.exam-labs.com\/blog\/microsoft-entra-users-groups-and-administrative-units#breadcrumblist"},"author":{"@id":"https:\/\/www.exam-labs.com\/blog\/author\/admin#author"},"creator":{"@id":"https:\/\/www.exam-labs.com\/blog\/author\/admin#author"},"datePublished":"2026-10-03T06:41:25+00:00","dateModified":"2026-10-13T09:14:56+00:00"},{"@type":"WebSite","@id":"https:\/\/www.exam-labs.com\/blog\/#website","url":"https:\/\/www.exam-labs.com\/blog\/","name":"Exam Labs Blog - IT Certifications in Easy Way","description":"Pass Your Certification Exam Easily","inLanguage":"en-US","publisher":{"@id":"https:\/\/www.exam-labs.com\/blog\/#organization"}}]},"og:locale":"en_US","og:site_name":"Exam-Labs - Pass Your Certification Exam Easily","og:type":"article","og:title":"Microsoft AZ-104: Microsoft Entra Users, Groups, and Administrative Units - Exam-Labs","og:description":"A Microsoft Entra tenant can contain thousands of users, groups, devices, applications, and administrators. The difficult part is not creating those objects. It is understanding what each object changes and, just as importantly, what it does not change. A user object gives the directory an identity to authenticate and manage. A group lets administrators treat","og:url":"https:\/\/www.exam-labs.com\/blog\/microsoft-entra-users-groups-and-administrative-units","article:published_time":"2026-10-03T06:41:25+00:00","article:modified_time":"2026-10-13T09:14:56+00:00","twitter:card":"summary_large_image","twitter:title":"Microsoft AZ-104: Microsoft Entra Users, Groups, and Administrative Units - Exam-Labs","twitter:description":"A Microsoft Entra tenant can contain thousands of users, groups, devices, applications, and administrators. The difficult part is not creating those objects. It is understanding what each object changes and, just as importantly, what it does not change. A user object gives the directory an identity to authenticate and manage. A group lets administrators treat"},"aioseo_meta_data":{"post_id":"18276","title":null,"description":null,"keywords":[],"keyphrases":{"focus":{"keyphrase":"","score":0,"analysis":{"keyphraseInTitle":{"score":0,"maxScore":9,"error":1}}},"additional":[]},"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":"","og_custom_url":null,"og_article_section":null,"og_article_tags":[],"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"BlogPosting","isEnabled":true},"graphs":[]},"schema_type":"default","schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":"-1","robots_max_videopreview":"-1","robots_max_imagepreview":"large","priority":null,"frequency":"default","local_seo":null,"limit_modified_date":false,"created":"2026-10-03 06:41:25","updated":"2026-10-14 14:06:46","focus_keyword":null,"additional_keywords":null,"truseo_locale":null,"primary_term":null,"ai":null,"breadcrumb_settings":null,"seo_analyzer_scan_date":null},"aioseo_breadcrumb":"<div class=\"aioseo-breadcrumbs\"><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/www.exam-labs.com\/blog\/\" title=\"Home\">Home<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">\u00bb<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/www.exam-labs.com\/blog\/category\/certifications\" title=\"Certifications\">Certifications<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">\u00bb<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/www.exam-labs.com\/blog\/category\/certifications\/microsoft\" title=\"Microsoft\">Microsoft<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">\u00bb<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\tMicrosoft AZ-104: Microsoft Entra Users, Groups, and Administrative Units\n\t\t<\/span><\/div>","aioseo_breadcrumb_json":[{"label":"Home","link":"https:\/\/www.exam-labs.com\/blog\/"},{"label":"Certifications","link":"https:\/\/www.exam-labs.com\/blog\/category\/certifications"},{"label":"Microsoft","link":"https:\/\/www.exam-labs.com\/blog\/category\/certifications\/microsoft"},{"label":"Microsoft AZ-104: Microsoft Entra Users, Groups, and Administrative Units","link":"https:\/\/www.exam-labs.com\/blog\/microsoft-entra-users-groups-and-administrative-units"}],"_links":{"self":[{"href":"https:\/\/www.exam-labs.com\/blog\/wp-json\/wp\/v2\/posts\/18276","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.exam-labs.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.exam-labs.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.exam-labs.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exam-labs.com\/blog\/wp-json\/wp\/v2\/comments?post=18276"}],"version-history":[{"count":7,"href":"https:\/\/www.exam-labs.com\/blog\/wp-json\/wp\/v2\/posts\/18276\/revisions"}],"predecessor-version":[{"id":25557,"href":"https:\/\/www.exam-labs.com\/blog\/wp-json\/wp\/v2\/posts\/18276\/revisions\/25557"}],"wp:attachment":[{"href":"https:\/\/www.exam-labs.com\/blog\/wp-json\/wp\/v2\/media?parent=18276"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exam-labs.com\/blog\/wp-json\/wp\/v2\/categories?post=18276"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exam-labs.com\/blog\/wp-json\/wp\/v2\/tags?post=18276"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}