Power Automate Flow moving Attachments in Email to MS List - can it get a Email as an attachment?

Thank you.

"I believe this is a limitation in Power Automate when dealing with emails attached as attachments within another email. While Power Automate can process standard file attachments and metadata, handling an email as an attachment requires additional steps because the attached email is treated as a .eml file, which is not directly supported for extraction or processing in the same way as regular file attachments."

(1) I have searched on MS Learn and other MS sites but cannot find any documentation that confirms this. But see links and screenshots below.....

(2) What would the additional steps be....currently any attachments including images in the body of the emails are extracted by the Flow and populated into the same SP site in the Shared Document library as the MS List is, and provides the name of the attachment as a hyperlink in the SP List column to the attachment to open from the SP Document library. It does not do this for the .eml attachment. The flow is designed to identify in a column of the SP List if the Email coming from Outlook to the SP List (not the Email attachment being referenced here) has any attachment. The Flow recognizes that the Email coming in from Outlook to SP List has .eml attachment as it lists in that column "true" but then does not extract the .eml name into the Attachment column list and does not provides a link to the attachment as other files in the Shared Document library. So it does this for all other documents but not .eml attachments (?).

(3) Appreciate the directions you provide to try but they are unclear for me. If there is any MS documentation to support this it would help or if you can elaborate on these steps. Again, the flow knows the email has an attachment and states True in the MS List column (as explained in (2) above) but in the column of Attachments in the MS List it does not list the .eml attachment as a hyperlink to the attachment, does not extract .eml attachment from the Outlook Email, and is not stored in the Shared Document library. 

(4) It needs to be determined if this is a limitation or a bug or the Flow needs to be edited to do so with a special action for .eml attachments in Power Automate. Infosys support from Microsoft Power Automate is claiming that .eml is considered an item and thus not an attachment; but per MS documents an item is also considered an attachment in the Graph API-see screenshot and links below. Infosys Power Automate M365 support does not clarify further and makes nonsensical excuses to limit support and not clarify the issue here- thus this outreach to the Community.

(5) Another brainwave i had is that if .eml is indeed a limitation from MS for whatever odd reason,what if we added an action item to convert the attached .eml to a pdf and then list in the column and share it in the Document library?

See following links if it helps to explain what I am contemplating. (I have to admit I am not a MS Flow expert but only operate them and utilize techs to build and maintain- my efforts are to realize if this is possible and if not, why not and what is really true. I apologize if anything I state here does not make sense but please free to ask me questions)

Following is a screenshot from a link identified below the screenshot:

Above screenshot from:

https://learn.microsoft.com/en-us/graph/api/resources/attachment?view=graph-rest-1.0

See also:

https://learn.microsoft.com/en-us/graph/api/resources/itemattachment?view=graph-rest-1.0

I also asked CoPilot but it references the following article which does not address the .eml aspect.

https://www.matthewdevaney.com/power-automate-save-email-attachments-to-sharepoint-library/

This article does not address .eml attachments in an Email, but pdfs, jpegs which work fine.

Thank you again for your response. Sincerely appreciated. Hope you can clarify (a) if in reality this is a limitation from MS Flow per documentation from MS or a bug (b) if neither then how to make the correction on the flow- what action item and expressions could get the .eml.

Incomplete datasets can compromise workflows and logic, especially in Healthcare and Legal discovery- I fail to understand why MS makes this a limitation if it is. These are Emails the core of global communications and are coming from Outlook a MS application utilizing a MS application Power Automate to list them in a MS List in a M365 SP site. There are no Apple or any 3rd party products in here- ALL MS.

Generative intelligence - AI will fail if all data is not being moved completely and can compromise Intelligence for humans and workflows. This is a very basic flow to get Emails into a MS list extracting all metadata from the Email into individual MS List columns to appreciate and understand communications with sometimes 1000s of Emails which cannot be done in Outlook- In Outlook you cannot even add and save comments on an email communication- this is so basic 101- a basic need that MS does not provide a working solution for- Commonsense.

In the same MS List there maybe a need to add Text messages, voice calls, Meeting recordings, transcriptions, physical meeting notes, and other sources of communications to provide a commonsense understanding of the full extent of the communications. If Communications data is compromised the logic and discovery from there would be corrupted 101.

To the broader community as well: Does Microsoft provide a platform to condense all data being communicated and exchanged between two or more parties in one concise platform to review which includes Emails, Texts, Chats, Voice mails, Phone calls, Online meetings, Physical meetings, Social media releases et al.....?

Thank you again Kidd_lp and the broader MS Community- always a work in progress as a community!

Look-out!

I believe this is a limitation in Power Automate when dealing with emails attached as attachments within another email. While Power Automate can process standard file attachments and metadata, handling an email as an attachment requires additional steps because the attached email is treated as a .eml file, which is not directly supported for extraction or processing in the same way as regular file attachments.

Try below:

1. Save the attached email (.eml file) to a SharePoint library
2. Extract metadata from the .eml file
3. Link the .eml file in your MS List