Windows 11 taskbars are quietly getting three new fixtures: compact, Graph-powered companion apps for people, files, and calendar that launch at startup by default and aim to shave seconds off the hundreds of micro-tasks that fracture a knowledge worker’s day. Microsoft started rolling out the suite through its Beta and Preview channels earlier this year, and as of late October 2025, the apps will install automatically on any Windows 11 device with Microsoft 365 desktop apps—unless an admin intervenes.
The People, File Search, and Calendar companions aren’t meant to replace Outlook, Teams, or OneDrive. They’re purposefully narrow taskbar utilities, originally previewed at Ignite 2024, that surface directory lookups, document search, and meeting joins in a single click. Microsoft calls them “micro-experiences” designed to reduce context switching, and early feedback from IT teams already piloting them reveals both genuine productivity wins and a checklist of configuration headaches that demand attention before broad deployment.
Three Small Apps, One Big Idea
Each companion occupies a fixed slot on the Windows 11 taskbar and pulls data exclusively from Microsoft Graph, meaning results respect existing tenant permissions. There’s no new data store; the apps simply present what users could already reach through a browser or desktop client—just faster and with less friction.
People companion acts as a system-wide directory query tool. Type a name and get a rich profile card with presence, working hours, contact methods, and an org-chart view. One click can start a Teams chat, call, or email—provided the user is licensed for Teams. Without that license, the companion degrades to a read-only directory lookup. A favorites list lets users pin frequent collaborators for instant access.
File Search companion attacks the “where did I save that?” problem across OneDrive, SharePoint, Teams, and Outlook attachments. It supports full-text search, filters for author, file type, and recency, and offers inline previews with share-or-copy-link actions. Notably, it indexes only Microsoft 365-stored content; local files and third-party cloud repositories are excluded. The search respects SharePoint and OneDrive sharing controls, so no one sees a file they shouldn’t.
Calendar companion squeezes an agenda and day view into a taskbar pop-up. Users can scroll through upcoming events, search by title or attendee, and join Teams meetings with one click. It handles lightweight interactions—glance, join, copy link—leaving heavy calendar management to the full Outlook client.
All three companions require Exchange Online and SharePoint Online service plans. The official license prerequisites are listed in Microsoft’s documentation, but the practical takeaway is straightforward: any user on a Microsoft 365 E3, E5, Business Premium, or equivalent plan that includes those online services can use the full suite. Missing plans mean limited functionality; for example, the People companion won’t offer calling features if Teams is absent.
The Rollout: Channel by Channel
Microsoft’s rollout cadence has been staggered and somewhat confusing. According to the company’s own community blog and early adopter reports, the companions first landed in the Beta Channel on April 1, 2025. A wider Preview Channel rollout followed on June 5, 2025, and a broader business rollout—presumably Current Channel—started in August 2025.
However, the official Microsoft Learn overview, updated in October 2025, states that “starting late October 2025, Windows 11 devices that have Microsoft 365 Apps will automatically install the companion apps as part of the update process.” This discrepancy likely reflects the difference between opt-in preview channels and the automatic, silent install that will hit all eligible devices when Microsoft flips the switch for general availability. IT teams who haven’t seen the apps yet should expect them to arrive as part of the October-November update cycle.
Users can download the companion apps manually now via the Microsoft Store or a standalone installer if they want to jump the line. For organizations that prefer a phased test, Microsoft recommends manually deploying the installer through Intune or another software distribution tool before the automatic rollout kicks in.
Automatic Install, Autostart, and the Admin Opt-Out
The default behavior will ruffle feathers in managed environments. On an eligible Windows 11 PC, the three companions install silently in the background and configure themselves to auto-launch at user login. Microsoft’s rationale is that a pre-warmed app delivers instant results when clicked, but that adds three more processes to the startup sequence and increases the background service footprint.
End users can disable autostart per app from within the companion’s own settings. For admins, the primary control is a single checkbox in the Microsoft 365 Apps admin center: uncheck “Enable automatic installation of Microsoft 365 companion apps” under Customization > Device Configuration > Modern Apps Settings. Crucially, that toggle only prevents future automatic installs; it does not remove companions already present on devices. To clean up existing installations, IT teams will need to script uninstalls or rely on endpoint management policies.
Taskbar pinning can be managed through the “Pin Copilot + Companions” setting in the admin center, or via traditional Group Policy/Intune configurations for Windows 11 taskbar layout. Admins who want the apps on every taskbar but dislike the default autolaunch can leave the installation checkbox enabled and separately manage startup behavior through policy, though Microsoft’s documentation strongly recommends allowing autostart for the best user experience.
Performance Footprint: Lightweight, but Not Weightless
Microsoft describes the companions as “lightweight” and built with a self-contained update system independent of Office update channels. In practice, early pilot measurements show the apps consume between 30–80 MB of RAM each when idle, with CPU spikes during initial sign-in and Graph synchronization. On a modern corporate laptop with 16 GB RAM, that’s negligible. On a virtual desktop with 8 GB RAM shared across multiple users, it’s noticeable enough that some VDI admins are already choosing to block the install.
Startup impact varies by device class. A 2023-era Intel i5 with an SSD sees an extra 1–2 seconds added to login time when all three companions launch. Older spinning-disk machines or those already burdened with other startup items may see a more pronounced delay. Microsoft hasn’t published official performance benchmarks, so peer benchmarking within a pilot group remains the best way to gauge real-world impact.
Battery life on laptops is another open question. While the companions are not constantly animating or polling at high frequency, they do maintain active connections to Microsoft Graph and occasionally update indexed content. IT teams that enforce aggressive power profiles should monitor for unexpected wake events or increased drain during sleep.
Security and Privacy: What the Companions Expose
The companions inherit the security boundaries of Microsoft Graph. File Search only returns documents the signed-in user already has access to; People only shows directory data within the scope of the tenant and any permitted external contacts. Calendar events reflect the user’s own permissions set in Outlook.
But the always-visible nature of a taskbar tool changes the threat surface. On a shared or kiosk device, someone walking by could glimpse a colleague’s upcoming meeting subject or a file preview snippet simply by glancing at the screen. Organizations that handle sensitive data should enforce lock screens and short session timeouts, and consider disabling companions on shared endpoints via policy.
Microsoft’s documentation notes that the Files companion does not automatically share anything—the user must explicitly click “share.” Still, the ease of copying a link or previewing a document might lead to casual sharing that bypasses established collaboration protocols. DLP and conditional access policies should be tested against companion actions. In early testing, the apps appear to respect SharePoint and OneDrive DLP rules, but organizations with strict exfiltration controls should verify that inline previews don’t cache sensitive content locally and that share actions appear in audit logs.
Telemetry is another grey area. The companions use Graph API calls that will show up in Azure AD sign-in logs, but Microsoft hasn’t detailed what diagnostic data the apps themselves send. Security teams should ensure SIEM rules capture companion-related events and that any outbound connections align with the organization’s data residency and privacy commitments.
Six Steps IT Admins Should Take Before Broad Rollout
- Pilot with real workloads. Select a group of 50–200 users across different departments and device types. Measure boot time, memory, and user satisfaction over a two-week period.
- Configure the admin opt-out early. Decide whether your organization wants automatic installs or a manual push. Set the checkbox in the Microsoft 365 Apps admin center accordingly before the late October wave hits.
- Test DLP and sharing controls. Deliberately try to share a file with an unauthorized user and verify that DLP blocks the action. Check that file previews don’t bypass Rights Management protection.
- Adjust session security for shared devices. Enforce lock screen timeouts, disable fast user switching where appropriate, and consider blocking companions via policy on devices used by multiple employees.
- Integrate companions into patch management. Although they update independently, treat them as a regular application in your inventory. Monitor for version bumps and include them in vulnerability scans.
- Communicate clearly with end users. Send a brief announcement explaining what the new taskbar icons are, how to disable autostart if desired, and where to report issues. A short FAQ prevents help desk tickets that start with “what is this new icon?”
Where the Companions Shine—and Where They Fall Short
The productivity promise is real for Microsoft-centric shops. A knowledge worker who looks up a colleague’s availability five times a day, searches for a SharePoint file three times, and joins four Teams meetings can reclaim 5–10 minutes daily just by avoiding full client launches. In organizations with thousands of employees, that adds up to significant capacity.
File Search, in particular, addresses a persistent pain point. Traditional Windows search has never been good at finding content inside Teams chats or deep within SharePoint document libraries. The companion’s unified index, while limited to Microsoft 365, returns results quickly and respects the user’s existing access.
The main gaps are ecosystem lock-in and platform exclusivity. The companions are Windows 11-only and tied to commercial Microsoft 365 licenses. Companies using macOS, ChromeOS, or Linux—even those with Microsoft 365—get no equivalent. And the apps offer no on-premises Exchange or file server integration, making them a non-starter for hybrid environments that haven’t fully migrated to the cloud.
Smaller annoyances include the lack of third-party extensibility. For now, the companion surface is strictly first-party Microsoft. There’s no way for a developer to build a Jira or Salesforce companion that lives beside People and Files, though the industry is watching for any hint that Microsoft might open the model.
The Bigger Picture: Windows as a Hub for Microsoft 365
The companions are the latest signal that Microsoft sees the Windows desktop as the prime surface for Graph-powered experiences. They follow efforts like the revamped File Explorer with OneDrive integration, the Search highlights in the taskbar, and the Copilot+PC push that embeds AI directly into the shell. Each move tightens the coupling between the OS and the cloud tenant, making it harder for end users to imagine a workday without a Microsoft endpoint.
For IT leaders, that deeper integration is a double-edged sword. It delivers measurable efficiency gains but also increases the complexity of managing the endpoint estate. Automatic installs, independent update cadences, and new telemetry streams mean admins can’t afford to ignore the companions. A well-managed rollout, with the opt-out checkbox set appropriately and a robust pilot behind it, lets an organization harvest the productivity wins while keeping its operational house in order.
As the late October 2025 deadline approaches, the clock is ticking for IT teams to decide whether these taskbar helpers are a welcome addition or an unwelcome surprise.