Microsoft has introduced a set of feed customization controls for the Copilot Discover feature in Edge Canary, giving users direct say over the AI-curated content that appears on their New Tab Page. The controls, spotted in recent experimental builds, expose options for language, region, channel selection, and card prioritization—all accessible from a cog wheel icon on the New Tab Page itself. This move marks a small but significant step toward user agency inside a browser that is rapidly being reshaped as an AI-first workspace.

What is Copilot Discover?

Copilot Discover is Microsoft’s successor to the traditional MSN/Discover feed that has occupied the Edge New Tab Page for years. Powered by Copilot’s curation and ranking logic, it blends standard news articles, personality-driven suggestions, and sponsored banner cards into a single stream labeled “Curated by Copilot.” In early Canary builds, the feed appears as a scrollable list of cards and tiles, with some items carrying thumbs-up/thumbs-down controls for quick feedback. The new controls put the user in the curator’s seat—at least to some degree.

The New Feed Controls: What’s Available

When enabled, the New Tab Page’s cog wheel (or settings icon) now contains a “Feed settings” entry that surfaces quick personalization toggles. The key controls include:

  • Region and language selection – set the preferred locale for feed content.
  • Channel selection – emphasize or hide entire topic channels from your stream.
  • Block/allow specific channels – granular control to remove sources or topics you never want to see.
  • Card prioritization – choose which types of cards (e.g., news, entertainment, sponsored) appear at the top of the feed.

These options aim to reduce the friction of digging through deep Settings menus, making personalization immediate and discoverable. Early testers report that the interface is straightforward, though server-side feature gating means not everyone who enables the required flags will see the same results.

How to Test the Experimental Controls

Because the feed settings are currently locked behind experimental flags in Edge Canary, you’ll need to roll up your sleeves to try them. The general process is:

  1. Install or update to the latest Microsoft Edge Canary channel.
  2. Navigate to edge://flags and search for terms like NTP or CMFeature.
  3. Enable the relevant flags:
    - The main Copilot New Tab Page flag (often labeled CMFeature or Unified Composer NTP).
    - The specific feed-integration flag, reported as CMFeature: Copilot Discover Integration or exposed at edge://flags/#edge-ntp-composer-feed-integration in some Canary builds.
  4. Restart Edge and, if prompted, toggle Copilot Mode on via your profile settings.
  5. Open a New Tab Page and click the cog wheel to access the Feed settings control.

Important caveats: Canary builds are highly volatile. Flag names and behaviors can change daily, and you may need to sign into a Microsoft account for full functionality. If the settings don’t appear, a full browser restart or even a Windows session restart can help; UI assets sometimes arrive in stages.

Disabling Copilot Discover or Reverting to the Classic Feed

Not every user wants AI curation on their New Tab Page. Microsoft has built in multiple opt-out paths:

  • Turn off Copilot Mode entirely – go to Settings > AI Innovations (or Copilot Mode) and toggle Copilot Mode off. This restores the older New Tab behavior and removes all AI-centric workflows.
  • Disable only the Copilot Discover feed – navigate to Settings > Start, Home, and New Tab Page > New Tab Page and toggle off “Copilot New Tab Page,” or select the “Classic / MSN” feed option. This brings back the familiar MSN-powered feed.
  • Remove Copilot UI affordances – under Appearance or Copilot/Sidebar settings, you can hide the Copilot toolbar button and inline compose features. This is particularly useful for privacy-conscious users or enterprise environments.

Under the Hood: Flags, Codenames, and Server Gating

