Disable persistant chat/channel history

%3CLINGO-SUB%20id%3D%22lingo-sub-379796%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20persistant%20chat%2Fchannel%20history%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-379796%22%20slang%3D%22en-US%22%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F305426%22%20target%3D%22_blank%22%3E%40josephstacklin%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EIMHO%20I%20don't%20believe%20that%20Teams%20will%20do%20what%20you%20need.%20You%20cannot%20turn%20off%20persistent%20chat%20and%20-%20if%20I%20am%20reading%20your%20requirements%20right%20-%20you%20need%20the%20chats%20to%20delete%20immediately%20after%20you%20have%20them.%20Even%20if%20you%20are%20using%20retention%20policies%2C%20then%20I%20don't%20think%20there%20is%20an%20implementable%20policy%20which%20you%20could%20set%20to%20delete%20the%20chats%20and%20remove%20them%20from%20Office%20365%20immediately%3A%20they%20would%20still%20be%20around%20for%20a%20period%20of%20time.%3CBR%20%2F%3E%3CBR%20%2F%3EAt%20least%20reading%20retention%20policies%20do%20not%20have%20a%20duration%20of%20fewer%20than%2030%20days%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fretention-policies%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fretention-policies%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3ESo%20I%20would%20say%20you%20may%20want%20to%20consider%20a%20third%20party%20application%20for%20chat%20in%20the%20immediate%20future.%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20that%20answers%20your%20question%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-379780%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20persistant%20chat%2Fchannel%20history%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-379780%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F305426%22%20target%3D%22_blank%22%3E%40josephstacklin%3C%2FA%3E%26nbsp%3BBy%20the%20way%20here%20is%20what%20a%20policy%20might%20look%20like.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EConfigure%20locations%20and%20how%20granular%20it%20is%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20811px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F95301i4CD226E11FB3D3EE%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22L1.png%22%20title%3D%22L1.png%22%20%2F%3E%3C%2FSPAN%3E%26nbsp%3BThe%20policy%20settings%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20938px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F95303iA9491C361DC17762%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22T1P.png%22%20title%3D%22T1P.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-379762%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20persistant%20chat%2Fchannel%20history%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-379762%22%20slang%3D%22en-US%22%3E%3CP%3ERetention%20policies%20in%20Microsoft%20Teams%20could%20help%20with%20this%2C%20have%20you%20seen%20those%20yet%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22%3CEM%3ETeams%20conversations%20are%20persistent%20and%20retained%20forever%20by%20default.%20With%20the%20introduction%20of%20retention%20policies%2C%20admins%20can%20configure%20retention%20policies%20(both%20preservation%20and%20%3CU%3Edeletion%3C%2FU%3E)%20in%20the%20Security%20%26amp%3B%20Compliance%20Center%20for%20Teams%20chat%20and%20channel%20messages.%20This%20helps%20organizations%20either%20retain%20data%20for%20compliance%20(namely%2C%20preservation%20policy)%20for%20a%20specific%20period%20or%20%3CU%3Eget%20rid%20of%20data%3C%2FU%3E%20(namely%2C%20%3CU%3Edeletion%20policy%3C%2FU%3E)%20if%20it%20is%20considered%20a%20liability%20%3CU%3Eafter%20a%20specific%20period%3C%2FU%3E.%3C%2FEM%3E%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fretention-policies%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fretention-policies%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-747317%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20persistant%20chat%2Fchannel%20history%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-747317%22%20slang%3D%22en-US%22%3E%3CP%3EThese%20comments%20are%20spot%20on.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20now%20the%20lowest%20option%20on%20the%20retention%20policies%20is%20that%20of%2030%20days.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20need%20something%20for%20shorter%20periods%20(ie%3A%20every%20day)%20-%20the%20best%20option%20might%20be%20via%20Graph%20API.%20You%20can%20delete%20messages%20that%20way%2C%20but%20will%20need%20to%20target%20them%201%20by%201...%20scripting%20it%20to%20grab%20all%20the%20Message%20Thread%20ID's%20from%201%20channel%20and%20delete%20them%20via%20Graph%20and%20have%20it%20run%20every%20day...%20%22might%22%20work.%20But%20this%20is%20all%20very%20far%20fetched%20and%20would%20need%20a%20lot%20of%20testing%20%3A)%3C%2Fimg%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fgraph%2Fapi%2Fresources%2Fteams-api-overview%3Fview%3Dgraph-rest-1.0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fgraph%2Fapi%2Fresources%2Fteams-api-overview%3Fview%3Dgraph-rest-1.0%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fgraph%2Fapi%2Fresources%2Fconversationthread%3Fview%3Dgraph-rest-1.0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fgraph%2Fapi%2Fresources%2Fconversationthread%3Fview%3Dgraph-rest-1.0%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ELogically%20though%2C%20it%20should%20work...%20might%20need%20quite%20a%20bit%20of%20coding%20and%20customization%20though.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESomething%20like%20this%20to%20get%20the%20thread%20list%20from%201%20group%3A%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22has-inner-focus%20focus-visible%22%20tabindex%3D%220%22%20data-focus-visible-added%3D%22%22%3E%3CCODE%20class%3D%22lang-http%22%20data-author-content%3D%22GET%20%2Fgroups%2F%7Bid%7D%2Fthreads%0A%22%3E%3CSPAN%20class%3D%22hljs-attribute%22%3EGET%20%2Fgroups%2F%7Bid%7D%2Fthreads%0A%3C%2FSPAN%3E%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3EThen%20something%20to%20delete%20it%3A%3C%2FP%3E%0A%3CPRE%20class%3D%22has-inner-focus%20focus-visible%22%20tabindex%3D%220%22%20data-focus-visible-added%3D%22%22%3E%3CCODE%20class%3D%22lang-http%22%20data-author-content%3D%22DELETE%20%2Fgroups%2F%7Bid%7D%2Fthreads%2F%7Bid%7D%0A%22%3E%3CSPAN%20class%3D%22hljs-attribute%22%3EDELETE%20%2Fgroups%2F%7Bid%7D%2Fthreads%2F%7Bid%7D%0A%3C%2FSPAN%3E%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOf%20course%2C%20you%20would%20need%20it%20make%20it%20very%20adaptable%20to%20an%20xxx%20number%20of%20threads.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-749045%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20persistant%20chat%2Fchannel%20history%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-749045%22%20slang%3D%22en-US%22%3EThis%20is%20a%20very%20cool%20idea%20using%20the%20Graph%20-%20but%20like%20you%20say%20Marco%20its%20going%20to%20raise%20the%20ongoing%20management.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20guess%20-%20thinking%20about%20it%20-%20that%20in%20order%20to%20implement%20this%20successfully%20you%20would%20at%20least%20need%20to%20lock%20down%20the%20Teams%20creation%20process%20and%20do%20that%20centrally%20-%20and%20then%20make%20this%20part%20of%20the%20setup%20because%20it%20would%20be%20pretty%20much%20a%20nightmare%20to%20let%20users%20create%20teams%20and%20then%20have%20to%20identify%20which%20ones%20don't%20have%20this%20periodically!%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-379741%22%20slang%3D%22en-US%22%3EDisable%20persistant%20chat%2Fchannel%20history%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-379741%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20company%20(for%20legal%20reasons)%20DOES%20NOT%20want%20persistent%20chat%20nor%20do%20they%20want%20to%20keep%20any%20backups%20of%20the%20chats.%20This%20is%20NON-NEGOTIABLE%20as%20legal%20has%20already%20put%20their%20foot%20down.%20Currently%20we're%20using%20Skype%20for%20Business%2FLync%20but%20as%20you%20all%20know%20this%20is%20clunky%2C%20can't%20easily%20be%20integrated%20into%20the%20Azure%20deployment%20(Microsoft%20company%20Portal)%2C%20and%20doesn't%20offer%20the%20quality%20of%20life%20improvements%20(ie%3A%20notifications)%20that%20most%20companies%20need%20in%20this%20day%20and%20age.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20teams%20(or%20a%20script%20on%20our%20Azure%20network)%20be%20set%20to%20auto%20remove%20or%20disable%20entirely%20persistant%20chat%20in%20MS%20Teams.%20To%20be%20clear%2C%20we%20STILL%20WANT%20EMAILS%20TO%20BE%20SAVED%20FOR%207%20YEARS.%20But%20again%2C%20FOR%20NON-NEGOTIABLE%20LEGAL%20REASONS%20we%20cannot%20keep%20chat%20history.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-379741%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-824945%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20persistant%20chat%2Fchannel%20history%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-824945%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2395%22%20target%3D%22_blank%22%3E%40Cian%20Allner%3C%2FA%3E%26nbsp%3BWhere%20did%20you%20find%20this%20retention%20policy%20configuration%3F%20I%20looked%20under%20Security%20and%20Compliance%20and%20I%20don't%20have%20this%20option.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-825090%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20persistant%20chat%2Fchannel%20history%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-825090%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F398989%22%20target%3D%22_blank%22%3E%40AMB202%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENote%20that%20the%20Security%20%26amp%3B%20Compliance%20center%20is%20being%20migrated%20to%202%20separate%20ones%3A%20one%20for%20Security%3B%20one%20for%20Compliance.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20the%20new%20Compliance%20center%3A%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EPolicies%20-%26gt%3B%20Retention%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F128762iBC8977B8EC0C985C%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20will%20actually%20be%20linked%20back%20to%20the%20old%20SCC%20(Security%20%26amp%3B%20Compliance%20Center)%2C%20then%20under%20%22Data%20Governance%22%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F128764i377E5C817627CB89%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22clipboard_image_1.png%22%20title%3D%22clipboard_image_1.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFinally%2C%20you%20will%20have%20the%20typical%20screen%2C%20like%20Cian%20showed%20above.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-896868%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20persistant%20chat%2Fchannel%20history%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-896868%22%20slang%3D%22en-US%22%3EHi!%3CBR%20%2F%3EI'm%20having%20the%20same%20issue%2C%20since%20MSF%20ecosystem%20changes%20every%20month%2C%20I%20was%20questioning%20if%20you%20found%20any%20solution%20to%20clear%20meetings%20from%20the%20%22history%22.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-902481%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20persistant%20chat%2Fchannel%20history%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-902481%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F421271%22%20target%3D%22_blank%22%3E%40Vasco_Ezeq%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20found%20a%20solution%20to%20this%20or%20know%20when%20Microsoft%20will%20be%20updating%20the%20retention%20policies%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20wanting%20chats%20to%20be%20deleted%20every%20day%20vs%20every%2030%20days.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-963972%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20persistant%20chat%2Fchannel%20history%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-963972%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F305426%22%20target%3D%22_blank%22%3E%40josephstacklin%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20customer%20in%20the%20same%20situation.%20They%20do%20not%20want%20any%20persistent%20chat%20out%20of%20concern%20the%20IMs%20could%20later%20be%20used%20in%20a%20court%20of%20law.%20MS%20has%20advised%20they%20are%20working%20on%20a%20reduction%20of%2030%20days%20to%2024%20hours%20for%20holding%20conversations%2C%20but%20even%20with%20this%20change%20it%20still%20doesn't%20meet%20their%20legal%20requirements.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20anyone%20aware%20of%20a%20tool%20through%20MS%20or%20a%20third%20party%20that%20allows%20you%20to%20create%20rules%20around%20content%20and%20redacts%20any%20statements%20that%20contain%20keywords%20as%20defined%20by%20the%20admin%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20in%20advance.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1038849%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20persistant%20chat%2Fchannel%20history%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1038849%22%20slang%3D%22en-US%22%3EGood%20news%20all%2C%3CBR%20%2F%3E%3CBR%20%2F%3EAs%20announced%20at%20Ignite%202019%20earlier%20this%20month%20you%20will%20be%20allowed%20to%20set%201%20day%20retention%20policies%20in%20Teams%2C%20which%20will%20solve%20this%20issue%3CBR%20%2F%3E%3CBR%20%2F%3ESee%20article%20here%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams-Blog%2FWhat-s-New-in-Microsoft-Teams-Microsoft-Ignite-2019%2Fba-p%2F937025%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams-Blog%2FWhat-s-New-in-Microsoft-Teams-Microsoft-Ignite-2019%2Fba-p%2F937025%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20that%20answers%20your%20question!%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1059205%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20persistant%20chat%2Fchannel%20history%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1059205%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F169605%22%20target%3D%22_blank%22%3E%40Christopher%20Hoard%3C%2FA%3E%26nbsp%3Bunfortunately%20they%20are%20not%20allowing%2024%20hour%20retention%20on%20chats.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETeams%20retention%20policies%20do%20not%20yet%20support%3A%3C%2FP%3E%3CUL%3E%3CLI%3EAdvanced%20retention%20policies%20don't%20apply%20to%20Teams%20chat%20and%20Teams%20channel%20message%20locations%3C%2FLI%3E%3CLI%3EDuration%20of%20fewer%20than%2030%20days%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fretention-policies%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fretention-policies%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1123505%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20persistant%20chat%2Fchannel%20history%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1123505%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F305426%22%20target%3D%22_blank%22%3E%40josephstacklin%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20this%20talk%20of%20wiping%20chat%20logs%20and%20such...%20why%3F%3CBR%20%2F%3EOther%20people%20have%20cited%20%22Legal%20Reasons%22%20as%20well%20but%20unless%20your%20discussing%20shady%20stuff%20in%20your%20chat...%20I%20don't%20see%20how%20this%20helps%20because%3A%3CBR%20%2F%3EEveryone%20I%20know%2C%20knows%20how%20to%20take%20a%20screen%20shot.%3CBR%20%2F%3EIf%20they%20want%20to%20use%20something%20said%20in%20a%20chat%20against%20you%20in%20the%20court%20of%20law%20then%20all%20they%20have%20to%20do%20is%20screen%20shot%20it.%3C%2FP%3E%3CP%3EScreen%20shots%20can%20be%20taken%20on%20PC%2C%20on%20tablet%2C%20on%20phone%20and%20you%20have%20no%20way%20to%20protect%20against%20it.%3CBR%20%2F%3EI'd%20say%20if%20you%20are%20relying%20on%20your%20Data%20Retention%20Policy%20to%20CYA%20when%20it%20comes%20to%20a%20chat%20then%20you%20don't%20really%20understand%20how%20modern%20devices%20work...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1059210%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20persistant%20chat%2Fchannel%20history%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1059210%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484669%22%20target%3D%22_blank%22%3E%40mday23%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F169605%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3E%40Christopher%20Hoard%3C%2FA%3E%3CSPAN%3E%26nbsp%3Bunfortunately%20they%20are%20not%20allowing%2024%20hour%20retention%20on%20chats.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EReally%3F%20If%20that%20is%20the%20case%20it%20would%20seemingly%20contradict%20this%20Microsoft%20365%20Roadmap%20item%20as%20well%20as%20their%20own%20announcement%20and%20sessions%20at%20Ignite%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F161014iC70549963B8D073F%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22TeRen.PNG%22%20title%3D%22TeRen.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20said%20previously%20this%20is%20something%20announced.%20It%20will%20be%20here%20in%20the%20near%20future.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBest%2C%20Chris%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

