Home

Concerns about Chat History

%3CLINGO-SUB%20id%3D%22lingo-sub-923560%22%20slang%3D%22en-US%22%3EConcerns%20about%20Chat%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-923560%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Everyone%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20is%20a%20thread%20over%20on%20Uservoice%20which%20concerns%20the%20retention%20of%20private%20chat%20conversations.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECurrently%20in%20Skype%20for%20Business%2C%20we%20can%20disable%20the%20capture%20of%20chat%20messages%20completely.%26nbsp%3B%20This%20is%20useful%20in%20organizations%20which%20have%20strict%20policies%20regarding%20transitory%20communications.%26nbsp%3B%20Unfortunately%2C%20Teams%20lacks%20this%20capability.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20most%20recent%20official%20response%20by%20the%20moderator%20is%20wildly%20off-base%20and%20tone-deaf.%26nbsp%3B%20As%20you%20can%20imagine%2C%20users%20are%20rightly%20confused%20and%20highly%20concerned%20about%20the%20current%20state%20of%20the%20product%2C%20especially%20now%20that%20Teams%20has%20a%20firm%20time%20frame%20for%20replacing%20Skype%20for%20Business.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20more%20clarity%20be%20provided%20about%20what%20is%20happening%20with%20the%20retention%20of%20private%20chat%20messages%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%2Fsuggestions%2F33535006-delete-private-chat-threads%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%22%3Ehttps%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%2Fsuggestions%2F33535006-delete-private-chat-threads%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-923560%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdoption%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESettings%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-924602%22%20slang%3D%22en-US%22%3ERe%3A%20Concerns%20about%20Chat%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-924602%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F75197%22%20target%3D%22_blank%22%3E%40Daniel%20Smith%3C%2FA%3E%26nbsp%3BIf%20you%20don't%20have%20any%20active%20retention%20policies%20private%20chat%20messages%20will%20be%20kept%20in%20the%20user%20mailbox%20until%20the%20user%20deletes%20it.%20You%20can%20setup%20retention%20policies%20that%20deletes%20private%20chat%20messages%20after%2030%20days%20(fewer%20days%20will%20be%20supported%20in%20the%20future).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-924769%22%20slang%3D%22en-US%22%3ERe%3A%20Concerns%20about%20Chat%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-924769%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20we%20understand%20that%20the%20best%20we%20can%20do%20is%20to%20delete%20history%20after%2030%20days.%26nbsp%3B%20The%20ability%20to%20delete%20after%2024%20hours%20is%20coming%2C%20but%20not%20ready%20for%20prime%20time.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnfortunately%2C%20in%20our%20industry%2C%20if%20data%20is%20captured%20(at%20all)%20then%20it%20must%20go%20under%20a%20long-term%20retention%20standard.%26nbsp%3B%20Under%20Skype%20for%20Business%2C%20we%20had%20the%20option%20to%20not%20capture%20any%20data%2C%20period.%26nbsp%3B%20The%20current%20architecture%20of%20Teams%20has%20introduced%20a%20mess%20of%20legal%20consequences%20due%20to%20this%20change.%3CBR%20%2F%3E%3CBR%20%2F%3EMany%20of%20the%20proposals%20suggest%20providing%20an%20option%20to%20have%20the%20storage%20of%26nbsp%3B%20all%20chat%20history%20cached%20on%20the%20user's%20local%20device%20rather%20than%20automatic%20storage%20in%20the%20cloud.%26nbsp%3B%20Policies%20can%20then%20be%20applied%20to%20determine%20how%20long%20each%20cache%20is%20retained%20(if%20at%20all).%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20really%20needs%20to%20address%20this%20issue%20with%20Teams.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-924825%22%20slang%3D%22en-US%22%3ERe%3A%20Concerns%20about%20Chat%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-924825%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F75197%22%20target%3D%22_blank%22%3E%40Daniel%20Smith%3C%2FA%3E%26nbsp%3BActually%20it%20will%20not%20be%20after%2024%20hours%2C%20it%20will%20take%20a%20few%20days%20before%20the%20data%20is%20completely%20removed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20have%20the%20option%20to%20turn%20off%20private%20chats%20or%20as%20you%20say%20you%20can%20implement%26nbsp%3B%3CSPAN%3Elong-term%20retention.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIf%20Microsoft%20see%20this%20as%20a%20big%20issue%20for%20on-boarding%26nbsp%3Bcustomers%20to%20Teams%20they%20will%20address%20this.%20I'm%20not%20sure%20that%20the%20uservoice%20you%20posted%20is%20addressing%20the%20issue%20you%20have.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EStoring%20the%20data%20in%20the%20cloud%20is%20the%20only%20way%20for%20companies%20with%20strict%20compliance%20restriction%20to%20have%20control%20over%20the%20data%2C%20if%20it%20was%20stored%20locally%20on%20client%20computers%20only%20that%20would%20not%20be%20possible.%20It%20would%20also%20be%20hard%20to%20solve%20synchronisation%26nbsp%3Bbetween%20different%20clients%20so%20that%20users%20always%20can%20reach%20their%20data.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-928213%22%20slang%3D%22en-US%22%3ERe%3A%20Concerns%20about%20Chat%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-928213%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F75197%22%20target%3D%22_blank%22%3E%40Daniel%20Smith%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%2F64%22%20target%3D%22_blank%22%3E%40Tony%20Redmond%3C%2FA%3E%26nbsp%3Bmay%20have%20some%20input%20here%20but%20to%20my%20knowledge%20nothing%20has%20been%20addressed%20here%2C%20but%20I%20would%20expect%20some%20of%20these%20scenario's%20to%20be%20in%20the%20product%20before%20they%20cut%20off%20Skype%20for%20Business%20assuming%20this%20wasn't%20an%20on-prem%20only%20option%3F%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAnyway%2C%20I%20would%20pay%20close%20attention%20to%20Teams%20security%2Fcompliance%2Fgovernance%20sessions%20at%20ignite%20here%20in%20two%20weeks%20to%20see%20if%20they%20announce%20or%20show%20anything%20on%20the%20roadmap%20that%20might%20mention%20this.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAnd%20if%20by%20chance%20you%20are%20going%2C%20stop%20by%20the%20Teams%20booths%20and%20strike%20some%20conversations%20with%20the%20product%20teams.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-928331%22%20slang%3D%22en-US%22%3ERe%3A%20Concerns%20about%20Chat%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-928331%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F869%22%20target%3D%22_blank%22%3E%40Chris%20Webb%3C%2FA%3E%26nbsp%3BAFAIK%2C%20the%20only%20public%20announcement%20on%20the%20topic%20is%20the%20reduction%20in%20the%20retention%20time%20window%20to%20a%20minimum%20of%2024%20hours.%20As%20has%20been%20pointed%20out%2C%20this%20doesn't%20mean%20that%20compliance%20items%20magically%20disappear%20once%20they%20reach%20a%20day%20old.%20It%20takes%20time%20for%20the%20mechanism%20to%20remove%20items%20from%20EXO%2C%20synchronize%20with%20Teams%2C%20and%20eventually%20disappear.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20this%20is%20a%20real%20big%20issue%2C%20then%20the%20customer%20should%20raise%20it%20with%20their%20Microsoft%20account%20manager%20and%20work%20it%20through%20the%20system.%20Microsoft%20responds%20much%20better%20when%20it%20has%20hard%20evidence%20that%20something%20is%20causing%20a%20real%20problem.%20Right%20now%2C%20the%20stance%20as%20I%20understand%20it%20is%20that%20it's%20good%20to%20capture%20compliance%20records%20because%20so%20many%20customers%20want%20this%20to%20happen.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-928406%22%20slang%3D%22en-US%22%3ERe%3A%20Concerns%20about%20Chat%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-928406%22%20slang%3D%22en-US%22%3EAgree%20Tony%2C%20thanks!%20%3CBR%20%2F%3E%3CBR%20%2F%3EDaniel%2C%20If%20long%20term%20compliance%20is%20a%20requirement%20since%20no%20retention%20might%20not%20be%20an%20option%20yet%2C%20long%20term%20compliance%20is%20really%20easy%20when%20it%20comes%20to%20Teams%20chats%20assuming%20you%20have%20Exchange%20Online%20mailboxes%20that%20is.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-935899%22%20slang%3D%22en-US%22%3ERe%3A%20Concerns%20about%20Chat%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-935899%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F869%22%20target%3D%22_blank%22%3E%40Chris%20Webb%3C%2FA%3E%26nbsp%3BThanks%20to%20everyone%20for%20the%20replies%2C%20this%20is%20very%20helpful.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20agency%20has%20a%20policy%20that%20IM%20may%20only%20be%20used%20for%20transitory%20communications.%26nbsp%3B%20No%20decision-making%2C%20etc.%20shall%20be%20done%20via%20this%20medium.%26nbsp%3B%20Regular%20email%20communications%20are%20retained%20as%20you'd%20expect.%26nbsp%3B%20What%20we've%20found%20is%20that%20having%20IMs%20kept%20private%20has%20created%20a%20%22relief%20valve%22%20of%20sorts%20for%20the%20employees%20where%20more%20informal%20communications%20are%20accepted.%26nbsp%3B%20It%20would%20be%20a%20terrible%20shame%20to%20lose%20this%20capability%20which%20currently%20exists%20with%20Skype%20for%20Business.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Daniel Smith
Occasional Contributor

