[METADATA UPDATE][Merge by 2023-09-05] Global allowlist metadata update #206
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A Pull Request has been made from the Learn Platform's Metadata Management System to update allowlist-driven metadata. Please review and merge this Pull Request within 5 days.
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.
Fixing#713729 Retag ms.prod excel to ms.service excel - MicrosoftDocs/nav-content
Why we make metadata updates
The Learn Content Architecture team manages business-facing reporting taxonomies that enable analytics for OKR reporting and content portfolio management. These taxonomies are referred to as ms.* allowlists. Allowlist values populate metadata attributes.
We regularly review allowlists to ensure they are accurate, useful, and align to curr ent business needs. Updates to allowlists and allowlist-driven metadata make reports cleaner, easier to use, and more consistent.
We regularly review allowlists to ensure they are accurate, useful, and align to current business needs. Updates to allowlists and allowlist-driven metadata make reports cleaner, easier to use, and more consistent. Since metadata attributes are included in the YAML header, certain types of allowlist changes require making content updates.
How does this affect me?
Once changes to allowlist-driven metadata are merged, standard dashboards and reports will reflect new values. You'll need to use new filter values in those dashboards and reports. If you have custom dashboards or Kusto queries, you might need to update those as well.
Frequently Asked Questions
Why does this Pull Request appear to be made by the Repository Owner? We open Pull Requests two different ways.
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.