Skip to content

[METADATA UPDATE][Merge by 2025-06-27] Magic metadata update - new values for ms.topic #1080

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

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

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 [email protected]. If you are not the correct contact for this content and repository, please notify [email protected].

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 [email protected] if you have questions or concerns or would like Pull Requests for metadata updates to merge automatically in future.

Fixing#9802744 Project Junk Drawer - changing ms.topic - microsoft-365-community-pr-glossary

Magic metadata update - new values for ms.topic
In order to provide better experiences for our customers and for SEO, and to get our content AI-ready, we are updating ms.topic values that were set to "conceptual" or "article" to more specific values that are more closely aligned with the article contents.

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.

Copy link
Contributor Author

Learn Build status updates of commit b286027:

💡 Validation status: suggestions

File Status Preview URL Details
Community/glossary.md 💡Suggestion View Details

Community/glossary.md

  • Line 97, Column 5: [Suggestion: learn-site-link-broken - See documentation] Link '/azure/active-directory/app-proxy/application-proxy' points to a learn site page that doesn't exist. Check the path or URL and update the link.

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.

Copy link
Contributor Author

Learn Build status updates of commit db10c4b:

✅ Validation status: passed

File Status Preview URL Details
Community/glossary.md ✅Succeeded View

For more details, please refer to the build report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants