Feedback: Loop, To Do, and Copilot/Work IQ Have Fundamental Data-Discoverability Gaps

**Category:** Microsoft Loop / Microsoft To Do / Microsoft 365 Copilot (Work IQ)

**Summary:** A day-long, hands-on investigation (creating, sharing, and re-locating the same task list through multiple M365 surfaces) surfaced several structural issues that prevent Copilot from reliably grounding on a user's own daily task content — even when using Microsoft's own recommended tools. Posting this as consolidated feedback rather than separate one-off tickets because the issues share a common root cause: **fragmented storage architecture that isn't transparent to end users, and inconsistent Copilot/Work IQ coverage across first-party productivity apps.**

---

## 1. Loop "My workspace" content is invisible to Copilot/Search — and there's no UI signal telling users this

When a Loop page/component is created directly in the Loop app (loop.cloud.microsoft), specifically in **My workspace**, it is stored in a user-owned **SharePoint Embedded container** (internally referenced as `CSP_...` in URLs). This container:

- Has no site interface and is **not surfaced in standard SharePoint/Graph search** by default (confirmed via Microsoft's own SharePoint Embedded dev docs: *"SPE content is in the SharePoint index but not surfaced in standard SharePoint searching"*).

- Is **not listed** in Work IQ's documented "Supported functionality" (Email, Meetings, OneDrive/SharePoint documents, Teams messages, Planner plans, Enterprise search — no mention of this container type).

- Cannot be opened/read via Microsoft Graph search or Copilot grounding, regardless of how many times the content is re-shared via email or Teams link.

**Reproduction:** Create a Loop page in My workspace → copy the page's share link → paste into an email or Teams message → send to yourself. The email/message is indexed and searchable, but the **linked Loop content is not** — Copilot can see that a link was shared, but cannot read what's on the other end.

**Why this matters:** Users have no way to know, from the UI, whether the Loop content they just created lives in an indexable location or a hidden one. The same "Loop Components" button behaves completely differently depending on entry point (see #2).

---

## 2. The exact same UI action ("Loop Components" button / sharing a component) produces content in *different, non-obvious storage backends* depending on where it's triggered

Through direct testing, the following was observed:

| Creation path | Resulting storage | Discoverable by Copilot/Search? |

| Loop app → My workspace → new page | SharePoint Embedded (`CSP_...` container) | ❌ No |

| Loop app → page → convert element to "Component" → copy link → paste in email | Still the same `CSP_...` container | ❌ No |

| **Teams chat** → Loop Components button → new component → send | OneDrive ("Microsoft Teams Chat Files" folder) | ✅ Yes |

| Loop component shared as `-my.sharepoint.com/personal/...` link | Personal OneDrive | ✅ Yes |

There is **no visual indicator** in the Loop or Teams UI that distinguishes these two families of storage. A user cannot tell, by looking at a component, whether it will ever be indexed. This makes "where should I put my recurring task tracker" an genuinely difficult, undocumented question for end users — we had to reverse-engineer the answer by inspecting URL domains across multiple test messages.

**Ask:** Either (a) unify storage so all Loop content is indexable by default, or (b) add a visible badge/tooltip in the Loop UI indicating "this content is stored in your personal workspace and won't be searchable/Copilot-discoverable outside this page" vs. "this content is in a shared, indexable location."

---

## 3. Loop "add to workspace" appears to create a shortcut, not a true move — ownership stays with the original creator/location

Adding an existing Loop component to a different (e.g., team) workspace generated a `.url` shortcut file rather than relocating the actual `.loop` file. The original file's location (and therefore its retention/discoverability characteristics) did not change. This isn't clearly communicated in the product — "add to workspace" reads like the content now *belongs* to that workspace.

---

## 4. Retention/discoverability interplay between Teams chat cleanup policies and Loop files needs clearer documentation

Per Microsoft's own retention docs, Teams message retention policies explicitly **exclude** files ("Emails and files that you use with Teams aren't included in retention policies for Teams"), and Loop files created in Teams chat land in the auto-generated "Microsoft Teams Chat Files" OneDrive folder, which does **not** appear on the list of folders with built-in expiration (unlike "Microsoft Copilot Chat Files," which auto-deletes after 30 days). This is good news for users worried about losing content when chats are periodically cleared — but it is **not documented anywhere user-facing**, and users are left to guess (or ask a forum) whether their task tracker will survive a chat retention sweep.

**Ask:** Add a plain-language note to Loop/Teams documentation clarifying that Loop files persist independently of chat message retention, unless a tenant admin has separately applied a retention label to that specific OneDrive folder.

---

## 5. Microsoft To Do is officially recommended for "individual tasks" but is **not included in Work IQ's supported data sources**

Microsoft's own guidance says: *"To work on individual tasks... start with To Do."* However, Work IQ's documented supported functionality list (Email, Meetings/calendar, OneDrive/SharePoint docs, Teams messages, People, **Microsoft Planner plans**, Enterprise search) explicitly names Planner but **omits To Do entirely**. This means:

- Copilot Chat cannot answer "what's on my To Do list today" — it has no grounding access to To Do task data at all.

- The only path to integrate To Do with an agent is a custom-built Graph API plugin (`/me/todo/lists`), which requires developer effort most end users can't do themselves.

- Multiple community threads (Tech Community, 2025–2026) confirm this gap has been raised repeatedly with no resolution: *"Doesn't look like Co-Pilot can natively interact with To Do just yet."*

**Ask:** Add Microsoft To Do to Work IQ's supported data sources. This is the most basic, universally-needed personal productivity data source in the entire suite, and it's currently a blind spot for the product Microsoft itself recommends as the default answer for personal task tracking.

---

## 6. To Do's flagged-email task preview truncates mid-sentence with no way to see the rest without leaving the app

When an email is flagged and appears in To Do's "Flagged email" list, the task detail pane shows a **truncated preview** of the email body — often cutting off mid-sentence at exactly the point where the actionable instruction is (e.g., "...we'll be looking for the item from" — no continuation). The only way to read the rest is to click "Open in Outlook" and leave the app entirely, defeating the purpose of a quick task-review pane. There is unused whitespace below the preview in the current UI, suggesting this is a low-effort truncation limit rather than a real space constraint.

This has been raised in the Microsoft Community forum since **January 2024** with zero replies/action: *"Having to open each email in a separate window is highly inefficient... Ideally, the email preview should take up whatever space remains in that righthand column."*

**Ask:** Either expand the preview pane to show full email body (space is clearly available), or make it resizable/scrollable so users aren't forced to leave the app to read one more sentence.

---

## 7. Overall: four overlapping personal/team task tools (To Do, Planner, Loop task lists, Teams Tasks app) with unclear, undocumented boundaries and uneven Copilot support

Each tool markets itself as suitable for slightly different scenarios, but:

- Sync between Loop task components and Planner reportedly creates a **new Plan per Loop component** rather than linking to an existing one — a bug/limitation raised on Tech Community since at least Oct 2025, still unresolved as of mid-2026, and explicitly called out by a commenter as something that "should have been a release blocker."

- "Add to Microsoft To Do" from Teams Copilot meeting recap action items has been intermittently available/unavailable, per community reports, with no clear roadmap status.

- None of this is explained in a single, current, authoritative "which tool for which scenario, and what's the Copilot support level for each" reference.

**Ask:** Publish (and keep updated) a single official comparison page that includes not just feature differences between To Do/Planner/Loop/Teams Tasks, but explicitly states **Copilot/Work IQ grounding support level** for each, so users can make an informed choice up front instead of discovering gaps through trial and error.

---

## Why this matters

Individually, each of these is a minor rough edge. Together, they mean that a fairly universal, basic task — "let Copilot help me track and recall my daily to-do list" — currently has **no reliable, fully-supported path** using only first-party Microsoft tools, despite Microsoft actively promoting an "AI-native," Copilot-everywhere vision across the 450M-seat M365 install base. A technically proficient user (myself) needed roughly a full day of trial-and-error, URL-inspection, and cross-referencing public docs to arrive at a partial workaround. That is not a reasonable bar for the average user, and it undercuts trust in Copilot's promise of "ask me anything about your work."

Happy to provide full repro steps, screenshots, or file/URL samples (redacted) if useful for triage.