logo
search
Update & Upgrade Problems

How to Manage Microsoft Teams and OneDrive Updates with SCCM

Maira MehtabMaira Mehtab Sep 27, 2026 869 views

Question details

The user wants to know if Configuration Manager (SCCM) can schedule Microsoft Teams and OneDrive updates outside of working hours to reduce network bandwidth consumption.

Product
Microsoft Teams and OneDrive
Device & OS
not provided
Scenario
Scheduling enterprise application updates via SCCM to optimize network usage during business hours.
Observed behavior
Teams and OneDrive updates are user-based and generally ignore machine-wide SCCM deployment schedules.
Before you start

Verify your current SCCM configuration and ensure you have administrative access to your Microsoft 365 deployment policies before adjusting any update rings.

Solution 1Recommended

Address User-Based Update Limitations via Official Channels

Because Teams and OneDrive updates are tied to individual user profiles, they cannot be managed using standard machine-wide SCCM schedules. You must use Microsoft's feedback and Q&A channels to explore custom enterprise workarounds.

Microsoft Teams and OneDrive are designed to update automatically in the background on a per-user basis. Because their executables typically reside in the user's AppData folder rather than Program Files, standard SCCM maintenance windows and software deployment schedules cannot reliably pause or schedule these updates.

To address these deployment challenges, system administrators must rely on Microsoft-specific administrative templates or seek custom deployment scripts from the community.

1
Submit a Feature Request

Navigate to the Microsoft 365 feedback community and submit a formal request for better SCCM scheduling integration for Teams and OneDrive updates to help manage network bandwidth.

2
Consult the Microsoft Q&A Forum

Visit the Microsoft Configuration Manager Q&A section and post your specific deployment scenario. Enterprise specialists and Microsoft engineers can provide custom PowerShell scripts or advanced Group Policy workarounds.

Application Update Mechanics: Teams and OneDrive prioritize individual user experience and security by updating when the application is idle, bypassing traditional centralized deployment tools like SCCM.
Free Microsoft Office alternative

Simplify Your Software Deployment with WPS Office

If user-based updates and complex Microsoft 365 deployment schedules are overwhelming your network, consider switching to WPS Office. It provides a lightweight, highly compatible, and easy-to-manage office suite tailored for modern enterprise deployment.

  1. 1. Download the Installer: Acquire the standard WPS Office installation package designed for quick deployment.
  2. 2. Deploy via SCCM: Easily package and deploy WPS Office across your network using standard Configuration Manager task sequences.
  3. 3. Manage Updates Centrally: Maintain control over your software versions without struggling against forced, user-based background updates.
Fully compatible with Microsoft Word, Excel, and PowerPoint formats.Lightweight installation package minimizes network bandwidth usage during enterprise deployment.Straightforward machine-wide installation simplifies centralized management and updates.Familiar user interface ensures a zero learning curve for your employees.
microsoft office alternative - wps office

Frequently Asked Questions

Why can't SCCM control Microsoft Teams updates?

Microsoft Teams installs natively into the user's local AppData folder rather than a central system directory. It includes its own background update mechanism that runs independently of machine-level SCCM policies and maintenance windows.

Can I use Group Policy (GPO) to control OneDrive updates instead of SCCM?

Yes, you can use OneDrive Administrative Templates (ADMX) in Group Policy to set the update ring (such as Insiders, Production, or Deferred). While this controls the release cadence, it still does not offer strict hour-by-hour scheduling.

Does the Teams Machine-Wide Installer solve this update issue?

No. The Machine-Wide Installer only places the setup files in Program Files. When a user logs in, it still extracts the application to their individual AppData folder, where it resumes updating on a user-by-user basis.