Teams chat link queries return messages from wrong threads

[jonburchel]

Problem

When providing a specific Teams chat link to \�sk_work_iq\ (e.g., \https://teams.microsoft.com/l/chat/19:xxx@thread.v2/conversations?context=...\), the tool returns messages from other chat threads rather than the one specified in the link.

Evidence

The citation URLs in the response contained different thread IDs (e.g., \19:3746a407-136f-4152-bed7-842b6cf1fbcc_..., \19:db0566a4...) than the thread ID provided in the query (\19:224760b7...). The tool appeared to search broadly across the user's chats rather than scoping to the specific linked conversation.

Impact

This caused us to act on completely wrong information: we interpreted another conversation's requests as the task at hand, made incorrect changes to a documentation repository, and had to revert and redo the work. The tool's output was confidently presented with citations, making it non-obvious that the results were from the wrong thread.

Expected behavior

When a specific Teams chat link is provided, \�sk_work_iq\ should scope its response to messages from that specific conversation thread, or clearly indicate if it cannot resolve the link to a specific thread.

Reproduction

1. Call \�sk_work_iq\ with a question referencing a specific Teams chat link
2. Observe that the returned messages and citation URLs reference different thread IDs than the one in the provided link

[darrelmiller]

Can you confirm that if you do the same thing via M365 Copilot Chat that you get the correct result? If not, then please hit the thumbs down and provide feedback. If you get different results, then let us know and we will follow up.

[jonburchel]

I was unable to find it in M365 either. I also tried a new conversation link to check if that works for either, but neither M365 nor workiq is able to see conversations via sharing links (and also not documents by THEIR sharing links either). It can only find things by knowing their NAME and what TEAM they are on, etc.! That is totally unworkable. We use sharing links CONSTANTLY for EVERYTHING. My new shared convo link I tried just now was: Maanav, McLean, and Sam | Group Chat | Microsoft ***@***.***/conversations?context=%7B%22contextType%22%3A%22chat%22%7D> From: Darrel ***@***.***> Sent: Friday, April 3, 2026 4:03 AM To: microsoft/work-iq ***@***.***> Cc: Author ***@***.***> Subject: Re: [microsoft/work-iq] Teams chat link queries return messages from wrong threads (Issue #96) Can you confirm that if you do the same thing via M365 Copilot Chat that you get the correct result? If not, then please hit the thumbs down and provide feedback. If you get different results, then let us know and we will follow up. - Reply to this email directly, view it on GitHub<#96 (comment)> or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABIGFM6ONUQMY3PEVTCR4ZD4T5V3JBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFUY2DINZWHE2KI3TBNVS2QYLDORXXEX3JMSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44SQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKRRGEZTQNJZGM2DSNMCUR2HS4DFUVUXG43VMWSXMYLMOVS2UNBRHA4DONRVGYYDHJ3UOJUWOZ3FOKTGG4TFMF2GK>. You are receiving this email because you authored the thread. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.