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
I am currently maintaining an Office 365 app registered in an Azure Active Directory. Recently I came across an issue while integrating the app for another AD tenant. The error was AADSTS650051: Application '<app-guid>' is requesting permissions that are either invalid or out of date. After removing API permission for ActivityReports.Read, everything started working again.
After fixing the issue, I searched a lot on whether this permission is still valid. But I could not find a definitive answer or any reference for this even. At last I found this permission to be present in scope value of the below sample response.
So, my question is - is the API permission still valid? Because it is not presented as an option in API permissions suitable for adding on an application. Added to that the behavior I described in at the beginning of this issue seems like the answer will be negative.
In that case, should this be present in the docs? Is there any place where API permission deprecation status can be checked along with API reference and needed API permission for that API?
The text was updated successfully, but these errors were encountered:
I am currently maintaining an Office 365 app registered in an Azure Active Directory. Recently I came across an issue while integrating the app for another AD tenant. The error was
AADSTS650051: Application '<app-guid>' is requesting permissions that are either invalid or out of date.
After removing API permission for ActivityReports.Read, everything started working again.After fixing the issue, I searched a lot on whether this permission is still valid. But I could not find a definitive answer or any reference for this even. At last I found this permission to be present in scope value of the below sample response.
https://github.com/MicrosoftDocs/office-365-management-api/blob/live/office-365-management-api/get-started-with-office-365-management-apis.md#sample-response
So, my question is - is the API permission still valid? Because it is not presented as an option in API permissions suitable for adding on an application. Added to that the behavior I described in at the beginning of this issue seems like the answer will be negative.
In that case, should this be present in the docs? Is there any place where API permission deprecation status can be checked along with API reference and needed API permission for that API?
The text was updated successfully, but these errors were encountered: