connection not configured for this service

[aaroh_bits]

Hi All,

Background Info

• Using Power Apps and Power Automate with back end as Dataverse.
• All Artefacts are under a Solution with maker.powerapps.com for ease to move to environments at later stage.   
• We need to generate PDF via OneDrive (no premium connector)  and send email to end user when workflow completes.
  
  

What Works:

• As flow owners for that workflow and has following connections
  
  
  
  
• Once workflow kicks in a success message in Power Apps is shown as
• Submit button action in Power Apps is as follows:

If(
   Not(IsSubmitError),
    IfError(
        PurchaseRequestApprovalSubmission.Run(Text(HelpDeskWorkflow)),
        UpdateContext({IsSubmitError: true});
        Notify(
            "The workflow was failed to start. Message: " & ErrorInfo.Message & "& Error Kind" & ErrorKind,
            Error
        ),
        UpdateContext({IsSubmitError: false})
    )
);

What does not work

Other non- flow owners do not trigger the workflow

• 
  User Alex as following connection and OneDrive connected for Alex’s account.
  
• But when I clicks on Submit  workflow, he gets this error
  
  
• Tried may other options such as
• We removed the OneDrive action inside flow, then re-add back. Then updating the connection reference inside the app.
• We ensured there’s no other dummy connection inside the flow. Then updating the connection reference inside the app.
• We Deleted the OneDrive connection that connects to the flow, then re-add back. Then updating the connection reference inside the app.
• We created another dummy app, trigger the workflow, then the error message shows up as: “HelpDeskWorkflow.Run failed: connection not configured for this service”.
• We created another dummy app, create another dummy flow, both are outside the solution, the workflow triggers just fine.
• We Exported the flow package (.zip), then import back to the environment.
• With the imported flow package (.zip), we created another dummy app and trigger the workflow, it works as per normal again. The flow was imported outside the solution and can’t be added into the solution.

Stumbled into a quite a few of issues in the community forum

PowerApps Flow Error : "Connection not configured for this service", when its in included in the Managed Solution and deployed

https://powerusers.microsoft.com/t5/Building-Power-Apps/PowerApps-Flow-Error-quot-Connection-not-con...
My experience with connector/connection problems, and multiple connections to same connector  
https://powerusers.microsoft.com/t5/Connecting-To-Data/My-experience-with-connector-connection-probl...

Connection not configured for this service (with Microsoft Support ticket details )

https://powerusers.microsoft.com/t5/Building-Power-Apps/Connection-not-configured-for-this-service/m...

Any suggestions or pointer will be greatly appreciated.

@martinav @CFernandes  @jinivthakkar  @Pstork1  @v-xida-msft 

[Aedu]

HEATFreight,

the app is used exclusively in the browser by > 300 users. The problems occurred when testing in the test environment with different testers. After a new deployment to the test environment, the problems occurred with other testers. It is sometimes with those testers, sometimes with other testers. Even with the account that performs the deployment. This account is also the owner of all artifacts, including the used connections. In the Prod environment (tested with some testers) the same problems occurred as well.

[HEATFreight]

Do you know what kind of connector is triggering the error? Is it that you are using CloudFlow.Run() or what?

If it's a cloud flow (Power Automate), have you checked the >Data >Connections tab in each of the effected environments to make sure all the connectors are properly configured with Status="Connected"? 

Do you use Power Automate Desktop (PAD) flows? Is the PAD machine always up and running?

Have you tried exporting and re-importing the solution?

[Aedu]

Yes, CloudFlow.Run() is used from a Canvas App.

Yes, all Connections are connected.

No, no PAD.

Yes, we regularly export the solution and re-import it into Test and Prod, because of maintenance and new features we implement in the app and flows. Always the same problems, before we apply the well known workaround.

[HEATFreight]

Oh another thing! I think I experienced an issue recently where a new Azure AD user was created and a M365 Premium license was assigned, but I think a CloudFlow.Run() was giving us this same error.

