how are you getting your access token? It seems like when you're utilizing a flow that's most likely client credentials as it sounds like you're not getting the delegated permissions, but the application permissions. For more information on permissions I suggest taking a look here : https://blogs.msdn.microsoft.com/aaddevsup/2018/05/21/finding-the-correct-permissions-for-a-microsoft-or-azure-active-directory-graph-call/
In addition to that, per your response the AAD Graph API is being deprecated and not supported anymore. If you'd like to get the next page feature working, please utilize the microsoft Graph API.
If you'd like there to be further support for the AAD Graph API please submit your feedback here : https://feedback.azure.com/forums/169401-azure-active-directory and if there's enough community support the product team will look into putting this on the roadmap for the future.
You could also file a support ticket to see if you can get this enabled/supported for your specific scenario.
Thanks,
- Frank Hu
@FrankHu-MSFT any news?
hey @NikitaKrivets-9470,
The well known id is a term meant for OIDC configs.
The ID you are using is the App Identifier for the app registration for your msft exchange online remote powershell which has already had permissions granted by some gobal admin to access https://reportingservice.activedirectory.windowsazure.com. This is a unique application registration as it's meant for a Microsoft first party application.
Your application already has the correct permissions and this is looking like an issue with the MSFT Graph API thanks for letting us know about this, I'll look into this further and see if we can get this issue resolved as soon as possible. Thanks!