Journaling Teams to Smarsh for compliance

%3CLINGO-SUB%20id%3D%22lingo-sub-78514%22%20slang%3D%22en-US%22%3EJournaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-78514%22%20slang%3D%22en-US%22%3EIs%20there%20any%20way%20to%20journal%20all%20teams%20chats%20to%20a%20email%20journal%20address%20for%20compliance%20purposes%3F%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-78514%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdoption%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297083%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297083%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20just%20performed%20a%20POC%20with%2017a-4%20data%20parser%20and%20we'll%20be%20using%20them.%26nbsp%3B%20They%20can%20extract%201-1%20chats%2C%20multi-party%20chats%20and%26nbsp%3Bchannel%20messages.%26nbsp%3B%20They%20don't%20get%20file%20attachments%20yet%20but%201-1%20non-image%20files%20is%20coming%20soon.%26nbsp%3B%20It%20formats%20the%20messages%20into%20EML%20format%20and%20sends%20to%20the%20mailbox%20of%20your%20choice.%26nbsp%3B%20%3CA%20href%3D%22http%3A%2F%2Fwww.17a-4.com%2Fdataparser%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fwww.17a-4.com%2Fdataparser%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-268733%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-268733%22%20slang%3D%22en-US%22%3EI%20got%20my%20information%20from%20Global%20Relay%2C%20and%20we%20have%20been%20following%20up%20and%20have%20reconfirmed%20a%20target%20release%20date%20of%20October%2015th%20(one%20week%20from%20now).%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-268729%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-268729%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20where%20did%20you%20get%20the%20information%3F%20any%20link%3F%20I%20am%20also%20at%20the%20junction%20of%20switching%20off%20teams%20due%20to%20its%20lack%20of%20journal%20features.%20Result%20from%20eDiscovery%20is%20too%20fragmented%20for%20my%20compliance%20to%20be%20useful.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-203289%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-203289%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EIf%20we%20are%20still%20using%20Hybrid%20mode%20with%20Exchange%20On-Premises%2C%20how%20do%20we%20archive%20Teams%20communications%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-191886%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-191886%22%20slang%3D%22en-US%22%3E%3CP%3EFYI%20-%20I%20just%26nbsp%3Bheard%20from%20Global%20Relay%20that%20they%20are%20added%20Teams%20support%20in%20Sept.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-181930%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-181930%22%20slang%3D%22en-US%22%3E%3CP%3E100%25%20agree%20with%20Bill.%20Microsoft%20needs%20to%20do%20more%20research%20and%20read%20what%20exactly%20the%20laws%20and%20regulations%20are.%20Sadly%2C%20we've%20had%20a%20pilot%20of%20Teams%20for%20the%20last%203%20weeks%20but%20at%20this%20point%20its%20somewhat%20useless%20due%20to%20the%20compliance%20issue.%20I%20did%20however%20find%20a%20company%20(not%20Smarsh%20or%20Global-Relay)%20that%20supposedly%20can%20handle%20the%20SEC%20compliance%20backup.%20Hopefully%20we%20can%20work%20it%20out%20because%20Teams%26nbsp%3Bfulfills%20our%20needs%20perfectly.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-181464%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-181464%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20does%20not%20seem%20to%20be%20true.%20It%20seems%20that%20Microsoft%20is%20thoroughly%20confused%20on%20what%20the%20requirement%20is%20for%20most%20SEC%2C%20FINRA%2C%20CFTC%20regulated%20companies%20are.%20The%20capability%20that%20is%20necessary%20is%20to%20be%20able%20to%20journal%20or%20send%20these%20messages%20off%20to%20a%203rd%20party%20data%20retention%20provider%20like%20global-relay%20or%20smarsh%20that%20retains%20these%20but%20also%20provides%20keyword%20and%20other%20heuristics%20to%20provide%20for%20review%20of%20suspect%20messages%20as%20well%20as%20random%20review%20of%20some%20percentage%20of%20messages.%20If%20the%20product%20can%20not%20do%20that%20in%20the%20same%20way%20that%20all%20other%20chat%20systems%20that%20are%20used%20in%20the%20industry%20do%2C%20then%20it%20will%20not%20get%20adopted%20and%20is%20impossible%20for%20us%20to%20use.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-181379%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-181379%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20now%20an%20old%20thread%2C%20Microsoft%20have%20now%20delivered%20on%20providing%20retention%20and%20deletion%20policies%20for%20Teams%20in%20line%20with%20how%20this%20works%20for%20the%20rest%20of%20Office%20365.%20See%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams-Blog%2FRetention-policies-for-Microsoft-Teams%2Fba-p%2F178011%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams-Blog%2FRetention-policies-for-Microsoft-Teams%2Fba-p%2F178011%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-181304%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-181304%22%20slang%3D%22en-US%22%3E%3CP%3EAnother%20user%20here%20looking%20to%20roll%20out%20Teams%20to%20our%20office.%20But%20must%20be%20within%20SEC%20compliance%20first.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELike%26nbsp%3B%26nbsp%3Bsaid%2C%20If%20anyone%20has%20figured%20it%20out%20please%20reach%20out!.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESince%20Skype%20for%20Business%20Cloud%20is%20getting%20phased%20out%20that's%20a%20waste%20of%20time%20to%20look%20at.%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20Slack!%20Atleast%20if%20in%20the%20future%20Teams%20reaches%20compliance%20we%20will%20have%20an%20easier%20time%20with%20user%20acceptance.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-166993%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-166993%22%20slang%3D%22en-US%22%3E%3CP%3EWatching%20this%20thread.%26nbsp%3B%20We%20need%20journaling%20for%20Teams%20as%20well.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'm%20struggling%20to%20set%20proper%20retention%20on%20S4B.%26nbsp%3B%20MS%20Support%20is%20struggling%20right%20along%20with%20me.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20anyone%20has%20that%20one%20figured%20out%2C%20I'd%20love%20to%20talk%20to%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-152493%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-152493%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F37137%22%20target%3D%22_blank%22%3E%40Ansuman%20Acharya%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EIs%20there%20a%20way%20to%20journal%20all%20the%20Teams%20IMs%20to%20external%20email%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAlso%2C%20currently%20Skype%20for%20Business%20IMs%20can%20be%20exported%20into%20Global%20Relay.%20Why%20can't%20Teams%20IMs%20be%20exported%20in%20a%20similar%20fashion%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-152492%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-152492%22%20slang%3D%22en-US%22%3E%3CP%3EI%20did%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F72916%22%20target%3D%22_blank%22%3E%40Michael%20Gorn%3C%2FA%3E.%20We%20don't%20have%20a%20ready%20made%20solution%20for%20this%20right%20now.%20But%2C%20we%20are%20pushing%20to%20add%20this%20as%20part%20of%20our%20extensibility%20play.%20When%20we%20do%20have%20the%20platform%20built%2C%20it%20will%20be%20easy%20to%20just%20extract%20Teams%20data%20via%20the%20Office%20Graph%20and%20listen%20to%20message%20notifications%20and%20so%20forth.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERight%20now%2C%20the%20way%20to%20get%20Teams%20data%20is%20to%20pull%20it%20out%20of%20mailboxes.%20Actiance%20Vantage%20is%20working%20in%20that%20mode.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151946%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151946%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F37137%22%20target%3D%22_blank%22%3E%40Ansuman%20Acharya%3C%2FA%3E%26nbsp%3Bany%20updates%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-143071%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-143071%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F37137%22%20target%3D%22_blank%22%3E%40Ansuman%20Acharya%3C%2FA%3E%26nbsp%3Bdid%20you%20see%20this%20thread%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-142895%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-142895%22%20slang%3D%22en-US%22%3E%3CP%3EThey%20obviously%20care%20exceptionally%20little%20about%20making%20this%20an%20actual%20enterprise%20product%20that%20can%20work%20for%20companies%20with%20any%20kind%20of%20regulatory%20compliance...%20It's%20been%20crickets%20for%20over%20a%20year%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134038%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134038%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F37137%22%20target%3D%22_blank%22%3E%40Ansuman%20Acharya%3C%2FA%3E%26nbsp%3Bdo%20you%20have%20any%20updates%20on%20this%3F%20Have%20you%20seen%20this%20thread%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-112917%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-112917%22%20slang%3D%22en-US%22%3E%3CP%3EYep%20us%20too.%20We%20turned%20off%20teams%20for%20275%20users%20because%20this%20appears%20to%20be%20completely%20stalled.%3C%2FP%3E%3CP%3EBill%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-110637%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-110637%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EWe%20are%20switching%20to%20Slack%20because%20they%20support%20archiving%20to%20Global%20Relay.%20Goodbye%20Teams.%20You%20just%20lost%20150%20users.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-98083%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-98083%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20turning%20off%20teams%20at%20the%20end%20of%20the%20week%2C%20the%20users%20love%20it%2C%20but%20the%20poor%20compliance%20features%20and%20lack%20of%20journaling%20is%20just%20a%20non-starter%20for%20any%20financial%20or%20regulated%20company..%20Really%20unfortunate%20Microsoft%20has%20chosen%20to%20totally%20ignore%20this%20large%20sector%20of%20potential%20users.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-98073%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-98073%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20you%20really%20want%20it%20and%20want%20it%20expidited%2C%20post%20and%20up%20vote%20over%20at%20User%20Voice%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-98072%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-98072%22%20slang%3D%22en-US%22%3E%3CP%3ESadly%20that%20is%20not%20the%20case.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-97631%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-97631%22%20slang%3D%22en-US%22%3E%3CP%3ECurrently%20Global%20Relay%20is%20archiving%20our%20%22Skype%20for%20Business%22%20messages%20that%20are%20also%20stored%20in%20the%20Exchange%20folder%20in%20Outlook.%20They%20are%20doing%20it%20through%20an%20API.%20I%20believe%20they%20should%20also%20be%20able%20to%20grab%20Microsoft%20Teams%20messages%20the%20same%20way.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-94084%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-94084%22%20slang%3D%22en-US%22%3E%3CP%3EYep%2C%20that%20would%20be%20me%20demostrating%20my%20lack%20of%20knowledge%20on%20how%20journaling%20tools%20work.%20If%20they%20use%20an%20EXO%20API%20to%20extract%20the%20information%2C%20then%20you%20should%20be%20able%20to%20do%20it%20because%20the%20API%20is%20how%20you%20do%20eDiscovery%20and%20holds.%20Sounds%20like%20your%20tools%20are%20leaning%20on%20a%20very%20old%20protocol%20that's%20fine%20for%20email%2C%20but%20as%20I%20said%2C%20Teams%20Chat%20in%20an%20EXO%20mailbox%20isn't%20email%2C%20so%20you%20can't%20use%20the%20same%20method%20you've%20always%20used.%20So%20if%20you%20want%20to%20keep%20on%20with%20business%20as%20usual%2C%20you'll%20need%20to%20wait%20for%20your%20third%20party%20to%20complete%20their%20inegration.%20That's%20frustrating%20because%20yeah%2C%20Teams%20is%20an%20outstanding%20tool%20and%20I've%20seen%20some%20really%20excellent%20use%20cases%20for%20Teams%20in%20the%20financial%20industries.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-94083%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-94083%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20the%20inital%20statement%20%22%3CSPAN%3EFrom%20there%20you%20can%20ship%20that%20information%20to%20Global%20Relay%20for%20compliance%20or%20manage%20it%20inplace%20via%20the%20Office%20365%20Security%20and%20Compliance%20Center.%22%20is%20totally%20incorrect%20then.%20There%20is%20no%20support%20to%20ship%20this%20to%20Global%20Relay%20or%20any%20other%20external%20services%20from%20what%20you%20are%20saying%20now%3B%20only%20that%20it%20is%20hypothetically%20possible%20with%20development%20work%20from%20both%20the%20Teams%20group%20and%20the%20vendor.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-94054%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-94054%22%20slang%3D%22en-US%22%3E%3CP%3EWell%20Teams%20Chat%20is%20stored%20in%20a%20%3CSTRONG%3Ehidden%3C%2FSTRONG%3E%20sub%20folder%20under%20Conversation%20History%20in%20Exchange%20Online%2C%20it%20is%20not%20an%20email%2C%20so%20using%20SMTP%20to%20ship%20it%20won't%20work%2C%20hence%20the%203rd%20parties%20working%20on%20intengration.%20The%20Teams%20product%20group%20may%20provide%20vendors%20with%20API%20information%20and%20vendors%20will%20take%20it%20from%20there.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-94050%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-94050%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20the%20first%20I%20have%20heard%20that.%20Both%20Smarsh%20and%20Microsoft%20have%20said%20%22they%20are%20working%20on%20it%22.%20Smarsh%20can%20ingest%20things%20through%20a%20native%20integration%20as%20they%20did%20with%20Lync%20or%20just%20through%20email%20journaling%20which%20is%20how%20slack%20and%20rocket.chat%20do%20it.%20How%20would%20one%20go%20about%20sending%20every%20Teams%20message%20to%20a%20journaling%20connector%20(SMTP)%20to%20do%20it%20the%20most%20basic%20way.%20All%20we%20need%20is%20some%20way%20for%20each%20message%20to%20get%20sent%20to%20our%20journal%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EBill%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-93850%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-93850%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20a%20hidden%20folder%20inside%20the%20Exchange%20Online%20Mailbox%20created%20to%20support%20the%20Team.%20You%20can%20run%20O365%20eDiscvoery%20against%20the%20mailbox%2C%20so%20it%20can%20be%20surfaced.%20I%20don't%20know%20enough%20about%20how%20Global%20Relay%20or%20Smarsh%20pull%20from%20Exchange%20Online%20to%20give%20you%20details%20on%20how%20to%20connect.%20At%20Microsoft%20we%20leave%20everything%20in%20place%20and%20use%20our%20own%20tools%20for%20audit%2C%20compliance%2C%20retention%20and%20discovery.%20From%20the%20perspective%20of%20Teams%2FEXO%2C%20the%20question%20is%20%22Does%20the%20built%20in%20mechinisim%20meet%20the%20regulatory%20standard%3F%22%20That%20I%20do%20not%20know%20the%20answer%20to.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-93777%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-93777%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20say%20you%20can%20send%20it%20to%20GlobalRelay%3F%20Can%20you%20elaborate%2C%20we%20use%20smarsh%20which%20is%20a%20very%20similar%20tool%20and%20could%20use%20Globnal%20Relay%2C%20I%20see%20no%20way%20to%20journal%20from%20teams%20to%20Smarsh%20or%20Global%20Relay%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-93155%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-93155%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20complianve%20features%20of%20Teams%20require%20you%20to%20use%20Exchange%20Online%2C%20see%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FFrequently-asked-questions-about-Microsoft-Teams-%2525E2%252580%252593-Admin-Help-05cbe533-2181-4e95-a4b0-52cd7695fafc%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FFrequently-asked-questions-about-Microsoft-Teams-%2525E2%252580%252593-Admin-Help-05cbe533-2181-4e95-a4b0-52cd7695fafc%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3EIn%20Microsoft%20Teams%2C%20security%20and%20compliance%20features%20like%20eDiscovery%2C%20Content%20Search%2C%20archiving%2C%20and%20legal%20hold%20work%20best%20in%20Exchange%20Online%20and%20SharePoint%20Online%20environments.%20For%20channel%20conversations%2C%20messages%20are%20journaled%20to%20the%20group%20mailbox%20in%20Exchange%20Online%2C%20where%20they're%20available%20for%20eDiscovery.%20If%20SharePoint%20Online%20and%20OneDrive%20for%20Business%20(using%20work%20or%20school%20account)%20are%20enabled%20across%20the%20organization%20and%20for%20users%2C%20these%20compliance%20features%20are%20available%20for%20all%20files%20within%20Teams%20as%20well.%0AImportant%3A%26nbsp%3BUsers%20who%20participate%20in%20conversations%20that%20are%20part%20of%20the%20Chat%20list%20in%20Microsoft%20Teams%20must%20have%20an%20Exchange%20Online%20(cloud-based)%20mailbox%20in%20order%20for%20an%20admin%20to%20search%20chat%20conversations.%20That's%20because%20conversations%20that%20are%20part%20of%20the%20Chat%20list%20are%20stored%20in%20the%20cloud-based%20mailboxes%20of%20the%20chat%20participants.%20If%20a%20chat%20participant%20doesn't%20have%20an%20Exchange%20Online%20mailbox%2C%20the%20admin%20won't%20be%20able%20to%20search%20or%20place%20a%20hold%20on%20chat%20conversations.%20For%20example%2C%20in%20an%20Exchange%20hybrid%20deployment%2C%20users%20with%20on-premises%20mailboxes%20might%20be%20able%20to%20participate%20in%20conversations%20that%20are%20part%20of%20the%20Chat%20list%20in%20Microsoft%20Teams.%20However%2C%20in%20this%20case%2C%20content%20from%20these%20conversations%20isn't%20searchable%20and%20can't%20be%20placed%20on%20hold%20because%20the%20users%20don't%20have%20cloud-based%20mailboxes.%20For%20more%20details%20about%20Content%20Searches%20and%20Microsoft%20Teams%2C%20see%20Microsoft%20Teams%20and%20Office%20365%20Groups.%3C%2FPRE%3E%3CDIV%20class%3D%22ocpAlert%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-92780%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-92780%22%20slang%3D%22en-US%22%3E%3CP%3EChannel%20conversations%20in%20Teams%20is%20stored%20in%20a%20hidden%20folder%20of%20a%20Shared%20Mailbox%20in%20Exchange%20Online.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPerson%20to%20person%20Chat%20is%20stored%20in%20a%20hidden%20subfolder%20of%20Conversation%20History%20each%20participants%20Exchange%20Mailbox.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFrom%20there%20you%20can%20ship%20that%20information%20to%20Global%20Relay%20for%20compliance%20or%20manage%20it%20inplace%20via%20the%20Office%20365%20Security%20and%20Compliance%20Center.%20Since%20if%20you're%20in%20the%20cloud%2C%20conversations%20and%20chat%20are%20retained...FOREVER!!!%20or%20as%20long%20as%20your%20retention%20policy%20says%20you%20have%20to.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20all%20hinges%20on%20a%20minimum%20configuration%20of%20Hybrid%20Exchange%2C%20but%20the%20more%20you%20have%20in%20the%20cloud%2C%20the%20better%20audit%20%26amp%3B%20compliance%20you'll%20have%20with%20it.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-92707%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-92707%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20you%20elaborate%20on%20that%2C%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1292%22%20target%3D%22_blank%22%3E%40Steven%20Collier%3C%2FA%3E%3F%20We%20don't%20use%20Exchange%20Online%20yet%20as%20we%20still%20have%20Exchange%202013%20on-premises.%20We%20journal%20all%20email%20messages%20going%20through%20Exchange%202013%20and%20they%20are%20sent%20offsite%20to%20Global%20Relay%20using%20the%20journaling%20rule.%20How%20do%20we%20journal%20the%20Teams%20content%3F%20Where%20do%20I%20put%20the%20journaling%20rule%20for%20this%20to%20happen%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-90241%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-90241%22%20slang%3D%22en-US%22%3E%3CP%3ETeams%20content%20is%20stored%20in%20the%20mailbox%20and%20sharepoint%20site%20associated%20with%20the%20Team.%20If%20you%20are%20journalling%20them%20then%20you%20already%20have%20the%20Teams%20content.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESee%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FRun-a-Content-Search-in-the-Office-365-Security-Compliance-Center-61852fd9-fe8a-4880-a339-cb19ed3bff4a%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%23teams%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FRun-a-Content-Search-in-the-Office-365-Security-Compliance-Center-61852fd9-fe8a-4880-a339-cb19ed3bff4a%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%23teams%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-90232%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-90232%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20we%20also%20need%20to%20journal%20all%20Microsoft%20Teams%20chats%20and%20other%20messages%20to%20Global%20Relay.%20We%20already%20journal%20our%20Exchange%20messages%20and%20we%20need%20to%20do%20the%20same%20for%20Microsoft%20Teams%20before%20we%20can%20deploy%20it%20to%20our%20users.%20This%20is%20a%20compliance%20requirement.%20Would%20you%20be%20able%20to%20implement%20that%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-78574%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20Teams%20to%20Smarsh%20for%20compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-78574%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20Bill%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20not%20aware%20of%20a%20way%20to%20journal%20teams%20chats%20to%20an%20email%20address%20but%20I%20do%20know%20you%20can%20use%20the%20Security%20and%20Compliance%20Center%20in%20Office%20365%20Admin%20Portal.%20These%20links%20might%20help%20further%20%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FRun-a-Content-Search-in-the-Office-365-Security-Compliance-Center-61852fd9-fe8a-4880-a339-cb19ed3bff4a%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FRun-a-Content-Search-in-the-Office-365-Security-Compliance-Center-61852fd9-fe8a-4880-a339-cb19ed3bff4a%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FRun-a-Content-Search-in-the-Office-365-Security-Compliance-Center-61852fd9-fe8a-4880-a339-cb19ed3bff4a%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%23teams%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FRun-a-Content-Search-in-the-Office-365-Security-Compliance-Center-61852fd9-fe8a-4880-a339-cb19ed3bff4a%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%23teams%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor
Is there any way to journal all teams chats to a email journal address for compliance purposes?
34 Replies