The Copilot New Tab Page experience is orchestrated across multiple layers:

  • Client flags (edge://flags) – toggle the UI and local behaviors.
  • Feed integration flag – specifically controls whether the Copilot feed is visible and integrated with the NTP composer code paths.
  • Server-side gating – even with flags enabled, Microsoft’s servers decide whether your account receives the curated feed or a placeholder. This is why some testers see a working feed while others only get the Copilot prompt or old MSN cards.

Internal codenames add to the confusion. Some Beta builds refer to the feed as “Ruby Feed,” while Canary uses “Copilot Discover.” Such inconsistency is par for the course in early experiments, but it complicates testing and reporting.

Privacy and Personalization: What the Controls Actually Change

Surface-level control is a welcome addition, but it exists within a broader system of data collection and curation. Key trade-offs include:

  • Personalization vs. profiling – choosing a language or channel inevitably signals preferences that Microsoft can use to refine recommendations. The company emphasizes that Copilot processing adheres to its privacy standards and that Copilot Mode is opt‑in, but testers should verify which telemetry is active.
  • Sponsored content – early Canary builds show large banner ads integrated directly into the AI-curated stream. The new feed settings let you hide the entire feed or tune channels, but there is no per‑ad opt‑out yet. For ad-averse users, the only bulletproof option is to disable the feed entirely.
  • Local vs. cloud processing – Copilot’s heavier operations (multi‑tab summarization, for instance) rely on cloud servers, and feed curation appears primarily server-driven. If strict data boundaries are essential, stick with the classic NTP and keep Copilot Mode off.

Where This Fits in Microsoft’s Broader Copilot Roadmap

Copilot Discover feed settings are one piece of a larger puzzle. Other Copilot-mode experiments bubbling up in Canary and Beta include:

  • Copilot theme – a visual browser frame that signals when Copilot Mode is active, aiming to provide a clear trust cue.
  • Multi‑tab summarization – lets Copilot synthesize information across open tabs, a core productivity feature for research and comparison shopping.
  • Scareware blocker controls – enhanced security heuristics that suppress misleading alert patterns and aggressive scareware content.

Taken together, these experiments reveal that Microsoft envisions Copilot Mode not as a simple chat sidebar, but as an entirely new browsing modality with its own UX, identity, and policy surfaces.

Practical Implications: Who Benefits and Who Should Be Cautious

Users who stand to gain:

  • Knowledge workers, students, and researchers who want contextual summaries and a glanceable, relevant feed.
  • Casual users comfortable with AI-driven personalization.
  • Power users and testers who enjoy exploring Canary flags and shaping early features.

Users who should exercise caution:

  • Privacy-conscious individuals who object to targeted promotions or AI curation without granular opt‑outs.
  • Enterprise administrators in regulated industries—policy controls and auditing for Copilot features are still evolving. Test on non-production images first.
  • Anyone who needs a stable workflow; Canary experiments can regress or change overnight.

Handy best practices:

  • If testing, use the cog wheel’s Feed settings to constrain channels and set language/region before letting the feed run for a few days.
  • Maintain a separate Edge profile for Canary to avoid contaminating your main profile.
  • Toggle “Show Feed” off the moment you see unwanted sponsored cards.
  • For enterprises, validate group policy interactions and deploy via staged rollouts only after confirming compliance.

Critical Analysis: Strengths, Risks, and Unanswered Questions

Strengths

  • Surface-level control: Putting feed settings directly on the New Tab Page cog wheel reduces friction and makes personalization immediate and discoverable.
  • Productivity promise: Multi‑tab synthesis and a tunable feed could save real time for research and decision-making.
  • Transparency cues: The Copilot theme and explicit “Curated by Copilot” labels are steps toward making AI involvement visible.

Risks and Concerns

  • Ad mixing and manipulation: Prominent sponsored cards blended into a curated stream can erode trust; users may struggle to separate editorial curation from paid placement. No ad‑level opt‑out exists yet.
  • Data surface creep: The richer context Copilot can access (open tabs, optionally history) magnifies the tradeoff between convenience and exposure. The new controls help but don’t eliminate this.
  • Control fragmentation: Flag‑and‑server gating creates an inconsistent experience—a toggle may appear inert because the server hasn’t delivered the feature. That fragmentation confuses users and complicates support.

Unanswered Questions

  • Will Microsoft add per‑source or per‑ad opt‑outs for sponsored content?
  • How will Copilot Discover respect Do Not Track signals or enterprise privacy policies at scale?
  • When (and if) will Copilot Mode’s free tier transition to a paid model, and how will that affect feed behaviour and access?

Conclusion

The arrival of Copilot Discover feed settings in Edge Canary is a small but meaningful acknowledgment that AI curation needs visible controls and clear opt‑outs. For users who want a smarter New Tab Page with more relevant content, these tools are a welcome upgrade. For privacy-minded users and IT administrators, the safest path remains cautious testing and reliance on the classic feed until per‑item controls mature. As Copilot Mode expands—with multi‑tab summarization, visual themes, and security enhancements already in test—the central challenge for Microsoft will be to keep that power transparent, controllable, and aligned with user expectations.