Skip to content

Archive legacy Modernization Scanner guidance#10959

Draft
TaoziZ03 wants to merge 3 commits into
SharePoint:mainfrom
TaoziZ03:titao/archive-modernization-scanner-docs
Draft

Archive legacy Modernization Scanner guidance#10959
TaoziZ03 wants to merge 3 commits into
SharePoint:mainfrom
TaoziZ03:titao/archive-modernization-scanner-docs

Conversation

@TaoziZ03

@TaoziZ03 TaoziZ03 commented Jul 21, 2026 •
edited
Loading

Copy link
Copy Markdown

Summary

  • add a Microsoft Learn overview page that introduces the Microsoft 365 Assessment tool before linking to the PnP documentation
  • move the legacy SharePoint Modernization Scanner navigation subtree under Archive without moving source files or changing existing Learn URLs
  • turn the existing Scanner landing page into an Assessment-first tool-selection page while preserving legacy instructions for existing users
  • add a reusable legacy notice to Scanner report and scenario pages
  • update short Scanner references according to current capability coverage

DocFX path cells use diff blocks: removed navigation paths start with -, and new paths start with +. Existing source files were not moved, so their published URLs remain unchanged.

DocFX navigation before and after

Before

Scenario guidance
├─ Overview
└─ Modernizing your classic SharePoint sites
   ├─ Overview
   ├─ Modernize the user interface
   │  ├─ Overview
   │  ├─ Maximize use of modern lists and libraries
   │  │  └─ Analyze and use the scanner data
   │  └─ Transform classic pages to modern pages
   ├─ SharePoint Modernization scanner
   │  ├─ Overview
   │  ├─ Understand the created reports
   │  │  ├─ Overview
   │  │  ├─ Microsoft 365 group connect report
   │  │  ├─ Modern list and libraries report
   │  │  ├─ Page modernization report
   │  │  ├─ Publishing portal modernization report
   │  │  ├─ Workflow usage report
   │  │  ├─ InfoPath usage report
   │  │  ├─ Blog usage report
   │  │  └─ SharePoint Designer customized forms report
   │  └─ Scanner FAQ
   ├─ SharePoint modernization guidance
   │  ├─ Overview
   │  └─ Assessment
   ├─ Connect to a Microsoft 365 group
   │  ├─ Overview
   │  └─ Analyze and use the scanner data
   └─ Modernize publishing portals
      ├─ Overview
      └─ Analyze and use the scanner data

Archive
├─ Overview
└─ Existing archived documentation

After

⭐ = This page directs users to Microsoft 365 Assessment when it supports the scenario.

Scenario guidance
├─ Overview
├─ Assess SharePoint modernization
│  └─ Overview ⭐
└─ Modernizing your classic SharePoint sites
   ├─ Overview
   ├─ Modernize the user interface
   │  ├─ Overview ⭐
   │  ├─ Maximize use of modern lists and libraries ⭐
   │  │  └─ Analyze legacy scanner data ⭐
   │  └─ Transform classic pages to modern pages
   ├─ SharePoint modernization guidance
   │  ├─ Overview ⭐
   │  └─ Legacy assessment delivery guidance ⭐
   ├─ Connect to a Microsoft 365 group
   │  ├─ Overview
   │  └─ Analyze legacy scanner data ⭐
   └─ Modernize publishing portals
      ├─ Overview ⭐
      └─ Analyze legacy scanner data ⭐

Archive
├─ Overview
├─ SharePoint Modernization scanner
│  ├─ Which assessment tool should I use? ⭐
│  ├─ Understand the legacy scanner reports
│  │  ├─ Overview ⭐
│  │  ├─ Microsoft 365 group connect report ⭐
│  │  ├─ Modern list and libraries report ⭐
│  │  ├─ Page modernization report ⭐
│  │  ├─ Publishing portal modernization report ⭐
│  │  ├─ Workflow usage report ⭐
│  │  ├─ InfoPath usage report ⭐
│  │  ├─ Blog usage report ⭐
│  │  └─ SharePoint Designer customized forms report ⭐
│  └─ Legacy scanner FAQ ⭐
└─ Existing archived documentation

