Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[METADATA UPDATE][Merge by 2023-09-05] Global allowlist metadata update #206

Merged
merged 1 commit into from
Aug 28, 2023

Conversation

learn-build-service-prod[bot]
Copy link
Contributor

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.

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

…a ms.prod=excel with ms.service=excel. This is part of the ms.prod/ms.service merge project.
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Hello, thanks for your contribution. However, as of October 201, Microsoft no longer regularly monitors contributions for this content. If you want to collaborate on content with us, we refer to the Microsoft Dynamics 365 Business Central.

@learn-build-service-prod
Copy link
Contributor Author

Learn Build status updates of commit ecef981:

💡 Validation status: suggestions

File Status Preview URL Details
dynamics-nav-app/admin-responding-to-requests-about-personal-data.md 💡Suggestion Details

dynamics-nav-app/admin-responding-to-requests-about-personal-data.md

  • Line 17, Column 476: [Suggestion: link-broken - See documentation] Link '/dynamics-nav/classifying-data' points to a page that doesn't exist. Check the path or URL and update the link.
  • Line 41, Column 1: [Suggestion: link-broken - See documentation] Link '/dynamics-nav/classifying-data' points to a page that doesn't exist. Check the path or URL and update the link.

For more details, please refer to the build report.

Note: Links can become broken if there are changes on the target sites. If you think the validation result is a false alarm, please use SiteHelp with option 'Content authoring and publishing -> False alarm on broken link validation' to 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.

For any questions, please:

@edupont04 edupont04 merged commit 90fc001 into main Aug 28, 2023
3 checks passed
@edupont04 edupont04 deleted the fba72c4d-c98a-4626-a055-be99b3184c36_90 branch August 28, 2023 08:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant