microsoftgraph / microsoftgraph/entra-powershell
Connect-Entra seems to give more Scopes than requested.
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 213
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
If I start a brand new PS console and connect using for example the Scope Group.Read.All...
Connect-Entra -TenantId xxxx -Scopes Group.Read.All
And then look at my Context using
(Get-EntraContext).Scopes
it will show all available scopes assigned to the Enterprise Application
Example...
![image](https://github.com/user-attachments/assets/1edfa930-1009-46cf-ae77-1b2177142255
I would expect the Context to only show the "Active" Context.Scopes I currently have available in the session.
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 in a fresh PowerShell console and reproduce the issue with Connect-Entra -TenantId xxxx -Scopes Group.Read.All, then inspect (Get-EntraContext).Scopes. Compare the requested scope with the scopes reported in the context; done when the context reports only the active scopes available in the session.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100