[METADATA UPDATE][Merge by 2026-05-25] Ms.topic: pattern assignment project

[learn-build-service-prod]

A Pull Request has been made from the Learn Platform's Metadata Management System. Please review and merge this Pull Request within 5 days. If you have any questions or concerns about the purpose of these metadata updates, please contact kellypi@microsoft.com. If you are not the correct contact for this content and repository, please notify Metadata-Management@microsoft.com.

If this Pull Request is not merged within 14 days, it will be automatically merged by our system to ensure the timeliness of the metadata update. This includes bypassing the Repository's Branch Policy, including if Review Required is enabled. Please notify Metadata-Management@microsoft.com if you have questions or concerns or would like Pull Requests for metadata updates to merge automatically in future.

Fixing#1109843 Learn Reporting Taxonomy Request 1109843 Remove ms.topic value conceptual

Ms.topic: pattern assignment project
Update to align ms.topic value with customer intent.

Frequently Asked Questions
Why does this Pull Request appear to be made by the Repository Owner? We open Pull Requests two different ways.

• For Git Repos with a permissioned Service Account, we open the PR from our Document Build Service Account.
• For Git Repos that we either do not have Service Account permission for or the repo is in Azure Repos (ADO) we open the Pull Requests in an automated way with the PR creator as the Repo owner.

How can I revert a Pull Request that has been merged and created an unexpected issue? Whether a PR has been merged manually or automatically, you can revert it if an issue arises. See Reverting a pull request - GitHub Docs.

[learn-build-service-prod]

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 status updates of commit 04de75a:

💡 Validation status: suggestions

File	Status	Preview URL	Details
docs/apis/migrate-webparts-with-migrationapi.md	💡Suggestion	View	Details
docs/apis/migration-perm-guidance.md	💡Suggestion	View	Details

docs/apis/migrate-webparts-with-migrationapi.md

• Line 4, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'jhendr' is not a valid Microsoft alias.

docs/apis/migration-perm-guidance.md

• Line 6, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'jhendr' is not a valid Microsoft alias.

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.