[METADATA UPDATE][Merge by 2023-10-05] Global metadata/header/navigation changes

[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 learn-metadata@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#890100 Replace invalid ms.topic="get-started-article" with correct value "get-started"

Why we make metadata updates
It's important that metadata is appropriately managed to ensure its ongoing relevancy, usefulness, and reflects the current business. For example, metadata is updated to reflect a product rebrand. Because some metadata values (slugs) are included in the YAML header, metadata updates require changes to the content itself.

For metadata used internally, these updates make reports cleaner, easier to use, more consistent, and more reflective of current business. 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.

For customer-facing metadata, these updates ensure our customers are seeing the most up-to-date metadata on Learn content that matches what they see elsewhere in the Microsoft universe.

Why we make header/navigation updates
Header changes and other site navigation updates are crucial for improving content findability and are made in support of the navigation model strategy driven by the Learn Information Architecture and Content Architecture teams.

After you accept the header/navigation changes, you may now see a new or different product-level header used on content in your repo, revised breadcrumbs, or other navigation-related changes, which will be specified in the commit message.

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.

[learn-build-service-prod]

Learn Build status updates of commit d0d157d:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
dynamics-nav-app/index.md	⚠️Warning		Details
dynamics-nav-app/across-log-changes.md	💡Suggestion		Details
dynamics-nav-app/madeira-business-functionality.md	💡Suggestion		Details
dynamics-nav-app/madeira-sell.md	💡Suggestion		Details
dynamics-nav-app/about-develop-extensions.md	✅Succeeded
dynamics-nav-app/financials-requirements.md	✅Succeeded
dynamics-nav-app/madeira-how-setup-email.md	✅Succeeded
dynamics-nav-app/madeira-no-outlook.md	✅Succeeded
dynamics-nav-app/madeira-powerbi.md	✅Succeeded

dynamics-nav-app/index.md

• Line 29, Column 113: [Warning: insecure-link - See documentation] Link 'http://community.dynamics.com/product/nav/f/34.aspx' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
• Line 29, Column 113: [Suggestion: link-broken - See documentation] Link 'http://community.dynamics.com/product/nav/f/34.aspx' points to a page that doesn't exist. Check the path or URL and update the link.
• Line 40, Column 3: [Suggestion: link-broken - See documentation] Link '/previous-versions/dynamicsnav-2009r2/gg502505(v=nav.60)' points to a page that doesn't exist. Check the path or URL and update the link.
• Line 41, Column 3: [Suggestion: link-broken - See documentation] Link '/previous-versions/dynamicsnav-2009/dd355204(v=nav.60)' points to a page that doesn't exist. Check the path or URL and update the link.

dynamics-nav-app/across-log-changes.md

• Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

dynamics-nav-app/madeira-business-functionality.md

• Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

dynamics-nav-app/madeira-sell.md

• Line 27, Column 18: [Suggestion: link-broken - See documentation] Link 'https://community.dynamics.com/business/f/758' 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:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[RetYn]

#sign-off