My company (for legal reasons) DOES NOT want persistent chat nor do they want to keep any backups of the chats. This is NON-NEGOTIABLE as legal has already put their foot down. Currently we're using Skype for Business/Lync but as you all know this is clunky, can't easily be integrated into the Azure deployment (Microsoft company Portal), and doesn't offer the quality of life improvements (ie: notifications) that most companies need in this day and age.

 

Can teams (or a script on our Azure network) be set to auto remove or disable entirely persistant chat in MS Teams. To be clear, we STILL WANT EMAILS TO BE SAVED FOR 7 YEARS. But again, FOR NON-NEGOTIABLE LEGAL REASONS we cannot keep chat history.

21 Replies
Highlighted

Retention policies in Microsoft Teams could help with this, have you seen those yet?

 

"Teams conversations are persistent and retained forever by default. With the introduction of retention policies, admins can configure retention policies (both preservation and deletion) in the Security & Compliance Center for Teams chat and channel messages. This helps organizations either retain data for compliance (namely, preservation policy) for a specific period or get rid of data (namely, deletion policy) if it is considered a liability after a specific period."

 

https://docs.microsoft.com/en-us/microsoftteams/retention-policies

Highlighted

@josephstacklin By the way here is what a policy might look like.

 

Configure locations and how granular it is

 

