You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are trying to deploy Teams app using app permissions in an automated process but it looks like is just allowed for a user with global admin permissions.
Steps to reproduce
we are authenticating using this line
m365 login --authType certificate --certificateFile "xxxxxxxx" --password "xxxxxxxx"--appId "xxxxxxxx" --tenant "xxxxxxxx"
and executing this line which is not working
m365 teams app publish --filePath "xxxxxxxx.zip"
Expected results
I was expecting to have the option to deploy a Teams application with an application with the right permissions.
Actual results
It looks like is just allowing to deploy an application when we are authenticated with a global admin.
Diagnostics
No response
CLI for Microsoft 365 version
4.4.0
nodejs version
10.24.1
Operating system (environment)
Windows
Shell
cmd
cli doctor
No response
Additional Info
No response
The text was updated successfully, but these errors were encountered:
Description
We are trying to deploy Teams app using app permissions in an automated process but it looks like is just allowed for a user with global admin permissions.
Steps to reproduce
we are authenticating using this line
m365 login --authType certificate --certificateFile "xxxxxxxx" --password "xxxxxxxx"--appId "xxxxxxxx" --tenant "xxxxxxxx"
and executing this line which is not working
m365 teams app publish --filePath "xxxxxxxx.zip"
Expected results
I was expecting to have the option to deploy a Teams application with an application with the right permissions.
Actual results
It looks like is just allowing to deploy an application when we are authenticated with a global admin.
Diagnostics
No response
CLI for Microsoft 365 version
4.4.0
nodejs version
10.24.1
Operating system (environment)
Windows
Shell
cmd
cli doctor
No response
Additional Info
No response
The text was updated successfully, but these errors were encountered: