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 

[kimxavier]

This didn't work for me, in my case it was happening in the DEV environment. 

The fix I found was to simply remove the flow inside the canvas app and add it back again. 

The error went away. 😉

[dkardokas]

No, other permissions should not be required - only Read at Organization level. Those were just the default settings in my environment.

[lyndzhang]

Raised a ticket with Microsoft Support. This is how we solved it (hopefully it stays solved!):

1. Go to Power Platform Admin

2. Go into the environment and then Settings - Security Roles

3. Make a copy of "Basic User" role, e.g., call it "Basic User 2" (This is because the "Basic User" role is read-only!)

4. Go into "Basic User 2" and change the "Read" permission for "Process" to "Organization"

5. Assign this new role "Basic User 2" to your users.

[IsabellaFranco]

That's right, guys! God works in mysterious ways. I had the same problem, I added the person to the environment as "Environment Creator" and "Basic User", it didn't work, but when I REMOVED it, it started to work.

[MarKar]

No this work around will work only for that person but not for all the people that have to use your flow in the app

[IsabellaFranco]

Unfortunately, yes, however, it solves the problem, albeit harshly. Has a solution been found for all users? I tried the suggestions in the post but nothing worked.

[kimxavier]

have you tried removing the flow inside the canvas app and adding it back?

[IsabellaFranco]

Sadly yes... But I will continue to try the alternatives.

[Pstork1]

The fix for all this is to build both the Power App and the flow inside a Solution. Then configure the connection references and Run only user settings. Then the flow will be recognized as long as the user has at least Basic User role in the environment.

[Martin1]

This worked for me, thank you!

[JeremyHancock]

After many hours of trying to make this work, I found that if I deploy through the UI, they only way I could get others to be able to run the flow, was to create an unmanaged layer and re-add the connection in the flow.

However, that isn't really a good solution. So I worked out how to deploy the solution using the pac cli.

Something like this:

#package from dev

pac auth select --index 2

pac solution publish

pac solution export --path c:\temp\solutionfilename.zip --name SolutionName --managed true --overwrite

#Deploy to test

pac auth select --index 3

pac solution import --path c:\temp\solutionfilename.zip -pc --settings-file c:\temp\SolutionNameDeploymentSettingsDev.json

#Deploy to prod

pac auth select --index 4

pac solution import --path c:\temp\solutionfilename.zip -pc --settings-file c:\temp\SolutionNameDeploymentSettingsProd.json

I had to generate the settings file and then work out how to populate the values. I have a number of environment variables pointing to SharePoint lists. The trick was to use the GUID list id for the values.

The settings file looks something like this:

{

  "EnvironmentVariables": [

    {

      "SchemaName": "jem_ErrorRecipient",

      "Value": "email@address.com"

    },

    {

      "SchemaName": "jem_shared_sharepointonline_<guid>",

      "Value": "<list guid>"

    },

    {

      "SchemaName": "jem_shared_sharepointonline_<guid>",

      "Value": "<list guid>"

    },

    {

      "SchemaName": "jem_shared_sharepointonline_<guid>",

      "Value": "https://<tenant>.sharepoint.com/sites/<sitename>"

    }

  ],

  "ConnectionReferences": [

    {

      "LogicalName": "jem_SiteConnection",

      "ConnectionId": "<connection id guid>",

      "ConnectorId": "/providers/Microsoft.PowerApps/apis/shared_sharepointonline"

    },

    {

      "LogicalName": "jem_sharedoffice365",

      "ConnectionId": "<connection id guid>",

      "ConnectorId": "/providers/Microsoft.PowerApps/apis/shared_office365"

    }

  ]

}

Once deployed, I had to share the app with my security enabled M365 group as a user and then add the group as 'Run only users' for the flow using the service account for the connections.

Then I found my test user could access the app and run the flow without the 'connection not configured for this service' error.

[jeeva1]

Great Functions 

[RobMolenaar]

I have a DEV, TEST and PROD environment.
In DEV and TEST environment I don't have the problem. Only in the PROD environment.

We fixed it by assigning the "App Opener" security role to the default org team via the Power Platform Admin Center.

Environments > Your Target Environment > Settings > Teams

1. Look for your default business unit team
2. Manage Security Roles 
3. Add the App Opener security role

The App opener security role has "Organization level" read access to the "Process" table/entity (Dataverse system table) which is somehow required in the target environment, for normal users to trigger flows from power apps. Strangely, this is not required in the source environment.

[sbroud]

Hi,

5. Under the Security Roles, find the Basic User role , click on  ellipses (...) >> Edit

This step is not doable because 

Also, I tried to copy this role and assign organization to Read (Process). Nthing changed. the problem persists.

Please assist

[jeeva1]

Run text are all clear and it's amazing that the units are quarterly managed by a version of programs by employees 

[Navansh]

The issue was resolved by addressing a situation where the App and flows were initially created separately outside of the Solution. These flows were then integrated into the App, and both were added to a Solution in the Development environment for eventual export to the Production environment as a Managed Solution.

Resolution Steps:

1. In the Development (Source) environment solution:

   • Remove the associated flows from the App.
   • Re-add the flows to the App.
   • Publish the customizations.
   • Export the solution as a managed solution.

2. In the Production (Target) environment:

   • Import the solution again as an update (assuming the solution was previously added but not functioning).

There appears to be a bug where, despite the flows continuing to work in the Source environment, a simple refresh of the flow from within the App in the solution triggers an error in the Source environment. However, if the flows are not refreshed, they continue to function without any errors.