File-by-file changes

File DocFX path change Change summary
docs/toc.yml Navigation configuration Adds the active Assessment entry, moves the Scanner subtree under Archive, and relabels legacy Scanner data pages.
docs/transform/assess-sharepoint-modernization.md 
+ Scenario guidance › Assess SharePoint modernization › Overview
/sharepoint/dev/transform/assess-sharepoint-modernization		 Introduces Microsoft 365 Assessment on Microsoft Learn before linking to PnP setup and module documentation.
docs/transform/modernize-scanner.md 
- Scenario guidance › Modernizing your classic SharePoint sites › SharePoint Modernization scanner › Overview
+ Archive › SharePoint Modernization scanner › Which assessment tool should I use?
URL unchanged: /sharepoint/dev/transform/modernize-scanner		 Reframes the page as an Assessment-vs-Scanner chooser while retaining legacy Scanner instructions and downloads.
docs/transform/modernize-scanner-reports.md 
- Scenario guidance › … › SharePoint Modernization scanner › Understand the created reports › Overview
+ Archive › SharePoint Modernization scanner › Understand the legacy scanner reports › Overview
URL unchanged		 Adds the shared legacy notice and preserves the legacy report index.
docs/transform/modernize-scanner-reports-groupconnect.md 
- Scenario guidance › … › Scanner reports › Microsoft 365 group connect report
+ Archive › … › Legacy scanner reports › Microsoft 365 group connect report
URL unchanged		 Adds the legacy notice; Groupify remains a Scanner-only assessment.
docs/transform/modernize-scanner-reports-lists.md 
- Scenario guidance › … › Scanner reports › Modern list and libraries report
+ Archive › … › Legacy scanner reports › Modern list and libraries report
URL unchanged		 Adds the legacy notice and retains the existing report schema.
docs/transform/modernize-scanner-reports-pages.md 
- Scenario guidance › … › Scanner reports › Page modernization report
+ Archive › … › Legacy scanner reports › Page modernization report
URL unchanged		 Adds the legacy notice; new page assessments are directed to Microsoft 365 Assessment.
docs/transform/modernize-scanner-reports-publishingportals.md 
- Scenario guidance › … › Scanner reports › Publishing portal modernization report
+ Archive › … › Legacy scanner reports › Publishing portal modernization report
URL unchanged		 Adds the legacy notice and preserves fields not yet available in Assessment.
docs/transform/modernize-scanner-reports-workflow.md 
- Scenario guidance › … › Scanner reports › Workflow usage report
+ Archive › … › Legacy scanner reports › Workflow usage report
URL unchanged		 Adds the legacy notice and retains retirement-era reference data.
docs/transform/modernize-scanner-reports-infopath.md 
- Scenario guidance › … › Scanner reports › InfoPath usage report
+ Archive › … › Legacy scanner reports › InfoPath usage report
URL unchanged		 Adds the legacy notice; new InfoPath assessments use Microsoft 365 Assessment.
docs/transform/modernize-scanner-reports-blogs.md 
- Scenario guidance › … › Scanner reports › Blog usage report
+ Archive › … › Legacy scanner reports › Blog usage report
URL unchanged		 Adds the legacy notice; new discovery uses the Classic Pages Assessment.
docs/transform/modernize-scanner-reports-customizedforms.md 
- Scenario guidance › … › Scanner reports › SharePoint Designer customized forms report
+ Archive › … › Legacy scanner reports › SharePoint Designer customized forms report
URL unchanged		 Adds the legacy notice; this remains a Scanner-only capability.
docs/transform/modernize-scanner-faq.yml 
- Scenario guidance › … › SharePoint Modernization scanner › Scanner FAQ
+ Archive › SharePoint Modernization scanner › Legacy scanner FAQ
URL unchanged		 Marks the FAQ as legacy while retaining existing-user instructions.
includes/snippets/open-source/modernization-scanner-legacy.md Reusable include; no published route Adds a consistent notice explaining Assessment-first and Scanner-only scenarios.
docs/transform/modernize-guidance-assessment.md 
- Scenario guidance › … › SharePoint modernization guidance › Assessment
+ Scenario guidance › … › SharePoint modernization guidance › Legacy assessment delivery guidance
URL unchanged		 Adds the legacy notice and keeps the Groupify-based delivery workflow available.
docs/transform/modernize-connect-to-office365-group-scanner.md 
- Scenario guidance › … › Connect to a Microsoft 365 group › Analyze and use the scanner data
+ Scenario guidance › … › Connect to a Microsoft 365 group › Analyze legacy scanner data
URL unchanged		 Adds the legacy notice; Groupify isn't currently available in Assessment.
docs/transform/modernize-userinterface-lists-and-libraries-scanner.md 
- Scenario guidance › … › Lists and libraries › Analyze and use the scanner data
+ Scenario guidance › … › Lists and libraries › Analyze legacy scanner data
URL unchanged		 Adds the legacy notice and preserves the existing report workflow.
docs/transform/modernize-publishing-portal-scanner.md 
- Scenario guidance › … › Modernize publishing portals › Analyze and use the scanner data
+ Scenario guidance › … › Modernize publishing portals › Analyze legacy scanner data
URL unchanged		 Adds the legacy notice and preserves fields not yet replaced by Assessment.
docs/community/open-source-projects.md Unchanged: /sharepoint/dev/community/open-source-projects Identifies the modernization repository as legacy tooling while preserving its existing redirected URL.
docs/solution-guidance/modern-experience-customizations.md Unchanged: /sharepoint/dev/solution-guidance/modern-experience-customizations Replaces the generic Scanner recommendation with the Assessment overview.
docs/transform/modernize-blogs.md Unchanged: /sharepoint/dev/transform/modernize-blogs Uses Classic Pages Assessment for new discovery and retains the legacy Blog report link.
docs/transform/modernize-branding.md Unchanged: /sharepoint/dev/transform/modernize-branding Directs new branding and extensibility inventory to Microsoft 365 Assessment.
docs/transform/modernize-connect-to-office365-group.md Unchanged: /sharepoint/dev/transform/modernize-connect-to-office365-group Retains the legacy Scanner because Groupify readiness isn't in Assessment.
docs/transform/modernize-customizations.md Unchanged: /sharepoint/dev/transform/modernize-customizations Directs list/library and extensibility assessment to Microsoft 365 Assessment.
docs/transform/modernize-guidance.md Unchanged: /sharepoint/dev/transform/modernize-guidance Adds the Assessment entry while retaining the Groupify scan required by the execution step.
docs/transform/modernize-publishing-portal.md Unchanged: /sharepoint/dev/transform/modernize-publishing-portal Explains partial Assessment coverage and retains Scanner for the complete legacy inventory.
docs/transform/modernize-userinterface.md Unchanged: /sharepoint/dev/transform/modernize-userinterface Uses Assessment for pages/lists/extensibility and legacy Scanner for Groupify.
docs/transform/modernize-userinterface-lists-and-libraries.md Unchanged: /sharepoint/dev/transform/modernize-userinterface-lists-and-libraries Directs new readiness assessment to the Classic Lists component.
docs/transform/modernize-userinterface-lists-and-libraries-rollout.md Unchanged: /sharepoint/dev/transform/modernize-userinterface-lists-and-libraries-rollout Updates both rollout approaches to use Microsoft 365 Assessment.
docs/transform/modernize-userinterface-lists-and-libraries-optout.md Unchanged: /sharepoint/dev/transform/modernize-userinterface-lists-and-libraries-optout Uses Assessment for new discovery while preserving the legacy ListOnly workflow.
docs/transform/modernize-userinterface-site-pages-dotnet.md Unchanged: /sharepoint/dev/transform/modernize-userinterface-site-pages-dotnet Identifies modern-page-feature detection as a legacy Scanner capability.
docs/transform/modernize-userinterface-site-pages-powershell.md Unchanged: /sharepoint/dev/transform/modernize-userinterface-site-pages-powershell Identifies modern-page-feature detection as a legacy Scanner capability.