I realized that I had previously created and subsequently deleted this same Azure AD user before, and after that I had aliased that email address to another user. But I forgot to remove the alias when assigning "Basic User" permission. I noticed that the username / email address was appended with a random string and the "email address" parameter for that Azure AD user was blank and it was not possible to set it to their actual email address. So I got rid of the aliased email address and set the "email address" parameter for that Azure AD user to their username, and that worked no problem with the alias removed. Then I went back to the >Environment >Users & Permissions >Basic User and removed the messed up version of the user, then added them back again and the random string was gone!

Problem fixed.

So if you see any users with random strings of characters appended to their email address in the >Environment >Users & Permissions >Basic User tab, then:

1) make sure that email address is not aliased
2) make sure to set the "email address" parameter in Azure AD to the user's email address
3) remove them and add them back to >Basic User

[Aedu]

Thank you for your support @HEATFreight, unfortunately it is not a problem with the AD users. No users have random strings appended to their email.

[HEATFreight]

Just taking blind stabs in the dark here, but are you using any premium connectors without the appropriate licensing?

[OliverR-82]

I am also facing this issue and none of the suggestions offered in this thread seem to fix it. I have a canvas PowerApp and a bunch of Power Automate flows (parent and child, all with run-only user permissions) and environment variables (to reference SP lists) bundled in a solution. Everything works fine in the unmanaged solution in the DEV environment, but after exporting as a managed solution to PROD, I get the error mentioned in the topic; the flows that are triggered from the PowerApp don't run.

As much as I love the Power Platform, I am not at all impressed with the whole 'Solutions' functionality. I'm sure it works great for Dataverse-only solutions, but once you include canvas apps and flows it seems the whole process is extremely troublesome and time consuming. From all of the comments I'm reading here it seems you're just better off with exporting as an unmanaged solution to PROD, and just have the discipline to not make any changes directly in PROD.

There's a lot of room for improvement in this part of the Power Platform IMO.

[HEATFreight]

I've been exporting my unmanaged solution from Dev and importing (still unmanaged) to Prod, and I don't have "connection not configured for this service", at least not regularly. When the error does happen, there has always been an identifiable reason for it, and the error went away after I followed easily google-able troubleshooting steps.

However, unmanaged solutions are not the proper way to push code from Dev to Prod. The only reason I haven't switched to a managed solution yet is because I have to recreate all my Custom Connectors in my Test environment and get all connections configured in Test, then I need to do a test run of converting an unmanaged solution to a managed solution in my Test environment. Once I've validated this process, I'll switch my Prod environment to managed as well.

And although it's not best practice, making changes directly in the unmanaged Prod solution isn't necessarily wrong. It's just that if you intend for the changes to be permanent, you must make the same changes in Dev so that you won't lose them the next time you push the unmanaged solution to Prod.

We test in Prod. YOLO ¯\_(ツ)_/¯

Anyway, you should make sure to "add required components" before exporting, assign "basic user" permissions in Prod, and get your flow connectors properly configured for "run-only users" vs. "use this connection".

Here is what New Bing has to say about this error:

Here are some more possible causes and solutions for this error in Power Apps:

The user does not have sufficient permissions to access the connection or service12. This could be because they are not assigned a proper security role, or they have not consented to use the connection. To fix this, you can try these steps2:
Navigate to Power Apps Admin Center
Select the Environment you are working
Click on Settings on top bar
Go to User + Permissions » Security Roles
Under the Security Roles, find the Basic User role , click on ellipses (…) » Edit
Under Customization tab » Select Process » assign Read access to the Organization
The connection is not included or configured properly in the managed solution or environment13. This could be because the connection is missing from the solution package, or it is not updated after deployment. To fix this, you can try these steps3:
Open your solution in Power Apps Studio
Go to Data » Connections
Check if your connection is listed there. If not, add it from New Connection button
If your connection is listed there, click on it and then click on Edit button
Re-enter your credentials and save the connection
The connection is corrupted or outdated and needs to be refreshed or recreated3. This could be because of changes in your service provider’s API, authentication method, or endpoint URL. To fix this, you can try these steps3:
Go to make.powerapps.com
Click on Data » Connections
Find your connection and click on it
Click on Repair button and follow the instructions
If that does not work, delete your connection and create a new one with the same name

