#Tag · bonfire.cafe

#Tag

Log in

@jukkan@mstdn.social · last month

"24 emails ought to be enough for anyone."
- Microsoft CEO, 2026.

Well, I don't know if Satya said that. But if he ever tried using Microsoft 365 Copilot to retrieve data from tens of emails in his mailbox, he'd get the same result as me.

Because #Copilot search tools don't support pagination.🙄 More details in this LI post: https://www.linkedin.com/feed/update/urn:li:activity:7412863547384414208/

#Microsoft365 #MSGraph

Copilot can’t return 25+ emails?

Examples of M365 Copilot responses for a query about emails that exceeded 24 items, as well as the same query via Copilot Search UI (which of course is an entirely different tool). — Copilot can’t return 25+ emails? Examples of M365 Copilot responses for a query about emails that exceeded 24 items, as well as the same query via Copilot Search UI (which of course is an entirely different tool).

If you try to retrieve data from tens of emails in your inbox in one go, Microsoft 365 Copilot is not the tool that can do it.

Access to MS Graph and the whole semantic index that Microsoft builds… | Jukka Niiranen | 13 comments

If you try to retrieve data from tens of emails in your inbox in one go, Microsoft 365 Copilot is not the tool that can do it. Access to MS Graph and the whole semantic index that Microsoft builds and maintains for you is the key selling point for choosing Copilot. You just have to remember that it's not like regular search. And that there is no one experience, nor any documented limits on when data will be cut off. Today, I asked my Copilot to analyze the frequency of specific emails that I've been getting since August. Powered by GPT-5.2 thinking, it went ahead, called Python tools and created charts for me. So far so good. Then, what was actually a nice improvement was that AFTER Copilot had completed the task, it admitted "you know, I can't actually complete your request". While this is not certain information, given it's an LLM that spits it out, it appears that tools like office365_search which Copilot calls don't support pagination. Instead, your AI assistant just gets the first set of matching records from Microsoft's data stores. In my case, I only got 24 emails from December. "If you want more, please use Windows Outlook classic and export the search results to a CSV", Copilot said. Oh great. Even the modern Outlook client can't actually give me the correct result data... This doesn't mean that there's a limit on how old information you can retrieve. It's just that what MS provides as tools for their AI assistant can't return data beyond these very low limits. Except if you go to Copilot Search. What's that? Well, it's of course NOT the search tool that Copilot the chatbot can use. It's rather an evolutionary version of what MS Search used to be. Which will return more results. And also not offer any way to export them into a CSV. This is where Copilot users struggle. They can't know when & why the tools fail. They get more reliable results when taking data outside the MS cloud and using some other AI chatbot to process the files and run basic Python tools. Not ideal from a compliance perspective, that's for sure. | 13 comments on LinkedIn

@jukkan@mstdn.social replied · last month

For future reference, I genrated this page of "Why can’t Microsoft 365 Copilot find my stuff?" from MS documentation, community blog posts, and vibes.✌️

https://vibes.jukkan.com/copilot-search-gotchas.html

#Microsoft365 #Copilot #MSgraph

Why can’t Microsoft 365 Copilot find my stuff?
Sometimes Copilot answers a question confidently, but the results feel incomplete—especially when you ask it to list or enumerate things (emails, files, meetings) over a long period. This page captures the most common reason: Copilot search is optimized for grounding (finding a useful subset), not for exhaustive export.

Think:
top matches
, not
full dump
Email search often skews
newest first
Counts can be misleading (or unavailable)
Mailbox scope matters (primary vs shared/archive) — Why can’t Microsoft 365 Copilot find my stuff? Sometimes Copilot answers a question confidently, but the results feel incomplete—especially when you ask it to list or enumerate things (emails, files, meetings) over a long period. This page captures the most common reason: Copilot search is optimized for grounding (finding a useful subset), not for exhaustive export. Think: top matches , not full dump Email search often skews newest first Counts can be misleading (or unavailable) Mailbox scope matters (primary vs shared/archive)

Why can't Microsoft 365 Copilot find my stuff?

@jukkan@mstdn.social · last month

"24 emails ought to be enough for anyone."
- Microsoft CEO, 2026.

Well, I don't know if Satya said that. But if he ever tried using Microsoft 365 Copilot to retrieve data from tens of emails in his mailbox, he'd get the same result as me.

Because #Copilot search tools don't support pagination.🙄 More details in this LI post: https://www.linkedin.com/feed/update/urn:li:activity:7412863547384414208/

#Microsoft365 #MSGraph

Copilot can’t return 25+ emails?

Examples of M365 Copilot responses for a query about emails that exceeded 24 items, as well as the same query via Copilot Search UI (which of course is an entirely different tool). — Copilot can’t return 25+ emails? Examples of M365 Copilot responses for a query about emails that exceeded 24 items, as well as the same query via Copilot Search UI (which of course is an entirely different tool).

If you try to retrieve data from tens of emails in your inbox in one go, Microsoft 365 Copilot is not the tool that can do it.

Access to MS Graph and the whole semantic index that Microsoft builds… | Jukka Niiranen | 13 comments

If you try to retrieve data from tens of emails in your inbox in one go, Microsoft 365 Copilot is not the tool that can do it. Access to MS Graph and the whole semantic index that Microsoft builds and maintains for you is the key selling point for choosing Copilot. You just have to remember that it's not like regular search. And that there is no one experience, nor any documented limits on when data will be cut off. Today, I asked my Copilot to analyze the frequency of specific emails that I've been getting since August. Powered by GPT-5.2 thinking, it went ahead, called Python tools and created charts for me. So far so good. Then, what was actually a nice improvement was that AFTER Copilot had completed the task, it admitted "you know, I can't actually complete your request". While this is not certain information, given it's an LLM that spits it out, it appears that tools like office365_search which Copilot calls don't support pagination. Instead, your AI assistant just gets the first set of matching records from Microsoft's data stores. In my case, I only got 24 emails from December. "If you want more, please use Windows Outlook classic and export the search results to a CSV", Copilot said. Oh great. Even the modern Outlook client can't actually give me the correct result data... This doesn't mean that there's a limit on how old information you can retrieve. It's just that what MS provides as tools for their AI assistant can't return data beyond these very low limits. Except if you go to Copilot Search. What's that? Well, it's of course NOT the search tool that Copilot the chatbot can use. It's rather an evolutionary version of what MS Search used to be. Which will return more results. And also not offer any way to export them into a CSV. This is where Copilot users struggle. They can't know when & why the tools fail. They get more reliable results when taking data outside the MS cloud and using some other AI chatbot to process the files and run basic Python tools. Not ideal from a compliance perspective, that's for sure. | 13 comments on LinkedIn

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances

Bonfire social · 1.0.2-alpha.7 no JS en

Automatic federation enabled

Log in