microsoftgraph / microsoftgraph/dataconnect-solutions
Clear requirements for approvers accounts
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 72
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Description
Requirements for approvers are not clear. UX design is fine, but what happens beneath this administrative actions is not clear. We use privileged accounts for admin actions that have no mailboxes, or teams. Such approval should be handled through separate admin notifications/requests queue channels inside O365 admin center.
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 provides no files, tests, or entry points. Start by locating the repository material covering approver accounts, privileged administrative actions, and O365 admin-center notification or request queues; done means the underlying approval behavior and requirements are explicitly defined.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100