Merge pull request #25307 from microsoftgraph/dkeshaw10-openExtFix

Fixed an error about open extensions

Author: Lauragra

concepts/extensibility-overview.md

@@ -863,6 +863,8 @@ You define and manage open extensions on the fly on resource instances. They're
 - The user object for Bruno can have no open extension property.
 - The user object for Alex can have an open extension named *socialSettings* with five properties: **theme**, **color**, **language**, **font**, and **fontSize**.
 
+Additionally, open extension properties can have any valid JSON structure.
+
 #### Create an open extension
 
 The following example shows an open extension definition with three properties and how the custom properties and associated data are presented on a resource instance.
@@ -1046,7 +1048,7 @@ The following table compares the extension types, which should help you decide w
 | Supported resource types | [user][] <br/>[device][] | [user][] <br/> [group][] <br/> [administrativeUnit][] <br/> [application][] <br/>[device][] <br/> [organization][] | [user][] <br/> [group][] <br/> [administrativeUnit][] <br/> [contact][] <br/> [device][] <br/> [event][] (both user and group calendars) <br/> [message][] <br/> [organization][] <br/> [post][] | [user][] <br/> [group][] <!--<br/> [administrativeUnit][]--> <br/> [contact][] <br/> [device][] <br/> [event][]<sup>1</sup> (both user and group calendars) <br/> [message][] <br/> [organization][] <br/> [post][] <br/> [todoTask][] <br/> [todoTaskList][] |
 | Strongly typed | No | Yes | Yes | No |
 | Filterable | Yes | Yes | Yes | No |
-| Can store a collection | No | Yes | No | No |
+| Can store a collection | No | Yes | No | Yes |
 | Tied to an "owner" application | No | Yes | Yes | No |
 | Managed via | Microsoft Graph <br/> Exchange admin center | Microsoft Graph | Microsoft Graph | Microsoft Graph |
 | Sync data from on-premises to extensions using [AD connect][] | Yes, for users | [Yes][ADConnect-YES] | No | No |