From what I have researched, the outlook connector returns embedded tables as plain text and not in a tabular formatted object.
In order to achieve your use case, you will need to parse the text values into a table structure that can then be later added to excel. I would suggest to parse the values into a lookup table component.
If the email body has information that is not within the embedded table, I would suggest to add a textual marker to the email to indicate when and where the table portion of the email starts and stops, i.e (TABLE STARTS, TABLE ENDS). That way you have a clear indication of where to begin parsing the table values into the lookup table.
You won't be able to push the data from outlook email directly into the lookup table as a source. Instead you will need to design your autx to parse through the text and assign the values to each of the rows and columns to the lookup table according to how the table is designed within the email.
This setup will only work if all tables exported from the email have static number of rows, numberof columns , and field names.