Hello Everyone,

 

There is a thread over on Uservoice which concerns the retention of private chat conversations.

 

Currently in Skype for Business, we can disable the capture of chat messages completely.  This is useful in organizations which have strict policies regarding transitory communications.  Unfortunately, Teams lacks this capability.

 

The most recent official response by the moderator is wildly off-base and tone-deaf.  As you can imagine, users are rightly confused and highly concerned about the current state of the product, especially now that Teams has a firm time frame for replacing Skype for Business.

 

Can more clarity be provided about what is happening with the retention of private chat messages?

 

Thank you.

 

https://microsoftteams.uservoice.com/forums/555103-public/suggestions/33535006-delete-private-chat-t...

7 Replies

@Daniel Smith If you don't have any active retention policies private chat messages will be kept in the user mailbox until the user deletes it. You can setup retention policies that deletes private chat messages after 30 days (fewer days will be supported in the future).

Yes, we understand that the best we can do is to delete history after 30 days.  The ability to delete after 24 hours is coming, but not ready for prime time.

 

Unfortunately, in our industry, if data is captured (at all) then it must go under a long-term retention standard.  Under Skype for Business, we had the option to not capture any data, period.  The current architecture of Teams has introduced a mess of legal consequences due to this change.

Many of the proposals suggest providing an option to have the storage of  all chat history cached on the user's local device rather than automatic storage in the cloud.  Policies can then be applied to determine how long each cache is retained (if at all).  

 

