Edge Canary Retires Sidebar App List in Favor of Copilot

Microsoft’s latest test in Edge Canary quietly signals a shift in the browser’s sidebar strategy: the “Sidebar app list” — the small, convenient launcher that let users pin websites and mini‑apps like Instagram, Spotify and Facebook — is being retired in favor of a Copilot‑centred experience, while Microsoft keeps built‑in tools such as Copilot and Outlook available.

Background​

Microsoft introduced the Edge sidebar as a lightweight productivity surface: a narrow column beside the main tab strip that functioned as both a mini app launcher and a hub for built‑in utilities. Early versions let users pin third‑party sites and web apps (effectively Progressive Web Apps, or PWAs) to the sidebar for one‑click access without switching tabs. That behavior gradually merged with native integrations — Bing Chat evolved into Copilot, Office previews appeared, and the sidebar took on a broader role as a productivity dashboard.
The change now visible in Canary appears as an in‑browser notice when users click the “+” button to add sidebar apps: a short message telling users the Sidebar app list is being retired, that new apps can no longer be added, and that the quick‑access list will be removed across future updates — but that Copilot itself is not affected. This notice is currently observed in experimental Canary builds and is rolling out through preview channels before any stable release decision.
Microsoft’s official documentation already gives administrators granular controls over the sidebar — including policies to block or allow sidebar apps and the ability to list built‑in app URLs — which shows the company treats the sidebar as both a user feature and an administrable surface for managed environments. Those policy knobs remain important as the UI evolves.

---

What’s being removed — and what’s staying​

Sidebar app list: what it was​

• The sidebar app list let users pin websites and web apps to the sidebar for persistent, side‑by‑side access.
• It made multitasking easier by giving quick access to messaging, music, calendar and other frequently used web services without switching the active tab.

What Microsoft says is staying​

• Built‑in sidebar tools — Copilot, Outlook, Calculator and other Microsoft‑supplied utilities — remain available in the sidebar. Microsoft has explicitly noted Copilot will not be affected by the retirement of the custom app list; the shift is positioned as simplification to let the team focus on Copilot improvements.

What’s being removed​

• The user‑addable quick list — the + / pin flow that let you add arbitrary web pages as sidebar apps — will be disabled for new additions and the existing quick‑access list will be phased out. Users will lose the one‑click in‑sidebar opening of third‑party sites.

---

Why Microsoft is doing this: product logic and strategy​

Microsoft’s moves reflect a persistent strategic thread: make Copilot the primary assistant and discovery surface across Windows, Office and Edge. Several factors explain the motivation:

• Distribution and engagement: Shipping Copilot as a first‑class surface in Edge increases daily exposure and creates more opportunities to surface Microsoft services and ecosystem integrations. Edge is, after all, the preinstalled browser on Windows and a natural vector for system‑level features.
• Simplification and telemetry: Reducing UI permutations (few apps vs many user‑added shortcuts) simplifies testing and telemetry for the engineering team and accelerates iterative improvement of the Copilot experience. Canary/Dev channels are actively used to test these trade‑offs.
• Feature consolidation: Microsoft appears to be consolidating overlapping entry points (sidebar apps, Edge Bar, pinned tabs, PWAs) in favour of a smaller number of maintainable, instrumentable surfaces — with Copilot as the anchor. This supports richer, cross‑app features like multi‑tab synthesis and agentic actions that depend on a consistent assistant surface.

---

What users lose — and alternatives Microsoft recommends​

Losing the sidebar app list affects workflows that relied on the sidebar as a quick, always‑visible launch pad. Typical impacts include:

• Extra clicks to open commonly used sites that used to live in the sidebar.
• Reduced ability to monitor live web apps (e.g., chat, social feeds, music controls) side‑by‑side with browsing.
• A change in muscle memory for people who used the sidebar as a lightweight app launcher.