L1.png The policy settings:

 

T1P.png

 

Highlighted
Hi @josephstacklin

IMHO I don't believe that Teams will do what you need. You cannot turn off persistent chat and - if I am reading your requirements right - you need the chats to delete immediately after you have them. Even if you are using retention policies, then I don't think there is an implementable policy which you could set to delete the chats and remove them from Office 365 immediately: they would still be around for a period of time.

At least reading retention policies do not have a duration of fewer than 30 days

https://docs.microsoft.com/en-us/microsoftteams/retention-policies

So I would say you may want to consider a third party application for chat in the immediate future.

Hope that answers your question

Best, Chris

Best, Chris
Highlighted

These comments are spot on.

 

For now the lowest option on the retention policies is that of 30 days.

 

If you need something for shorter periods (ie: every day) - the best option might be via Graph API. You can delete messages that way, but will need to target them 1 by 1... scripting it to grab all the Message Thread ID's from 1 channel and delete them via Graph and have it run every day... "might" work. But this is all very far fetched and would need a lot of testing :) 

 

https://docs.microsoft.com/en-us/graph/api/resources/teams-api-overview?view=graph-rest-1.0

 

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

 

Logically though, it should work... might need quite a bit of coding and customization though.

 

Something like this to get the thread list from 1 group: 

