microsoftgraph / microsoftgraph/entra-powershell
🚀 Cmdlets are performant at scale
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 213
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
Current Challenge:
Entra PowerShell prioritizes usability, but customers also want a balance between performance and usability. For large tenants with thousands of objects, better performance can reduce costs and improve engineering efficiency.
Why it matters:
Many Entra PowerShell customers manage large tenants with thousands or millions of objects like users, groups, and applications. High performance is essential to:
- Reduce execution times
- Lower operational costs
- Support large-scale automation
- Improve responsiveness and user experience
Roadmap tracker:
This issue serves as a roadmap tracker.
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
The issue names no files, tests, or cmdlet entry points. Start by defining performance targets and large-tenant scenarios, then identify the affected cmdlets and existing benchmarks. Done should be a concrete, validated performance improvement for the agreed scenarios.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100