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
Bug report: Impossible to create team when using application permissions #4916
Comments
Thanks, @MathijsVerbeeck for rising this 👍. We will try to recheck this one ASAP |
Makes sense I guess. I think the only fix here would be to introduce 2 new options
Both can be used with delegated or app only auth, but they will be required when using app only auth. |
I also thought something like that. Makes sense too. |
Yeah, a team needs at least an owner indeed. We could also add a |
I'd say we start with just specifying a single owner, to at least get this command to work, and we can extend this command in general in the future I believe. |
I suggest that we decide now if we'd like to support a single- or multiple users, so that we can avoid breaking changes later on. If I for example look at |
So
? |
What are |
Yes, thinking about that though: why do we even do that? If it's a GUID or an UPN, why don't we verify what kind of value is being used in the CLI? Should be easy to do, and it would clean up a lot of commands with these superfluous options. |
I don't know. 😊 |
Any updates regarding this issue? |
Should we add 2 options? |
Let's do that. And |
Could include that one as well, so do we agree to add the options below?
|
Perfect. Thank you @martinlingstuyl, @milanholemans for the awesome brainstorm. |
Sure thing.! |
Awesome 🤩. |
That's a bummer! I think we should stick to the spec and update the team members afterward. |
Sure thing. So I create the team using the first user passed in either one of the |
One (hopefully final) further remark I have is that we will have to only include this when using |
good point, I don't think there is any better approach at the moment than enforcing |
Hey @MathijsVerbeeck, just checking in. What is the latest regarding this issue? |
Resetting due to lack of response |
Can I restart working on this one? |
Priority
(Low) Something is a little off
Description
It is currently impossible to create a team when using application permissions. This is due to the application permissions request expecting a
members
property in the request body, and we currently do not demand this.More information can be found on this URL: https://learn.microsoft.com/en-us/graph/api/team-post?view=graph-rest-1.0&tabs=http#examples
Steps to reproduce
m365 teams team add --name 'TEST' --description 'TEST'
Expected results
Team being created or a prompt for members
Actual results
Error: Request failed with status code 400
Diagnostics
The text was updated successfully, but these errors were encountered: