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

New command: outlook mailbox settings get #6567

Open
MartinM85 opened this issue Jan 17, 2025 · 1 comment · May be fixed by #6569
Open

New command: outlook mailbox settings get #6567

MartinM85 opened this issue Jan 17, 2025 · 1 comment · May be fixed by #6569

Comments

@MartinM85
Copy link
Contributor

Usage

m365 outlook mailbox settings get [options]

Description

Get the user's mailbox settings

Options

Option Description
-i, --userId [userId] The ID of the Microsoft Entra user for which you want to get mailbox settings. Specify either userId or userName, but not both. This option is required when using application permissions.
-n, --userName [userName] The UPN of the Microsoft Entra user for which you want to get mailbox settings. Specify either userId or userName, but not both. This option is required when using application permissions.

Examples

Get mailbox settings of signed-in user

m365 outlook mailbox settings get

Get mailbox settings of a user specified by id

m365 outlook mailbox settings get --userId 1caf7dcd-7e83-4c3a-94f7-932a1299c844

Default properties

Additional Info

The signed-in users can edit only theirs mailbox settings. It's not possible to read mailbox settings of another user with delegated permissions.

The options userId and userName should be specified only when the command is executed with application permissions.

https://learn.microsoft.com/en-us/graph/api/user-get-mailboxsettings?view=graph-rest-1.0&tabs=http

I wanted to add the properties option, but the endpoint ignores $select query parameter, so it's not possible to get specific settings, only all mailbox settings

I will work on it

@martinlingstuyl
Copy link
Contributor

Looks fine @MartinM85!

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

Successfully merging a pull request may close this issue.

2 participants