Microsoft 365 Companions on Windows 11: Calendar, File Search, People

Microsoft has quietly begun embedding three new Microsoft 365 “companion” apps into the Windows 11 taskbar — Calendar, File Search, and People — small, focused helpers designed to pull calendar events, corporate files, and contact details one click away from the desktop and reduce time lost to context switching. (learn.microsoft.com)

Background​

Microsoft first previewed the companion concept at Ignite and in Insider channels as a way to bring frequently needed Microsoft 365 information into the Windows shell. The idea is deliberately narrow: deliver a micro-interaction surface so users can look up a colleague, preview a document, or join a meeting without launching full Outlook, Teams, or Office apps. That strategy aligns with Microsoft’s stated goals for tighter Windows–Microsoft 365 integration and reducing workflow friction. (theverge.com)
Microsoft’s official documentation describes the suite as Microsoft 365 companion apps (preview) and lists eligibility, deployment schedule, and admin controls. The rollout has been staged through Beta and Preview channels; public documentation lists Beta availability beginning earlier in 2025 and Preview availability in June 2025. Administrators can opt out of automatic installation via the Microsoft 365 Apps admin center, and end users can stop the apps from auto-launching at login from each app’s settings. (learn.microsoft.com, support.microsoft.com)

---

What the three companion apps do​

Each companion is built to be compact, fast, and confined to a short set of high-value actions. Below is a practical breakdown of capabilities and limits.

Calendar companion — quick meeting control and glanceable schedules​

• Displays your Microsoft 365 calendar in a compact taskbar window so you can view today or agenda views at a glance.
• Lets you join Teams meetings, copy meeting links, edit appointments, and search for meetings by organizer, attendee, or title.
• Supports quick actions such as editing meeting details and opening the full calendar when deeper work is necessary.

The Calendar companion is intentionally not a full-featured calendar client; it is optimized for micro-tasks like joining meetings and checking what’s next. Microsoft notes it reads your Microsoft 365 calendar and respects existing sharing/visibility settings. (learn.microsoft.com)

File Search companion — a single-pane view for Microsoft 365 content​

• Searches across OneDrive, SharePoint, Teams, and Outlook attachments from a unified search box.
• Provides filters for author, file type, recency, and whether someone created/edited/shared a file.
• Offers inline previews so you can confirm a document before opening it in a heavier client, plus direct Share or Copy Link actions.

File Search returns results only for Microsoft 365–hosted content and respects tenant permissions so users see only files they already have access to. The experience is meant to replace a lot of small file-hunting detours into File Explorer or individual Office apps. (learn.microsoft.com)

People companion — fast org lookup and quick contact actions​

• Shows a searchable directory and org chart views so you can look up colleagues by name, role, department, or skill.
• Lets you view presence and working hours, add favorites, and perform one-click actions like starting a Teams chat or beginning a Teams call.
• Sends short “quick messages” via Teams from within the companion; calling and messaging require that the user’s tenant includes Teams licenses.

People is built for very short communications and pre-meeting checks — it’s not intended to replace contact management inside Outlook or a full Teams directory. (support.microsoft.com)

---

How the apps arrive on devices (deployment and requirements)​

Microsoft ties companion app availability to several factors: Windows 11, installed Microsoft 365 desktop apps, tenant update channel, and license SKU.

• Devices must be running Windows 11; Windows 10 is not supported for companions at launch. (learn.microsoft.com)
• The companion apps are distributed through Microsoft 365 update channels. Microsoft documentation lists concrete dates for Beta Channel and Current Channel (Preview) rollouts. Administrators should consult their channel schedules because availability is channel-dependent. (learn.microsoft.com)
• Companions auto-install for eligible systems by default. Admins can disable future automatic installations via the Microsoft 365 Apps admin center (Customization > Device Configuration > Modern Apps Settings), but clearing that option does not uninstall already-installed apps. End users can stop the apps from launching at Windows login inside each app’s settings. (learn.microsoft.com, support.microsoft.com)

Practical implication: IT teams need to check their tenant channel and the admin center configuration to confirm whether companions will show up on managed endpoints and to plan removal or blocking if that’s desired.

---

Administrative controls, enterprise deployment & governance​

For enterprises, companion apps introduce management, compliance, and change-control considerations.

• Admin opt-out: The Microsoft 365 Apps admin center provides a toggle to prevent future automatic installations of the companions; it does not retroactively remove installed apps, so admins must script removal or use device management to uninstall if necessary. (learn.microsoft.com)
• Taskbar pinning and autostart: Admins can influence whether the apps are pinned to the taskbar or automatically start, and users can toggle Auto-Start off inside the app settings. Both levels matter for UX and resource planning. (learn.microsoft.com)
• Update cadence: Companion apps receive updates on a separate cadence from classical Office apps, requiring teams to add them to their update and validation cycles. This separate channeling can complicate patch management.
• Audit and eDiscovery: Actions taken via the companions (like sharing a file or joining a meeting) should surface in tenant audit logs consistent with existing compliance policies, but tenants must validate how inline previews and search indexing interact with eDiscovery and retention rules before enabling broad use. Microsoft says companions respect Microsoft 365 permissions, but governance owners should validate behavior against contractual and regulatory obligations.

Recommended checklist for IT before wide deployment:

• Pilot with a representative group on the same channel you plan to adopt.
• Audit sharing and permissions for SharePoint/OneDrive to reduce accidental exposure via quick previews.
• Update patching playbooks to include the companions’ update cadence.
• Decide on autostart and pinning policy and implement through device management if needed.
• Communicate to users how to disable autostart and how previews work to minimize accidental sharing.

---

Security, privacy, and compliance — what to watch for​

The companions surface sensitive workplace data from Microsoft 365 and therefore bring specific risks and mitigations.

• Permission model: Companions rely on Microsoft Graph and the same permission model as other Microsoft 365 apps — you only see files and calendar items you already have access to. That reduces the chance of unauthorized access, but easier access also increases the chance of accidental exposure (for example, previewing a sensitive file in a public place). (learn.microsoft.com)
• Preview risk: Inline previews let users glance at document contents without opening full apps. This is convenient but raises the risk of shoulder-surfing or accidentally copying sensitive snippets. Organizations with strict screen privacy policies should update user guidance and consider screen-lock or physical privacy filters.
• Telemetry and data residency: Companion features call Microsoft Graph and may rely on indexing or cached metadata. Administrators should validate how that indexing respects data residency rules and how telemetry interacts with compliance logs. If a tenant has tight eDiscovery or retention rules, test companion behaviors before enabling them broadly.
• Licensing and functionality limits: Some actions (e.g., starting Teams calls or quick messaging) require Teams licensing. If Teams is not available in the tenant, the People companion still provides directory info but disables communications features. This avoids surprising breakage but means the full feature set depends on tenant licensing. (support.microsoft.com)

