Created a flow which takes Emails from MS Exchange folder - manual trigger- to process 1500 emails or more in cycles of 500 each into SP List which extracts all the metadata data from each email and creates an item with access to attachments, time, date, subject, body of email, importance, read receipt, IsDraft, et al, in columns of the list. It all comes through nice - the only problem is that the registered tenant is 8+ hours in time zone from where currently the user is operating. All activity on Outlook & Exchange primary follows local time - all replied emails et al have the local time and is the established time zone that needs to be used to make sure all matches. In meshing all this with text and voice all data is chronologically sequenced to realize the factual background in any case. Thus, time is a critical component and a very necessary metadata record for any record on the planet. We need to have consistency and reliability in this data point to make the planet move and unfortunately to my amazing surprise MS Flow in Year 2026 has the inability to correct this as there is no space anywhere to enforce the time of the record (which is -8 hours to the tenant location) - than the time of the tenant location (+8 hours) on a .eml file saved in SP Documents- it provides the time of the tenant location in the .eml copy and if printed from there by anyone as a legal record are printing emails with inaccurate time - Time referenced in emails is (-8) hours to the tenant location but the Flow only has the option to allow for tenant location time is what MICROSOFT PowerAutomate support stated yesterday and is a major limitation not addressed.
(a) I need to confirm if this is true- the .eml file of the body of the email picks up the tenant location date and time than the local outlook user date and time where the activity is occurring in Outlook. (b) If this is true is there any workaround? (c) Is there any Microsoft documentation available to explain this phenomenon officially to share with the opposing attorneys and the judge in court to make them realize the different date and time for the .eml saved in Documents of SharePoints will have time +8 hours which makes a difference in a Date as well.
How could you provide two date and time sets (one in the List and one in the .eml body of the email saved in SharePoint being +8 hours ahead- if the Judge were to see both those records, he may believe none. We need to enforce the Outlook email user account time record in the .eml of the body of the email in the shared documents- the list provides a link to open the document .eml and that shows a date and time +8 hours! We need to correct that!! This .eml is produced as an output of the flow and in doing so the FLOW only allows the time from the tenant location to show up on the file when opened.
PROBLEM: There are 3 data points for Date & Time here for the MS Flow described above.
(1) Primary/Original Time as recorded by "Outlook/Exchange" for all communications for this 'user' (uses user time and location) -the right time for all records and needs to be used globally/universally for all records related to this user- this is the time in the user's workflow as in Outlook as well.
(2) The Date & Time that gets populated in a column of the "MS List" to which this Email from Exchange is also populated as .eml in another column per MS Flow- the time here follows the original time as in the Email as in Outlook time and not Tenant account location- this is an isolated data item which provides the Date & Time of the Email and has no other data in the cell and no other data links- it's simply a Date & Time Column in the MS List which is able to pick up the date and time from the Outlook of the user.
(3) THIS IS WHERE THE PROBLEM IS- The email gets filed in the SharePoint folders but when you open it via a link from the list it opens the email and provides a date and time for tenant location and not that of date and time in Outlook user workflow- if someone were to use this email they would print or refernce the body of the email with a link and the time there will be different from what it was in the Outlook user which shows in the MS List column as the time of Outlook user as well.
There needs to be a way to have the email preserved as it was in the Exchange/Outlook from where this file is coming - the same date should be in the .eml as well- very confusing to have multiple time zones with no time zones mentioned and being unrelated to the workflow, as the workflow is local for this user and is referenced in every communication to the user's time zone than the tenant location and this record is different b.w. Outlook, MS List vs SharePoint documents- how can you have two date and time data points for the same item in the same site??????
I am aware i have been repititive in the communication above but want to make sure i am getting the message across- and if someone misundertands these community blogs can go in the wrong direction.Please feel free to ask me questoins. If this does not make sense to folks please let me know and i will upload some screenshots to make it easier to digest.
Thank you for your consideration to this post and possible solution !!
A Date & Time issue in Year 2026 on SharePoint (?)