Compatibility

  • no existing Scanner document source path or Learn URL is changed
  • legacy report schemas, FAQ content, downloads, and scanner-only workflows remain available
  • existing SharePoint/sp-dev-modernization links are preserved because GitHub redirects them to pnp/modernization
  • the active navigation entry stays on Microsoft Learn and links to PnP only after introducing the Assessment tool

Validation

  • full DocFX build completed successfully
  • no date-only files remain in the PR
  • the existing FAQ YAML warning and unrelated pre-existing TOC warning remain

titao
Archive legacy modernization scanner guidance
61177c9 
Make Microsoft 365 Assessment the active modernization assessment entry, retain the legacy Scanner documentation under Archive, and update scenario references according to current capability coverage.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: a7db0d98-be53-48c2-9488-9a226f457144
@learn-build-service-prod

learn-build-service-prod Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod

learn-build-service-prod Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 61177c9:

💡 Validation status: suggestions

File Status Preview URL Details
docs/community/open-source-projects.md 💡Suggestion View Details
docs/transform/modernize-scanner-faq.yml 💡Suggestion View Details
docs/features/groupify/groupify-overview.md ✅Succeeded View
docs/scenario-guidance/Branding.md ✅Succeeded View
docs/solution-guidance/modern-experience-customizations.md ✅Succeeded View
docs/toc.yml ✅Succeeded View
docs/transform/assess-sharepoint-modernization.md ✅Succeeded View
docs/transform/modernize-blogs.md ✅Succeeded View
docs/transform/modernize-branding.md ✅Succeeded View
docs/transform/modernize-connect-to-office365-group-scanner.md ✅Succeeded View
docs/transform/modernize-connect-to-office365-group.md ✅Succeeded View
docs/transform/modernize-customizations.md ✅Succeeded View
docs/transform/modernize-guidance-assessment.md ✅Succeeded View
docs/transform/modernize-guidance.md ✅Succeeded View
docs/transform/modernize-publishing-portal-scanner.md ✅Succeeded View
docs/transform/modernize-publishing-portal.md ✅Succeeded View
docs/transform/modernize-scanner-reports-blogs.md ✅Succeeded View
docs/transform/modernize-scanner-reports-customizedforms.md ✅Succeeded View
docs/transform/modernize-scanner-reports-groupconnect.md ✅Succeeded View
docs/transform/modernize-scanner-reports-infopath.md ✅Succeeded View
docs/transform/modernize-scanner-reports-lists.md ✅Succeeded View
docs/transform/modernize-scanner-reports-pages.md ✅Succeeded View
docs/transform/modernize-scanner-reports-publishingportals.md ✅Succeeded View
docs/transform/modernize-scanner-reports-workflow.md ✅Succeeded View
docs/transform/modernize-scanner-reports.md ✅Succeeded View

