Thanks Gemini..
It sounds frustrating when a shared link doesn't just work! Let's break down why your user might be seeing the "Start a Power Apps trial?" message even with their existing licenses and the behavior they're experiencing when accessing the app directly.
Here's a likely explanation and some things to consider:
Why the "Start a Power Apps trial?" Message with the Link:
The key issue here likely lies in how Power Apps licensing is enforced when accessing an app through a direct link, especially when it involves standard connectors (like Office365Outlook) and premium connectors (like Dataverse and Listings).
- Direct Link Enforcement: When a user opens a Power App through a shared link, the Power Platform needs to quickly determine if they have the necessary licenses to use that specific app. Even if they have broader Microsoft 365 licenses, those don't automatically grant rights to use all Power Apps, especially those leveraging premium features.
- Premium Connector Requirement: Your app uses Dataverse and Listings, which are premium connectors. To use an app that includes premium connectors, the user needs a standalone Power Apps license (like "Power Apps per user" or "Power Apps per app") or their organization needs to have capacity-based licensing that covers their usage. The Microsoft 365 E5 license includes some Power Platform capabilities, but typically not the full rights to use apps with premium connectors.
- "Test License" Context: The "Start a Power Apps trial?" message strongly suggests that the system isn't recognizing an appropriate paid Power Apps license for this user in the context of accessing the app via the link.
Why the User Can Open the App Directly:
The fact that the user can open and use the app when navigating directly to the Power Platform portal suggests a couple of possibilities:
- Existing Trial or Limited Entitlement: Perhaps the user had a Power Apps trial active at some point, and while it might be expiring or not fully covering direct link access, it still allows them to see and run the app within the Power Platform environment.
- Different Licensing Check: When a user logs into the Power Platform, the system might perform a broader check of their available entitlements. It's possible that their Microsoft 365 E5 license grants some basic Power Platform usage rights that are sufficient when navigating within the environment, even if it doesn't cover direct access via a link for apps with premium connectors.
- App Sharing Permissions: The app might have been shared with them in a way that grants them basic usage rights within the Power Platform environment, but the direct link access triggers a more stringent license check.
In Summary:
The most probable reason is that using premium connectors (Dataverse and Listings) requires a standalone Power Apps license for the user to access the app, especially through a direct shared link. Their existing licenses, while valuable, don't inherently grant them the necessary Power Apps permissions for this scenario.
Here's what you should do to resolve this:
- Verify Power Apps Licensing: Confirm whether the user has a standalone Power Apps license (Per User or Per App). You can check this in the Microsoft 365 Admin Center under the user's licenses.
- Consider Power Apps per App Licensing: If only specific users need access to this app, the "Power Apps per app" license might be a cost-effective solution.
- Evaluate Capacity-Based Licensing: If your organization has a significant number of users needing access to Power Apps with premium connectors, exploring capacity-based licensing might be beneficial.
- Review Sharing Settings: Double-check how the app was shared. Ensure the user has the correct permissions assigned to them.
- Educate the User: Explain that accessing apps with premium features often requires a specific Power Apps license beyond their standard Microsoft 365 subscription.
Let me know if you can provide more details about the specific Power Apps licensing your organization has, and we can narrow down the exact cause and best solution!