And here is what ChatGPT says:

The "connection not configured for this service" error in Power Apps can occur due to several reasons. Here are some of the most common issues that could cause this error:

Missing Connection: The connection for the data source may not be configured in Power Apps. You may need to create a new connection or modify an existing one.

Incorrect Connection: The connection for the data source may not be configured correctly. Ensure that you have entered the correct credentials and that the connection settings match the data source.

Incompatible Connector: Power Apps may not support the connector used for the data source. Ensure that you are using a compatible connector.

Insufficient Permissions: The account used to connect to the data source may not have sufficient permissions to access the data. Check the permissions of the account used to connect to the data source.

Outdated Connection: The connection for the data source may be outdated or expired. Refresh the connection by re-entering the credentials or reconnecting to the data source.

Server Issue: There may be an issue with the server hosting the data source. Try connecting to the data source from another device or at a later time.

Firewall Issue: The connection may be blocked by a firewall or other security measures. Check with your IT team to ensure that the connection is not blocked.

Incorrect Configuration: The data source may not be configured correctly. Check the configuration settings for the data source.

Data Source Unavailable: The data source may be unavailable due to maintenance or other issues. Check with the data source provider to ensure that the data source is available.

Incorrect API Version: Power Apps may not support the API version used by the data source. Ensure that you are using a supported API version.

These are some of the most common issues that can cause the "connection not configured for this service" error in Power Apps. If you are still experiencing the issue after troubleshooting these potential causes, you may need to seek further assistance from Power Apps support.

I think it can also be that the flow is turned off, when you get 'connection not configured for this service' with a Flow.Run().

They should make that error more specific as to which of the many possible causes is to blame.

[qwerty123456]

Dude, thanks for taking the time and posting this. I had the same issue.

[Aedu]

In our case it was finally the case that for an unknown reason the connection reference could not map the existing connection when updating the managed solution. After a lot of trial and error, the only solution was to delete and recreate the connection references and adjust all flows accordingly. Setting the connection references manually after the deployment is not an option for us, as we are aiming for an automated deployment without manual adjustments.

Furthermore, I got the impression that every time the warning "You may break your PowerApps triggered flow with the changes on the triggers." is displayed when making adjustments within a flow, i.e. not on the flow trigger itself but in an action in the flow, it is extremely advisable to either update or delete and re-add the reference to the flow in all callers of the flow.

Everything else that was suggested in this already quite long thread did not help.

Nevertheless, thanks to all who have supported here with suggestions. In the end, every hint helped to narrow down and solve the problem.

[PaulLF]

I experienced this issue today although my scenario was slightly different to the OP, but I'll explain the setup and solution since googling let me here anyway.

I have an app and flow developed in our development environment (by me) where I have the system administrator role. Everything worked fine there, and I packaged up the app into a solution with all the other components it required. One thing I did which I normally don't do is include the connection references in the solution; I did this as the first exported version without them failed to import into our production environment as the PowerApps for Makers connection reference wasn't included - which is odd as it normally lets you create them on import, but whatever.

Once everything was successfully imported I tried running the app, but when the flow was called I received the same error as the OP:

[Flow name].Run failed: Connection not configured for this service.

I looked for solutions, tried modifying the Basic User role (although this made no sense as I was running the app in production with my own account which was system admin in that environment too) that didn't work so I decided to edit the app in production and see if I could see the issue (yay for unmanaged solutions).

When checking the Power Automate tab in the app I could see that the flow was listed as Not Connected, and it advised me to remove and re-add the flow. I can only assume that some combination of packaging the flow, app and connection references together in the solution broke the links between them stopping it from working at runtime.

Removing the flow from the app and re-adding it fixed the issue. I haven't tested yet with a non-admin account yet, but I'll update my post when I've had a chance to do that.

