You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/fundamentals/custom-security-attributes-overview.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,7 +66,7 @@ While both extensions and custom security attributes can be used to extend objec
66
66
| Supported objects | Depends on the extension type | Users and service principals |
67
67
| Restricted access | No. Anyone with permissions to read the object can read the extension data. | Yes. Read and write access is restricted through a separate set of permissions and RBAC. |
68
68
| When to use | Store data to be used by an application <br/> Store non-sensitive data | Store sensitive data <br/> Use for authorization scenarios |
69
-
| License requirements | Available with the basic license | Basic capabilities are available with an Azure AD Premium P1 license |
69
+
| License requirements | Available in all editions of Azure AD | Requires an Azure AD Premium P1 or P2 license |
70
70
71
71
For more information about working with extensions, see [Add custom data to resources using extensions](/graph/extensibility-overview).
0 commit comments