Skip to content

Commit ea9cbbd

Browse files
authored
Align extensions terminology
1 parent 87cb658 commit ea9cbbd

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -55,13 +55,13 @@ Currently, you can add custom security attributes for the following Azure AD obj
5555
- Azure AD enterprise applications (service principals)
5656
- Managed identities for Azure resources
5757

58-
## How do custom security attributes compare with directory schema extensions?
58+
## How do custom security attributes compare with directory extensions?
5959

60-
Here are some ways that custom security attributes compare with [directory schema extensions](../develop/active-directory-schema-extensions.md):
60+
Here are some ways that custom security attributes compare with [directory extensions](../develop/active-directory-schema-extensions.md):
6161

62-
- Directory schema extensions cannot be used for authorization scenarios and attributes because the access control for the extension attributes is tied to the Azure AD object. Custom security attributes can be used for authorization and attributes needing access control because the custom security attributes can be managed and protected through separate permissions.
63-
- Directory schema extensions are tied to an application and share the lifecycle of an application. Custom security attributes are tenant wide and not tied to an application.
64-
- Directory schema extensions support assigning a single value to an attribute. Custom security attributes support assigning multiple values to an attribute.
62+
- Directory extensions cannot be used for authorization scenarios and attributes because the access control for the extension attributes is tied to the Azure AD object. Custom security attributes can be used for authorization and attributes needing access control because the custom security attributes can be managed and protected through separate permissions.
63+
- Directory extensions are tied to an application and share the lifecycle of an application. Custom security attributes are tenant wide and not tied to an application.
64+
- Directory extensions support assigning a single value to an attribute. Custom security attributes support assigning multiple values to an attribute.
6565

6666
## Steps to use custom security attributes
6767

0 commit comments

Comments
 (0)