Mobile Teams Adaptive Card Power Apps Open Link

Question

I developed an app using Power Apps and configured it so that if a URL contains parameters in the OnStart event, it navigates to a specific screen.

I tried to open a Power Apps URL containing parameters in an Adaptive Card using the Action.OpenUrl method via Power Automate. While the parameters work correctly and the app opens without issues in Teams on a PC or the web, they do not work in the Teams mobile app.

So, I’m currently using a TextBlock to display the link as hyperlink text. However, while this works internally within Teams on PC or the web, on Mobile Teams, it only works if I open the link via the “Open in Teams?” pop-up after it’s initially opened in a web browser.

• When using Action.OpenUrl in an Adaptive Card, it doesn’t work properly, but when I share the URL embedded there via chat, the parameters are linked correctly and it opens as expected.
• Finally, I set it up so that clicking a URL linked to a Container would open that URL, but this caused the in-app Power Apps to open twice. I had to press the back button twice to return to the Teams chat screen.

I’m wondering if there are any plans to address these issues.

If there’s no current solution, I’d like to know when improvements might be implemented.

Answer 1

Hi,

This is a known behavior on Teams mobile — the Action.OpenUrl in Adaptive Cards doesn't always handle Power Apps deep links correctly on iOS/Android.

What works:

Use the full Power Apps URL with the https://apps.powerapps.com/play/ format and add &source=teams at the end. Example:

https://apps.powerapps.com/play/YOUR-APP-ID?tenantId=YOUR-TENANT-ID&source=teams

If the link still doesn't open on mobile:

Try wrapping it in a Teams deep link instead:

https://teams.microsoft.com/l/entity/APP-ID/tab?webUrl=YOUR-ENCODED-URL

Alternative approach: Use Action.Submit instead of Action.OpenUrl and handle the navigation via Power Automate flow triggered from the card — more reliable on mobile clients.

Hope this helps. Let me know if you need help with the specific URL format for your app.

Answer 2

Hi @김현서 

Thanks for bringing this issue to our attention. 

Please note that this is a user-to-user support forum. Moderators, contributors, and external Microsoft employees do not have access to back-end systems since we lack the tools to collect logs or diagnose your issue comprehensively. Our role here is limited to sharing technical guidance based on publicly available resources and experience.   

From my findings, this appears to be a limitation with Adaptive Cards and deep linking in Microsoft Teams, particularly on mobile clients. The behavior of Action.OpenUrl can vary depending on whether the user is on desktop, web, or mobile, which leads to inconsistencies when passing parameters into Power Apps.  

At present, Microsoft has not announced a timeline for resolving these limitations. Improvements to Adaptive Cards and deep-linking behaviors are typically introduced gradually through service updates, and differences across platforms are expected.  

In your case, you mentioned that clicking a URL linked to a Container caused the Power App to open twice. I’ve seen a similar report on GitHub bug report: When using Action.OpenUrl in Declarative Agent, the URL was opened twice. · Issue #1454…), but no official fix has been provided yet.  

Since you’ve already tested using a TextBlock hyperlink, here are a few additional approaches worth considering: 

-Use Microsoft Teams deep links instead of standard Power Apps URLs when possible. You can refer to Deep links overview - Teams | Microsoft Learn. 

-Share the Power Apps link directly in Teams chat, as it is handled more reliably across devices. 

-Leverage the StartScreen property in Power Apps for more reliable parameter-based navigation. (This works on my test) 

I tried to reproduce your scenario, but without more details I wasn’t able to replicate the same behavior. If possible, please share your Adaptive Card payload so others can test under similar conditions.  

In the meantime, you may want to:  

-Post a new thread on GitHub, where engineers and community contributors may be able to provide more targeted insights. See: Participating in a discussion - GitHub Docs.

-Raise a support ticket through Services Hub, which route the issue directly to Microsoft engineering teams. Please note that this portal is a paid ticket and access is subject to certain conditions, you can read more at: Services Hub sign in FAQs | Microsoft Learn.  

Thank you for your patience and understanding.  

---

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

Answer 3

Teams mobile and Power Apps mobile handle deep links and URL navigation differently from the desktop/web clients, and this is the root of the behavior being observed. There is no configuration in Adaptive Cards or Power Apps that can change how the Teams mobile client currently processes these URLs.

From the available information:

1. Power Apps deep links and parameters
   • Model-driven and other Power Apps scenarios rely on specific URL parameters and, on mobile, on the platform’s deep-link handling.
   • Deep links can open in the browser instead of the app depending on device and MDM settings. On some Android devices, for example, it is necessary to explicitly associate apps.powerapps.com with the Power Apps mobile app so that links open directly in the app instead of the browser.
   • This behavior is controlled by the OS and any Mobile Device Management policies, not by Adaptive Cards or Power Apps.
2. Action.OpenUrl behavior
   • Action.OpenUrl simply instructs the host (Teams) to open a URL in an external or embedded browser. The host app (Teams desktop, web, or mobile) decides whether to open in an in-app web view, external browser, or hand off to another app.
   • Because Teams mobile and Teams desktop/web use different URL-handling logic, a URL that correctly passes parameters and deep-links on desktop/web may not be handled the same way on mobile.
3. Multiple openings / back-button behavior
   • When a URL is wired both to an Action.OpenUrl and to a container tap (or when the OS and Teams both react to the same link), the result can be that the target app appears to open twice, requiring multiple back presses. This is a side effect of how the host app and OS each handle the navigation and is not configurable from Adaptive Cards.
4. Current options and limitations
   • There is no documented switch or setting in Adaptive Cards or Power Apps that forces Teams mobile to treat the URL the same way as Teams desktop/web.
   • The only supported mitigations in the provided documentation are:
     • Ensuring mobile OS and MDM settings are configured so that Power Apps deep links open directly in the Power Apps mobile app instead of a browser where possible.
     • Using the documented deep-link parameters for model-driven apps and ensuring the URL is correctly formed.
   • Any change to how Teams mobile handles Action.OpenUrl or Power Apps deep links would require product updates in Teams and/or Power Apps. No timelines or plans for such changes are documented in the provided material.

Given the available documentation, there is no supported way to guarantee identical behavior between Teams desktop/web and Teams mobile for Action.OpenUrl with Power Apps URLs, and no published schedule for improvements.

---

References:

• Use deep links with the Power Apps mobile app
• Action.OpenUrl
• Open apps, forms, views, dialogs, and reports with a URL