[METADATA UPDATE][Merge by 2023-07-13] Product-level header addition to prevent navigation issues

[learn-build-service-prod]

The "uhfHeaderId" field is being added to the Global Metadata section of this docfx file to prevent navigation issues because it is completely missing. For background on product-level headers, please review the product-level header requirements here: Navigation model overview | Microsoft Learn. Any changes to existing metadata fields will be communicated in advance of PRs.

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 docs-allowlist-mgmt@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#851590 Add uhfHeaderId = MSDocsHeader-Entra

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 2e047e9:

✅ Validation status: passed

File	Status	Preview URL	Details
java/docfx.json	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

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