Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include needed Graph API permissions per each command #6380

Closed
nanddeepn opened this issue Sep 23, 2024 · 3 comments
Closed

Include needed Graph API permissions per each command #6380

nanddeepn opened this issue Sep 23, 2024 · 3 comments
Labels

Comments

@nanddeepn
Copy link
Contributor

nanddeepn commented Sep 23, 2024

Priority

(Low) Something is a little off

Description

Hi,
Not sure if this is already covered under any other issue or in backlog.

As we need to setup our own App registration, we should include the Graph APIs permissions needed per command in the documentation.

Steps to reproduce

Include the Graph APIs permissions needed per command in the documentation.

Expected results

Graph APIs permissions included in the documentation

Actual results

Current documentation does not include Graph APIs permissions needed to execute a specific command.

Diagnostics

No response

CLI for Microsoft 365 version

v9.1.0

nodejs version

v20.9.0

Operating system (environment)

Windows

Shell

PowerShell

cli doctor

No response

Additional Info

No response

@nanddeepn nanddeepn added the bug label Sep 23, 2024
@waldekmastykarz waldekmastykarz changed the title Bug report: Include needed Graph API permissions per each command Include needed Graph API permissions per each command Sep 23, 2024
@waldekmastykarz
Copy link
Member

Thanks for raising this @nanddeepn. We've discussed it in the past and recently opened a PR that helps us automate it (#6342). Shortly, we'll create an epic to track updating all commands with the necessary information.

@milanholemans
Copy link
Contributor

milanholemans commented Sep 23, 2024

We also have an (old) issue regarding how we should display it in the docs: #4399

@Jwaegebaert
Copy link
Contributor

Since we're already tracking this, it should be safe to close.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants