Files are duplicated when posting in a secure Teams channel

Iron Contributor

A couple of weeks ago my client's Teams started duplicating every file that I posted in a secure channel. That is, I'd write a post, attach a document that was already saved in a Teams folder (via the paperclip icon) and two things happen: 1. The file takes a while to attach as seen by a progress bar, as if it's uploading; and 2. It immediately creates a duplicate of the document into the parent SharePoint folder (that is, the top level secure channel folder). From there, I'll end up working in the original document I had saved in the sub-folder and everyone else who accesses the document via the Post, is using the new version in the parent-level folder. Ok, so I logged a ticket with my client's IT as they do have a very unusual set up for their whole Microsoft environment and to all of us this is a very new issue none of us has heard of before, so they logged a ticket with Microsoft. However, today I tested it in my tenant - and got exactly the same result! This is not a standalone issue - my tenant is set up completely differently to my client's and I suspect we are not even on the same type of business licence (they'd be on enterprise and I'm just a small business). Not only is this weird but we are going insane trying to keep track of the correct versions and archiving all the duplicates. Has anyone seen this? Any ideas on whether there is a new default setting or something happening on microsoft's end? And importantly, any idea how to fix this?

3 Replies
I also noticed this in the NewTeams.
In the previous Teams (classic) the option was provided to use the link to the file instead of the file itself.
This option is still not provided in the NewTeams.
Indeed, it leads to errors, in short, posting with added files cannot be used (for the time being?).

@LizP1 - We noticed this also in our tenant, with "New" and "Old" Teams, but only in "Shared Channels"! When choosing an already uploaded file in the channel folder structure in the post, a copy is created on the highest level. It's not happening in private or normal channels.

Quick update: I logged this Microsoft and had a call with a couple of the Dev team. Apparently this was a known issue to them in random tenants across the world, and a fix was due by end of July. I also logged it via a different tenant and that support team said it was intended, expected behaviour! I explained 'no' and connected them to the other Dev team. I haven't had the issue recently but if it's still happening in your tenant, definitely log an issue and keep pushing until they find the team who is fixing it!