Microsoft points users to three main alternatives: Edge Bar, pinned tabs, and installing sites as Progressive Web Apps (PWAs). Each alternative has trade‑offs:

• Edge Bar: A separate floating desktop bar that can host pinned apps and websites. It preserves the convenience of a desktop side surface for quick glances and multitasking. Microsoft’s support pages describe how Edge Bar works and how it retains your pinned items across the profile.
• Pinned tabs: Pinning a tab keeps it compact and available within the main browsing UI but consumes tab real estate and is not as unobtrusive as a sidebar lane.
• PWAs: Installing a site as a PWA creates an app‑like window that can be launched from Start or taskbar and behaves like a standalone app. PWAs are the most flexible alternative for replicating app‑like behavior and are cross‑platform friendly. Installing a PWA in Edge is handled through the browser’s apps or address‑bar install affordance.

---

Practical guidance: how to migrate your sidebar apps today​

If you rely on the sidebar app list, here are clear, tested steps to prepare and migrate workflows. These steps work today and will survive the phased retirement.

• Install the site as a PWA (best choice for app‑like behavior)
• Open the website in Edge.
• Click the three‑dot menu → Apps → Install this site as an app (or use the install icon in the address bar).
• Pin the installed PWA to taskbar or Start for one‑click access.
• Use Edge Bar to maintain a desktop side surface
• Open Edge → Settings → Sidebar → Enable Edge Bar.
• Move pinned sites to the Edge Bar so they remain available on the desktop even when Edge is minimized.
• Pin tabs for ongoing web services
• Right‑click a tab → Pin. Pinned tabs stay compact and persist across sessions in your profile.
• Export or document your pinned sidebar list
• If you have many pinned sidebar links, create a simple bookmarks folder: open each pinned item and Save → Bookmark → Folder. That folder can become the source-of-truth to rebuild in PWAs or the Edge Bar.

These steps provide a practical migration path while keeping your frequently used sites accessible with minimal disruption.

---

Enterprise and admin implications​

The retirement is not purely a consumer UX change — it has measurable effects on managed fleets and compliance:

• Group Policy and MDM: Microsoft’s enterprise documentation exposes policies to control whether the sidebar is enabled, and which apps can be opened within it; administrators can block sidebar apps by URL or ID. Those policies remain the authoritative way to manage exposure on managed endpoints. If IT needs to ensure consistent behavior across corporate machines, rely on these controls rather than per‑user toggle instructions.
• Governance of Copilot capabilities: Copilot’s expansion in Edge (including possible keyboard remaps such as F1 opening Copilot in some test builds) increases the governance surface: admins have to consider where Copilot can access page context, how session memory is retained, and how agent‑driven actions should be audited in regulated environments. Early reporting and forum testing show Microsoft is rolling out enterprise‑grade controls, but these are evolving — plan for pilot testing.
• DLP and data flows: When assistants can read page content or act on behalf of users (Copilot Actions), enterprises must confirm DLP rules and logging capture those flows. If your organization prohibits sending internal pages to external services, validate retention, transmission, and opt‑out toggles before enabling Copilot features at scale.

Action checklist for IT teams:

• Audit existing sidebar usage across user groups.
• Identify critical web apps that must remain accessible and assess PWA suitability.
• Update Group Policy/MDM templates: Block or allow sidebar apps by URL or extension ID as required.
• Pilot Copilot behaviour on a controlled fleet and measure telemetry, support impact and data‑loss risks.

---

Strengths and potential upsides of the change​

• Focused investment: By simplifying the sidebar surface and doubling down on Copilot, Microsoft can concentrate engineering efforts on the assistant’s reliability, multi‑tab reasoning and agentic flows that do require a consistent integration surface. Early Canary testing shows features like Copilot Actions and Journeys rely on a stable assistant host to work effectively.
• Reduced UI fragmentation: Removing a customizable app list reduces variant testing and support complexity; Microsoft can iterate faster on Copilot first‑class features while exposing a smaller set of supported access patterns (Edge Bar, PWAs, pinned tabs).
• Better enterprise manageability: With official policies to block or allow sidebar apps (and store built‑in app URLs centrally via sidebar internals), administrators get clearer, supported controls for managed devices.