GET /groups/{id}/threads

Then something to delete it:

DELETE /groups/{id}/threads/{id}

 

Of course, you would need it make it very adaptable to an xxx number of threads.

Highlighted
This is a very cool idea using the Graph - but like you say Marco its going to raise the ongoing management.

I guess - thinking about it - that in order to implement this successfully you would at least need to lock down the Teams creation process and do that centrally - and then make this part of the setup because it would be pretty much a nightmare to let users create teams and then have to identify which ones don't have this periodically!

Best, Chris
Highlighted

@Cian Allner Where did you find this retention policy configuration? I looked under Security and Compliance and I don't have this option. 

Highlighted

@AMB202 

Note that the Security & Compliance center is being migrated to 2 separate ones: one for Security; one for Compliance.

 

In the new Compliance center:


Policies -> Retention

clipboard_image_0.png

 

You will actually be linked back to the old SCC (Security & Compliance Center), then under "Data Governance"

 

clipboard_image_1.png

 

Finally, you will have the typical screen, like Cian showed above.

Highlighted
Hi!
I'm having the same issue, since MSF ecosystem changes every month, I was questioning if you found any solution to clear meetings from the "history".
Highlighted

@Vasco_Ezeq 

 

Has anyone found a solution to this or know when Microsoft will be updating the retention policies?

 

