Start free trial
Collaboration Governance

Recommendations for Effective Content Management for Sites & Teams

Recommendations for Effective Content Management for Sites & Teams

The main recommendations for managing content in Microsoft 365 sites and Teams: know which app stores its data in which SharePoint location, limit file versions, use metadata and views to find content, and apply retention so obsolete content is deleted.

We live in a time where collaboration and information sharing are crucial to our daily work lives. It is a good thing Microsoft is there to help out with its Microsoft 365 apps. Their apps, which we use to manage our regular tasks, projects, and communications, have become indispensable. However, with the ease of collaboration and the increase in Microsoft 365 apps comes the challenge of content sprawl.

As teams grow and projects multiply, the volume of documents, videos, notes, and other valuable data scattered across various sites and teams can become overwhelming. Without proper management and protection, this sprawl can lead to inefficiencies, security risks, and productivity issues.

To address these concerns, it is crucial to implement strategies that not only manage but also protect your content. In the first part of this series, we focus on managing your content sprawl in sites and teams. The next article will dive deeper into protecting your content sprawl.

Crucial features for managing your content sprawl

To successfully manage your content sprawl, you need to have an understanding of the following features:

  • Microsoft 365 Groups
  • Versioning
  • Metadata & views SharePoint agents
  • Retention

Microsoft 365 Groups

A team in Microsoft Teams and a team site in SharePoint are both part of the underlying Microsoft 365 Groups architecture. A Microsoft 365 Group is essentially a security group in Entra ID.

Artboard 1_11

Microsoft 365 Groups provide a centralized membership (owners, members, and guests) for specific Microsoft 365 apps. These are, at the moment of writing, the following apps:

  • Planner
  • SharePoint
  • Microsoft Teams
  • Stream
  • Loop
  • Exchange
  • Power BI
  • Office
  • OneNote

All these apps are, in one way or another, connected with a site and team. These apps create their own type of content. To successfully manage this content, it is crucial to understand the type of content that is created and where it is stored.

Artboard 1_6

Let’s dive a bit deeper into a couple of the Microsoft 365 Apps that store their data in the document library of your SharePoint Team Site.

Stream

Microsoft Stream is a fantastic service for recording and streaming (see what I did there) videos and meeting recordings within Microsoft 365. Business users can manually upload videos to OneDrive or SharePoint, but the storage location for meetings depends on a few factors. Are you the organizer of a meeting? The recording is stored in your OneDrive.

Artboard 1_4

Is the meeting organized within a team’s channel?

Artboard 1_2

The recording is stored in the corresponding folder in the SharePoint document library.

Artboard 1_3

OneNote

OneNote has been a steady part of sites & teams since the introduction of Microsoft 365 Groups (I believe it was still called Office 365 Groups). The link can be found in the quick launch menu of the SharePoint Team Site:

Artboard 1_10

Or in a tab within a team in Microsoft Teams:

Artboard 1_9

Be aware: These days, you have to manually add it as a tab first. The Notebook itself is stored in the Site Assets library:

Artboard 1_8

Loop

Loop is a relatively new member of the Microsoft 365 Apps family. Personally, I am a huge fan of Loop, and I can see it taking over OneNote in the near future.

Loop components are created in Copilot Pages, Loop App, Teams channel meetings, Teams channel, Teams private chat, Teams private meeting note, Outlook email message, OneNote for Windows or the Web, and last but not least, Whiteboard. Are you still here? This is a lot, isn’t it?

For the scope of our article, it’s important to remember the following:

  • Components created in standard channels in Teams are stored in the respective channel folder on the associated SharePoint site.
  • Components created in private channels in Teams are stored in the document library of the associated SharePoint site for that private channel.

Now that you are up to date on the storage locations of your favorite Microsoft 365 apps, it is time to look at a couple of strategies to manage the content.

Versioning

The files on your SharePoint Team Site use versioning. Each time a file is modified a new version is created. This can go fast, especially with co-authoring. If multiple people are frequently updating a document, new versions will be created each time they save their changes.

SharePoint is using something called the ‘Delta Storage’ principle. Instead of storing entire copies of a document for each version, SharePoint stores only the changes (deltas) made between versions. This means that if you make a small edit to a document, only that change is stored, not the entire document. That said. More files with hundreds of versions use up more storage in your Microsoft 365 tenant.

To manage versions of your files, you can use the settings of the document library:

Artboard 1_5

Or you configure the settings for new sites in the SharePoint Administration Center:

Artboard 1_1

Microsoft introduced new settings for automatically deleting versions based on either an intelligent algorithm tied to creation data or a specific timeframe. I would advise limiting the number of files to 100. The versioning setting in the SharePoint Administration Center applies only to libraries in new sites. To change the settings of existing sites. You can use PowerShell.

Metadata & views

According to Microsoft, you can store 30 million documents in a document library. We can all agree that’s not a good idea due to the impact on the performance. To successfully influence the performance, you can use metadata and views. In the past, creating and changing views was a painful experience.