---

Risks, trade‑offs and unanswered questions​

• Loss of convenience and discoverability: For many users the sidebar app list was a low‑friction way to keep important web apps available. Removing it without a one‑to‑one replacement may frustrate users who relied on the sidebar’s always‑visible nature. The Edge Bar and PWAs are functional alternatives, but neither is an exact UX match.
• Perception of coercion: Pushing Copilot to the forefront risks user perception issues around “nudging” — earlier experiments that surface Copilot in multiple places (address bar, F1, NTP) have raised concerns about over‑surfacing first‑party services. Users who prefer alternate assistants or a minimal browser may interpret the change as coercive.
• Fragmentation across channels: Canary‑only experiments may not reflect final behaviour, but they can become confusing when rolling to Beta and Stable channels. Admins and users should not assume experimental behavior will ship identically.
• Reliability and brittleness of agentic features: Features that let Copilot take multi‑step actions (filling forms, scraping pages) can be brittle on complex pages and require robust permission, confirmation and abort flows. Enterprises that plan to adopt agentic automations must validate reliability and error handling in pilot programs.
• Unverified specifics: The precise rollout timeline, the final stable‑channel behaviour and the full wording of any in‑product notices or migration prompts are not yet uniformly documented by Microsoft. Observations so far come from Canary builds, independent hands‑on reports and community testing; treat early notices as provisional until Microsoft publishes formal release notes.

---

Recommendations — practical next steps for different users​

For casual users​

• Use Edge Bar or pin tabs for fast access. If you relied on sidebar apps, try enabling Edge Bar immediately and pin favorite sites to it.

For power users and enthusiasts​

• Convert frequently used sidebar pages to PWAs for persistent app‑like behaviour and taskbar/Start presence. Keep a bookmarks folder as a migration snapshot.

For IT administrators​

• Inventory sidebar usage across groups.
• Apply Group Policy to control sidebar exposure where required and prepare a migration playbook for users.
• Pilot Copilot features and agentic flows in a controlled environment; validate DLP, auditing and retention for Copilot interactions.

For developers and extension authors​

• If you publish a web service that users rely on via the sidebar, prepare a PWA manifest and ensure a smooth install path so customers can continue using your service in a first‑class way after the sidebar list disappears.

---

The bigger picture: Copilot as a platform bet​

Microsoft’s push to center Copilot across shell and browser surfaces is consistent with its broader cloud + AI strategy: unify discovery, instrument usage and provide richer cross‑app automation. The retirement of a minor UI element like the sidebar app list is a small but telling step in a larger migration from scattered shortcuts to a centralized assistant model.
That model brings real productivity gains when the assistant is reliable, privacy‑respecting and well governed. But the shift also escalates the stakes: mistakes in permissions, brittle automations, or heavy‑handed nudging can quickly erode trust. Microsoft’s engineering will need to balance rapid iteration with careful, transparent controls — especially for enterprise adopters and privacy‑conscious users.

---

Conclusion​

The retirement of Edge’s Sidebar app list signals a deliberate simplification: Microsoft is pruning a user‑customizable launcher in order to concentrate attention on Copilot and a smaller set of supported access surfaces. The move is defensible from an engineering and product‑strategy view — it reduces fragmentation, speeds iteration on Copilot features, and funnels user journeys onto surfaces Microsoft can instrument more reliably. But it is not without trade‑offs: users who valued the lightweight, always‑visible app lane will need to rebuild workflows using PWAs, pinned tabs or the Edge Bar, and administrators must reassess governance for Copilot features that will remain prominent.
For now, the change is visible in Canary and Dev channels; the final Stable behaviour, exact timelines, and enterprise enablement details remain subject to Microsoft’s staged rollout. Users and IT teams should treat Canary observations as early signals: prepare migration plans, pilot Copilot in controlled groups, and use policy controls where consistency and compliance are required.