Flagged caveat: Microsoft’s documentation states that companions respect permissions and privacy controls, but the specific interaction of inline previews with third-party eDiscovery tools and certain regulatory workflows may vary by tenant configuration. Verify behavior in an isolated compliance pilot before enterprise roll-out.

---

User experience, performance, and device impact​

The companions are described as “lightweight,” but adding always-on helpers to the taskbar has non-zero consequences.

• Performance: While each companion is designed to be small, they add background processes and network calls to Graph. Devices with lower CPU, memory, or poor connectivity should be tested for real-world impact. Admins should include low-spec machines in pilots to measure resource use.
• Taskbar real estate: Taskbar space is limited; some users will welcome the instant access, while others may see the companions as clutter or duplication of existing apps (Outlook, Teams, File Explorer). Organizations should offer straightforward opt-out instructions to avoid user friction.
• Duplication concerns: The companions deliberately duplicate small aspects of Outlook/Teams. That’s intentional — micro-interactions — but duplicative surfaces can confuse users if the UX doesn’t clearly show when an action opens the heavier client vs. performing the quick action inline. Clear UI affordances and user guidance will reduce confusion.

---

How to manage and get the most out of companions (practical advice)​

For administrators:

• Add the companions to your update tracking and validation lists because they update differently from standard Office apps.
• Use device management to control pinning and uninstallation for managed fleets where policy requires it. (learn.microsoft.com)
• Run a short privacy/compliance pilot focusing on inline preview behavior and audit logging.

For end users:

• If the apps auto-launch and you don’t want them at startup, open the companion’s Settings and toggle Auto-Start at Windows login off. This option is exposed in each app’s Settings. (support.microsoft.com)
• Pin or unpin companions via the right-click taskbar menu to keep your workspace tidy. (techcommunity.microsoft.com)
• Remember that File Search only returns Microsoft 365 files; it will not find local-only or third-party cloud files unless those are surfaced through OneDrive/SharePoint sync. (learn.microsoft.com)

Short list of quick wins:

• Use Calendar companion for one-click meeting joins and to copy meeting links without opening Outlook. (learn.microsoft.com)
• Use File Search to preview documents before launching heavy apps; this reduces memory and context switching. (learn.microsoft.com)
• Use People for pre-meeting checks — who is in the meeting, reporting lines, and presence information. (support.microsoft.com)

---

What’s not yet supported and what remains speculative​

• Mobile versions are not available at launch; Microsoft explicitly says mobile companions are “not yet available,” which leaves open future plans but does not confirm them. Treat mobile support as speculative until Microsoft publishes concrete plans. (support.microsoft.com)
• Third‑party companionship: Microsoft has not documented a third-party developer model for companions at this time. Enterprises that rely heavily on non-Microsoft content sources should not assume those sources will be integrated. If third-party integration is required, maintain alternative workflows.
• AI-driven evolution: Public commentary hints that future companions could tie more deeply into Copilot or other AI services. Any AI-driven proactive behavior would materially change the privacy and governance picture; until Microsoft documents such features, treat them as aspirational and plan accordingly.

---

Critical analysis — strengths, trade-offs, and risks​

Strengths

• Fewer context switches: The companions are likely to reduce the number of short app launches and tab switches, which cumulatively save time and cognitive load over a workday.
• Familiar, focused interactions: Each app focuses on a small set of high-value tasks rather than trying to be a full client — an approach that aligns with observed productivity gains from micro-interaction tooling.
• Consistent enterprise data access: Because companions use Microsoft Graph and tenant identities, they present a consistent, manageable view across devices and sessions. (learn.microsoft.com)

Trade-offs and risks

• Surface duplication and fragmentation: Users may be confused by multiple places to do the same small tasks (Outlook vs. Calendar companion, File Explorer vs. File Search). This duplicative surface can increase calls to helpdesk if not communicated and governed properly.
• Privacy and preview exposure: Inline previews and easier sharing shorten the path to accidental exposure. Organizations handling regulated or sensitive data must treat companions as a change to their threat model.
• Management overhead: A separate update cadence and installation behavior increases the operational surface area for IT teams who must add companions to testing and patching rotations.

Actionable risk mitigations:

• Stage deployments and keep strict pilot criteria tied to compliance and performance metrics.
• Update acceptable use policies and quick-reference user guidance explaining how to disable autostart and hide companions.
• Add the companions to standard vulnerability and update inventories so they’re included in regular patch cycles.

---

Looking ahead — ecosystem implications​

Embedding Microsoft 365 functionality directly into the Windows taskbar is more than a UI convenience; it’s a strategic move to deepen the tie between Windows and Microsoft 365 services. For organizations, that makes Windows 11 more attractive as the primary endpoint for managed knowledge work. For users, the risk is that the taskbar becomes crowded with overlapping experiences.
The longer-term questions are whether Microsoft will:

• Open the companion model to third-party developers, enabling a broader ecosystem of mini-apps in the taskbar.
• Integrate companions with Copilot or other proactive AI to deliver suggestions or actions — a change that would create additional compliance and telemetry considerations.

Until Microsoft publishes further developer guidance or product roadmaps, those possibilities remain plausible but unconfirmed. (theverge.com)

---

Conclusion​

Microsoft’s new Microsoft 365 companion apps for Windows 11 — Calendar, File Search, and People — deliver a targeted approach to shaving small but frequent productivity costs by surfacing meetings, files, and contacts directly in the taskbar. They’re well suited to quick, in-context actions: one-click meeting joins, rapid file previews, and fast org lookups. At the same time, these micro-apps introduce enterprise considerations around deployment control, update cadence, preview privacy, and management overhead that IT teams must treat as part of their standard change-control and compliance processes. (learn.microsoft.com)
For now, organizations should pilot companions on representative devices, validate compliance and eDiscovery behavior, and update user guidance so employees can enjoy the productivity gains without creating new governance or security gaps. The feature set is useful and pragmatic, but adoption should be managed — not automatic — in environments with heightened data sensitivity. (support.microsoft.com)

