2026 Update Companion Guide: Unleash the Power of Microsoft Teams, SharePoint, OneDrive, Lists and More

What's Changed Since This Session

---

How to Build This Today

Module 1: Teams, Channels, and File Management Setup

The session showed you Module 1: Speakers demoed standing up a Microsoft Team, creating channels, and managing files using the associated SharePoint site, OneDrive, and Teams file tabs. Here's how you'd build that same thing today in April 2026.

The fundamental architecture of Microsoft Teams remains anchored to Microsoft 365 Groups and SharePoint. However, the user interface and file management protocols have matured significantly to support seamless multi-tenant collaboration and AI-driven insights. The platform no longer requires complex manual permission management for external partners, automatically handling backend permissions when users collaborate on shared files and Microsoft Loop components.

Step-by-Step Creation of a Team and Channels

The process for establishing a new collaboration hub requires navigating the refreshed 2026 Teams desktop client. This new interface consolidates multi-tenant activity into a single, unified experience.

• Navigate to the left-hand sidebar of the application. Select the Chat icon if utilizing the combined view, or the Teams icon if utilizing the separate view.
• Locate the New items option situated above the list of active chats and channels, and select it.
• Choose New team from the resulting dropdown menu.
• Enter a unique name for the team and provide a clear description.
• Configure the mandatory Sensitivity Labels. If the organization utilizes Microsoft Purview data classification, select the appropriate label (e.g., "Internal," "Secure"). These labels automatically dictate guest access and encryption policies across the underlying SharePoint backend.
• Select the privacy level: Private for owner-managed membership, or Public for communities open to the entire organization.
• Configure the first channel. While historically locked as the "General" channel, administrators can now customize this initial channel's name during setup or rename it post-creation.
• Select Create to deploy the environment. The platform instantaneously provisions the Microsoft Team, a dedicated SharePoint site, and a shared OneNote notebook.

Quick Win: To manage the inevitable influx of modern cross-channel communications, press Shift + Enter on the keyboard to instantly mark all chat and channel messages as read. For tracking unsent work, utilize the new Drafts icon under the Chat tab to quickly locate unsubmitted messages and files.

Modern File Management and Collaboration

Managing files across Teams, SharePoint, and OneDrive has been significantly streamlined. The introduction of the new multi-tenant, multi-account experience consolidates notifications across different organizational environments into a single feed. Users can seamlessly share files and respond to cross-tenant threads without constantly switching accounts.

Furthermore, privacy and security are prioritized by default. When sharing images containing sensitive location and device details, Teams now automatically removes EXIF metadata from the shared files. Navigation is also more fluid; when users transition between different applications within Teams, the new Pick up where you left off feature in OneDrive ensures they return precisely to their last-viewed location, preserving context and saving time.

Integrating Microsoft 365 Copilot

File discovery and management are now deeply integrated with Microsoft 365 Copilot Chat. This feature is natively accessible across Teams chats, channels, and meetings as of April 2026.14

Instead of manually digging through complex file tabs, users can prompt Copilot to summarize threaded channels, analyze attached documents, or locate specific data points within the team's underlying SharePoint document library. Live meeting indicators now make it easy to see and jump right into active threaded channel meetings, keeping the entire team in the loop while Copilot generates context-aware summaries of the ongoing discussion.

Official Microsoft Documentation:

• (https://support.microsoft.com/en-us/office/create-a-team-from-scratch-in-microsoft-teams-174adf5f-846b-4780-b765-de1a0a737e2b).
• (https://support.microsoft.com/en-us/office/what-s-new-in-microsoft-teams-d7092a6d-c896-424c-b362-a472d5f105de).

---

Module 2: Backend SharePoint Team Site Configuration

The session showed you Module 2: Configuring the backend SharePoint team site for a Team, including site design/customization, permissions/security management, and content organization. Here's how you'd build that same thing today in April 2026.

The era of manually dragging and dropping individual web parts to assemble a SharePoint site is transitioning into a legacy practice. Following SharePoint's 25th anniversary in March 2026, Microsoft launched "AI in SharePoint," fundamentally introducing Agentic Building. This transforms site configuration from a highly technical task into a collaborative, natural language orchestration process.

Step-by-Step Agentic Site Building

Administrators and site owners no longer build from scratch; they co-create with an AI partner powered by large language models, including Anthropic's Claude, integrated directly into the Microsoft 365 ecosystem.

• Navigate to the newly provisioned SharePoint site connected to the Microsoft Team.
• Locate and select the floating action button for AI in SharePoint, which provides context-aware building suggestions based on the user's role.
• Describe the goal of the site using natural language. For example: "Configure this team site as a project tracking hub for the Q3 marketing campaign, prioritizing a library for high-resolution video assets and a list for task assignments.".1
• Review the structured solution plan generated by the AI agent. This plan outlines the proposed architecture, including necessary pages, libraries, lists, and starter content.
• Iterate and refine the plan by conversing with the AI. Prompt the system to adjust column types or metadata fields before generation if the initial layout is insufficient.
• Approve the plan to execute the build. The agentic system performs the heavy lifting, orchestrating the backend creation of sites, pages, and "intelligent libraries".1

Advanced Manual Customization (Flexible Sections)

For organizations requiring granular control over page aesthetics beyond the AI's initial output, the 2026 visual refresh introduces Flexible Sections. This drag-and-drop layout design frees administrators from rigid column constraints.

• Enter Edit mode on the target SharePoint page.
• Edit a section panel to unlock the flexible grid layout.
• Drag and drop web parts freely across the grid.
• Resize section boundaries, group related web parts together, or arrange layers to create overlapping effects, such as placing text web parts directly over image web parts for a modern look and feel.

Content Governance and Security Management

With AI and Copilot deeply embedded across the platform, backend security is paramount. The legacy approach of open permissions is a major organizational risk in 2026, as Copilot will seamlessly surface any overshared content it can access across the tenant. Secure-by-design governance in SharePoint is critical to every agent deployment.

Organizations utilizing Microsoft 365 Copilot licenses must leverage the SharePoint Admin Agent to manage lifecycle and permissions. Administrators can use natural language to analyze tenant-wide permissions and instantly flag oversharing risks.

Furthermore, document libraries now utilize custom AI skills. Instead of forcing users to fill out metadata tags manually, administrators can configure "intelligent libraries" that automatically extract and apply metadata as files are uploaded. This ensures content remains organized and properly governed by organizational standards without manual intervention.

Warning: Prior to full Copilot deployment on a site, it is absolutely critical to enable comprehensive Microsoft Purview Audit logging. Navigate to the Purview center and ensure retention is configured for events such as CopilotInteraction and SearchQueryPerformed. This is vital for maintaining compliance and tracking how AI agents interact with the newly configured SharePoint data.

Quick Win: Utilize the SharePoint Admin Agent to automatically identify and surface inactive sites for cleanup. Simply ask the agent: "Identify all sites without an active owner or activity in the last 90 days," and let the system generate the actionable report.

Official Microsoft Documentation:

• (https://learn.microsoft.com/en-us/sharepoint/get-ready-copilot-sharepoint-advanced-management).
• (https://techcommunity.microsoft.com/blog/spblog/introducing-new-agentic-building-in-sharepoint-and-more-updates/4497987).

---

Module 3: Pre-packaged Teams Apps (Automation without Coding)

The session showed you Module 3: Installing and using pre-packaged Teams apps - Approvals app, Updates app, and Virtual Appointments app for automation without coding. Here's how you'd build that same thing today in April 2026.

The ecosystem of pre-packaged Teams applications has undergone a massive consolidation, shifting away from fragmented single-purpose applications toward centralized, AI-driven automation hubs. Forward-thinking organizations now treat Teams as a seamless container for operational workflows rather than a standalone interface.

The Retirement of Updates and Office 365 Connectors

A critical operational alert for 2026: The legacy Office 365 Connectors service is undergoing final deprecation. The rollout to progressively disable these connectors begins May , 2026, and concludes on May , 2026.3 Consequently, the standalone Updates App and its associated legacy connectors are being fully absorbed into the Workflows App v2.4

To build automated updates and notifications today, the process is streamlined through Power Automate.

• Navigate to the left-hand navigation bar in Teams, click Apps, and select Workflows (which is installed by default and powers the new automation experience).
• To recreate a routine team update prompt, search the redesigned template catalog for "Send webhook alerts to a channel" or select specific update templates.
• Utilize the new natural language-to-flow capabilities. A user can simply type: "Request a weekly status update from the marketing team every Friday at 3 PM and post the results to the General channel".4
• The system automatically provisions the incoming webhook and adaptive card formats required. As of April 2026, this infrastructure fully supports posting to both shared and private channels, as well as the legacy Message Card format for backward compatibility.

Deploying the Approvals App

While the Approvals App remains accessible as a standalone personal app, its integration into the broader Teams channel environment is now heavily mediated through the Workflows infrastructure to leverage Microsoft Dataverse. This design aligns with Microsoft's push for centralized approval management across the entire ecosystem.

• Access the Approvals App via the Teams menu bar. Pin it to the navigation rail for quick access.
• Note that the initial creation of an approval triggers the backend provisioning of the Approval solution within the default Microsoft Dataverse environment. This requires the user to have permissions to create a Dataverse database and an active Power Automate license.
• To build a robust, no-code approval process, attach an Approvals - Start and wait for an approval action within a standard Workflow.
• This integration allows approvers to respond seamlessly directly from an adaptive card within their Teams chat, their Outlook email inbox, or the centralized Approvals center within Power Automate.

Virtual Appointments: Basic vs. Premium

The Virtual Appointments application has been strategically bifurcated to differentiate between standard utility and advanced enterprise capabilities.

• Basic Capabilities (Teams Enterprise): Organizations can still build a standard virtual appointment experience using base licenses. Users can schedule appointments through the Microsoft Bookings integration, and external attendees can join via a mobile browser without downloading the Teams client. Standard features include a basic waiting room and automated email confirmations.
• Advanced Capabilities (Teams Premium required): To replicate the high-end, automated appointment tracking often required by enterprise service centers, the tenant must have Teams Premium licenses. This add-on license unlocks critical features such as SMS text notifications, custom-branded waiting rooms, a comprehensive queue view for on-demand appointments, and advanced organizational analytics.

Quick Win: Do not wait until the late May 2026 deprecation deadline to address legacy integrations. Immediately migrate any legacy webhooks or standalone Update apps. Hover over the options ellipsis next to the target Teams channel, select Workflows, and utilize the "Send webhook alerts to a channel" template to seamlessly generate a modern, compliant Workflows Webhook URL.

Official Microsoft Documentation:

• (https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/).
• (https://learn.microsoft.com/en-us/microsoft-365/frontline/virtual-appointments-app).

---

Module 4: Building an Issue Management App with Microsoft Lists

The session showed you Module 4: Building an issue management app using Microsoft Lists and integrating it into a Team. Here's how you'd build that same thing today in April 2026.

Microsoft Lists remains the premier data-tracking application within the Microsoft 365 ecosystem. However, creating a custom issue tracker no longer requires tedious manual column configuration, formatting rules, or navigating complex template deployments. In 2026, AI-powered capabilities can build, structure, and manage these Lists in mere minutes via natural language interpretation.

Step-by-Step AI List Generation

• Access the Microsoft Lists application via the Microsoft 365 app launcher or directly within a SharePoint modern site.
• Instead of starting from a blank grid or selecting the legacy "Issue Tracker" template, utilize the AI generation prompt interface. Describe the exact parameters of the required tracker.
• Provide a detailed prompt. Example: "Create a software bug issue tracker that includes columns for Issue Title, Severity Level (High, Medium, Low), Assigned Developer, Date Reported, and a Yes/No toggle for resolution status.".11
• The AI automatically generates the underlying schema, configuring the correct column types (Person, Choice, Date, Multiple Lines of Text, etc.) and instantly applies conditional formatting rules (e.g., automatically color-coding "High" severity issues in red).
• Refine custom views instantly. Instruct the AI to generate specific visual layouts. Prompt: "Create a Board view organized by Severity Level, and a Gallery view for easy mobile reading." The system builds these instantly, bypassing manual view configuration.

Integrating Lists into a Teams Channel

Embedding the finished issue tracker directly into the workflow of a Teams channel remains a critical best practice for user adoption and visibility.

• Navigate to the desired channel within Microsoft Teams where the project is managed.
• Select the + (Add a tab) icon located at the top of the channel interface.
• Search for and select the Lists application from the tab dialog box.
• Choose the option to Add an existing list and select the newly generated AI Issue Tracker.
• Ensure the "Post to the channel about this tab" checkbox is selected to automatically generate an announcement in the Teams channel, notifying colleagues that the new tool is available.

Automating the Issue Tracker

To elevate the issue tracker from a static spreadsheet into an automated application, administrators must leverage Quick Steps integrated seamlessly with Power Automate.

• Open the newly created List within Teams or SharePoint.
• Select the ellipsis (...) near the top menu, click Integrate, then select Quick steps, and choose Create a quick step.
• Configure a custom action, such as Execute a flow.
• Provide the unique Flow ID. To find this, navigate to 'My flows' in Power Automate and select 'Get flow identifier' in the export menu. This ID links the List to a specific backend process (e.g., a Power Automate flow designed to email the assigned developer when a high-priority bug is logged).
• Once saved, users can select any item on the list and trigger complex, multi-step backend processes with a single click from the Automate menu.

Warning: When utilizing the "Execute a flow" Quick Step action, users who do not have explicit permission to run the target flow will receive an error message upon attempting to execute the quick step. Administrators must add the list or library as a co-owner on the target flow to properly grant overarching permissions.

Quick Win: Ensure users maximize the new Microsoft 365 Copilot Chat in "work mode." As of February 2026, users can ground their Copilot prompts directly on specific SharePoint lists. A project manager can open Copilot Chat and type, "Analyze the Issue Tracker list and summarize all unresolved High severity bugs assigned to Sarah," instantly querying the live list data without opening the tab. Furthermore, users can easily create a Microsoft Planner task from a list item or file directly in the Copilot app by selecting the "Add to" context menu and choosing "To Do".35

Official Microsoft Documentation:

• Create a quick step for your list or library.
• (https://support.microsoft.com/en-us/office/add-a-sharepoint-page-list-or-document-library-as-a-tab-in-teams-131edef1-455f-4c67-a8ce-efa2ebf25f0b).

---

Licensing Quick Reference

The commercial pricing and packaging architecture for Microsoft 365 undergoes massive updates in 2026. Prices for standard enterprise suites increase globally on July , 2026.15 Concurrently, Microsoft introduces the Microsoft 365 E7 (Frontier Suite) on May , 2026, a comprehensive bundle designed to standardize organization-wide AI and agentic capabilities. Furthermore, as of April , 2026, select features previously gated behind Teams Premium have migrated down to Teams Enterprise licenses to increase baseline value.

The April , 2026, licensing updates also introduced Teams Attendee Capacity Packs, enabling Teams Enterprise users to scale events up to 100,000 participants, replacing the legacy Large Event Assistance Program (LEAP). Additionally, the Microsoft Enterprise Content Delivery Network (eCDN) and advanced organizational branding for meetings are now included directly within the base Teams Enterprise license, shifting them out of the Premium tier. However, administrators must ensure at least one active Teams Premium license remains in the tenant to actively manage Premium feature deployment.