Hi,

Since yesterday (03/19/24) some users are reporting us that when they move a file with the same name a 1 is appended to the end of the name, instead of showing the conflict window asking the user if they want to keep both files or replace the file.

Expected behavior: if there is a file or folder with the same name, the conflict window is displayed asking if you want to replace or keep both.

New behavior: after some tests a 1 is automatically added at the end of the name.

Was there any bulletin or communication from MS about this change?

Is there any way to change that behavior, via powershell, central administration or user settings?

Hi,

Since yesterday (03/19/24) some users are reporting us that when they move a file with the same name a 1 is appended to the end of the name, instead of showing the conflict window asking the user if they want to keep both files or replace the file.

Expected behavior: if there is a file or folder with the same name, the conflict window is displayed asking if you want to replace or keep both.

New behavior: after some tests a 1 is automatically added at the end of the name.

Was there any bulletin or communication from MS about this change?

Is there any way to change that behavior, via powershell, central administration or user settings?

Lfonteina It sounds like you've encountered an unexpected change in SharePoint Online where the conflict resolution window no longer appears, and instead, files are automatically renamed by appending a '1' at the end.

This change might be due to a recent update or policy adjustment in SharePoint that hasn't been clearly communicated. To tackle this, your first step should be to check the Microsoft 365 Message Center and the Microsoft 365 Roadmap for any announcements related to SharePoint file management. These platforms typically detail updates and changes, which might explain the new behavior you're seeing.

If nothing turns up there, it would be wise to review the settings in the SharePoint and OneDrive admin centers. Occasionally, updates introduce new settings that could affect file handling, and these might have been set by default during a recent update. If you're comfortable with PowerShell, you can also explore using SharePoint Management Shell to see if there are new cmdlets or parameters that allow you to revert to the previous file conflict resolution behavior.

This might involve scripting a solution that reinstates the conflict resolution dialog for end users. Since individual user settings in SharePoint Online generally don't include file handling preferences to this extent, it’s unlikely the change was made there, but it’s always good to confirm there aren’t any overlooked settings. If all else fails, reaching out to Microsoft Support can provide a direct line to more detailed assistance. They can offer insights into whether this behavior is a bug, a feature, or an unintended consequence of another update. Engaging with the SharePoint community through forums like Tech Community can also be helpful.

Other users might be experiencing the same issue and could have already found a workaround or received a fix. Navigating these steps should help clarify why the behavior changed and how you can manage it moving forward.