Study guide
3.2 Groups & Custom Security Attributes
Exam SC-300: Microsoft Identity and Access Administrator Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts & Logistics 1.2 Audience Profile, Zero Trust & Role Scope 1.3 Skills Measured & Study Map
2 Entra Tenant Administration
2.1 Tenant Properties, Domains & Company Branding 2.2 Built-in & Custom Roles, Effective Permissions 2.3 Administrative Units
3 Users, Groups, Licenses & Devices
3.1 Create, Configure & Manage Users 3.2 Groups & Custom Security Attributes 3.3 Licenses, Bulk Operations & Device Join
4 External Identities & Cross-Tenant Access
4.1 External Collaboration & Guest Lifecycle 4.2 Cross-Tenant Access Settings 4.3 Cross-Tenant Sync & External Identity Providers
5 Hybrid Identity
5.1 Entra Connect Sync vs Cloud Sync 5.2 PHS, PTA & Seamless SSO 5.3 AD FS Migration & Connect Health
6 Authentication Methods & MFA
6.1 Authentication Methods Portfolio 6.2 MFA, SSPR & Password Protection 6.3 Passwordless, Session Control & Entra Kerberos
7 Conditional Access
7.1 Planning, Assignments & Controls 7.2 Session Management, Device Restrictions & CAE 7.3 Auth Context, Protected Actions, Templates & Troubleshooting
8 Identity Protection & Global Secure Access
8.1 User Risk & Sign-in Risk 8.2 MFA Registration Campaigns & Risky Workloads 8.3 Global Secure Access
9 Workload & Managed Identities
9.1 Selecting Identities for Apps & Azure Workloads 9.2 Create, Assign & Use Managed Identities 9.3 Service Principals Fundamentals
10 Enterprise Apps & App Registrations
10.1 Enterprise Applications Integration 10.2 App Registrations, API Permissions & App Roles 10.3 Application Proxy & Consent
11 Microsoft Defender for Cloud Apps
11.1 Cloud Discovery & Connected Apps 11.2 CA App Control & Session Policies 11.3 OAuth App Policies & Catalog Management
12 Entitlement Management
12.1 Catalogs & Access Packages 12.2 Access Requests & Terms of Use 12.3 Connected Organizations & External User Lifecycle
13 Access Reviews
13.1 Plan & Create Access Reviews 13.2 Monitor & Respond to Access Reviews
14 Privileged Identity Management
14.1 PIM for Entra Roles & Azure Resources 14.2 PIM for Groups, Approval & Audit 14.3 Break-Glass (Emergency Access) Accounts
15 Monitoring, Logs & Secure Score
15.1 Sign-in, Audit & Provisioning Logs 15.2 Diagnostics, KQL & Workbooks 15.3 Identity Secure Score
3.2 Groups & Custom Security Attributes
Key Takeaways Explain This Topic AI
Security groups are the primary vehicle for assigning access to apps, roles, and Conditional Access inclusions/exclusions; Microsoft 365 groups add collaboration artifacts such as a shared mailbox, calendar, and SharePoint site.
Assigned membership is static and admin- or owner-managed; dynamic user and dynamic device membership evaluate rules against directory attributes and keep membership current automatically.
Dynamic membership rules use expression syntax against attributes (for example department, job title, or user type); rule design quality directly affects access correctness and license cost.
Nesting of security groups has practical limits for some scenarios (notably group-based licensing and some application assignments); do not assume unlimited nesting works everywhere.
Custom security attributes are tenant-defined key/value attributes organized in attribute sets, assigned to directory objects, and used for fine-grained governance, filtering, and authorization scenarios beyond built-in schema.
Last updated: July 2026
Groups as the unit of scale
Managing access user-by-user does not scale. Microsoft Entra ID groups are how identity administrators assign applications, Conditional Access scope, licenses (group-based licensing), Microsoft 365 collaboration resources, and many governance packages. SC-300 tests whether you can pick the right group type , the right membership model , and—when built-in attributes are not enough— custom security attributes for richer targeting.
Security groups versus Microsoft 365 groups
- Feature Security group Microsoft 365 group
- Primary purpose Security and access control Collaboration + can also be used for access
Mail-enabled option Can be mail-enabled (distribution-like scenarios) via Exchange, but classic use is security Always includes group email and collaboration resources
Collaboration resources None by default Shared mailbox, calendar, SharePoint team site, Planner (ecosystem dependent)
Typical uses App assignments, CA include/exclude, role-eligible groups, network access targeting Project teams, departments that need a shared workspace
Membership types Assigned, dynamic user, dynamic device Assigned or dynamic user (not dynamic device)
Nested groups Supported with important scenario limits Nesting behavior differs; know security-group nesting limits for access scenarios
Exam bias: if the scenario is only about granting access to an enterprise application or scoping Conditional Access , choose a security group unless the scenario explicitly needs Microsoft 365 collaboration artifacts. If the scenario emphasizes Team / shared site / group mailbox , choose a Microsoft 365 group .
Microsoft 365 groups can be used for some access scenarios, but security groups remain the cleaner mental model for pure authorization constructs on the exam.
- Assigned versus dynamic membership
- Assigned membership
Administrators or group owners add and remove members explicitly.
Predictable and simple for small, stable populations (break-glass exclusion group, VIP CA exclusion with strict change control, project app pilots).
Does not auto-correct when people change department or leave a project—governance (access reviews) becomes important.
Dynamic user membership
You write a membership rule based on user attributes.
Entra continuously evaluates the rule and adds/removes users as attributes change.
Ideal for “all users in Department equals Finance,” “all members with jobTitle contains Intern,” or “userType equals Guest” patterns.
Dynamic device membership
Rules evaluate device attributes (for example OS type, displayName patterns, device ownership).
Used for device-targeted access and management patterns.
Microsoft 365 groups do not support dynamic device membership —that is a frequent distractor.
- Membership type Best for Risk if misused
- Assigned Privileged exclusions, small controlled sets, exceptions Stale membership without reviews
- Dynamic user Org-structure driven access and licensing Bad rules → wrong access at scale
- Dynamic device Device-based targeting for security groups Over-broad device rules
- Dynamic membership rules — concepts you must know
Dynamic rules use a simple expression language. Conceptual building blocks:
Properties: department , jobTitle , companyName , usageLocation , userType , extension attributes, and more.
Operators: equals, notEquals, startsWith, endsWith, contains, match (regex-style patterns in supported forms), and logical -and / -or .
Direct reports rule patterns and other advanced constructions appear in docs; for SC-300, focus on attribute equality/contains and logical combination.
Processing: rule changes trigger re-evaluation; large tenants can take time to recompute membership.
Example conceptual rules (illustrative):
(user.department -eq "Finance") — all Finance users.
(user.department -eq "Finance") -and (user.usageLocation -eq "US") — Finance in the United States only.
(user.userType -eq "Guest") — all guest users (often for CA or governance targeting).
Design tips the exam rewards:
Prefer stable authoritative attributes (HR-synced department) over free-text fields users can change themselves.
Avoid overlapping dynamic groups that fight each other for mutually exclusive license SKUs without a clear design.
Remember that dynamic membership requires appropriate Entra ID licensing (historically Entra ID P1 for dynamic groups)—know that dynamic groups are a premium capability in enterprise designs.
Nested groups and limits awareness
Nesting means putting a group inside another group so membership is transitive for some evaluation engines.
Key awareness points for SC-300 (not a deep combinatorial math exercise):
Security group nesting is commonly used in on-premises AD thinking, but cloud resource assignment engines do not all honor nesting the same way .
Group-based licensing does not support nested groups for license assignment—the user must be a direct member of the licensed group for licenses to apply via that feature.
Some application assignments and Conditional Access evaluations expect direct membership depending on configuration; when in doubt, exam items often steer you to direct membership for licensing and critical access.
Deep nesting increases troubleshooting difficulty (“why does this user have access?”).
Practical rule: use nesting sparingly in cloud-first designs; prefer dynamic rules or clear single-purpose groups for licensing and CA.
Group ownership, visibility, and self-service
Beyond type and membership:
Owners can manage membership (for assigned groups) without being Global Administrators—aligns with least privilege.
Visibility / privacy settings on Microsoft 365 groups affect discovery and guest access patterns.
Access reviews (later domain) can target group membership to clean up assigned groups over time.
PIM for Groups can make membership eligible rather than permanent for privileged groups—advanced governance, but know groups are a PIM target later.
Custom security attributes
Custom security attributes in Microsoft Entra ID let administrators define tenant-specific attributes beyond the built-in user schema. They are designed for governed, filterable metadata used in authorization and operational scenarios .
Building blocks
Concept Meaning
Attribute set A container that groups related attributes and is a unit of delegation (who can define or assign attributes in that set)
Attribute definition Name, description, data type (string, integer, boolean, etc.), single vs multi-valued, and whether values are predefined
Assignment Values attached to directory objects (commonly users; also supported on other object types depending on feature scope)
Filter / consume Other features and custom apps can read attributes for authorization decisions and administrative filtering
Why not just use department or extensionAttribute1?
Built-in attributes and on-premises extension attributes are often already overloaded by HR and Exchange. Custom security attributes provide:
Separation of concerns — security/governance data separate from mail nickname or department.
Delegated administration — attribute sets can be managed by specific roles without granting full user admin rights.
Governed catalog — definitions are explicit, typed, and auditable.
Authorization scenarios — applications and policies can make decisions based on attributes such as Clearance=Secret , ContractType=VendorManaged , or DataBoundary=EU without inventing shadow databases.
Lifecycle of using custom security attributes
Plan attribute sets (for example ProjectGovernance , Clearance , CostCenterSecurity ).
Define attributes with types and allowed values where appropriate.
Assign values to users (or other objects) as part of joiner/mover processes.
Consume in apps, administrative unit filters, custom claims/apps, automation, or reporting.
Audit and review who can assign sensitive attributes—attribute assignment is itself a privileged operation class.
Custom security attributes are not a replacement for groups. Groups still express collections for assignment. Attributes express descriptive facts that many systems can filter on. Often you combine both: a dynamic group rule cannot always express every custom-security-attribute scenario the same way apps can via Graph filters—know them as complementary tools.
Governance and authorization scenarios (exam framing)
Expect scenario questions like:
“Finance users should automatically get the Finance apps group” → dynamic security group on department .
“We need a Team with SharePoint for Project Orion” → Microsoft 365 group .
“Only direct members should receive E5 via group-based licensing” → no nested groups for that license group.
“We must tag users with a regulated clearance level managed by the security team only” → custom security attribute set with delegated permissions, not a free-text department field.
“Exclude a small set of emergency accounts from a CA policy” → small assigned security group , tightly controlled.
Common traps
Using a Microsoft 365 group when only a security principal is required (or vice versa when collaboration is required).
Expecting dynamic device membership on Microsoft 365 groups.
Assuming nested groups receive group-based licenses .
Writing dynamic rules on non-authoritative attributes users can edit arbitrarily.
Treating custom security attributes as ungoverned notes fields—definitions and assignment rights matter.
Master group type, membership model, nesting limits, and custom security attributes as a single toolkit for scalable access design on SC-300.