As of February HTTP connectors became Premium in Flow. However, I am probably not the only person that had a misunderstanding that using the "Response" action with Flow SQL Server actions with Azure SQL Server. Apparently the "Response" action is considered "part" of the "HTTP Connector" and is therefore Premium. Unfortunately, my client's tenant and my company's tenant didn't start to get a licensing popup until about 2 weeks ago so I had no idea that the "Response" action was Premium.
I think my misunderstanding was reasonable given that:
Azure SQL Server is a standard connector
Microsoft’s recommendation on how to return Flow SQL Server action array results to PowerApps is to use the “Response” action
Therefore, I assumed the “Response” action in this instance was “Standard”
In the meantime I have come up with a partial workaround. I can rewrite SQL Server queries and stored procedures in Flow so they will return a list of unique keys via the “Respond to PowerApps” action (which allows only one value or a list of one value, so useless for array purposes). I’ll put these into a collection into PowerApps and then can use the ForAll and/or Filter commands to retrieve the filtered array of SQL Server items I want. However, this won’t solve some of the problems that PowerApps has with understanding SQL Server data types, various delegation issues or complex key situations.
Therefore, I suggest that Microsoft create a new, non-premium action in Flow that will return an array of results from Azure SQL Server actions to PowerApps, similar to how "Response" does now. I think this makes sense because returning results from Azure SQL Server has nothing to do with HTTP, so the current "Response" action is actually an inappropriate way to return Azure SQL Server data to PowerApps.