Hey Bill,

 

I'm not aware of a way to journal teams chats to an email address but I do know you can use the Security and Compliance Center in Office 365 Admin Portal. These links might help further https://support.office.com/en-us/article/Run-a-Content-Search-in-the-Office-365-Security-Compliance-...

 

https://support.office.com/en-us/article/Run-a-Content-Search-in-the-Office-365-Security-Compliance-...

 

Yes, we also need to journal all Microsoft Teams chats and other messages to Global Relay. We already journal our Exchange messages and we need to do the same for Microsoft Teams before we can deploy it to our users. This is a compliance requirement. Would you be able to implement that?

Teams content is stored in the mailbox and sharepoint site associated with the Team. If you are journalling them then you already have the Teams content.

 

See https://support.office.com/en-us/article/Run-a-Content-Search-in-the-Office-365-Security-Compliance-...

 

Can you elaborate on that, @Steven Collier? We don't use Exchange Online yet as we still have Exchange 2013 on-premises. We journal all email messages going through Exchange 2013 and they are sent offsite to Global Relay using the journaling rule. How do we journal the Teams content? Where do I put the journaling rule for this to happen?

Channel conversations in Teams is stored in a hidden folder of a Shared Mailbox in Exchange Online. 

 

Person to person Chat is stored in a hidden subfolder of Conversation History each participants Exchange Mailbox. 

 

