microsoft / microsoft/work-iq

ask: cannot read or resolve SharePoint direct sharing URLs

Open
#166 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PowerShell
Stars
1k
Forks
132
Avg merge
5d 19h
Merged PRs (30d)
6

Description

Summary

ask_work_iq cannot retrieve content from a direct SharePoint sharing URL. When given a URL like https://microsoft.sharepoint.com/:w:/t/TeamName/..., it attempts an enterprise file search instead of resolving the sharing link, and returns no results.

Reproduction

  1. Ask: What is the content of the document at https://microsoft.sharepoint.com/:w:/t/CLPMSandboxv2/cQoGEnAVLo-...
  2. Response: "I couldn't retrieve that document. No matching file was returned by the search service."

Expected behavior

When a user provides a direct SharePoint sharing URL, WorkIQ should:

  1. Resolve the sharing link via the Graph API (e.g. /shares/{encodedUrl}/driveItem)
  2. Retrieve and summarize the document content

Context

Users frequently share documents via SharePoint sharing links. Being unable to read them makes WorkIQ ineffective for a core document collaboration workflow.

Environment

  • Copilot CLI 1.0.74-3
  • WorkIQ MCP plugin (npm @microsoft/workiq)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the ask_work_iq handling for URLs and the enterprise file-search fallback. Check how a SharePoint sharing URL can be encoded for the Graph API /shares/{encodedUrl}/driveItem endpoint. Done means a direct sharing URL resolves, the document content is retrieved, and the response summarizes it instead of returning no results.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
api, backend, search
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.