SharePoint / SharePoint/sp-dev-docs

Broken link in Hosted Workbench

Open
#10,777 2 comments 1 reaction 1 assignee View on GitHub

@Ashlesha-MSFT is already working on this.

Since Apr 17, 2026.

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

Description

Target SharePoint environment

SharePoint Online

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

💥 SharePoint Framework

Developer environment

Windows

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

Hosted workbench in SharePoint Online

Describe the bug / error

In the Hosted workbench (_layouts/15/workbench.aspx), there is a broken link on the Web part data dialog. The link for "Learn about provisioning SharePoint assets from your SharePoint client-side web part" currently points to https://dev.office.com/sharepoint/docs/spfx/web-parts/get-started/provision-sp-assets-from-package. The link fails to load the page.

Steps to reproduce
  1. Open the Hosted workbench on any site collection
  2. Click the Web part data option from the menu
  3. At the bottom of the page, click the "Learn about provisioning SharePoint assets from your SharePoint client-side web part" link
  4. New tab opens to "https://dev.office.com/sharepoint/docs/spfx/web-parts/get-started/provision-sp-assets-from-package" with error (DNS_PROBE_FINISHED_NXDOMAIN).
Image
Expected behavior

Link should open to correct page, which appears to be

https://learn.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/get-started/provision-sp-assets-from-package

Looks like there should be a DNS redirect, but dev.office.com is not redirecting to the new Learn page.

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.