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
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
#Configure Authorized client applications for service (TodoListService-OBO-sample-v2)
....
In the manifest editor, change the "knownClientApplications": [] line so that the array contains the Client ID of the client application (TodoListClient-OBO-sample-v2) as an element of the array.
This does not work. At least, not in my tenant. No matter whether client appId is added or is not added to knownClientApplications, the user is still presented with 'Need admin approval' page:
What does work is pre-authorizing that client application:
and pre-assigning the scope. Then the user doesn't get the consent dialog at all.
So (at least, in my tenant) it is either a mandatory admin consent or no consent.
Probably, this needs to be clarified in the readme.
The text was updated successfully, but these errors were encountered:
This issue is for a: (mark with an
x
)This does not work. At least, not in my tenant. No matter whether client appId is added or is not added to
knownClientApplications
, the user is still presented with 'Need admin approval' page:What does work is pre-authorizing that client application:

and pre-assigning the scope. Then the user doesn't get the consent dialog at all.
So (at least, in my tenant) it is either a mandatory admin consent or no consent.
Probably, this needs to be clarified in the readme.
The text was updated successfully, but these errors were encountered: