Teams Tab: Power Apps Connection Auth Loop, Works Fine via Direct URL

(1) Share

Report

Posted on by _Judy_

109

- English

Dear Microsoft Support Team,
We are experiencing an intermittent login issue with our Power Apps app ("Training Calendar") embedded in Microsoft Teams, starting today.

When users open the Training Calendar tab inside Teams (multiple channels/groups), they are repeatedly shown the permission dialog for SharePoint and Office 365 Outlook but the app fails to load. The issue is intermittent — sometimes it works, sometimes it doesn't. However, opening the app via direct URL always works fine.

Questions

1. What is the root cause? Is there an ongoing service incident?

2. How can we permanently fix this?

Thank you. Looking forward to your response.

Best regards

- Chinese

我們的 Power Apps 應用程式「Training Calendar」從今天開始，在 Microsoft Teams 中出現間歇性無法登入的問題。

在 Teams 不同群組中開啟 Training Calendar 分頁時，會一直出現 SharePoint 和 Office 365 Outlook 的授權對話框，但應用程式無法正常載入。問題為間歇性發生，但若直接使用網址（URL）開啟，則完全正常。

1.根本原因為何？目前是否有服務異常事件？

2.如何永久解決此問題？

感謝

USER3.png

USER2.png

USER01.png

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:

Error handling

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Vish WR 3,748 on at

Like
a
(4)

Report
Copy link

Link copied!

@_Judy_

This is a known Teams iframe auth issue. When Power Apps is embedded in Teams, it runs inside an iframe and Teams blocks third-party cookie/token flows intermittently depending on browser settings and the Teams client version — which is why direct URL always works but Teams doesn't.

A few things worth checking:

First, make sure all users have already consented to the SharePoint and Outlook connectors at least once via the direct URL. Teams sometimes can't complete the consent popup inside the iframe.

Second, check the Microsoft 365 Service Health dashboard to rule out an ongoing incident — go to admin.microsoft.com → Health → Service health.

For a more permanent fix, the app needs to be published to Teams properly via Power Apps (Share → Add to Teams) rather than just embedding the URL as a tab. That way Teams handles the auth token handoff natively instead of going through the iframe popup flow

Vishnu WR

LinkedIn - My Tech Space

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥

Was this reply helpful? Yes No
_Judy_ 109 on at

Like
a
(1)

Report
Copy link

Link copied!
Hi Vishnu,

Thank you for your response!

Regarding your suggestions:

All users are already using the correct method — the app is published to Teams via Power Apps (Share → Add to Teams), not embedded via URL.

We checked the Microsoft Service Health status at status.cloud.microsoft and found the following warning:
"Service degradation on Microsoft consumer products.

Could this service degradation be the root cause of today's intermittent authentication issue in Teams?

Looking forward to your thoughts. Thank you!

Was this reply helpful? Yes No
Vish WR 3,748 on at

Like
a
(2)

Report
Copy link

Link copied!

@_Judy_

yes could be due to the service disruption , is is solved now ?

Vishnu WR

LinkedIn - My Tech Space

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥

Was this reply helpful? Yes No