"Parse csv" action without third party, privacy concerns

[JoeCrozier]

Right now I have a flow that looks like this:

In short, when a .csv file is saved in a sharepoint drive, it emails me with an html table in the email, showing me what was in the csv.  Works great.

My concern is that my data has to go through a third party action.  That 'encodian' step.  Encodian has a page on data security and to be honest it sounds good, but if someone at my organization saw I was sending data through a third party they might be concerned.  
I guess my question is two fold:
1- I didnt install it or anything myself, it was just there.  Does that mean someone at my organization already put it in our software? And/or its somewhat trusted by Microsoft?
2- Is there an alternative way to do this without using Encodian? Ideally that is about as straightforward? I see articles like this that would probably get me through it but I'll be honest, I barely accomplished this flow and had to ask for help on here and stackoverflow to do it.  Is there a push button step like Encodian but thats not third party?

[takolota · Accepted solution]

It may not be as easy to understand as Encodian, but there is this template where you can insert the dynamic content for the CSV file data, set your parameters, set the expressions for the column numbers you want, & get a JSON output that you can then use Parse JSON on to get the outputs in your dynamic content.

https://powerusers.microsoft.com/t5/Power-Automate-Cookbook/CSV-to-Dataset/td-p/1508191

It’s good if you need to process larger files with more challenging issues like in-data commas.

[AlexEncodian]

@JoeCrozier 

Sorry to hear you don't want to use Encodian. To answer some your first question: someone must have put it into the flow or used a template that included an Encodian action. We do automatically appear on Power Automate because we have been approved and vetted by Microsoft but we do not automatically appear inside flows - someone must have built the flow and selected Encodian (or selected a template).

Note, we are 100% Azure PaaS based so its as close to using a native connector as it can be. We don't use VMs for processing to reduce our costs etc. We use Azure for storage, databases, processing, we use Azure Front Door as our firewall, etc. 

And the way Microsoft architected Power Automate means that your data is never accessed in its source location. It is always uploaded into the flow (e.g. "get file content") and passed from action to action before you have to return it to a source environment e.g. SharePoint by "creating a file" for example. So Encodian will never have access to your company's source environment but of course we will temporarily process what is running through the flow.

[JoeCrozier]

Thank you.  I actually really like it and after having posted this question I ran the security concerns by my supervisor.  She is not worried about those and thinks its fine, BUT we are probably going to run into a usage limit for the free account I created.  It looks like for a free account you get 50 'actions' per month and we're going to hit at least 60.  Probably wont want to upgrade to paid account.  Think I'll look for a non-third party way.