Connection not configured for this service issue for specific users.

[rbn_nue]

Hi Folks,

I had recently exported a managed solution to our QA environment in power apps. I tested the app and everything seems to work just fine. But when I shared the app with QA team, they are getting the error: "Connection not configured for this service" for all flows. 

I read somewhere that users needs to be given access to flows and this will solve the issue. I added couple users as basic user to the environment and enabled read access to process table. This enabled the app to work properly for those users. But this does not make sense. We do not share any environment with end users and it had worked fine. Even our existing prod and dev environments are not shared with anyone directly. Only the app is shared. Enabling access for all users to environment so that they can use app does not feel right.

Could anyone please suggest what I'm doing wrong here?

Thank you. 

[BCBuizer]

Hi @rbn_nue ,

A possible solution has been posted here: https://powerusers.microsoft.com/t5/Building-Power-Apps/Flows-not-being-triggered-by-PowerApp-quot-C...

[jatcube]

Connection not configured error is a real pain. I've been struggling with it recently. Couple things I found out from experience

1. It's a "container" error message, meaning there are multiple underlying causes why you'd see it - makes it pretty much impossible to diagnose, those are e.g.
2. Corrupt (non-existent) connection references in new environment.
3. The canvas app mysteriously lost the connection to the flow (only after solution is exported) as there seems to be a bug with the export or import solution likely due to the implementation of the new in-app Power Automate Pane
4. Multiple users edited the flow or the canvas app
5. New connectors were added since managed solution was last imported (wizard won't prompt to connect new connection references upon import - MS bug)
6. Connection references are not included in the solution

Quick steps to resolve

1. If your app was created before the Power Automate Pane got rolled out, always try that first.
2. Then check connection references in the solution.
3. Then modify your flows and connections (delete additional authors and their connections).
4. Delete managed solution and reimport, creating new connection references.

In more detail:

1. If you're not precious about adding users back, etc then simplest is to Delete managed solution -> reimport it -> create/set up connections on import -> share app with users
2. Click on 3 dots of each flow in solution ->Advanced -> Add required objects -> Publish all customizations -> Export -> Import into managed environment.
3. Edit flows to use the Powerapps V2 connector -> reconnect flows to canvas app using the new Power Automate Pane -> Save and republish app -> step 2.
4. Remove all connection references in flows, recreate them with just one user (make sure that the flows only use connection references.) -> step 3 -> step 2
5. Check basic user rights in managed environment.
6. Support ticket to MS
7. Sometimes it may be necessary to completely recreate flows and reconnect them to the app (last resort).

Hope that helps

[rbn_nue]

Hi @BCBuizer ,

Thank you for the suggestion. Although, like I mentioned it does not make sense to share the flow with end users, while it has been working fine in dev without this action. 

Thank you.

[jatcube]

@rbn_nue have you checked out my suggestions? I've been in similar situations before and sharing the flow with users was never the solution as we're talking about managed solutions that use connection references that allow them access to the flow actions. But I get it, it's a nasty error to get and there's no straightforward solution. Let me know

[rbn_nue]

Hi @jatcube ,

Appreciate your suggestions. Although, since it was urgent I did the below to solve the issue:

• Exported app as managed but allowed customization for app
• After import edited the app from Default solution, refreshed all flows.

Immediately after this, app started working for users that had issue. But this fix is not advisable in production. 

Some quick notes from your suggestions:

• I'm already using power apps v2 trigger.
• Deleting the solution and reimport have not worked for me.
• The first time I exported, I had ensured to add required objects and publish all customizations (around 100 flows are there, doing this each time is not practical. Please share if you have any scripts to automate this., but it still did not work.
• We had previously followed single user connection reference for all flows. But still had received the error. At that time we solved it by re-adding all flows from dev and export again.
• Providing users with basic user rights in environment and ensure read access to process table will solve the issue. But in production we won't add users to environment.

I'll be submitting a ticket to MS (Not expecting much from them) and do some for research and test from my end. Will share if I get any positive outcomes. 

Thank you.