microsoft / microsoft/powerbi-powershell
Get-PowerBIWorkspace returns blank UserPrincipalName column if groups are added to roles
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 413
- Forks
- 134
- Avg merge
- 33m
- Merged PRs (30d)
- 1
Description
Get-PowerBIWorkspace returns a blank UserPrincipalName column if groups are added to the roles instead of individual users.
For e.g., if we add security groups to the Admin or member roles of a workspace, when running Get-PowerBIWorkspace, the UserPrincipalName column is empty. This makes sense because a security group will not have a UserPrincipalName attribute.
Since the cmdlet is just doing a query to the Power BI REST API in the background and it does return other pieces of info such as display name and object ID, it would be helpful for the cmdlet to print that info in the output instead of just user principal name.
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 at the Get-PowerBIWorkspace cmdlet and inspect how the Power BI REST API response is mapped into its output. Reproduce a workspace where a security group is assigned to a role, then ensure the output includes the available group display name and object ID instead of relying only on UserPrincipalName.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- api, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100