---

Source: PCMag Microsoft 365 Shortcut Apps Rolling Out in Windows 11: Here's What You Get

 

[ChatGPT]

Microsoft’s latest push to blur the lines between the cloud and the desktop has landed: a trio of lightweight Microsoft 365 “companion” apps — People, File Search, and Calendar — are now appearing in the Windows 11 taskbar for business and enterprise Microsoft 365 customers, offering one-click access to contacts, documents, and meetings without opening full Office clients.

Background​

Microsoft first unveiled the concept of taskbar companion apps for Microsoft 365 at its Ignite conference late last year. The idea was simple: provide contextual, intent-focused micro-apps that let knowledge workers retrieve the most common workplace data (who to contact, where a file lives, when a meeting starts) without breaking flow. After months in beta across Insider and preview channels, Microsoft moved the companions into broader distribution earlier this summer, and vendors and IT teams are now seeing them propagate to Windows 11 devices that have Microsoft 365 apps installed.
These companions are intentionally lightweight. Rather than replacing Outlook, Teams, SharePoint, or OneDrive, they act as targeted entry points that rely on Microsoft Graph and existing Microsoft 365 permissions to surface identity and content. The rollout is automatic on systems tied to eligible Microsoft 365 business SKUs, although administrators can block installation and users can disable autostart if they prefer a cleaner boot profile.

---

What the companions do — an overview​

The three companions focus on the three most frequent interruptions knowledge workers face:

• People: a quick directory and organizational chart viewer that lets users find colleagues, check availability, and initiate Teams chats, calls, or emails without opening a full communication client.
• File Search: a taskbar-based search surface for Microsoft 365 documents that searches OneDrive, SharePoint, Teams, and Outlook, with file previews, filters, and direct sharing links.
• Calendar: a condensed calendar view that shows upcoming events, lets users search appointments, and enables joining meetings from the taskbar.

Each app is designed for short interactions — look up a person, grab a file link, or confirm the next meeting — and then get back to work. They are small by design and auto-launch at login to provide quick access, although that behavior can be changed.

---

People companion: identity fast lanes​

What it offers​

The People companion brings a browsable organizational chart and an enterprise directory to the taskbar. Key capabilities include:

• Search by name, title, department, location, or skills.
• Browse reporting lines in an org chart view.
• View contact cards with phone, email, location, and presence information.
• Start a Teams chat or call, or compose an email directly from a contact card.
• Pin favorites for rapid access.

Because it reads directory data from Microsoft 365 and Azure Active Directory via Microsoft Graph, the People companion surfaces the same profile data already used across Office apps. Presence indicators reflect Teams availability when a Teams license is present.

Strengths​

• Speed: For quick lookup or a fast Teams message, the People companion removes the friction of opening Outlook or Teams.
• Context: The org chart view helps users discover who to contact for a given project or function without switching apps.
• Consistency: It uses Microsoft’s existing identity backend, so profile data stays consistent across the estate.

Caveats and risks​

• Dependency on directory hygiene: The companion’s usefulness is tied directly to the accuracy of Azure AD profile data. Poorly maintained job titles, missing reporting information, or outdated contact details will degrade the experience.
• Privacy and visibility concerns: Because the app surfaces directory information, organizations must validate that the displayed fields and presence markers align with privacy policies and employee expectations.
• License gating: Some presence and communication pathways depend on Teams licensing; users without Teams access may see limited functionality.

---

File Search companion: targeted document retrieval​

What it offers​

The File Search companion is a focused search tool that queries Microsoft 365 storage locations — OneDrive, SharePoint, Teams files, and attached documents in Outlook — using filename, author, or keyword. Notable features include:

• Fast indexed search across Microsoft 365 content.
• File previews inline within the taskbar UI.
• Filters for file type, author, and date to narrow results.
• One-click copy/share link generation and the ability to open a document in its native web or desktop app.

This app is meant for short retrieval tasks: find that spreadsheet, grab the link to the latest deck, or preview a document to confirm it’s the right version.

Strengths​

• Contextual retrieval: Because File Search focuses solely on Microsoft 365 assets and respects existing permissions, users get targeted, relevant results.
• Preview + share: The ability to preview and generate share links from the taskbar speeds up collaboration workflows without switching context.
• Lower cognitive overhead: The stripped-down interface reduces noise compared to a full SharePoint or OneDrive web experience.

Caveats and risks​

• Scope limitation: File Search currently indexes Microsoft 365 content. Local non-Microsoft documents and third-party cloud stores do not appear in results.
• Permissions surface: While the companion respects Microsoft 365 permissions, users may attempt to access or share links to sensitive files more casually because the barrier to sharing is lower. Guardrails and training are essential.
• Performance and indexing: Organizations should evaluate indexing behavior for large tenants; although companions are small, search performance relies on service-side indexing and Graph queries.

---

Calendar companion: quick scheduling and meeting joins​

What it offers​

The Calendar companion offers a compact view of a user’s Microsoft 365 calendar directly from the taskbar. Primary capabilities include:

• A condensed day or week view.
• Search for appointments and meetings.
• One-click join for Teams meetings, and the ability to view meeting details without launching Outlook.

It’s intended for users to confirm upcoming commitments or jump into a meeting quickly, preserving visual context on the desktop.

Strengths​

• Reduced friction for meeting joins: The calendar peek reduces the number of steps to join a meeting, which is useful when switching tasks frequently.
• Lightweight schedule checks: Quick access to next meetings and times helps minimize desktop task switching.

Caveats and risks​

• Functionality overlap: The Calendar companion duplicates functionality available in Outlook and Windows’ native calendar integration, potentially leading to user confusion about which interface to use.
• License and meeting platform dependencies: Full join functionality depends on Teams/meeting provider integration; users relying on other conferencing platforms may not realize functionality is limited.

---

Deployment, admin controls, and IT implications​

How the apps are being distributed​

The companions are rolling out to Windows 11 devices that have Microsoft 365 apps installed and are tied to eligible Microsoft 365 business and enterprise SKUs. Microsoft pushed these apps through Insider channels earlier in the year before expanding to preview and broader release. By default the companions auto-install and autostart after login, but this behavior is configurable.

Administrative controls​

IT administrators have several levers to control the companions:

• Block installation or prevent autostart with management policies and device configuration through enterprise management tools.
• Pinning behavior can be managed by configuring taskbar pin items via group policy or device management profiles.
• Organizations can pilot deployment to a subset of users before mass rollout.

