How to Organize IT Support Teams for New Microsoft 365 Services
Question details
IT teams need a structured approach to support emerging Microsoft 365 services and develop employee skills accordingly.

- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Planning IT support structures for newly adopted Microsoft 365 applications like Planner, To Do, Loop, and Copilot.
- Observed behavior
- Existing support structures lack clear definitions and training paths for efficiently handling tickets related to newer M365 services.
Before restructuring your support team, audit your current Microsoft 365 licensing to identify exactly which new services your organization is actively using or planning to deploy.
Establish a Phased Support Strategy for Emerging M365 Apps
A structured framework helps correctly route tickets for new services to the right IT tiers and ensures staff are adequately trained.
To effectively support new Microsoft 365 services, IT departments must transition from generic helpdesk models to specialized tier structures.
This involves grouping applications by complexity and function, and ensuring that escalated tickets reach technicians with specific training.
List all newly adopted services. Group them by function, such as Task Management (Planner, To Do), Collaboration (Loop), and AI Services (Copilot).
Assign Level 1 (L1) support to handle basic access, login, and UI questions. Assign Level 2 (L2) and Level 3 (L3) to manage permissions, data governance, and complex integrations.
Evaluate your current IT team's proficiency with the new tools. Identify areas where specialized training or hiring new talent is necessary.
Utilize Microsoft Learn and official documentation to create customized learning paths for your L2 and L3 technicians.
Track ticket resolution times and escalation rates for the new services. Adjust your support structure and training programs based on these metrics as the services evolve.

Simplify Your IT Overhead with WPS Office
Managing support for complex Microsoft 365 services can drain IT resources. Consider WPS Office as a lightweight, free alternative that requires minimal IT support, features a highly familiar interface, and boasts deep compatibility with Microsoft formats.
- 1. Deploy effortlessly: Download and install WPS Office across your organization with a lightweight installer that minimizes deployment friction.
- 2. Ensure seamless adoption: Allow employees to transition easily using a familiar, tabbed interface that requires little to no retraining.
- 3. Reduce support tickets: Benefit from a streamlined ecosystem that minimizes complex administrative overhead and synchronization errors.

Frequently Asked Questions
Which Microsoft 365 services usually require specialized Level 3 support?
Advanced tools like Microsoft Copilot and complex SharePoint/Loop integrations often require Level 3 support due to their data governance, permissions, and security compliance implications.
How can we efficiently train our current support team on Microsoft Loop and Planner?
Utilize the Microsoft Learn platform to create tailored learning paths. Assign team members specific modules related to task management, workspace configurations, and troubleshooting.
What is the best way to handle tickets for newly released M365 features?
Establish a specialized pilot group within your IT team. Route all early-stage tickets to them so they can document solutions and build a comprehensive knowledge base for L1 and L2 teams.
Should we hire new staff or upskill existing IT support for Microsoft 365 AI tools?
Upskilling existing staff is generally more effective, as they already understand your organization's infrastructure. However, hiring a dedicated Microsoft 365 architect may be necessary if your current team lacks foundational cloud architecture experience.




