Microsoft Loop fails with AADSTS650057 when requesting Wrike resource

Ryan LaRoche - Admin 20 Reputation points
2026-08-12T18:57:40.9866667+00:00

I'm troubleshooting a Microsoft Loop issue affecting one user.

Tom can access most Loop workspaces normally, but specific pages in SOFA Huddle and MIT Budget Results fail to open. Other users can access those same workspaces successfully.

The problem occurs across Loop desktop, Teams, Edge, Chrome, InPrivate, and even a separate RDS environment, so it does not appear to be device-specific.

We have already:

  • Removed/re-added Tom's workspace membership.

Re-shared the SOFA Huddle workspace. Tested from a separate RDS environment. Provided Microsoft Support with HAR logs and a screen recording.

The key finding is in Microsoft Entra sign-in logs. Authentication and MFA succeed, but Loop then fails with:

AADSTS650057 – Invalid resource

Client: Microsoft Loop App Loop App ID: [Moderator note: personal info removed] Requested Resource: Wrike Wrike Resource/App ID: [Moderator note: personal info removed]

That App ID is the exact ID of our tenant's Wrike Enterprise Application.

Tom is not assigned to the Wrike application, it has no admin-consented permissions, and we have not configured Loop to use Wrike.

Why would Microsoft Loop request our Wrike resource when Tom opens specific Loop pages? Could a Loop workspace/page contain a stale or hidden reference to a third-party application, or is there an Entra authorization issue causing Loop to request the wrong resource?

Microsoft Support has referred us to the Entra/Authentication team, but we're looking for additional insight before making changes to the Wrike application.

Microsoft 365 and Office | Loop | For business
0 comments No comments

Answer accepted by question author
Lin v 1,285 Reputation points Independent Advisor
2026-08-12T19:59:59.69+00:00

Hi Ryan,

Thank you for providing such detailed troubleshooting information and for sharing the findings from your investigation.

After reviewing the details you've provided, this appears to be a fairly advanced scenario. The observation that Microsoft Loop is requesting the Wrike resource when specific pages are opened is certainly an interesting finding and may require deeper investigation to understand the underlying behavior.

Based on the scope and focus of this forum, which primarily supports break-fix and general product troubleshooting scenarios, it may be difficult for the community to provide definitive guidance regarding the underlying authentication flow or service-side behavior involved here.

If you already have an active Microsoft Support case, I would encourage you to continue working with the support team in parallel. Given the nature of the issue, determining the root cause may require access to backend diagnostics, service telemetry, and coordination across the relevant product teams, which are not available through community forums.

Microsoft Support is likely in the best position to investigate why the Wrike resource request is occurring and whether it is related to Loop, Entra authentication, page metadata, or another integration-specific condition.‌

I hope this information is helpful. Wishing you the best in identifying the underlying cause of the issue.

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.