Recommended IT rollout strategy​

• Run a pilot with a representative cross-section of departments to observe user behavior and support implications.
• Validate directory and SharePoint/OneDrive hygiene to ensure the surfaced data is accurate and appropriately permissioned.
• Update endpoint management profiles to control whether the apps auto-install or autostart.
• Prepare help desk and support documentation addressing common questions: uninstalling companions, disabling autostart, and privacy expectations.
• Communicate deployment plans and training to reduce confusion about overlapping features with Outlook, Teams, and Windows search.

---

Security, privacy, and compliance considerations​

Data flow and permissions​

The companions rely on Microsoft Graph to surface identity and content from Microsoft 365. They do not introduce a new backend for storing enterprise data; rather, they query existing services and respect the same permission boundaries. However, because the apps make discovery and sharing easier, organizations must reassess policy and controls around sharing and visibility.

Potential risks​

• Accidental oversharing: Simplified link sharing from the taskbar can enable quicker distribution of files. Without clear guardrails, this can increase the risk of accidental external sharing.
• Surface area for phishing or social engineering: The People companion makes it simpler to find and impersonate colleagues; phishing simulations and awareness training should account for people-discovery tools.
• Startup and telemetry: While lightweight, any app that auto-launches increases startup overhead. Telemetry and logging generated by companions should be understood and documented in acceptable use and monitoring policies.

Mitigations​

• Enforce conditional access and data loss prevention (DLP) policies across Microsoft 365 to ensure that share links and downloads adhere to compliance rules.
• Use endpoint management and Microsoft 365 admin controls to limit automatic installation for sensitive user groups.
• Educate users about best practices for sharing, and maintain a clear policy on whom to contact to report suspicious messages or file requests.

---

User experience and desktop ergonomics​

Productivity gains​

For users who frequently need to look up colleagues, fetch documents, or join meetings, the companions save several seconds per interaction — a small advantage that compounds across a day. The apps are especially valuable during focused work when users want to minimize window switching and context loss.

UX friction and clutter​

The presence of three new icons in the taskbar raises legitimate UX concerns. Many organizations aim to keep the taskbar minimal; automatic pinning and autostart behavior may be unwelcome for users who prefer a streamlined workspace. Administrators should plan pinning behavior carefully and offer guidance for users who want to disable or uninstall the apps.

Overlapping functionality​

Windows already offers multiple entry points to similar data: Start menu search connected to work accounts, Outlook/Teams clients, and the Windows calendar integration. The companions create additional surfaces with overlapping capabilities. This can be a net positive — offering options — but also risks confusing non-technical users and increasing support tickets for account-related errors at login or authentication.

---

Where companions fit relative to Windows Search and Copilot​

The companions are complementary to other Microsoft efforts to surface work-related information on Windows. Windows Search includes work-account integration and already pulls organizational data and files into search results. Separately, Microsoft has advanced a Windows AI search and Copilot integration for semantic and local indexing on Copilot+ devices.

• The companions are taskbar micro-apps optimized for quick, focused tasks and rely on Graph queries and indexing at the cloud level.
• Windows Search and Copilot are broader in scope: Windows Search remains the universal search hub (settings, apps, files, and the web), while Copilot and AI search aim to bring conversational and semantic search, sometimes with local device indexing for privacy-preserving offline experiences.

For IT teams, the key consideration is whether to treat companions as an extension of work-account search or as a separate, user-facing capability that needs its own training, telemetry, and lifecycle management.

---

Real-world reception and early troubleshooting notes​

Early user feedback in community hubs and insider channels shows a mixed reception. Many users praise the speed and convenience, particularly for quick lookups and meeting joins. Other users have reported reliability issues during early testing — error dialogs on first-run, problems signing in when multiple accounts are present on a single device, and confusion over why the apps appeared on personal devices unexpectedly.
Administrators report seeing requests to disable the companions for knowledge workers who prefer minimal taskbar clutter or who use non-Microsoft meeting platforms. Support teams should be prepared for common first-run problems:

• Multiple account confusion: Guide users on how to sign in with the correct work account or remove unintended account tokens.
• App removal: Document how to uninstall the companions and how to disable autostart via Settings or Task Manager.
• Authentication errors: Confirm that device compliance and Conditional Access policies are not blocking companion authentication.

---

Practical guidance: admin and user checklists​

For IT administrators​

• Audit who will receive the companions by mapping eligible Microsoft 365 SKUs and device inventories.
• Configure deployment policy: pilot group -> phased rollout -> enterprise rollout.
• Decide pinning strategy and control with taskbar policy settings.
• Review DLP and sharing policies to account for quicker file sharing paths.
• Update helpdesk knowledge base with step-by-step fixes for sign-in and uninstall scenarios.

For end users​

• If the companions are distracting, disable autostart in the app settings or via Task Manager.
• Pin only the companions you use to reduce visual clutter.
• Use the People app to confirm contact details before sharing sensitive information.
• When sharing files from File Search, double-check permissions on generated links.
• Report unexpected behavior or sign-in problems to IT with screenshots of error messages.

---

Business impact and strategic assessment​

The companions present a low-friction way for Microsoft to embed 365 experiences deeper into Windows 11. For organizations that have invested heavily in Microsoft 365 and prioritize speed and integrated workflows, the companions can deliver small but meaningful productivity wins. They reduce the frequency of full app launches and help keep context during complex tasks.
However, the benefits are not universal. Organizations with strict minimalism in desktop UX, those that use a heterogeneous toolset for meetings and file storage, or companies with heavy privacy and compliance requirements may find the companions add management overhead. The decision to adopt companions should be evaluated alongside existing endpoint management practices and data governance policies.

---

Future directions and what to watch​

The companion model creates opportunities and questions for future evolution:

• Expansion of search scope: Will File Search eventually include non-Microsoft cloud stores or local semantic indexing?
• Third-party integration: Will Microsoft open the companion surfaces to third-party enterprise apps, and if so, how will governance be enforced?
• AI and semantic capabilities: Integration with Copilot and AI search could enable conversational queries (e.g., “find the slide with last quarter’s revenue”), but that raises additional compute, privacy, and licensing considerations.
• Platform consistency: As Windows and Microsoft 365 continue to converge, expect more micro-apps or quick surfaces for common enterprise tasks — but enterprise policy controls and telemetry will need to keep pace.

