Skip to content

Commit 8b290d3

Browse files
committed
Managed identities edits
1 parent 76c0971 commit 8b290d3

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

articles/active-directory/fundamentals/custom-security-attributes-overview.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -23,19 +23,23 @@ Custom security attributes in Microsoft Entra ID are business-specific attribute
2323

2424
## Why use custom security attributes?
2525

26+
Custom security attributes support the following scenarios:
27+
2628
- Extend user profiles, such as add Hourly Salary to all my employees.
2729
- Ensure only administrators can see the Hourly Salary attribute in my employees' profiles.
2830
- Categorize hundreds or thousands of applications to easily create a filterable inventory for auditing.
2931
- Grant users access to the Azure Storage blobs belonging to a project.
3032

3133
## What can I do with custom security attributes?
3234

35+
Custom security attributes have the following capabilities:
36+
3337
- Define business-specific information (attributes) for your tenant.
34-
- Add a set of custom security attributes on users, applications, Microsoft Entra resources, or Azure resources.
38+
- Add a set of custom security attributes on users and applications.
3539
- Manage Microsoft Entra objects using custom security attributes with queries and filters.
3640
- Provide attribute governance so attributes determine who can get access.
3741

38-
Custom security attributes **aren't** supported in the following scenarios:
42+
Custom security attributes **aren't** supported in the following areas:
3943

4044
- [Microsoft Entra Domain Services](../../active-directory-domain-services/overview.md)
4145
- [SAML token claims](../develop/saml-claims-customization.md)
@@ -59,7 +63,6 @@ Currently, you can add custom security attributes for the following Microsoft En
5963

6064
- Microsoft Entra users
6165
- Microsoft Entra enterprise applications (service principals)
62-
- Managed identities for Azure resources
6366

6467
## How do custom security attributes compare with extensions?
6568

@@ -122,7 +125,7 @@ To better understand custom security attributes, you can refer back to the follo
122125
| attribute definition | The schema of a custom security attribute or key-value pair. For example, the custom security attribute name, description, data type, and predefined values. |
123126
| attribute set | A collection of related custom security attributes. Attribute sets can be delegated to other users for defining and assigning custom security attributes. |
124127
| attribute name | A unique name of a custom security attribute within an attribute set. The combination of attribute set and attribute name forms a unique attribute for your tenant. |
125-
| attribute assignment | The assignment of a custom security attribute to a Microsoft Entra object, such as users, enterprise applications (service principals), and managed identities. |
128+
| attribute assignment | The assignment of a custom security attribute to a Microsoft Entra object, such as users and enterprise applications (service principals). |
126129
| predefined value | A value that is allowed for a custom security attribute. |
127130

128131
## Custom security attribute properties

0 commit comments

Comments
 (0)