SharePoint / SharePoint/sp-dev-docs

Clarification on PnP Search v4.11.0 Dependency on Microsoft Graph Toolkit (MGT)

Open
#10,986 3 comments 0 reactions 1 assignee View on GitHub

@Ashlesha-MSFT is already working on this.

Since Aug 11, 2026.

Needs: Author Feedback sharepoint-developer-support
Dominant language
PowerShell
Stars
1.4k
Forks
1.1k
Avg merge
4d 12h
Merged PRs (30d)
12

Description

What type of issue is this?

Question

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Target SharePoint environment

SharePoint Online

What browser(s) / client(s) have you tested
  • 💥 Internet Explorer
  • 💥 Microsoft Edge
  • 💥 Google Chrome
  • 💥 FireFox
  • 💥 Safari
  • mobile (iOS/iPadOS)
  • mobile (Android)
  • not applicable
  • other (enter in the "Additional environment details" area below)
Additional environment details
  • browser version
  • SPFx version
  • Node.js version
  • etc
Issue description

Hello everyone,

I have a question regarding PnP Search v4.11.0 and its dependency on Microsoft Graph Toolkit (MGT).

Since Microsoft has announced the retirement of MGT effective August 28, 2026, I wanted to understand whether this retirement will have any impact on applications using PnP Search v4.11.0.

Does PnP Search v4.11.0 have any dependency on MGT that would require customers to migrate or update their solutions? Or is it unaffected by the MGT retirement?

I'm looking for clarification on this so we can plan our migration strategy appropriately.

Thank you in advance for your guidance.
Umashankar Padhan

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.