From there you can ship that information to Global Relay for compliance or manage it inplace via the Office 365 Security and Compliance Center. Since if you're in the cloud, conversations and chat are retained...FOREVER!!! or as long as your retention policy says you have to.

 

This all hinges on a minimum configuration of Hybrid Exchange, but the more you have in the cloud, the better audit & compliance you'll have with it.

 

The complianve features of Teams require you to use Exchange Online, see https://support.office.com/en-us/article/Frequently-asked-questions-about-Microsoft-Teams-%25E2%2580...

 

 

In Microsoft Teams, security and compliance features like eDiscovery, Content Search, archiving, and legal hold work best in Exchange Online and SharePoint Online environments. For channel conversations, messages are journaled to the group mailbox in Exchange Online, where they're available for eDiscovery. If SharePoint Online and OneDrive for Business (using work or school account) are enabled across the organization and for users, these compliance features are available for all files within Teams as well.
Important: Users who participate in conversations that are part of the Chat list in Microsoft Teams must have an Exchange Online (cloud-based) mailbox in order for an admin to search chat conversations. That's because conversations that are part of the Chat list are stored in the cloud-based mailboxes of the chat participants. If a chat participant doesn't have an Exchange Online mailbox, the admin won't be able to search or place a hold on chat conversations. For example, in an Exchange hybrid deployment, users with on-premises mailboxes might be able to participate in conversations that are part of the Chat list in Microsoft Teams. However, in this case, content from these conversations isn't searchable and can't be placed on hold because the users don't have cloud-based mailboxes. For more details about Content Searches and Microsoft Teams, see Microsoft Teams and Office 365 Groups.
 

