Open cedomm opened 1 week ago
Found the cause of the issue, it only happens if Enhanced tracking protection is enabled, and it is by default :
In the console, we can see that the call to the OAUTH 2.0 authorization endpoint seems discarded as it never gets a response, and toggling the details show no info at all for the request :
It is really strange that this feature blocks such a standard call.
@cedomm Enhanced tracking protection disables 3P cookies. This in turn is causing issues with the getAccessTokenAPI. Refer to https://learn.microsoft.com/en-us/office/dev/add-ins/develop/troubleshoot-sso-in-office-add-ins#13001 for workaround of this error code.
Calls to Office.auth.getAccessToken() throws a 13001 error in Firefox but works fine in Chrome / Edge. It used to work in Firefox too so this must be some regression. In the documentation this error is listed for Safari :
source : https://learn.microsoft.com/en-us/javascript/api/office/office.auth?view=common-js-preview#office-office-auth-getaccesstoken-member(1)
Your Environment
Platform: Outlook Web Browser: Firefox The task pane add-in is running in compose mode.
Expected behavior
The access token should be retrieved.
Current behavior
A 13001 error "The user is not signed into Office" is thrown.