cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

connection not configured for this service

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

    aaroh_bits_0-1618457635286.png

     



  • Once workflow kicks in a success message in Power Apps is shown asaaroh_bits_6-1618457780193.png

     

  • 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.
    aaroh_bits_2-1618457635295.png
  • But when I clicks on Submit  workflow, he gets this error

     

    aaroh_bits_3-1618457635296.png

  • 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 

115 REPLIES 115

Thank you for this post!!!

Aedu
Advocate II
Advocate II

Hello together
We have followed all the points, but it still does not work for us:
- All users are users with security role Basic User
- Security role adjusted for process on Read Organization
- Run Only Users for the flows are set. All users are allowed to run the flows
- Solutions are imported with the same account that is used for development. This means that the owner of all artifacts (app, flow, connection references, connection) is the same in all environments.

 

Our deployment policy is that we can only install managed.

 

Currently our solution after installing or updating a solution is to open the app in the managed environment in edit mode, remove all flows and re-add them.

 

Any other ideas on what else can be done to fix the problem?

Vitss
Resolver II
Resolver II

My experience is you may not edit the apps in the Edit Mode. It breaks your solution. After doing that the App updates dit not came through (although the version number was updated).

My advice is

  • to import solutions with a service account (that also need to have all licenses needed to make the apps and flows) that ensures the working of all solutions, custom connectors etc. after the builder may have left the company.
  • Make sure on which connector the service is failing.
  • In case of Custom connectors, what caused a problem with me, you need an extra solution with this connectors in it, it seamed crucial to enroll this solution before the solution using the connectors.
  • If using an onPrem datagateway make sure the users that trigger the flow using a connector using the gateway needs to have admin rights on the gateway.

Thank you for your reply.

Maybe I was not precise enough. Development of all artifacts and deployment is already done with a service account.
The app uses 8 flows. In the dev environment everything works fine (of course). After the managed installation or update in the test environment (where we remove all unmananged layers beforehand) no more flows can be called from the app. It is like the link between the app and the flows is broken (as described in the original problem message at the beginning of this thread). It is not that the connections of the flows are no longer authorized. And we already have a custom solution for the custom connectors, which we import first, then make sure they are reauthorized before importing the solution with the app and flows. OnPrem Data Gateway is not in the game.

Vitss
Resolver II
Resolver II

And in the test environment?

If it does not work there either I suggest deleting the whole solution(s) and reimport it again.

Aedu
Advocate II
Advocate II

That might just work. But since this is a customer installation where > 30 people are testing, this would not be such a good idea because it changes the link to the app.
And most importantly, it wouldn't work in the Productive environment because then > 300 users would have to get a new link every time after each update.

Vitss
Resolver II
Resolver II

For the test environment, my opinion is that is where it is mentioned for, the Prod environment that is indeed critical. 

Log a service request with microsoft itself?

Yes I have the same issue too.

When i deploy from Dev to Test, Dev is unmanaged and Test is Managed solution.

One of the flow status is Not Connected after deployed to Test environment. 

I need to click connected manually after I deployed to Test. It created an unmanaged layer which is very annoying. 

This can cause potential issues if you were to want to get your app pen tested as users are able to query the process table via the api and return the definition of all flows even ones they shouldn't see.

 

We have been able to resolve this by using the "Power App (V2)" trigger. This then allows you to set run-only permissions for the flow. Here are the exact steps we use.

 

  1. Create a team in dataverse ( we used and Azure AD Security group) and ensure all users that need to run your flow are added to it.
  2. Create a Flow that uses the "Manually triger a flow" trigger. This flow contains all the logic and connections to dataverse using the connection reference. This flow ends with a "Response" action to pass the result back to the parent flow.
  3. On this flow go to the details screen and click Edit on the "Run only users" section. Under "connections used change all options from "Provide by run only user" to "Use this connection....".
  4. Create a flow that uses the "Power Apps (V2)" trigger. This flow then uses the "Run a child flow" action to call the flow created in step 2. This flow ends with a "Response" action to pass the result back to the app.
  5. On this flow go to the details screen and click Edit on the "Run only users" then add the group created at step1 to the list of run only users.

 

Hope this is helpful as I have been unable to find an example explaining this.

 

Update 

 

A small change you don't need to have 2 separate flows as long as on the one with the connections you do step 3.

Gilmour
Post Patron
Post Patron

Thank you @MatthewBurrows will give it a try!

leeal
New Member

Hi there, we've encountered a similar issue with one of our customers ("Connection not configured for this service"). They are hesitant to either add users to a security group or alter security roles for other users. Is there any other workaround we can try/recommend to them?

Hi I have the same issue.

I have even deleted slq connections in my development environment, My app and flows just make http requests to an api.

It does not use sql connections directly.

I tried with the solution provided and I got the same error.

 

 

@leeal Do you only get this problem once you package up the solution and deploy to a new environment? Or are you getting it in the environment where you developed the app?

@marcosrobles are you able to post a screenshot of the flows section in details for the app and the details screen of the flow?

Aedu
Advocate II
Advocate II

Been a while since the last post in this thread. Is there any news here that I may have missed? Is there a solution? Maybe from Microsoft or is everyone still helping themselves with individual workarounds?

HEATFreight_0-1676471953326.png

Easy fix!

Aedu
Advocate II
Advocate II

Unfortunately this does not fix the problem in our environments as others have already mentioned in this thread. So nothing new.

Do you have multiple environments, like Dev / Test / Prod???

Are you sure you set the Basic User permission in the environment where the app runs?

Have you shared the app with the user in that same environment where you add the Basic User permission?

Do you have a situation with "Run only users" or Parent/Child flows?

Aedu
Advocate II
Advocate II

Yes, multipe environments. In all environmetns read access for process permission is set to Organization.

Yes, checked in all environment above setting for Basic User.

Yes, the app is shared with the users in all environments.

Yes, we use "Run only user". Assigned two dataverse teams and these teams have Basic User Role assigned as well.  Any insights to that setting regarding the problems mentioned in this thread?

Is the "Connection not configured for this service" error only happening to certain users? What if you play the app in the Power Apps editor (like open the app in the editor and then click the "Play" button), then perform the action which triggers the error. Does the error still happen for the maker or only the users?

 

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (836)