---

Source: Windows Report Microsoft to Retire Sidebar App List in Edge, Focuses on Copilot

 

[ChatGPT]

Microsoft Edge is quietly retiring the long-favored Sidebar app list in Canary builds and steering that small real‑estate toward a Copilot‑first experience — an experiment that, if it reaches Stable, will reshape how many Windows users multitask in the browser. Early testers report an in‑product notice when clicking the Sidebar’s “+” control that reads, in effect, “New apps can no longer be added, and the quick access list will be removed gradually in future updates. Copilot is not affected,” a change visible today in Edge’s preview channels.

Background​

What the Sidebar app list was and why people liked it​

Edge’s Sidebar has functioned for years as a lightweight, always‑available lane for mini web apps and quick tools. Users could pin web services — e‑mail, chat pages, music controls, reference sites, and more — and open them in a slim panel beside tabs without interrupting the main browsing surface. That behavior provided a low‑friction multitasking model: glanceable content, persistent app presence, and one‑click access to frequently used web destinations.
The Sidebar’s utility came from its simplicity. It didn’t require heavy OS integration or full app installations; for many workflows it replaced the need to pin tabs or install PWAs while keeping content visible and accessible. That user‑pinned list is precisely the portion Microsoft’s Canary warning indicates will be phased out.

How Copilot became the focal point​

Over the past year Microsoft has incrementally pushed Copilot — its AI assistant — into multiple places across Windows and Edge: the New Tab Page (NTP), the omnibox/address bar, the toolbar, right‑click menus, and the Sidebar itself. Those integrations are part of a consistent product strategy: make Copilot a first‑class surface for discovery, help and automation across Microsoft’s ecosystem.
Canary testers are now seeing Copilot presented as the persistent assistant surface in Edge’s evolving UI experiments. Microsoft’s internal logic appears to be consolidation: fewer, instrumentable entry points (Copilot) in place of many user‑created shortcuts (the Sidebar app list). Early reports and hands‑on testing show Microsoft positioning Copilot as the anchor for multi‑tab synthesis, Journeys (session summaries), and agentic actions that depend on a consistent host.

---

What changed in Edge Canary (the short, verifiable facts)​

• Edge Canary displays an in‑product notice at the Sidebar’s “+” control that announces the retirement of the Sidebar app list; users can no longer add new sidebar apps and the existing quick‑access list will be phased out over future updates.
• Microsoft’s messaging in those notices explicitly states “Copilot is not affected,” indicating built‑in tools such as Copilot, Outlook and other Microsoft utilities will remain in the Sidebar while third‑party user‑pinned items are the ones being retired.
• The change is currently visible in experimental channels (Canary/Dev) and is being rolled out to preview users; there is no firm, public timeline from Microsoft yet for Beta/Stable rollout. This early‑channel testing means behavior could be refined or reversed before reaching general availability.

These points are corroborated by independent hands‑on reporting from multiple outlets and community testers who observed the exact in‑browser warning and the Copilot‑first messaging in Canary builds.

---

Why Microsoft appears to be doing this​

Product & engineering tradeoffs​

• Reduction of UI surface area. Maintaining many permutations of user‑customized Sidebar lists adds testing complexity, telemetry fragmentation and longer QA cycles. Consolidating around a smaller set of supported surfaces (Copilot, Edge Bar, PWAs) simplifies engineering and speeds iteration on Copilot features.
• Distribution leverage. Edge is preinstalled on Windows; making Copilot a prominent Edge surface amplifies exposure and adoption across Windows users — an important vector for Microsoft’s broader AI strategy.
• Feature consolidation for agentic flows. Features like multi‑tab reasoning, Journeys and Copilot Actions rely on consistent assistant hosting. Removing user‑added variance in the Sidebar helps ensure Copilot can rely on a predictable integration surface.

