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
{{ message }}
Repository navigation
Unable to extract AdministrativeUnit member: "Invalid property 'businessPhones' specified in $select #3154
I'm trying to verify that users I'm creating join an administrative unit with dynamic membership rules. Instead of querying the members, I figure I can just try to extract the given member. The documentation does not give any C# samples, but I found that I can address the administrativeUnit membership using
So when I'm trying this, I'm getting an exception with message
Invalid property 'businessPhones' specified in $select.
However, I'm not making any selects, so it seems the SDK is injecting something.
Expected behavior
await graphServiceClient.Directory.AdministrativeUnits[unitId].Members[memberId].GraphUser.GetAsync()` should return the User in case it's there, or an exception Resource_not_Found if memberId is not a member of the Administrative Unit.
How to reproduce
For an existing Administrative Unit with id unitIdand a user that is a member with id memberId call
Ahh, heheh.. in fact that's the workaround I implemented and then found the other issue. But can I take it that since this issue is still open, the underlying server issue will be resolved eventually or do I have to do something else? Opening actual MS Graph API cases has been made excessively difficult by MS with the subscription requirement
Activity
MartinM85 commentedon Jul 29, 2026
It seems to me that the error is on the server side:
returns the error Invalid property 'businessPhones' specified in $select.
ssteiner commentedon Aug 10, 2026
So.. what can I do to get this fixed?
MartinM85 commentedon Aug 10, 2026
Use workaround from #3156
ssteiner commentedon Aug 10, 2026
Ahh, heheh.. in fact that's the workaround I implemented and then found the other issue. But can I take it that since this issue is still open, the underlying server issue will be resolved eventually or do I have to do something else? Opening actual MS Graph API cases has been made excessively difficult by MS with the subscription requirement