@JamesHamil-MSFT - yes that would work. However, Azure AD Graph is already deprecated and earmarked for end-of-life June 2022.
Clearly we have a gap here.
@MuhammadUsmanshaikh-5935 @JamesHamil-MSFT Please file a feature request to provide Microsoft Graph APIs for managing B2C user's photos
@MaksymRossiitsev-4837 If we were to increase the limit, would you consider this option? How much data would you store in the open extension?
Also - although it's not explicit, the doc does say that this applies to all supported directory resources - organization is a directory resource..
@HenryIrawan-2047 - sorry for the late response. Can you tell us what the resultant URI is, that is being requested here please?
@CRichard-3658 sorry for the late response.
This really looks like your client app does not have permissions to read group details, and hence you are getting a security trimmed response. See https://docs.microsoft.com/en-us/graph/permissions-reference?context=graph%2Fapi%2F1.0&view=graph-rest-1.0#limited-information-returned-for-inaccessible-member-objects.
We can more easily confirm this if you supply the client-request-id and timestamp for the cases where the response only contains the id value (and the rest of the property values are null).
Hi @GyorgyAdorjan-7944 - sorry for the late response. Not sure if you resolved the issue.
Can you send the full error message (including client request ID and the timestamp) so we can investigate further.
@aapo-1256 Can you please provide the request-id and timestamp in your question to help us track down the problem.
When I run a similar query it works for me, as documented.
@sethsteele-4398 Can you provide the full error response including the request-id and timestamp please so we can investigate further?
Actually @SivakoteswaraRaoSadhu-1708 please use the GA version of this endpoint here: https://docs.microsoft.com/en-us/graph/api/resources/groupsetting?view=graph-rest-1.0
That is correct. Neither of those extension mechanisms (unfortunately) can be used with dynamic membership rules. Maybe in the future it might be possible with schema extensions, but it's unlikely to be the case for open extensions (ever), mainly because this aren't schematized.
Directory Extensions (extensionProperties is where you store extension definitions for Directory Extensions) are still fully supported through Microsoft Graph and are NOT deprecated.
So in your case you will need to use Directory Extensions to work with your dynamic membership scenario.
We're working on a plan now for improvements to schema extensions, including support in all Identity features. However at this time, this work is not committed I'm sorry to say.
As such, the only recommendation I can make at this time is to use Directory Extensions (through Microsoft Graph), if support for the other identity features like dynamic memberships is key for your app. There are no plans AFAIK to deprecate support for Directory Extensions (through Microsoft Graph).
You could do both and keep them in sync - but that's kind of painful and doubly eats into one of the limits - https://docs.microsoft.com/en-us/graph/known-issues?context=graph%2Fapi%2F1.0&view=graph-rest-1.0#limit-of-100-schema-extension-property-values-allowed-per-resource-instance. But at least it might future proof you if we ever commit to the work I alluded to above.
Hope this helps - and yes it's Q & A :)
You need to use the id value and not the appId value when addressing an application in a request. See https://docs.microsoft.com/en-us/graph/api/resources/application?view=graph-rest-1.0#properties for the difference.