microsoftgraph / microsoftgraph/entra-powershell

🙏 Clarify use case or fix functionality for Get-SponsorsAndOwners

Open
#1,593 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature Roadmap ToTriage
Dominant language
PowerShell
Stars
213
Forks
46
PR merge metrics
No merged PRs in 30d

Description

Describe the feature

This cmdlet asks for Sponsor User Ids, Group Ids, and/or Owner User Ids. It runs successfully, but just returns the same id that was provided as an input. Its unclear what is actually being validated here and whether the cmdlet is working successfully. It seems like this may be a bug in the cmdlet, but I might be missing something on the expected functionality (in which case this may be useful to clarify in docs).

Example:
Get-SponsorsAndOwners
Enter sponsor user IDs (comma-separated, or press Enter to skip): c395aa15-4378-4149-8f4f-d2a03b86f38d
Enter sponsor group IDs (comma-separated, or press Enter to skip):
Enter owner user IDs (comma-separated, or press Enter to skip):

Name Value


SponsorGroupIds
OwnerUserIds
SponsorUserIds c395aa15-4378-4149-8f4f-d2a03b86f38d

How will this feature enhance your project and further the project’s overall goals? Who will benefit from this feature (i.e. all users; the project team)?
Eliminate confusion (or incorrect behavior) when running the cmdlet.

Describe alternatives you've considered
N/A

Additional context

N/A

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Get-SponsorsAndOwners cmdlet and its documentation, then reproduce the example using a sponsor user ID. Determine what validation or lookup the cmdlet is expected to perform; done means either the behavior is corrected with coverage or the expected use and result are clearly documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.