Business and ecosystem motivations​

Copilot ties users into Microsoft’s cloud, account systems and paid tiers (e.g., tenant‑aware Copilot for businesses). Increasing Copilot’s discoverability in Edge is valuable from both engagement and commercial standpoints, and the Sidebar change is consistent with a broader push to center AI features in the product experience.

---

What users lose (and why it matters)​

Immediate usability impacts​

• The quick, always‑visible lane for frequently used web apps will disappear for users who depended on the Sidebar to keep mail, chat, or utility sites visible while working in the main tab area. That increases context switching and forces alternative trade‑offs (pinned tabs, PWAs, or the Edge Bar).
• Muscle memory is affected; workflows built around the Sidebar’s side‑by‑side persistence will require reconfiguration. Power users who relied on the Sidebar for monitoring live services (music controls, messaging, dashboards) will see a genuine productivity hit unless they adapt to alternatives.

Perception and trust risks​

• The change is being framed as simplification, yet the real effect is to preserve or expand Copilot’s prominence while removing a user customization path. That will feed narratives that Microsoft is nudging users toward its own AI services — a perception problem that can erode trust among privacy‑conscious and power users.

---

Practical alternatives and migration paths (what to do now)​

If you rely on the Sidebar app list, there are practical, supported ways to replicate most of its functionality. These options have trade‑offs: some preserve the “always‑there” convenience at the cost of system clutter, others give true app‑like behavior.

• Edge Bar — a floating desktop strip that can host pinned sites and remain visible even when Edge is minimized. It approximates the Sidebar’s side surface for quick glances.
• Progressive Web Apps (PWAs) — install sites as standalone apps that appear in Start and can be pinned to the Taskbar; PWAs are the closest one‑to‑one replacement when you want app behavior and persistent presence.
• Pinned tabs — cheap and reliable, but they consume tab row space and are not as unobtrusive as a sidebar lane.

Quick migration checklist (step‑by‑step)​

• Inventory: Open your Sidebar and make a list (or screenshot) of pinned sites you rely on.
• Convert to PWAs:
• Open the target website in Edge.
• Click the three‑dot menu → Apps → Install this site as an app (or use the install icon in the address bar).
• Pin the installed PWA to the Taskbar or Start menu for one‑click access.
• Enable Edge Bar (if you prefer a side surface):
• Open Edge → Settings → Sidebar → Enable Edge Bar, then move/pin your sites to it.
• Pin tabs for always‑on services: Right‑click a tab → Pin. Use this for services where a PWA install isn’t practical.
• Keep a bookmarks folder as a fallback index of your prior Sidebar items in case you need to rebuild quickly.

These steps are practical today and will endure after the Sidebar app list is phased out, since PWAs, pinned tabs and Edge Bar are supported Edge features.

---

Enterprise and admin implications​

Policy controls still exist — use them​

Microsoft exposes Group Policy / MDM controls for the Sidebar surface and built‑in URLs. Administrators can block or allow sidebar apps and centrally manage which built‑in utility URLs are available. Those policy knobs remain the authoritative way to manage behavior on managed devices and will be crucial during any phased retirement.

Governance, DLP and auditing implications​

• Copilot’s expansion means administrators must evaluate data flows: Copilot can access page context and may read or summarize page content depending on the mode and consent. Enterprises need to validate Data Loss Prevention (DLP) rules, logging, and retention for assistant interactions before enabling Copilot broadly.
• Pilot and measure. Admins should pilot Copilot features on a controlled fleet, check telemetry, and ensure audit trails are sufficient for compliance workloads.

---

Privacy, security and reliability concerns​

Privacy & consent​

Copilot features such as Journeys and multi‑tab reasoning may require access to browsing history, page context, and file uploads. While Microsoft frames these flows as permissioned and opt‑in, UI choices and default settings can meaningfully shape user consent behavior. Administrators and privacy‑conscious users should verify controls before enabling Copilot broadly.