---

Conclusion​

The Microsoft 365 companion apps for Windows 11 deliver a pragmatic answer to a familiar workplace friction: frequent, short interactions that interrupt focused work. People, File Search, and Calendar provide quick, consistent access to directory information, files, and meetings right from the taskbar, and for many knowledge workers this will shave away frequent context switches and save measurable time over the course of a day.
At the same time, the companions introduce management considerations, overlapping interfaces, and potential privacy and sharing risks that require administrative planning. Organizations that pilot thoughtfully, tighten sharing and DLP rules, and prepare users with clear guidance will realize the benefits while minimizing support and compliance exposure.
In short, the companions are a useful productivity accelerant for Microsoft 365-centric environments — but they are not a drop-in solution for every enterprise. Careful rollout, governance, and user education will determine whether they become a valued convenience or an avoidable source of desktop clutter.

---

Source: Absolute Geeks Microsoft rolls out lightweight office taskbar apps for Windows 11

 

[ChatGPT]

Microsoft has begun rolling out three new lightweight Microsoft 365 “companion” apps — People, File Search, and Calendar — that sit in the Windows 11 taskbar and promise to shave micro‑interruptions out of the modern workday by surfacing contacts, documents, and meetings in a compact, fast interface. These mini‑apps install automatically on Windows 11 devices with Microsoft 365 desktop apps and launch at startup by default, while administrators retain controls to prevent automatic installs and users can disable autostart locally. (learn.microsoft.com, theverge.com)

Background / Overview​

Microsoft first revealed the taskbar‑level companion concept during its Ignite keynote and subsequent Insider previews, positioning the companions as intentionally narrow, Graph‑powered micro‑experiences rather than replacements for Outlook, Teams, SharePoint, or OneDrive. The goal is simple: reduce context switching by putting the most frequent, short interactions — looking up a colleague, previewing a file, joining a meeting — one click away in the Windows 11 shell. (theverge.com, techcommunity.microsoft.com)
The suite includes three first‑party companions:

• People — quick directory lookup and org chart navigation with one‑click actions to message, call, or email colleagues.
• File Search — a single‑pane search for Microsoft 365 files (OneDrive, SharePoint, Teams, Outlook attachments), with filters, preview, and share options.
• Calendar — an at‑a‑glance calendar and meeting join surface that supports searching events and quick meeting actions. (learn.microsoft.com)

Microsoft documents these companions as a Windows 11‑only feature that leverages Microsoft Graph and tenant identities so results and actions respect existing Microsoft 365 permissioning. Eligibility and rollout are tied to Microsoft 365 update channels — Beta availability began in early April 2025 and the Preview/Current Channel (Preview) distribution widened in June 2025, with a broader business rollout beginning in August 2025. (learn.microsoft.com, blog-en.topedia.com)

---

What each companion does — detailed breakdown​

People companion​

The People companion provides fast directory search and an organizational‑chart view that surfaces profile cards with presence, working hours, and contact methods. From a profile card users can:

• Start a Teams chat, audio or video call (when Teams is licensed and available).
• Compose an email.
• Pin colleagues to favorites for rapid access. (learn.microsoft.com, techcommunity.microsoft.com)

The companion emphasizes glanceable information: availability badges, role and location data, and direct actions without opening Teams or Outlook. Licensing and tenant configuration matter here — if a user or tenant lacks Teams licensing, communication actions can be limited while directory and org‑chart data still appear. (learn.microsoft.com)

File Search companion​

File Search is designed to solve the “where did I save that file?” problem inside Microsoft 365. Key capabilities include:

• Full‑text and metadata search across OneDrive, SharePoint, Microsoft Teams, and Outlook attachments.
• Filters for author, file type, recency and people.
• Inline file preview and one‑click share or copy link actions so documents can be distributed without launching heavier clients. (learn.microsoft.com, support.microsoft.com)

Important scope note: File Search currently indexes Microsoft 365‑managed content only — local non‑M365 files or third‑party cloud stores are not included. Permission enforcement is tenant‑scoped: users see only the files they already have access to. (learn.microsoft.com)

Calendar companion​

The Calendar companion surfaces a condensed view of your Microsoft 365 calendar directly from the taskbar. It supports:

• Agenda and day views for quick schedule checks.
• Search for events by title, organizer or attendee.
• One‑click join for Teams meetings and lightweight meeting actions such as copying meeting links or opening the full calendar when deeper edits are required. (learn.microsoft.com, support.microsoft.com)

The companion is designed for micro‑interactions: quick glances and meeting joins rather than full calendar management workflows.

---

Deployment, update cadence, and control points​

How the apps are delivered​

The companions are delivered as part of the Microsoft 365 apps update process. Microsoft lists the release cadence and channel availability explicitly: Beta Channel availability since April 1, 2025 and Preview Channel availability from June 5, 2025, with staged rollouts to business tenants thereafter. Devices must be running Windows 11 and have Microsoft 365 desktop apps installed to be eligible. (learn.microsoft.com, blog-en.topedia.com)

Automatic install and autostart behavior​

By default, eligible Windows 11 devices will receive the companion apps automatically and the apps are configured to auto‑launch at startup after installation. End users can disable autolaunch in each app’s settings. Administrators who want to prevent future automatic installs can do so from the Microsoft 365 Apps admin center (Customization > Device Configuration > Modern Apps Settings → clear the checkbox for Enable automatic installation of Microsoft 365 companion apps). Note that clearing the admin checkbox prevents future automatic installs but does not retroactively uninstall companions already present on devices. (learn.microsoft.com, support.microsoft.com)

Update and lifecycle considerations​

Companion apps receive periodic feature and quality updates on a cadence that is different from traditional Office apps like Word and Excel. IT should therefore add them to application inventories and patch management processes to ensure compatibility testing and compliance with organizational change control. Microsoft has explicitly warned that their update channel and cadence differ from the classic Microsoft 365 clients. (learn.microsoft.com)

---

Why Microsoft is doing this — strategy and product logic​

The strategic motivations are threefold:

• Reduce context switching — frequent small tasks create disproportionate productivity loss; companions aim to reclaim those micro‑moments.
• Deepen Windows + Microsoft 365 integration — embedding Graph‑aware experiences in the shell strengthens the platform lock‑in for organizations already invested in Microsoft services.
• Nudge migration to Windows 11 and managed tenants — exclusivity to Windows 11 and admin‑tied rollout channels create incentives for tenants to modernize their fleets and management posture. (learn.microsoft.com, theverge.com)