This comment lists only the first 25 files in the pull request.

docs/community/open-source-projects.md

  • Line 2, Column 1: [Suggestion: ms-service-suggested] Missing required attribute: 'ms.service'. ms.service is suggested for each article that is published on Learn.

docs/transform/modernize-scanner-faq.yml

  • Line 3, Column 3: [Suggestion: ms-service-suggested] Missing required attribute: 'ms.service'. ms.service is suggested for each article that is published on Learn.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

TaoziZ03
TaoziZ03 commented Jul 21, 2026
View reviewed changes
Comment thread docs/community/open-source-projects.md
TaoziZ03
TaoziZ03 commented Jul 21, 2026
View reviewed changes
Comment thread docs/features/groupify/groupify-overview.md Outdated

- [Connect a classic SharePoint team site to a new Microsoft 365 group](../../transform/modernize-connect-to-office365-group.md)
- [SharePoint Modernization scanner tool](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization)
- [Legacy SharePoint Modernization Scanner](../../transform/modernize-scanner.md)

@TaoziZ03 TaoziZ03 Jul 21, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to PM: do we need legacy prefix?
to copilot: the path is correct. don't modify.

titao
Preserve legacy modernization repository links
a74ba66 
Keep the existing SharePoint/sp-dev-modernization URLs because GitHub redirects them to the canonical pnp/modernization repository.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: a7db0d98-be53-48c2-9488-9a226f457144
@learn-build-service-prod

