This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(41.6, 67%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWC%3C/text%3E%3C/svg%3E)
Hi Team,
I created one AAD app and added A, B, C Permissions and user authorize app via granting permission from their admin. But as an OAuth app owner, if I add more permissions let b x,y and when user retry to authorize. New consent screen is not appearing with added permissions. It directly provides access token with old scopes(A, B, C).
So how can I make the user get consent screen for every change in scope of request call
@soumi-MSFT I tried using v1.0 oauth2. In v1.0 there is no way for providing scopes. So how this can be achieved in v1.0?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 2%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
@WMio Connectors , If you are using v1.0 endpoints, since there is no way to mention specific scopes in the request, hence you would need to add prompt=consent at the end of the request so that the consent screen appears along with the permissions.
@WMio Connectors , Just wanted to check if the above response helped.
Do let us know if this helps and if there are any more queries around this, please do let us know so that we can help you further. Also, please do not forget to accept the response as Answer; if the above response helped in answering your query.
@WMio Connectors , For the time being you can mention the new Permissions in the scope (in case using v2.0 endpoint) of the Request URL and try. I tried the same and it works for me.
https://login.microsoftonline.com/common/oauth2/v2.0/authorize?client_id=xxx-xxx-xxxx&response_type=code&redirect_uri=http%3A%2F%2Flocalhost%3A3456&response_mode=fragment&scope=openid%20offline_access Bookings.Read.All&state=12345
Bookings.Read.All, is the new Permission that I added and tested and it appeared in the Consent Page.
Hope this helps.
Do let us know if this helps and if there are any more queries around this, please do let us know so that we can help you further. Also, please do not forget to accept the response as Answer; if the above response helped in answering your query.
@WMio Connectors , Also, you can use the following request also:
Here, I used the scope as https://graph.microsoft.com/.default and added prompt=consent to the request. This would also bring up all the consents including the new ones. This is like forcing the consent page to come up with all the available permissions. When you use the prompt=consent, at that time, all permissions which are consented by the admin or user earlier would also list up but when you provide a consent it wont take any effect for the already consented permissions. Incase the list contains any new permission, the consent would only effect only on the new permissions.