From a product design perspective, the companions are explicitly positioned as complementary helpers rather than replacements for full clients — small, fast, and focused.

---

Strengths: Where this will likely help​

• Faster micro‑tasks: Quick lookups, previews, and meeting joins that previously required full client launches can now be handled in seconds, reducing cognitive load and interruption cost. (learn.microsoft.com)
• Consistent enterprise view: Because the companions use Microsoft Graph, they present a unified view of directory, file and calendar data that respects tenant permissions, making results predictable across managed devices. (learn.microsoft.com)
• Low UI friction: Taskbar placement and a compact UI minimize screen real estate consumption, which is valuable for users juggling multiple windows and monitors. (theverge.com)
• Administrative controls: Admins can block future automatic installs and control taskbar pinning programmatically, giving IT teams policy levers to manage adoption at scale. (learn.microsoft.com)

---

Risks and trade‑offs IT teams must weigh​

Unexpected installs and boot behavior​

Automatic installation and autostart may be perceived as intrusive in controlled environments or on resource‑constrained endpoints. The fact that autostart is enabled by default (and apps launch at startup) increases background service surface area and may affect boot times, battery life on laptops, and telemetry expectations. Administrators should plan pilot groups and telemetry to measure impact before broad rollout. (learn.microsoft.com, blog-en.topedia.com)

Privacy and data exposure concerns​

Although companions respect Microsoft 365 permissions and surface only content accessible to the signed‑in user, moving directory, file previews, and calendar items into an always‑available shell element raises legitimate privacy questions:

• Shared devices may expose glanceable calendar or contact details at login screens unless session controls and lock screens are enforced.
• Inline file previews may surface content to anyone with access to a logged‑in session.
  Enterprises that handle sensitive data should review session security, conditional access, and endpoint lock policies before broad enabling. (learn.microsoft.com)

Licensing and capability gating​

Some companion actions (notably Teams calls and chats) are gated by Microsoft 365 licensing and Teams availability. Organizations using third‑party communication stacks or limited Microsoft licensing should expect degraded functionality for some companion actions. The People companion remains a directory viewer without call/message actions when Teams is absent. (learn.microsoft.com)

Management and patching complexity​

Because the companions update on a different cadence, they add another moving part to application inventories and update processes. IT teams should ensure the companions are included in testing matrices and vulnerability scans, and consider whether companion updates need to be controlled in the same way as other endpoint apps. (learn.microsoft.com)

---

Practical guidance for IT administrators​

• Pilot before broad deployment.
• Choose a representative set of Windows 11 devices (desktop, laptop, managed, BYOD) and measure boot times, memory usage, and user satisfaction.
• Review and configure admin opt‑out or pinning.
• To prevent future auto‑installs: sign in to Microsoft 365 Apps admin center → Customization → Device Configuration → Modern Apps Settings → clear Enable automatic installation of Microsoft 365 companion apps. Remember this does not remove companions already installed. (learn.microsoft.com)
• Adjust group policies and endpoint management.
• Add companions to application inventories and patch workflows, and consider Group Policy or Intune controls for autostart and telemetry.
• Harden sessions and conditional access.
• Ensure lock screens, session timeouts, and conditional access policies are configured so that glanceable data isn’t exposed on shared or public devices.
• Communicate with users.
• Notify users about the companions, how to disable autostart, and where to report UX or performance issues. Provide quick how‑to documentation for disabling autostart within each app’s settings. (support.microsoft.com)

---

User experience and performance impact​

Early public reporting and Microsoft documentation indicate the companions are intentionally lightweight, but “lightweight” is relative and the actual resource footprint will vary by device class, background preload behavior, and how many companions are pinned and running. Because the apps are set to auto‑launch, organizations should watch:

• Startup memory allocations after first boot.
• Resume and sleep behavior on mobile devices.
• Interactions with Startup Boost and other preloading mechanisms Microsoft uses to accelerate Office app launches. (learn.microsoft.com)

For most mid‑to‑high spec business desktops and corporate laptops, the measurable impact is likely small; for old hardware or constrained virtual desktop images, administrators should measure and consider disabling autostart or blocking installs.

---

Security posture: what to check now​

• Confirm that companion binaries and update channels are included in endpoint AV and EDR allow/block lists.
• Ensure SIEM/telemetry rules capture companion‑related authentication and Graph API calls that might indicate misconfiguration or exfiltration vectors.
• Validate that File Search obeys tenant‑level DLP and SharePoint/OneDrive sharing controls; inline preview should not bypass document protection. (learn.microsoft.com)

If organizations enforce strict data exfiltration prevention, they should test whether companion‑driven copy link or share actions respect corporate DLP rules in practice.

---

Adoption scenarios and real‑world value​

• Knowledge worker desks: Frequent lookups and quick joins will save tens of seconds per micro‑task; aggregated across teams this can be meaningful.
• Hybrid meetings: Quick meeting joins and calendar glances reduce friction for distributed teams who hop between calls.
• Distributed document collaboration: File Search simplifies finding shared artifacts in large SharePoint structures or Teams channels when users don’t remember exact paths.

The companions do not displace full clients for power tasks, but they do change the heuristics for quick interactions — and that is their explicit design point. (theverge.com, learn.microsoft.com)

---

What remains uncertain or needs verification​

• Long‑term update cadence and patch SLAs: Microsoft states companions update on a different cadence, but enterprise SLAs and expected security patch intervals should be confirmed with vendor contracts and rollout notes.
• Telemetry and data residency specifics: While Microsoft documents that Graph and tenant permissions are used, organizations with strict data residency or telemetry requirements should verify exactly what logs are generated and where they are stored.
• Third‑party integration roadmap: Microsoft has not publicly committed to opening the companion surface to third‑party developers; whether the taskbar companion model will become a platform is currently undefined. These items should be validated with Microsoft support or account teams for high‑assurance environments. (learn.microsoft.com, techcommunity.microsoft.com)

---

Recommended checklist for rolling out companions in a controlled way​

• Identify pilot groups and schedule a two‑week trial window.
• Record baseline boot times, memory usage, and top‑N user complaints.
• Configure the Microsoft 365 Apps admin center to control installation policy for pilot vs. general population. (learn.microsoft.com)
• Test File Search results against DLP and SharePoint permissions.
• Validate People companion behavior for guest/external accounts and Teams licensing boundaries.
• Communicate user controls (how to disable autostart and how to unpin) and provide a short FAQ for common issues.
• After pilot, review telemetry and decide on gradual broader rollout or selective blocking.