learn-build-service-prod Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod

learn-build-service-prod Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit a74ba66:

💡 Validation status: suggestions

File Status Preview URL Details
docs/community/open-source-projects.md 💡Suggestion View Details
docs/transform/modernize-scanner-faq.yml 💡Suggestion View Details
docs/features/groupify/groupify-overview.md ✅Succeeded View
docs/scenario-guidance/Branding.md ✅Succeeded View
docs/solution-guidance/modern-experience-customizations.md ✅Succeeded View
docs/toc.yml ✅Succeeded View
docs/transform/assess-sharepoint-modernization.md ✅Succeeded View
docs/transform/modernize-blogs.md ✅Succeeded View
docs/transform/modernize-branding.md ✅Succeeded View
docs/transform/modernize-connect-to-office365-group-scanner.md ✅Succeeded View
docs/transform/modernize-connect-to-office365-group.md ✅Succeeded View
docs/transform/modernize-customizations.md ✅Succeeded View
docs/transform/modernize-guidance-assessment.md ✅Succeeded View
docs/transform/modernize-guidance.md ✅Succeeded View
docs/transform/modernize-publishing-portal-scanner.md ✅Succeeded View
docs/transform/modernize-publishing-portal.md ✅Succeeded View
docs/transform/modernize-scanner-reports-blogs.md ✅Succeeded View
docs/transform/modernize-scanner-reports-customizedforms.md ✅Succeeded View
docs/transform/modernize-scanner-reports-groupconnect.md ✅Succeeded View
docs/transform/modernize-scanner-reports-infopath.md ✅Succeeded View
docs/transform/modernize-scanner-reports-lists.md ✅Succeeded View
docs/transform/modernize-scanner-reports-pages.md ✅Succeeded View
docs/transform/modernize-scanner-reports-publishingportals.md ✅Succeeded View
docs/transform/modernize-scanner-reports-workflow.md ✅Succeeded View
docs/transform/modernize-scanner-reports.md ✅Succeeded View

This comment lists only the first 25 files in the pull request.

docs/community/open-source-projects.md

  • Line 2, Column 1: [Suggestion: ms-service-suggested] Missing required attribute: 'ms.service'. ms.service is suggested for each article that is published on Learn.

docs/transform/modernize-scanner-faq.yml

  • Line 3, Column 3: [Suggestion: ms-service-suggested] Missing required attribute: 'ms.service'. ms.service is suggested for each article that is published on Learn.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

titao
Remove date-only documentation changes
a7d8f2c 
Restore the original dates on files whose link changes were reverted, keeping the PR focused on meaningful content updates.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: a7db0d98-be53-48c2-9488-9a226f457144
@learn-build-service-prod

learn-build-service-prod Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod

learn-build-service-prod Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit a7d8f2c:

💡 Validation status: suggestions

File Status Preview URL Details
docs/community/open-source-projects.md 💡Suggestion View Details
docs/transform/modernize-scanner-faq.yml 💡Suggestion View Details
docs/solution-guidance/modern-experience-customizations.md ✅Succeeded View
docs/toc.yml ✅Succeeded View
docs/transform/assess-sharepoint-modernization.md ✅Succeeded View
docs/transform/modernize-blogs.md ✅Succeeded View
docs/transform/modernize-branding.md ✅Succeeded View
docs/transform/modernize-connect-to-office365-group-scanner.md ✅Succeeded View
docs/transform/modernize-connect-to-office365-group.md ✅Succeeded View
docs/transform/modernize-customizations.md ✅Succeeded View
docs/transform/modernize-guidance-assessment.md ✅Succeeded View
docs/transform/modernize-guidance.md ✅Succeeded View
docs/transform/modernize-publishing-portal-scanner.md ✅Succeeded View
docs/transform/modernize-publishing-portal.md ✅Succeeded View
docs/transform/modernize-scanner-reports-blogs.md ✅Succeeded View
docs/transform/modernize-scanner-reports-customizedforms.md ✅Succeeded View
docs/transform/modernize-scanner-reports-groupconnect.md ✅Succeeded View
docs/transform/modernize-scanner-reports-infopath.md ✅Succeeded View
docs/transform/modernize-scanner-reports-lists.md ✅Succeeded View
docs/transform/modernize-scanner-reports-pages.md ✅Succeeded View
docs/transform/modernize-scanner-reports-publishingportals.md ✅Succeeded View
docs/transform/modernize-scanner-reports-workflow.md ✅Succeeded View
docs/transform/modernize-scanner-reports.md ✅Succeeded View
docs/transform/modernize-scanner.md ✅Succeeded View
docs/transform/modernize-userinterface-lists-and-libraries-optout.md ✅Succeeded View