You say you can send it to GlobalRelay? Can you elaborate, we use smarsh which is a very similar tool and could use Globnal Relay, I see no way to journal from teams to Smarsh or Global Relay

It's a hidden folder inside the Exchange Online Mailbox created to support the Team. You can run O365 eDiscvoery against the mailbox, so it can be surfaced. I don't know enough about how Global Relay or Smarsh pull from Exchange Online to give you details on how to connect. At Microsoft we leave everything in place and use our own tools for audit, compliance, retention and discovery. From the perspective of Teams/EXO, the question is "Does the built in mechinisim meet the regulatory standard?" That I do not know the answer to. 

This is the first I have heard that. Both Smarsh and Microsoft have said "they are working on it". Smarsh can ingest things through a native integration as they did with Lync or just through email journaling which is how slack and rocket.chat do it. How would one go about sending every Teams message to a journaling connector (SMTP) to do it the most basic way. All we need is some way for each message to get sent to our journal

Thanks,

Bill

 

Well Teams Chat is stored in a hidden sub folder under Conversation History in Exchange Online, it is not an email, so using SMTP to ship it won't work, hence the 3rd parties working on intengration. The Teams product group may provide vendors with API information and vendors will take it from there. 

So the inital statement "From there you can ship that information to Global Relay for compliance or manage it inplace via the Office 365 Security and Compliance Center." is totally incorrect then. There is no support to ship this to Global Relay or any other external services from what you are saying now; only that it is hypothetically possible with development work from both the Teams group and the vendor.