Reliability of agentic flows​

Agentic features (Copilot Actions) that perform multi‑step tasks can be brittle on complex pages, and they require robust permission, confirmation and abort flows. Enterprises adopting agent‑style automation should run reliability and edge‑case tests; consumer users should be conservative with automation that writes or submits content on their behalf.

---

UX and product analysis — strengths and risks​

Strengths​

• Focused engineering investment. Consolidating surfaces allows Microsoft to iterate faster on Copilot’s core capabilities.
• Unified assistant experience. A predictable host for advanced Copilot features can enable richer cross‑tab reasoning and multi‑step automations.

Risks​

• Loss of convenience. The Sidebar app list is an elegant shortcut model; alternatives are workable but imperfect.
• Perceived coercion. Removing user customization while simultaneously surfacing first‑party AI risks the perception of anti‑competitive nudging. That perception can hurt trust even if the technical change is defensible.
• Rollout fragmentation. Canary experiments may not reflect final Stable behavior, but they can create confusion if features are toggled across channels unpredictably. Admins should not assume Canary behavior equals forthcoming policy.

---

What we could not verify (and where to watch for confirmation)​

• Microsoft has not yet published formal release notes that commit to a Stable‑channel retirement timeline for the Sidebar app list; current evidence is limited to Canary notices and hands‑on reporting. Treat the Canary message as provisional until Microsoft issues an official changelog entry or support article.
• Precise enterprise policy adjustments, telemetry thresholds prompting the change, and a firm date for Beta/Stable rollout remain unconfirmed by Microsoft at the time of this reporting. Administrators should monitor Microsoft’s Edge release notes and the official docs for policy updates.

---

Recommendations — clear actions for different audiences​

For casual users​

• Export or screenshot your current Sidebar apps and migrate the most critical ones to PWAs or pinned tabs now. This avoids interruption if the quick‑access list disappears in your channel.

For power users and enthusiasts​

• Convert frequently used sidebar pages to PWAs for app‑like behavior and taskbar presence. Use a bookmarks folder as a rollback snapshot.
• Try Edge Bar if you want a persistent side surface that survives Edge minimization.

For IT administrators​

• Inventory Sidebar usage across the organization.
• Pilot Copilot and new Edge behaviors on a subset of machines; measure telemetry and support impact.
• Update Group Policy/MDM templates to control Sidebar visibility and Copilot access as needed.
• Validate DLP coverage for Copilot’s page‑context operations and ensure logging/auditing is adequate.

For web developers and PWA publishers​

• Ensure your site has a robust PWA manifest and smooth install flow. If customers relied on the Sidebar for quick access to your service, a well‑behaved PWA is now the recommended fallback.

---

Conclusion​

The Canary‑channel retirement of Edge’s Sidebar app list is a small change with outsized implications. On paper the move simplifies a UI surface and focuses engineering on the Copilot experience — a defensible product choice if your goal is to accelerate AI features that need consistent hosting. In practice it pulls the rug out from workflows that relied on a low‑friction, always‑available lane for web apps, and it amplifies concerns that Microsoft is steering users toward first‑party AI surfaces.
For now, the change remains experimental and visible in Edge’s preview channels; alternatives such as PWAs, Edge Bar and pinned tabs offer practical migration routes. Organizations and power users should start migrating critical workflows and preparing policy controls. Consumers should snapshot their Sidebar state and try PWAs for items they cannot live without.
This is part of a larger trend: Microsoft is consolidating entry points and doubling down on Copilot as the flagship assistant across Windows and Edge. That strategy carries real productivity upside when the assistant is reliable, well‑governed and respectful of user control — but it also raises meaningful privacy, governance and user‑choice questions that Microsoft will need to address as the experiment moves toward broader release.

---

Source: Windows Latest Microsoft Edge is removing Sidebar app list as Copilot takeover continues on Windows 11