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
Implementation note: split these into documented scope presets before release. The current default scope string is broad and convenient for testing, but commercial onboarding should explain exactly why each scope exists and allow lower-scope profiles where possible.
144
+
Implementation note: keep the default scope string below known admin-consent-required delegated scopes where possible. `ChannelMessage.Read.All`is needed for channel message reads, but it should be requested explicitly with `--scopes` or through a customer-owned app because Microsoft marks it as admin-consent required.
The `scope` parameter is explicit so admin consent matches the CLI's default
68
+
delegated Graph scopes instead of every static permission configured on the app
69
+
registration.
70
+
67
71
Use a concrete tenant ID or verified tenant domain for customer onboarding. `organizations` is useful for sign-in discovery, but a customer admin consent link should normally target the customer's tenant explicitly.
68
72
69
73
## Current delegated permissions
@@ -76,15 +80,20 @@ offline_access
76
80
Team.ReadBasic.All
77
81
Channel.ReadBasic.All
78
82
ChannelMessage.Send
79
-
ChannelMessage.Read.All
80
83
Chat.ReadWrite
81
84
ChatMessage.Send
82
85
ChatMessage.Read
83
86
User.ReadBasic.All
84
87
Presence.Read.All
85
88
```
86
89
87
-
These permissions cover the current read/write message, team/channel discovery, chat, user lookup, and presence smoke tests. Future features may need additional consent.
90
+
These permissions cover the current chat read/write, channel-send, team/channel discovery, user lookup, and presence smoke tests. The default does not include `ChannelMessage.Read.All` because Microsoft marks that delegated Graph scope as admin-consent required. Add it explicitly when a workflow needs channel message reads:
91
+
92
+
```bash
93
+
teams auth login --device-code --scopes "User.Read ChannelMessage.Read.All offline_access"
Copy file name to clipboardExpand all lines: docs/faq.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,15 +44,14 @@ offline_access
44
44
Team.ReadBasic.All
45
45
Channel.ReadBasic.All
46
46
ChannelMessage.Send
47
-
ChannelMessage.Read.All
48
47
Chat.ReadWrite
49
48
ChatMessage.Send
50
49
ChatMessage.Read
51
50
User.ReadBasic.All
52
51
Presence.Read.All
53
52
```
54
53
55
-
Customers should review these during admin consent. Future features may require additional permissions.
54
+
The default avoids `ChannelMessage.Read.All` because Microsoft marks that delegated Graph scope as admin-consent required. Customers that need channel message reads should grant it explicitly with `--scopes` or through a customer-owned app. Future features may require additional permissions.
0 commit comments