Hello there,

A few days ago, some of the Excel reportings I’m maintaining for a client stopped working because they get an “access denied” error when accessing data. I’m using OData connections to get relevant informations from both the data sources below :

https://xxx.sharepoint.com/sites/pwa/_api/projectdata

https://xxx.sharepoint.com/sites/pwa/_api/projectserver/calendars(‘calendarid’)

The first data source is the usual one to get all the projects-related data. This one seems to still work fine when using the Admin account (authenticated using the “professionnal account” authentication type).

The second one I used to get the calendar exception list from the Standard calendar. It worked fine too until a few days ago and now I can’t access it anymore, even with the Admin credentials.

When I try to reconnect to the data source I meet a message that says “We can’t authenticate you with the given credentials. Try again.”.

Did the authentication method for calendar access changed these last days ? Has anyone encountered this issue ?

Thank you very much

​Hello there, A few days ago, some of the Excel reportings I’m maintaining for a client stopped working because they get an “access denied” error when accessing data. I’m using OData connections to get relevant informations from both the data sources below :https://xxx.sharepoint.com/sites/pwa/_api/projectdatahttps://xxx.sharepoint.com/sites/pwa/_api/projectserver/calendars(‘calendarid’) The first data source is the usual one to get all the projects-related data. This one seems to still work fine when using the Admin account (authenticated using the “professionnal account” authentication type).The second one I used to get the calendar exception list from the Standard calendar. It worked fine too until a few days ago and now I can’t access it anymore, even with the Admin credentials.When I try to reconnect to the data source I meet a message that says “We can’t authenticate you with the given credentials. Try again.”.Did the authentication method for calendar access changed these last days ? Has anyone encountered this issue ? Thank you very much  Read More

​