Microsoft really needs to address this issue with Teams.

@Daniel Smith Actually it will not be after 24 hours, it will take a few days before the data is completely removed.

 

You have the option to turn off private chats or as you say you can implement long-term retention.

 

If Microsoft see this as a big issue for on-boarding customers to Teams they will address this. I'm not sure that the uservoice you posted is addressing the issue you have.

 

Storing the data in the cloud is the only way for companies with strict compliance restriction to have control over the data, if it was stored locally on client computers only that would not be possible. It would also be hard to solve synchronisation between different clients so that users always can reach their data.

@Daniel Smith 

 

@Tony Redmond may have some input here but to my knowledge nothing has been addressed here, but I would expect some of these scenario's to be in the product before they cut off Skype for Business assuming this wasn't an on-prem only option? 

 

Anyway, I would pay close attention to Teams security/compliance/governance sessions at ignite here in two weeks to see if they announce or show anything on the roadmap that might mention this. 

 

And if by chance you are going, stop by the Teams booths and strike some conversations with the product teams. 

@Chris Webb AFAIK, the only public announcement on the topic is the reduction in the retention time window to a minimum of 24 hours. As has been pointed out, this doesn't mean that compliance items magically disappear once they reach a day old. It takes time for the mechanism to remove items from EXO, synchronize with Teams, and eventually disappear.

 

If this is a real big issue, then the customer should raise it with their Microsoft account manager and work it through the system. Microsoft responds much better when it has hard evidence that something is causing a real problem. Right now, the stance as I understand it is that it's good to capture compliance records because so many customers want this to happen.

Agree Tony, thanks!

Daniel, If long term compliance is a requirement since no retention might not be an option yet, long term compliance is really easy when it comes to Teams chats assuming you have Exchange Online mailboxes that is.

@Chris Webb Thanks to everyone for the replies, this is very helpful.

 

Our agency has a policy that IM may only be used for transitory communications.  No decision-making, etc. shall be done via this medium.  Regular email communications are retained as you'd expect.  What we've found is that having IMs kept private has created a "relief valve" of sorts for the employees where more informal communications are accepted.  It would be a terrible shame to lose this capability which currently exists with Skype for Business.

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
35 Replies
Extentions Synchronization
ChirmyRam in Discussions on
3 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
9 Replies