Exporting MS Teams Content from Advanced EDiscovery

%3CLINGO-SUB%20id%3D%22lingo-sub-3002711%22%20slang%3D%22en-US%22%3EExporting%20MS%20Teams%20Content%20from%20Advanced%20EDiscovery%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3002711%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20Teams%20content%20is%20collected%20from%20AeD%20and%20placed%20into%20threaded%20transcripts%2C%20I've%20noted%20there%20have%20been%20many%20challenges%20when%20you%20need%20to%20export%20it%20and%20review%20either%20natively%20or%20in%20a%20review%20platform.%26nbsp%3B%20I've%20listed%20some%20of%20the%20issues%20I've%20come%20across%20and%20wonder%20if%20there%20are%20others%20in%20the%20community%20with%20similar%20views%20and%20how%20they%20have%20resolved%20them.%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3EHTML%20output%20-%20PDF%20was%20removed%20and%20now%20is%20only%20available%20in%20HTML.%20This%20does%20not%20render%20well%20nor%20does%20the%20embedded%20metadata%20for%20a%20thread%20appear%20in%20the%20HTML%20output%20(ie.%20Channel%20name%2C%20thread%20ID%2C%20time%20zone%2C%20etc...).%20Embedded%20Images%2C%20gifs%2C%20and%20emojis%20do%20not%20render%20and%20are%20often%20treated%20as%20attachments%20thus%20making%20it%20difficult%20to%20identify.%20A%20PDF%20output%20is%20needed%20and%20there%20should%20be%20more%20content%20in%20the%20body%20to%20allow%20for%20native%20review.%26nbsp%3B%3C%2FLI%3E%3CLI%3ELoad%20File%20-%20unless%20you%20choose%20to%20export%20to%20PST%20(which%20does%20not%20export%20to%20PST)%2C%20the%20output%20is%20placed%20into%20GUID-named%20HTML%20files%20with%20a%20load%20file%20that%20cannot%20be%20understood%20based%20on%20the%20field%20provided.%20Additionally%2C%20you%20cannot%20easily%20map%20these%20fields%20into%20a%20review%20platform%20because%20they%20are%20not%20recognized.%26nbsp%3B%3C%2FLI%3E%3CLI%3EJoin%2FLeave%20information%20is%20not%20available%20in%20these%20threads.%26nbsp%3B%3C%2FLI%3E%3CLI%3EOutput%20of%20the%20HTML%20files%20and%20attachments%20are%20in%20a%20flat%20output.%20There%20is%20no%20way%20to%20easily%20identify%20if%20a%20threaded%20export%20was%20part%20of%20a%20channel%2C%20sub-channel%2C%20or%20private%20channel%20within%20a%20Team.%20A%20hierarchy%20is%20needed%20to%20help%20identify%20this%20content.%26nbsp%3B%20The%20file%20names%20need%20an%20improved%20naming%20convention%20as%20well%20so%20that%20they%20can%20be%20identified%20by%20TEAM_CHANNEL_DATE%20or%20similar%20means.%26nbsp%3B%3C%2FLI%3E%3C%2FUL%3E%3CP%3EThere%20are%20improvements%20being%20made%20all%20the%20time%2C%20but%20the%20general%20assumption%20is%20that%20AeD%20is%20the%20only%20tool%20that%20should%20be%20used%20for%20O365%20discovery%20is%20a%20bit%20much.%20Organizations%20are%20complex%20and%20need%20options%20when%20on-prem%20and%20cloud%20data%20need%20to%20be%20viewed%20together%20or%20sent%20to%20external%20parties%20for%20processing%20and%20review.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3002711%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdvanced%20eDiscovery%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

When Teams content is collected from AeD and placed into threaded transcripts, I've noted there have been many challenges when you need to export it and review either natively or in a review platform.  I've listed some of the issues I've come across and wonder if there are others in the community with similar views and how they have resolved them. 

  • HTML output - PDF was removed and now is only available in HTML. This does not render well nor does the embedded metadata for a thread appear in the HTML output (ie. Channel name, thread ID, time zone, etc...). Embedded Images, gifs, and emojis do not render and are often treated as attachments thus making it difficult to identify. A PDF output is needed and there should be more content in the body to allow for native review. 
  • Load File - unless you choose to export to PST (which does not export to PST), the output is placed into GUID-named HTML files with a load file that cannot be understood based on the field provided. Additionally, you cannot easily map these fields into a review platform because they are not recognized. 
  • Join/Leave information is not available in these threads. 
  • Output of the HTML files and attachments are in a flat output. There is no way to easily identify if a threaded export was part of a channel, sub-channel, or private channel within a Team. A hierarchy is needed to help identify this content.  The file names need an improved naming convention as well so that they can be identified by TEAM_CHANNEL_DATE or similar means. 

There are improvements being made all the time, but the general assumption is that AeD is the only tool that should be used for O365 discovery is a bit much. Organizations are complex and need options when on-prem and cloud data need to be viewed together or sent to external parties for processing and review. 

0 Replies