We are wanting chats to be deleted every day vs every 30 days.

Highlighted

@josephstacklin 

 

I have a customer in the same situation. They do not want any persistent chat out of concern the IMs could later be used in a court of law. MS has advised they are working on a reduction of 30 days to 24 hours for holding conversations, but even with this change it still doesn't meet their legal requirements.

 

Is anyone aware of a tool through MS or a third party that allows you to create rules around content and redacts any statements that contain keywords as defined by the admin?

 

Thank you in advance.

 

 

Highlighted
Good news all,

As announced at Ignite 2019 earlier this month you will be allowed to set 1 day retention policies in Teams, which will solve this issue

See article here

https://techcommunity.microsoft.com/t5/Microsoft-Teams-Blog/What-s-New-in-Microsoft-Teams-Microsoft-...

Hope that answers your question!

Best, Chris
Highlighted

@Christopher Hoard unfortunately they are not allowing 24 hour retention on chats. 

 

Teams retention policies do not yet support:

  • Advanced retention policies don't apply to Teams chat and Teams channel message locations
  • Duration of fewer than 30 days

https://docs.microsoft.com/en-us/microsoftteams/retention-policies

Highlighted

@mday23 

 

@Christopher Hoard unfortunately they are not allowing 24 hour retention on chats. 

 

