[METADATA UPDATE] Global allowlist metadata update

[learn-build-service-prod]

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 you are not the correct contact for this content and repository, please notify [email protected].
• Please notify [email protected] if you have questions or concerns or would like Pull Requests for allowlist metadata updates to merge automatically in future.
• If you have questions or concerns about these metadata changes, please use https://aka.ms/AllowlistFeedback or contact [email protected] to let us know.

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.

Why we make metadata updates
The Skilling Content Architecture (CA) team manages business-facing reporting taxonomies that enable analytics for OKR reporting and content portfolio management. We refer to these taxonomies as allowlists. Allowlist values populate metadata attributes.

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.

Because metadata attributes are included in the YAML header, content updates are a prerequisite for certain types of allowlist changes.

**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.

• 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.