This comment lists only the first 25 files in the pull request.

docs/community/open-source-projects.md

  • Line 2, Column 1: [Suggestion: ms-service-suggested] Missing required attribute: 'ms.service'. ms.service is suggested for each article that is published on Learn.

docs/transform/modernize-scanner-faq.yml

  • Line 3, Column 3: [Suggestion: ms-service-suggested] Missing required attribute: 'ms.service'. ms.service is suggested for each article that is published on Learn.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@microsoft-github-policy-service

microsoft-github-policy-service Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

@TaoziZ03 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

  1. Definitions.
    “Code” means the computer software code, whether in human-readable or machine-executable form,
    that is delivered by You to Microsoft under this Agreement.
    “Project” means any of the projects owned or managed by Microsoft and offered under a license
    approved by the Open Source Initiative (www.opensource.org).
    “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
    Project, including but not limited to communication on electronic mailing lists, source code control
    systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
    discussing and improving that Project, but excluding communication that is conspicuously marked or
    otherwise designated in writing by You as “Not a Submission.”
    “Submission” means the Code and any other copyrightable material Submitted by You, including any
    associated comments and documentation.
  2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
    Project. This Agreement covers any and all Submissions that You, now or in the future (except as
    described in Section 4 below), Submit to any Project.
  3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
    Should You wish to Submit materials that are not Your original work, You may Submit them separately
    to the Project if You (a) retain all copyright and license information that was in the materials as You
    received them, (b) in the description accompanying Your Submission, include the phrase “Submission
    containing materials of a third party:” followed by the names of the third party and any licenses or other
    restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
    guidelines concerning Submissions.
  4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
    for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
    Submission is made in the course of Your work for an employer or Your employer has intellectual
    property rights in Your Submission by contract or applicable law, You must secure permission from Your
    employer to make the Submission before signing this Agreement. In that case, the term “You” in this
    Agreement will refer to You and the employer collectively. If You change employers in the future and
    desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
    and secure permission from the new employer before Submitting those Submissions.
  5. Licenses.
  • Copyright License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
    Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
    the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
    parties.
  • Patent License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
    Your patent claims that are necessarily infringed by the Submission or the combination of the
    Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
    import or otherwise dispose of the Submission alone or with the Project.
  • Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
    No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
    granted by implication, exhaustion, estoppel or otherwise.
  1. Representations and Warranties. You represent that You are legally entitled to grant the above
    licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
    have disclosed under Section 3). You represent that You have secured permission from Your employer to
    make the Submission in cases where Your Submission is made in the course of Your work for Your
    employer or Your employer has intellectual property rights in Your Submission by contract or applicable
    law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
    have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
    You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
    REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
    EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
    PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
    NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
  2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
    You later become aware that would make Your representations in this Agreement inaccurate in any
    respect.
  3. Information about Submissions. You agree that contributions to Projects and information about
    contributions may be maintained indefinitely and disclosed publicly, including Your name and other
    information that You submit with Your Submission.
  4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
    the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
    Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
    exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
    defenses of lack of personal jurisdiction and forum non-conveniens.
  5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

@TaoziZ03 TaoziZ03 mentioned this pull request Jul 22, 2026
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@TaoziZ03