cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
aaroh_bits
Helper V
Helper V

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?

sky_sats
Advocate I
Advocate I

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?

marcosrobles
New Member

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

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Top Kudoed Authors
Users online (4,671)