I'm working on an Azure AD integration that works with multiple regions. Ideally I'd use delta queries whenever possible, however as not all regions support delta queries I have a check for delta query support as per this answer. However recently the check broke. It turns out that the microsoft. prefix has been removed from the return type (ie microsoft.graph.group became graph.group). I can't find any information about this change in the changelog and I'd prefer to make the check as future-proof as possible, so my question is - what value should I check for? Currently my intent is to check for the support of delta query for a type that ends with graph.group and a type that ends with graph.user.
How to correctly determine if a given Azure AD region supports delta queries?
Viewed 133
2 Answers
There seems not to be a change log for Microsoft Graph metadata.
But there is a history list for Microsoft Graph metadata.
See history for V1.0 metadata and Beta metadata.
For V1.0, the microsoft. prefix was removed in the Jan 28 version. And for Beta it was removed in the Feb 26 version.
Now that it has been changed, I believe it will continue to maintain this version (without the Microsoft. prefix). So you should check ReturnType Type="Collection(graph.user)" and ReturnType Type="Collection(graph.group)" currently.
I did some research and apparently the $metadata endpoint returns OData CSDL metadata. As per the documentation on the Schema element, the Schema element must include a Namespace attribute and may include an Alias attribute. The nominal types may be qualified with either. With that in mind one could check the defined namespace and alias and then figure out the possible ways to refer to the user and group types.
Related