Microsoft’s quietly broad rework of Edge’s right-hand real estate is beginning to show real consequences: the user‑addable
Sidebar app list — the tiny lane where people pinned mini web apps and quick site shortcuts — is being retired, and the change is already visible to testers in Edge’s early channels. The company’s in‑product notices and support guidance make two things clear: users can no longer add new sidebar apps, existing quick‑access entries will be removed in a forthcoming update, and
Copilot — Microsoft’s AI assistant — is explicitly
not being removed. What’s missing is a firm timeline and full official documentation about the scope of the rollout, which leaves power users, IT administrators, and developers scrambling to understand impact and plan mitigations.
Background
The Edge sidebar evolved into a compact productivity surface over the last several years. Originally a modest set of built‑in tools (Calculator, Outlook preview, Drop, Games, and a few others), it gained a flexible “pin any site” workflow that let users add arbitrary web pages and create lightweight web apps that opened in a narrow side pane. That blend of utility and friction‑free multitasking made the sidebar popular with users who wanted glanceable content — chat, music players, small dashboards — without leaving the current tab or opening a full new window.
Microsoft has, in parallel, been integrating Copilot deeply into both Windows and Edge. Copilot now surfaces across menus, the New Tab experience, the omnibox, and is accessible via sidebar in many builds. This heavier investment in the AI assistant appears to be a significant factor in Edge’s UI decisions, and the recent notices in Canary and Dev builds signal a shift toward giving Copilot priority over user‑customized sidebar apps.
What’s important to stress up front: Microsoft has not published a definitive removal date for the sidebar app list, and some official support pages continue to describe the Edge Bar and sidebar features for specific platforms. The in‑product message seen by testers says only that the sidebar app list “is being retired,” that “new apps can no longer be added,” and that the “quick access list will be removed gradually in future updates,” while also noting Copilot will remain unaffected. In short: the functionality is being wound down, but the exact timing and scope remain intentionally vague.
What changed — the facts you can rely on
- In Edge Canary and other early preview builds, attempting to add a new sidebar app now surfaces a deprecation notice that clearly states the user‑addable Sidebar app list is being retired.
- The notice indicates new apps can no longer be added, and that the quick access list (the small lane of pinned third‑party sites/apps) will be removed gradually.
- Microsoft’s messaging states Copilot is not affected, implying built‑in Microsoft sidebar tools will continue to be available.
- Microsoft support pages and Edge feature documentation still describe the Edge Bar and Sidebar features in various contexts (for example, Edge Bar on Windows 10); however, Microsoft has not published a conclusive “retirement date” or a full step‑by‑step migration plan for users.
- Separately, Edge is also notifying users that other features (notably Collections) are in the process of being retired or restricted — indicating a broader simplification push in the product.
These are not rumors: the deprecation message is visible in product builds used by testers and has been reproduced by multiple independent observers. Yet because Microsoft’s formal documentation remains sparse on exact dates, affected user segments, and the handling of pinned apps, some details still carry uncertainty.
Who is affected — consumers, enterprise, and what “starting with” might mean
The in‑product notice and media reports indicate the wind‑down is rolling out through Edge’s early channels first. A few important points about affected groups:
- Testers in Edge Canary and Dev have reported the deprecation message; those channels are often where UI experiments appear before any stable release.
- There are reports and claims that the deprecation will start with Microsoft account (MSA) users, though that specific phasing detail is not documented in a single centralized Microsoft page as of the time of writing. Because Microsoft sometimes stages rollouts by account type, profile, region, or channel, it’s plausible — but this particular “MSA first” claim should be treated as partially verified and flagged as uncertain until Microsoft confirms it in an official support article or release note.
- Enterprise customers (Azure AD / work and school accounts) should not assume parity in timing. Organizations often receive different update cadences and policy controls; IT admins must monitor enterprise release notes and Group Policy documentation to know how/when changes land.
If you rely on a personal Microsoft account and use the sidebar to pin frequently used web apps, prepare for change. If you’re in an organizational environment, consult your IT admin team and the Edge enterprise policy documentation to understand whether your deployment will be altered and how to control or replicate the functionality.
Why Microsoft is making this change — product strategy and plausible drivers
Several strategic and product plausibility points explain why Microsoft might retire the sidebar app list:
- Consolidation around Copilot: Copilot is being positioned as a central, attention‑grabbing assistant across Windows and Edge. Allocating the sidebar’s limited UI real estate to Copilot and other core built‑in tools simplifies the product surface for Microsoft and raises daily exposure for Copilot.
- Low usage and maintenance cost: Some legacy or lightly used features are expensive to maintain. If telemetry shows the custom pin list has comparatively low engagement, Microsoft may remove it to reduce complexity and long‑term maintenance overhead.
- UX simplification: Microsoft’s stated rationale — “simplifying Edge” — is a classic product justification. The company appears to be trimming customization options that create inconsistent experiences across users, favoring a tighter, more curated set of features.
- Product convergence and redundancy: Several alternatives already exist for quick access to sites (PWAs, pinned tabs, Edge Bar, Favorites). Microsoft may be encouraging migration to those alternatives to prevent UI overlap and fragmentation.
All of these reasons are consistent with what’s visible in product behaviour and public reporting. However, product strategy choices have trade‑offs — and not every user benefits equally from simplification.
Immediate consequences for users
If the sidebar app list disappears on your device, here’s what you will likely see and lose:
- You will no longer be able to add new sites directly via the sidebar’s + / pin flow.
- At some later point, the visible quick‑access list of previously pinned third‑party sites will be removed from the sidebar. The exact behavior for existing pins (whether they are preserved elsewhere or simply deleted) is not consistently documented and may vary by build.
- Built‑in tools such as Copilot, Outlook, Calculator, and other Microsoft‑supplied utilities will remain accessible in the sidebar (per Microsoft messaging).
- Users who rely on the sidebar to view mobile-optimized pages (music players, chat apps, social feeds) in a slim vertical pane will lose that frictionless workflow, unless they adopt alternatives described below.
If you use the sidebar heavily, this is functionally significant: the sidebar’s strength is not just access but the ability to interact with a site in a narrow, always‑available pane next to your content — something that pinned tabs and even PWAs do not replicate exactly.
Alternatives and mitigations — what to do now
Microsoft and reporting sources point to several ways users can replicate sidebar functionality. Here are practical, prioritized options:
- Install the site as a Progressive Web App (PWA). PWAs run in their own window, can be pinned to the taskbar, and often preserve a compact UI. For web services that you treated as “mini‑apps” in the sidebar, installing a PWA is the most robust alternative.
- Use the Edge Bar (Windows 10 desktop feature). Edge Bar can host pinned sites and keeps them accessible from the desktop without opening a full browser window. Note: Edge Bar availability and behavior vary by Windows version.
- Pin pages to Favorites or the Favorites bar for quick access. This does not reproduce an always‑visible side pane, but it preserves link discoverability.
- Keep an eye on built‑in Microsoft sidebar tools (Copilot, Outlook, etc.). If your workflow uses Outlook previews or Microsoft 365 integration, those built‑ins will remain.
- Create keyboard or system shortcuts that open small windows for the sites you used as sidebar apps. If you’re technically inclined, launch PWAs with small window dimensions for a similar effect.
- Export or backup any data you keep in features adjacent to the sidebar workflow (for example, if you used Collections to save pages alongside sidebar usage, export those Collections now; options vary and some export formats lose notes/images).
Steps to install a PWA (generic guidance):
- Open the site in Microsoft Edge.
- From the browser menu, choose “Install site as app” or look for a plus/installation indicator in the address bar.
- Configure the PWA’s window behavior and optionally pin it to the taskbar or Start menu.
Note: If you rely on paired desktop behavior (Edge Bar on Windows 10), follow the Edge Bar settings to enable automatic opening or to move the sidebar to your desktop.
Enterprise-level controls and administration
Microsoft’s enterprise documentation for managing the sidebar is an essential resource for IT admins. Notable policy controls and technical specifics include:
- Edge admins can use policies such as EdgeSidebarAppUrlHostBlockList to control which sidebar apps are blocked (this policy applies to certain Edge versions and is documented in Microsoft’s enterprise documentation).
- Organizations can force‑install specific sidebar apps via ExtensionInstallForceList, which installs sidebar apps silently and prevents users from removing them — useful for ensuring essential built‑ins remain available to endpoints.
- The enterprise documentation identifies built‑in sidebar apps (Copilot, Shopping, Games, Office, Outlook, Drop, Image Creator, OneNote, Designer, etc.) and provides guidance for admin blocklists and forced installs.
- Because retirements and UI experiments often appear first in Canary/Dev channels, enterprises should monitor the Edge release notes and the Microsoft Tech Community announcements to ensure timely responses.
If your organization depends on the sidebar for critical workflows, immediate steps are:
- Audit which users rely on sidebar‑pinned content.
- Plan migrations to PWAs, managed bookmarks, or enterprise‑deployed web apps.
- Update Group Policy templates and prepare controlled rollouts for any replacements.
Administrators should be careful: policy controls can
force or
block sidebar apps, but they cannot resurrect functionality that Microsoft removes from the product itself. Long term planning and migration are preferable to short‑term lock‑ins.
Developer and partner implications
For web developers and service providers who relied on the sidebar as a distribution surface, the retirement introduces a few concrete risks and actions:
- Loss of an easy distribution point: third‑party sites that gained visibility as sidebar mini‑apps will lose that channel for user engagement.
- PWA adoption becomes more important: encouraging users to install your site as a PWA ensures persistence beyond Edge UI experiments.
- Rethink notification and revisit strategies: if sidebar visibility drove re‑engagement, developers should consider push notifications (careful with UX), deep linking, and progressive installation flows.
- Test narrow viewport experiences: the sidebar often approximated mobile vertical layouts. Developers should ensure their sites render cleanly in narrow windows/PWA frames to maintain a similar experience.
If your product team relied on the Edge sidebar's discoverability, begin shifting messaging and technical work to support PWA installation and small-window compatibility.
User data, privacy, and portability — what to watch for
A recurring pattern with feature retirements is friction around data portability. Microsoft’s earlier retirements (such as parts of Collections) show that export options are sometimes limited or lossy.
Key considerations for users:
- If you keep notes, images, or annotations tied to in‑browser features that are being removed, export them now where possible. Export formats vary in fidelity.
- Don’t assume pinned app entries are consultable after removal. If a pinned sidebar entry contains session data or tokens, verify whether that state will be preserved elsewhere (PWAs, cookies) or discarded.
- For families or shared machines tied to Microsoft accounts, check each profile — browser customizations are often profile‑scoped.
Until Microsoft publishes a definitive migration plan and data retention guarantees, users should proactively back up content and move critical workflows to supported alternatives.
Accessibility and power‑user workflows
The sidebar served as more than a cosmetic convenience for many users with specific workflows and accessibility needs. Examples:
- Users with limited screen real estate or specific motor accessibility preferences could keep small, predictable panes open without context switching.
- Multitaskers who rely on glanceable side information (chat windows, music, timers) lose a low‑friction option to keep that data visible.
- Assistive technology that hooks into Edge might depend on predictable UI surfaces; changes to the sidebar could require reconfiguration.
Microsoft has historically considered accessibility in major UI changes, but users with assistive device workflows should test alternative approaches (PWAs launched in small windows, dedicated apps, or pinned tabs with specific zoom/contrast settings).
Risks and tradeoffs — the longer view
Microsoft’s decision to simplify Edge by removing user‑addable sidebar apps has several structural risks:
- Feature churn and loss of trust: frequent removals of once‑prominent features (sidebar app list, Collections) can erode trust among enthusiasts who invest time in customizing the browser.
- Increased dependency on Copilot/Centralized features: the company is concentrating user attention on Copilot, which has strategic benefits for Microsoft but reduces user choice and increases platform lock‑in.
- Fragmentation for third‑party developers: removal of presentation surfaces can make distribution inconsistent across browsers and versions, pressuring developers to invest in PWAs or native clients.
- Enterprise disruption: workplace workflows that used the sidebar for lightweight tools could see productivity loss if migration isn’t carefully managed.
- Accessibility regressions: UI changes risk negatively affecting users who configured workflows around the sidebar’s persistent presence.
All of these are tradeoffs Microsoft appears willing to make for the benefits of simplification and Copilot prominence. The scale of negative effects will hinge on rollout timing, alternative tooling availability, and the company’s communication with affected users.
Recommendations — concrete steps for readers
For end users:
- Export any data associated with Edge features you use (Collections, pinned notes) as soon as you can.
- Install critical sites as PWAs and configure them to run in their own window.
- Move frequently used sites to Favorites and the Favorites bar as a short‑term hedge.
- If you rely on Edge Bar on Windows 10, verify whether the feature remains usable on your device and enable automatic opening if helpful.
For developers and web teams:
- Ensure your sites are PWA‑ready and verify small‑window usability.
- Update onboarding flows to prompt users to install the PWA (don’t rely on the sidebar for discovery).
- Test notification strategies and deep links to replace passive visibility that the sidebar previously provided.
For IT admins:
- Inventory dependencies on the sidebar across users and groups.
- Use Group Policy controls to manage sidebar behavior as long as the product allows (EdgeSidebarAppUrlHostBlockList, ExtensionInstallForceList).
- Prepare migration scripts and enterprise install packages for PWAs where necessary.
- Communicate migration timelines and training resources to affected users.
What to expect next — timeline and signals to watch
Because Microsoft has not published a fixed retirement date, expect a phased approach:
- Canary and Dev channels will continue to surface UI changes, warnings, and incremental removals.
- Microsoft may roll the change to Beta and Stable channels gradually — watch the Edge release notes and Microsoft Tech Community.
- Official support pages (Edge help, Edge Bar) may be updated to include migration steps and more precise timelines.
- If Microsoft intends to preserve user data, it will likely add export or migration prompts inside the product UI (as it has with Collections). If those prompts do not appear, assume more manual migration is necessary.
Watch for these signals in your own client: if the + / pin flow refuses new additions, or if the in‑product message explicitly lists an account or profile type (MSA vs. AAD), that indicates which cohorts are being changed first.
Conclusions
Microsoft’s retirement of the
Sidebar app list signals a deliberate pivot in Edge’s product strategy: prioritize built‑in, high‑impact surfaces like
Copilot while trimming customization points that fragment UI and consume maintenance cycles. For users who relied on the sidebar’s compact, glanceable web apps, this is a meaningful loss of convenience and flexibility. For developers and enterprise administrators, it’s a reminder to favor standards‑based, durable distribution models (PWAs, managed web apps, enterprise deployment policies) over ephemeral product surfaces.
The key takeaway is this: don’t wait. The deprecation is already visible to early testers, and the absence of a firm timeline means the functional phase‑out could accelerate. Back up data, migrate critical short workflows to PWAs or taskbar‑pinned apps, and if you’re an admin, prepare policies and communication for your users. Microsoft’s move may simplify Edge for a large percentage of users — but simplification that removes useful tools without clear, robust replacements carries real costs. Users and organizations that act now will preserve continuity; those who wait will face surprises.
For now, the sidebar is not gone everywhere, and Copilot remains. But if you depend on the sidebar’s quick‑access lane, treat this not as a curiosity in Canary, but as a signal to plan and migrate before the UI you depend on disappears.
Source: Microsoft Support
Streamline access to your favorite sites and apps with Sidebar in Microsoft Edge - Microsoft Support