One key reason for information sprawl in M365 is that users struggle to locate the data they need, prompting them to create their own copies in separate containers, OneDrive, and Teams. When information is replicated across these different applications, new versions are generated continuously, leading to an accumulation of duplicate data. This scenario often escalates to terabytes of information, making it increasingly challenging to find anything relevant. Furthermore, the problem worsens when tools like Co-Pilot consume this scattered data, resulting in skewed responses.

To effectively combat sprawl, it’s essential to address the root cause by establishing a solid information architecture that organizes and houses the data. Additionally, implementing process controls is vital to ensure that containers are properly managed throughout their creation, usage, and disposition phases.