[METADATA UPDATE][Merge by 2026-08-03] Global ms.service and ms.subservice metadata update

[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 docs-allowlist-mgmt@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#1157670 Remove ms.subservice = web-pages paired with ms.service = aspnet-framework. Replaced by ms.subservice = web-pages paired with ms.service = aspnet-4x
Fixing#1157663 Remove ms.subservice = spa paired with ms.service = aspnet-framework. Replaced by ms.subservice = spa paired with ms.service = aspnet-4x
Fixing#1157668 Remove ms.subservice = web-forms paired with ms.service = aspnet-framework. Replaced by ms.subservice = web-forms paired with ms.service = aspnet-4x
Fixing#1157659 Remove ms.subservice = mobile paired with ms.service = aspnet-framework. Replaced by ms.subservice = mobile paired with ms.service = aspnet-4x
Fixing#1157657 Remove ms.subservice = ajax paired with ms.service = aspnet-framework. Replaced by ms.subservice = ajax paired with ms.service = aspnet-4x
Fixing#1157661 Remove ms.subservice = overview paired with ms.service = aspnet-framework. Replaced by ms.subservice = overview paired with ms.service = aspnet-4x
Fixing#1157662 Remove ms.subservice = signalr paired with ms.service = aspnet-framework. Replaced by ms.subservice = signalr paired with ms.service = aspnet-4x
Fixing#1157658 Remove ms.subservice = identity paired with ms.service = aspnet-framework. Replaced by ms.subservice = identity paired with ms.service = aspnet-4x
Fixing#1157664 Remove ms.subservice = visual-studio paired with ms.service = aspnet-framework. Replaced by ms.subservice = visual-studio paired with ms.service = aspnet-4x
Fixing#1157669 Remove ms.subservice = web-hooks paired with ms.service = aspnet-framework. Replaced by ms.subservice = web-hooks paired with ms.service = aspnet-4x
Fixing#1157660 Remove ms.subservice = mvc paired with ms.service = aspnet-framework. Replaced by ms.subservice = mvc paired with ms.service = aspnet-4x
Fixing#1157666 Remove ms.subservice = web-api paired with ms.service = aspnet-framework. Replaced by ms.subservice = web-api paired with ms.service = aspnet-4x
Fixing#1157671 Remove ms.subservice = whitepapers paired with ms.service = aspnet-framework. Replaced by ms.subservice = whitepapers paired with ms.service = aspnet-4x

Who initiated this PR?
The Learn Platform and Product (LPP) Site Experience team manages the Learn platform's reporting taxonomies that enable content analytics for OKR reporting and content portfolio management. Reporting taxonomy values populate metadata attributes.

We regularly review reporting taxonomies to ensure they are accurate, useful, and align to current business needs. Updates to reporting taxonomies and associated metadata make reports cleaner, easier to use, and more consistent.

Why are we updating ms.service/ms.subservice metadata?
Objective: Ensure ms.service attribute reliably reflects product affiliation.

Issues: 1. Currently, ms.service taxonomy values mix product and non-product concepts. Non-product concepts represent real reporting needs but aren't strictly about products. 2. Slugs (machine readable identifiers) don't reflect Microsoft branding guidelines. This is leading to inaccurate metadata on content.

Actions: 1. Revise taxonomy structure so "ms.service" represents the name of a branded Microsoft product, product family, or branding terminology. 2. Update slugs to comply with branding guidelines.

Outcome: 1. Establish a baseline for a comprehensive product data model representing all Microsoft offerings. 2. Ensure that report filters driven by ms.service will be based on product. 3. Improved metadata quality.

Why it matters

• Efficiency in Content Auditing: Revising the taxonomy structure will enable more precise content audits, fostering repeatable business processes and alleviating the burden of large-scale, one-off audit projects.
• Semantic Precision: The ms.service taxonomy will have meaningful, universally understood semantic values.
• Consistent Metadata: This work contributes to the accuracy and uniformity of contextual metadata within the Learn Knowledge Base.
• RAG Pipeline Efficiency: The Learn Knowledge Service's RAG pipeline will benefit from increased accuracy of product attribution of content.

How does this affect me?
After changes are complete, standard dashboards and reports will reflect new values, so you'll need to use new filter values. If you have any custom dashboards or Kusto queries, you might need to update those also.

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.