Update - I've tested this with non-admin accounts and it is working as expected.

[Aedu]

so you too have arrived where you don't want to be in terms of automated deployments. Namely, where you have to perform manual tasks after the automated deployment. Automated deployments may not be an issue for you.

What can also help to solve the problem is to open all dependent flows in edit mode and save them again before exporting the solution from the dev environment. Then do the same with the app: open in edit mode, update all flows, save and publish the app. Then do not wait for days, but export the solution immediately.

This may help because I noticed that very often when I open a flow in edit mode, the save button becomes active right away, even though I haven't changed anything yet. Other times I open a flow and the save button is not active. For me, this means that Microsoft has made changes in the background that affect my flows, but only when I save them again. I can therefore well imagine that in such cases the connection from the app to the flow can be affected somehow.

[indhaa]

I don't have any issues after I did this

1. Navigate to Power Apps Admin Center
2. Selected the Environment you are working and the environment migrating to.
3. Go to Security Roles
4. Under the Security Roles, find the Basic User role , click on ellipses (...) >> Edit
5. Under Customization tab >> Select Process >> assign Read access to the Organization
   
   
6. Make sure the flow owners on both environment is same
7. If not you can delete the flow and import again
   
   Don't have any issues afterwards

[Aedu]

Thank you, this tip has been mentioned several times in this thread and has brought nothing. Quite a long thread here, probably you missed it when looking through before repeating the answer here.

[indhaa]

Hi,

Yah I saw that. 
Just want to let everyone know that I don't have this issue when migrating between the environment after doing the 7 step. Updating ONLY the permission didn't help me too. Have to make sure the when migrating flow owner is same for both environment. I'm assuming this was the issue

After doing this I don't have any issue. Pls Check  

[DeeTronSEAM]

Having the same problem with a cloud flow using a PApps (v2) triggered flow that fails to fire from the Canvas app in the same (managed) solution deployed to production enviro.  While attempting to make the suggested mods to the "Basic User" Security Role I struggled with being unable to make ANY mods to that role.  This doc seems to best explain that behavior: https://learn.microsoft.com/en-us/power-platform/release-plan/2023wave1/data-platform/secure-securit... 

As I can't believe this secRole mod is required STILL....despite all too many years with similar dumba$$ gaps in MSFT products....I'm going to try some other options before doing the custom security role as the article suggests is needed.  Wish me luck.

[johnjohn123]

I am facing the same issue..

I have a canvas app , where i am calling a workflow , using this code:-

Set(varAppLink,GetEnvironmentVariables.Run("new_PowerAppsLink").value);
Set(varPermissionsGroup,GetEnvironmentVariables.Run("mlf_GroupsIDs").value);
Set(varShowTabs,GetEnvironmentVariables.Run("mlf_ShowAllTabs").value);

now this is working for all users on our development environment, but when i deploy this solution (as managed solution) to our PROD environment, all users except me is getting this error message "GetEnvironmentVariables.Run failed: connection not configured for this service" ...any advice?

The flow mainly get some environment variables any return them to power app, as follow:-

any advice? is this a permission issue?

[Pstork1]

Did you set the Run Only users on the Connection References the flow is using in the Solution?

[johnjohn123]

@Pstork1 we do not need to do so,, as this is working on the development environment without setting any special settings inside the Run Only user section. i were able to find a workaround , where i edited the power app inside the managed solution inside the PROD environment, remove the flows inside power app and re-added them, then it work.. so the issue is not related to the Run Only settings....

[Pstork1]

If you move the solution to the prod environment and don't make the change to the Run only settings then the users will try to run those connections in their own security context. That is normally where this particular error comes from.  But yes, editing the flows in the production environment will add them to a unmanaged layer which will bypass the issue with not setting the run only settings since the flows in the managed solution will then be ignored.  But in my experience not setting the Run Only settings is exactly what leads to the error you are seeing. Adding an unmanaged layer will also block changes that are made to the original solution from taking effect when a new version of the managed solution is imported. So yes its a workaround, but its one that will cause additional problems in the future.