Really? If that is the case it would seemingly contradict this Microsoft 365 Roadmap item as well as their own announcement and sessions at Ignite

 

TeRen.PNG

 

As said previously this is something announced. It will be here in the near future.

 

Best, Chris

Highlighted

@josephstacklin 

All this talk of wiping chat logs and such... why?
Other people have cited "Legal Reasons" as well but unless your discussing shady stuff in your chat... I don't see how this helps because:
Everyone I know, knows how to take a screen shot.
If they want to use something said in a chat against you in the court of law then all they have to do is screen shot it.

Screen shots can be taken on PC, on tablet, on phone and you have no way to protect against it.
I'd say if you are relying on your Data Retention Policy to CYA when it comes to a chat then you don't really understand how modern devices work...

Highlighted
Government entities have retention periods they must abide by. This means certain records like documents or email should be deleted after the specified retention. This is to protect those organizations that are forced to provide documents for public records requests. That is why retention is a requirement for chats because with Skype for business you could just disable history. Someone taking screenshots wouldn't be a known record by the organization.
Highlighted

@JoshStinsman 

 

I am not in the legal or governance departments so I am not sure their reasoning. My guess is that they feel that not knowing what is said, even though someone can still screenshot it, is better than dealing with potential fallout from the customers or co-workers raising legal questions. I however, am not sure and do not speak for my company nor their goals as, again, I do not know for certain their reasoning. But with the retiring of Lync in 2021 I hope Microsoft can do something to help us disable persistence. 

Highlighted

Why didn't MSFT simply design it like Skype for Business? In SfB, you can simply go into the app's setting and disable the saving of the conversation. Once you close out of the conversation, it's gone. Whether it's 24 hours or 30 days.

Highlighted

@JoshStinsman 

 

Great point.  People complain because they are given an edict that wasn't thought through and the product doesn't do what they want.  Its a COTS service folks.  If you don't want Persisted Chat, don't use it.  FYI, you can turn off chat in Teams.  But arbitrary demands such as, "I want chat to disappear immediately after the user(s) are done" is plain dumb.  

 

"legal reasons" is an excuse and an indicator that those folks didn't understand what they were buying.  I have had many discussions with various customer legal teams; chat is not informal - no different than email.  If folks are concerned, they should use the encrypted audio.  One day retention on chat is available.  If that doesn't work for you, don't use persisted chat services like WebEx Teams, MSFT Teams, Slack et al.  

 

I wonder if folks apply the same "deal breaker" rules to SharePoint Teams, Yammer, Facebook and others?

Highlighted

@josephstacklin 

 

I hear this is how SnapChat works.