---

Bottom line​

The Microsoft 365 companion apps bring practical, narrowly scoped helpers to the Windows 11 taskbar with clear productivity promise for Microsoft‑centric organizations: faster contact lookups, quicker file retrieval, and instant meeting joins. The design tradeoffs — automatic installation, autostart behavior, update cadence, and privacy/permission surface — mean IT teams should treat this as a change‑management event rather than a zero‑touch gain. A measured pilot, updated management policies, and an explicit plan for telemetry and DLP verification will let organizations reap the productivity benefit while containing the operational and security risks. (learn.microsoft.com, theverge.com)

---

Microsoft’s official companion documentation and the early reporting that accompanied the rollout provide the core technical specifics and admin controls; administrators should consult the Microsoft 365 Apps admin center and product pages for step‑by‑step opt‑out instructions and channel timing when planning deployments. (learn.microsoft.com, support.microsoft.com)

---

Source: Tech Edition Microsoft launches lightweight Office taskbar apps for Windows 11

 

[ChatGPT]

Microsoft is quietly shipping three compact Microsoft 365 “companion” apps — Calendar, File Search, and People — that live in the Windows 11 taskbar to give knowledge workers one‑click access to meetings, documents, and colleagues without opening full Office or Teams windows. et previewed the companion app concept during its Ignite and Insider channel previews as part of a broader push to fuse Microsoft 365 services more tightly into the Windows 11 shell. The apps are intentionally small, single‑purpose interfaces built to surface high‑value information with minimal context switching: glance at your day, find a file, or look up who reports to whom — all from the taskbar.
The rollout targets Windows 11 devices k is being staged through Microsoft’s update channels. Early availability started in Insider/Beta channels and moved into wider preview rings before a broader business rollout; Microsoft’s documentation and independent coverage confirm the staged distribution and the platform restriction to Windows 11.

---

What the companion apps are — the essentials​

Each companion is built for stcing full clients. They rely on Microsoft Graph and tenant identities to surface content while respecting the existing Microsoft 365 permission model.

Calendar companion: fast meeting controls and glide‑over schedules​

• Purpose: Present a compact, glanceable view of your Microsoft 365 calendar from the taskbar.
• Key functions: day/agenda views, search for events by organizer/attendee/title, one‑click join for Teams meetings, copy meeting links, and quick edits that can open the full calendar for deeper changes.
• Design goal: Micro‑interactions — check what’s next or join a meeting without launching Outlook.

File Search companiane for Microsoft 365 content​

• Purpose: Help users quickly locate Microsoft 365 documents across Oeams, and Outlook attachments.
• Key functions: unified search box supporting filename and full‑text queries, filters by author/file type/recency, inline previews, and direct share or “copy link” actions so you can distribute a document without opening Word or SharePoint.
• Scope note: Searches are limited to Microsoft 365–hosted content; local, non‑M365 files and third‑party cloud stores are not included at launch. Permissions are enf hey already have access to.

People companion: org charts, presence, and quick communication​

• Purpose: Provide fast directory lookups and an organizational chart view to find colleagues and start short interactions.
• **Key functiontle/department/skill, browse reporting lines, view contact cards with phone/email/location/presence, pin favorites, and initiate Teams chats/calls or compose email drafts from a profile card (Teams‑dependent features require appropriate licensing).
• Design goal: Reduce friction for pre‑meeting checks and ad‑hoc outreach without opening Teams or Outlook.

---

Deployment, management and admin controls​

The companion apps are distributed through the Microsoft 365 apps updanh at login after installation. That behavior is configurable: end users can disable autostart in each app’s settiistrators can prevent future automatic installs via the Microsoft 365 Apps admin center. Note that admin opt‑outs generally prevent future installs but may not remove companions already installed on endpoints.
Key operational points for IT:

• Platform requirement: Windows 11 only; Windows 10 devices are not eligible under the current rollout.
• Automatic install: Eligible devices often receive the companions automatically depending on update channel settings; admins can block future installs aalled companions.
• Autostart control: Users can toggle Auto‑Start at Windows login off in each companion’s Settings. Administrators can nd startup behavior through management tools.
• Update cadence: Companion apps receive feature and quality updates on a cadence separate from classic Office apps; IT should include them in inventories and patch prot IT and security teams should evaluate

The companions bring real convenience, but they also introduce new administrative, privacy, and compliance considerations. The following sections boil ical checks and recommended actions.

Identity and directory hygiene​

The People companion’s usefulness depends directly on the quality of Azure Active Directory profile data. I stale reporting relationships, or mismatched phone numbers will degrade the experience and may surface inaccurate org charts. Organizations should audit Azure AD attributes and enforce profile standards before widespread companion deployment.

Permissions and eDiscovery​

File Search and Calendar surface Microsoft 365 content based on Graph‑driven permissions. That means the companions will show only what a user already has access to, but IT must validate how those surfaces interact with existing eDiscovery, retention labels, and Data Loss Prevention (DLP) policies. Pilot rollouts should include eDiscovery and DLP testing to confirm expected behavior under seare actions.

Telemetry, privacy, and presence​

The People companion shows presence and working hours by reading Teams/Graph data. Organizations with strict privacy policies or unionized workforces should confirm which presence indicators are appropriate to display and whether employers need to adjust visibility settings or internal policy communications before the companion appears in users’ taskbars.

Endpoint hygiene and patch management​

Becausollow a different cadence, IT must add them to application inventories and patch management workflows. They should also be included in vulnerability scanning and software‑asset management to avoid blind spots in compliance reporting.

Network and performance considerations​

Although the companions are lightweight, File Search uses content indexing and previews that rely on Graph calls and, humbnails or previews. Organizations with constrained WAN links or metered connections should pilot to measure additional Graph/API traffic and adjust QoS or caching policies if necessary. If devices are set to autostart many background helpers, cumulative startup overhead can affect perceived login times

Practical rollout checklist for IT (recommended phased approach)​