Yep, that would be me demostrating my lack of knowledge on how journaling tools work. If they use an EXO API to extract the information, then you should be able to do it because the API is how you do eDiscovery and holds. Sounds like your tools are leaning on a very old protocol that's fine for email, but as I said, Teams Chat in an EXO mailbox isn't email, so you can't use the same method you've always used. So if you want to keep on with business as usual, you'll need to wait for your third party to complete their inegration. That's frustrating because yeah, Teams is an outstanding tool and I've seen some really excellent use cases for Teams in the financial industries. 

Currently Global Relay is archiving our "Skype for Business" messages that are also stored in the Exchange folder in Outlook. They are doing it through an API. I believe they should also be able to grab Microsoft Teams messages the same way.

Sadly that is not the case.

If you really want it and want it expidited, post and up vote over at User Voice https://microsoftteams.uservoice.com/forums/555103-public

We are turning off teams at the end of the week, the users love it, but the poor compliance features and lack of journaling is just a non-starter for any financial or regulated company.. Really unfortunate Microsoft has chosen to totally ignore this large sector of potential users. 

We are switching to Slack because they support archiving to Global Relay. Goodbye Teams. You just lost 150 users.

Yep us too. We turned off teams for 275 users because this appears to be completely stalled.

Bill

 

@Ansuman Acharya do you have any updates on this? Have you seen this thread?