microsoftgraph / microsoftgraph/msgraph-sdk-powershell
Support per module default output formatting (Get-MgUser's and Get-MgBetaUser's UserType property: Now you see it, now you don't)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 898
- Forks
- 230
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 31
Description
Different versions of SDK and Graph API cause different, inconsistent, behavior for the UserType property.
SDK v1, v1.0 endpoint: Get-MgUser doesn't return UserType by default
SDK v1, beta endpoint: Get-MgUser returns and displays UserType by default
SDK v2, v1.0 endpoint: Get-MgUser doesn't return UserType by default
SDK v2, beta endpoint: Get-MgBetaUser returns UserType, but it's not displayed in the output by default
Behavior also changes when -Property is used, if we get the specified user or list all users
PS> get-mgbetauser -property signinactivity -userid ac4de573-e369-4dcb-bbd2-170c4a0b667c | select usertype
UserType
--------
PS> get-mgbetauser -property signinactivity | select usertype
UserType
--------
Member
Member
...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Get-MgUser and Get-MgBetaUser examples across SDK v1 and v2, comparing the v1.0 and beta endpoints with and without -Property and with a specific user versus listing users. Trace how each module chooses default output properties. Done means UserType is returned and displayed consistently for the supported cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- api, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100