• Inventory and eligibility
• Confirm which devices are Windows 11 and have Microsoft 365 desktop apps installed.
• Map eligible users and groups to pilot cohorts.
• Pilot and validation
• Enable companions for a small, representative group that includes helpdesk, compliance, and networking teams.
• Test eDiscovery, DLP, presence visibility, and file‑sharing flows.
• Policy and configuration
• Decide on auto‑inst Microsoft 365 Apps admin center and record them in change control.
• Prepare step‑by‑step guidance for users on disabling autostart and hiding companions.
• Monitoring and inventory
• Add companions to software‑asset inventories, endpoint cycles.
• Track telemetry for startup times and API usage to identify any performance regressions.
• Education and governance
• Produce quick reference material that explains privacy controls, sharing etisable companions.
• Update acceptable use and data handling guidance to include companion behaviors.

---

User experience — what end users will notice​

For everyday knowledge workers, the companions aim to shave small but frosts. Expect the following immediate benefits and limitations:

• Benefits
• Rapid, one‑click access to key items without launching heavyweight clients.
• Reduced context switching for common micro‑tasks: a file link, or send a quick Teams message.
• Unified file search across Microsoft 365 sources from a single pane.
• Limitations
• Not a replacement for full applications — the companions are optimized for short interactionsng or long‑form collaboration.
• Functionality that depends on Teams or specific Microsoft 365 licenses may be limited for users without those services.
• Mobile versions are not yet available at launch; companions are currently desktop‑only. This suggests future plans may include mobile alternatives, but that is not confirmed. Treat mobile availability as an open item.

---

Security and privacy deep dive​

Comphat organizations treat as sensitive. The following are the highest‑impactconsiderations.

Data access model and least privilege​

Companions respect Microsoft 365 permissioning, which is good — users see only files and calendar items they wever, the convenience of quick share and copy‑link actions increases the chance of accidental oversharing. Reinforce least‑ppolicies, and configure DLP policies to catch risky link shares or attachments even when performed via a companion.

Local caching and preview thumbnails​

Inline previews and file thumbnails are convenience features thatpies on the endpoint. Confirm how previews are cached, where temporary files live, and whether those buffers are covered by endpoint encryption and disk‑wiping procedures. If necessary, tighten policies around local caching or configure selective wipe for managed devices.

Logging and auditing​

Ensure that actions performed via companions — file shares, meeting joins, quick messages — are captured in audit logs and are available to compliance tooling. If companion‑initiated actions are not fully instrumented in existing logs, file an escalation with Microsoft support before you broaden the rollout.

expectations​

The People companion surfaces presence and working hours data from Teams. This visibility can trigger employee privacy concerns in certain jurisdictions. Align presence visibility with corporate policy, and offer communication to staff on what will be displayed and how to adjust personal settings.

---

User controls and recovery options​

• To stop companions from autostarting: opetings and toggle Auto‑Start at Windows login to Off. Administrators can also enforce autostart behaviors centrally.
• To prevent future automatic installs: use the Microsoft 365 Apps admin center and clear the checkbox for automatic installation of Microsoft 365 companion apps under Device Configuration → Modern Apps Settings. Notall companions already present; removal can require additional steps.
• If unwanted companions are already installed at scale, coordinate with support channels and use Intune/Group Policy alternatives to remove or hide the apps while preserving end‑user productivity. Plan a rollback path as part of your pilot.

---

Measurable ROI anons​

The productivity gains from companions are incremental but recurring. Small time savings per micro‑task compound: shaving 10–30 seconds off dozens of daily lookups can add meaningful saved time across teams. That said, measuraberal factors:

• Frequency of micro‑tasks in your organization (how often users search for files, check calendars, or look up colleagues).
• The quality of directory data and Microsoft 365 adoption maturity (Graph connectivity, Teams usage).
• The cost of additional management overhead, including training,ntorying yet another update cadence.

A conservative approach is to pilot, measure time‑saved metrics for a sample cohort, and then scale with clear governance and training.

---

Future directions and open questions​

The companion model ric and product questions that IT and procurement teams should watch:

• Third‑party companions: Will Microsoft open the companion APIs to third parties to enable a broader ecosystem of taskbar micro‑apps? If so, governance and security policies will need to adapt rapidly.
• Deeper AI integration: Companions could evolve to include Copilot‑style features — conversational queries like “find last quarter’s revenue slide” — which would introduce additional compute, telemetry, and compliance considerations.
• Search scope expansion:ventually include non‑Microsoft clouds or local semantic indexing? That shift would alter the data protection and indexing morm parity: Mobile versions aren’t available at launch, but Microsoft’s wording suggests they may be considered later. Mobile companions would require rethinking authentication and network behavior for mobile data plans and offline resilience.

These are plausible directions but not confirmed product commitments. Treat them as watchpoints rather than assumptions.

---

Final assessment — strengths and risks​

The Microsoft 365 companion apps deliver a pragmatic productivity improvement for Microsoft‑centric, Windows 11 environments. Their strengths are clear:

• Speed and convenience: Immediate access to meetings, files, and people reduces micro‑interruptions and context switches.
• Consistency: Because the companions use Microsoft Graph and tenant identity, they present consistent organization data across endpoints.
• Low friction for end users: Quick actions like copy link, preview, or one‑click join are valuable for everyday workflows.

At the same time, they introduce tangible risks:

• Governance overhead: New update cadences, logging needs, and inclusion in asset inventories increase IT workload.
• Privacy and DLP surface area: Qw actions expand the attack surface for accidental data exposure; DLP and retention policies must be validated against companion behaviors.
• Potential desktop clutter: Without careful management, the taskbar can become crowded with overlapping experiences or third‑party mini‑apps in the future.

---

Recommended next steps (practical and immediate)​

• Run a targeted pilot that includes helpdesk, compliance, and a representative set of know eDiscovery, DLP, and sharing behavior end‑to‑end with the companions active.
• Update Microsoft 365 Apps admin center settings to reflect your for automatic install and document the decision in change control.
• Create short user guidance that explains how to disable autos, and how the apps respect tenant permissions.
• Add companions to your software inventory and patch/monitoring cycles.

These steps let organizations realize the productirolling governance, privacy, and security exposure.

---

Microsoft’s companion apps for Windows 11 are a measured move toward making the taskbar a lightweight micro‑workspace for common enterprisely save time and reduce friction for Microsoft 365‑centric teams, but the net benefit depends on disciplined rollout, robust governance, and clear user education.ilot carefully and align companions with existing data protection and asset management practices will capture the upside while avoiding the common pitfalls.

---

Source: PCMag Australia Microsoft 365 Shortcut Apps Rolling Out in Windows 11: Here's What You Get