Skip to content

Commit 41de326

Browse files
committed
fixing paragraph
1 parent d18d352 commit 41de326

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

docs-conceptual/azureadps-2.0/using-extension-attributes-sample.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,8 @@ If an organization consents to “read only” permissions for an application wi
3232

3333
If the application is deleted or consent is removed in the other organization’s directory, the extension property becomes inaccessible on the target directory object. If the extension is deleted by the application, it also becomes inaccessible on the target directory object. If a multi-tenant application adds additional extension properties after consent was granted, these properties become immediately accessible in the other organization’s directory.
3434

35-
>Note: If an extension property’s value is set on an object and that property becomes inaccessible in that object’s directory, the property still counts against that object’s limit of 100 extension property values. The only way to remove the property value from consideration once it has been set is to explicitly set it to null. You cannot do this if the extension property is inaccessible.
35+
>[!NOTE]
36+
> If an extension property’s value is set on an object and that property becomes inaccessible in that object’s directory, the property still counts against that object’s limit of 100 extension property values. The only way to remove the property value from consideration once it has been set is to explicitly set it to null. You cannot do this if the extension property is inaccessible.
3637
3738
You can read more about extension properties in [this article.](https://msdn.microsoft.com/library/azure/ad/graph/howto/azure-ad-graph-api-directory-schema-extensions)
3839

0 commit comments

Comments
 (0)