cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
jmc
Level: Powered On

The user does not have a service plan adequate for the non-Standard connection.

I am trying to create a flow that will insert a row in a SQL database whenever a row is created in Common Data Service. However, when I click "Create flow", it says that the user does not have a service plan adequate for the non-Standard connection. I'm assuming the non-Standard connection is referring to the Common Data Service connection, which is a Premium connection. I have Flow Plan 2. I have no idea why this could be happening because I supposedly should have access to premium connectors. Any ideas on a setting I'm missing or something of that nature?

image.pngimage.png

3 REPLIES 3
Community Support Team
Community Support Team

Re: The user does not have a service plan adequate for the non-Standard connection.

Hi @jmc,

 

Please take a look at Office 365 Admin Center, check the user licenses information from there.

Make sure the Microsoft Flow Plan 2 is assigned to the user.

Besides, please also take a check for the connections used for the Action added in your flow. Such as the SQL Server Connection, and the action followed.

I just tried the Common Data Service trigger, and the flow could be saved from my side, which made me think the issue should be caused by the other Actions you used in your flow.

Regards,

Michael

 

 

Community Support Team _ Michael Shao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
SergeyAslanov
Level: Powered On

Re: The user does not have a service plan adequate for the non-Standard connection.

Hello,

 

The same issue. Were you able to solve it?

 lL6ZZD5

flow connections.JPG

_jmk_
Level: Power Up

Re: The user does not have a service plan adequate for the non-Standard connection.

I had this problem too. I had a Flow that I had been using and was still able to trigger without issue. However, when I attempted save (even without making any changes) this same error message appeared. 

 

The problem was occuring across any Flow that I owned that had a HTTP request or response step in it (which is a built in connector so should not present any problem in terms of plan level).

 

I think it is a bug at Microsoft's end. What worked for me (do not ask me why) was sharing the Flow with a colleague. I was then able to save my changes.

Helpful resources

Announcements
firstImage

Better Together Contest Finalists Announced!

Congrats to the finalists of our ‘Better Together’-themed T-shirt design contest! Click for the top entries.

firstImage

Incoming: New and improved badges!

Look out for new contribution recognition badges coming SOON!

firstImage

New & Improved Power Automate Community Cookbook

We've updated and improved the layout and uploading format of the Power Automate Cookbook!

thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

sixthImage

Community Summit North America

The top training and networking event across the globe for Microsoft Business Applications

Top Solution Authors
Top Kudoed Authors
Users online (3,745)