Over the years, Microsoft made significant improvements. For example, creating or adjusting your metadata within the library without opening the library settings:

Artboard 1-1

Combined with the filter button, this is a powerful feature: Description automatically generated:

Artboard 1_14

By using metadata, views, and filters, you can find your files more quickly.

SharePoint Agent

Riding on the Microsoft Copilot wave, there is a new feature called SharePoint agents. You can connect an agent to a document library:

Artboard 1_12

You can use the default settings or use Copilot Studio for more advanced settings. That’s something for a follow-up article! After the agent is created, which literally takes 10 seconds, you can start using the prompt:

Artboard 1_15

You get three default prompts (you can change these during the edit process) and directly look for content:

Artboard 1_13

Your organization needs a Microsoft 365 Copilot license to start using SharePoint agents.

Follow this link to learn more about Copilot and agent governance.

Retention

Let’s get something straight. You don’t have to keep all your data forever. There are laws and regulations around certain types of information that you are required to detect, maintain, and or delete.

For the vast majority of business users, it’s impossible to know, or remember, what information needs to be maintained and or deleted. This is where Microsoft Purview Data Lifecycle Management steps in. I advise you to review your internal retention policies and apply them using retention labels and policies. These can be applied manually or automatically.

Before we finish the first part of this article, I want to briefly go back to meeting recordings. These can be automatically deleted after a specified number of days. You can enable this feature in the Microsoft Teams Administration Center:

Artboard 1_7 (1)

After the recording is deleted, the business user who recorded the meeting receives an email notification with the option to recover the deleted recording.

Conclusion

The integration of Microsoft 365 features such as versioning, metadata & views, SharePoint Agents, and retention significantly improves the efficiency of your file management. These features not only streamline your file management but also grant peace of mind by ensuring that essential data is preserved while obsolete information is securely deleted from your Microsoft 365 tenant. By enabling these features, you can maintain an organized and compliant environment that supports your business objectives with greater ease and reliability.

A note from Rencore

The opportunities for sprawl across your M365 tenant increase with every new app or service adopted by business users in your organization, and Rencore helps organizations stay in control of their cloud collaboration technologies.

Specifically, Rencore Governance can inventory all your SharePoint and OneDrive files and automate the complete lifecycle management of your content. You can learn more here.

For a declutter starting point, please download our tenant tidy-up checklist.

Access tidy-up checklist today

Common questions on this

Where are Teams meeting recordings stored?
It depends on who organized the meeting. If you are the organizer, the recording is stored in your OneDrive. If the meeting was organized within a team's channel, the recording is stored in the corresponding folder of the SharePoint document library. Recordings can be deleted automatically after a specified number of days, which you enable in the Microsoft Teams admin center, and the person who recorded the meeting gets an email with the option to recover it.
Where are Loop components stored?
Components created in standard channels in Teams are stored in the respective channel folder on the associated SharePoint site. Components created in private channels are stored in the document library of the SharePoint site associated with that private channel. Because Loop components can be created in many places, from Copilot Pages and Teams chats to Outlook messages and Whiteboard, you need to know the storage location before you decide on permissions, versioning or retention.
How many versions of a file should SharePoint keep?
Every save creates a new version, and this goes fast with co-authoring. SharePoint uses delta storage, so it stores only the changes between versions, but files with hundreds of versions still use more storage in your tenant. A sensible approach is to limit versions to around 100. Set it in the document library settings, or in the SharePoint admin center for new sites. Existing sites need PowerShell, because the admin center setting applies only to libraries in new sites.
Can a SharePoint document library hold millions of files?
According to Microsoft, a document library can store 30 million documents, but that is not a good idea because of the impact on performance. Use metadata, views and filters instead of ever deeper folder structures so people can find files quickly. Microsoft has improved this considerably: you can create or adjust metadata columns inside the library without opening the library settings, and combine them with the filter button to narrow a large library down.
Do I have to keep all my content in Microsoft 365 forever?
No. Laws and regulations require certain types of information to be detected, kept or deleted, but most business users cannot know or remember which ones. Review your internal retention policies first, then apply them with retention labels and policies in Microsoft Purview Data Lifecycle Management, either manually or automatically. Content that no longer has to be kept can then be deleted, which keeps storage under control and the tenant compliant.
What does Microsoft 365 not tell me about the content in my sites and Teams?
The native features manage settings, such as versioning, views and retention, site by site and library by library. SharePoint Advanced Management can flag inactive or ownerless sites. It does not give you one view across Teams, OneDrive, Power Platform and agents with an owner and a lifecycle for each. Rencore Governance can inventory all your SharePoint and OneDrive files and automate the lifecycle management of your content, so sprawl is found and handled at tenant scale.

Last updated 12 November 2026

Related articles

Rencore newsletter

Subscribe to our newsletter

Get the latest insights on governing Microsoft 365, Copilot and AI agents, delivered to your inbox.

Loading form