Fix duplicate-titles build warning for MS Teams customization doc

[Copilot]

Build validation flagged duplicate titles between GA-version and Public-Preview-Version of the MS Teams customization doc.

Changes

• Added (GA) suffix to title metadata and H1 heading in GA-version/.../customize-the-name-and-icon-of-the-training-tab-in-ms-teams.md

- title: Customize the name and icon of the training tab in MS Teams
+ title: Customize the name and icon of the training tab in MS Teams (GA)

Public-Preview-Version file retains the original title, making both unique within the docset.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[test] fix build warnings</issue_title>
<issue_description>Please fix the following build warnings

Severity	Type	ms.author	ms.service	ms.subservice	ms.topic	Code (click link for details)	File	Message	Line, Column	Time
Warning	User	nikotha	azure			duplicate-titles	microsoft-community-training/GA-version/infrastructure-management/configure-your-platform-infrastructure/customize-the-name-and-icon-of-the-training-tab-in-ms-teams.md	Title 'Customize the name and icon of the training tab in MS Teams' is duplicated in: 'GA-version/infrastructure-management/configure-your-platform-infrastructure/customize-the-name-and-icon-of-the-training-tab-in-ms-teams.md(2,8), Public-Preview-Version/infrastructure-management/configure-your-platform-infrastructure/customize-the-name-and-icon-of-the-training-tab-in-ms-teams.md(2,8)'. Titles must be unique within a docset.

duplicate-h1s

H1 '{h1-text}' is duplicated with other articles: '{file-path-1}', ...'{file-path-n}'. First level headings must be unique within a docset.

Description

For SEO, H1 headings (#) must be unique within a docset, and ideally should be unique across the site.

Resolution

Edit one or more first level heading so all H1s in your docset are unique.

For more information about how to write H1s, see [SEO: Tips for writing a heading 1 (H1)] below.

Optimize main headings (H1s)

This article shares some tips and best practices for optimizing H1s in your Learn content. The H1 is the main heading at the top of a page. It has the second greatest effect on search ranking and the greatest effect on relevance. Like the meta title, the H1 must quickly communicate the intent of the article–what a customer can learn or accomplish with the article.

Why are H1s important?

Search engines perform the complex task of trying to understand the meaning and content of a page. To achieve that, the crawler uses different signals, one of which is the content in the H1. Using your primary keyword in the H1 helps search engines understand the intent of the page and improves rank. H1s also have a significant impact on Copilot responses.

Along with helping search engines understand your content, the H1 also organizes the information on the page, which helps to improve the user experience and accessibility for readers. Increasing the readability of your page keeps users on the page longer.

Don't confuse the H1 with the meta title; they're two different elements. The H1 displays at the top of the article and has a limit of 100 characters including spaces. The meta title is in the article metadata and displays in the browser bar and on the search engine results page.

Rules for writing H1s

• There's only one H1. Ensure that every page has a single, unique H1 that is informative and specific to the on-page copy (Don't use the same H1 on two or more pages).
• Include the primary keyword in the H1. to improve keyword rank and increase time on page.
• Echo the language and intent from the meta title. Because the H1 allows more characters than a title, it can be more descriptive. It's best if you don't duplicate the meta title word-for-word.
• Ensure that the H1 is specific instead of general. It needs to communicate a specific intent.
• Add product/technology to the H1 if it creates more clarity and specificity.
• Write headings in sentence case (without a period).
• Don't use bold or italicized text in headings.
• Clarify error codes in headings. For pages that cover error codes, it's important to send a clear message to search engines that the content is referring to a resolution to an error instead of being an error itself. Pages that don't provide clarity often return a soft 404. Begin your heading with [Resolved] or [Fixed] in these cases.
• It's okay to incorporate multiple H2s and H3s on a page.

Heading examples

Example 1

Original H1: Devices (seven characters)

Edited H1: Overview of device APIs for Windows desktop app technologies (60 characters)

The original H1 is vague and overlaps with other Win32 pages. The updated H1 is much more informative and specific to the page, which ultimately helps search engines rank the content more effectively. One word is unlikely to ever be enough to describe the intent of a page. Add detail to sparse or short H1 text.

Example 2

Original H1: Getting started (15 characters)

Edited H1: Get sta...

• Fixes [test] fix build warnings #458

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[learn-build-service-prod]

Learn Build status updates of commit bca6e53:

⚠️ Validation status: warnings

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.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[learn-build-service-prod]

Learn Build status updates of commit d05edf7:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
microsoft-community-training/GA-version/infrastructure-management/configure-your-platform-infrastructure/customize-the-name-and-icon-of-the-training-tab-in-ms-teams.md	⚠️Warning	View	Details

microsoft-community-training/GA-version/infrastructure-management/configure-your-platform-infrastructure/customize-the-name-and-icon-of-the-training-tab-in-ms-teams.md

• Line 2, Column 1: [Warning: ms-topic-missing - See documentation] Missing required attribute: 'ms.topic'.
• Line 11, Column 1: [Warning: h1-not-first - See documentation] Markdown content is not allowed before H1 'Customize the name and icon of the training tab in MS Teams (GA)'.
• Line 2, Column 1: [Suggestion: ms-date-missing - See documentation] Missing required attribute: 'ms.date'.
• Line 6, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'This article assumes you have followed the steps outlined in the MS Teams installation (upto Step 2) and received the Team Manifest file from the Customer Support Team.' is duplicated in 'GA-version/infrastructure-management/configure-your-platform-infrastructure/customize-the-name-and-icon-of-the-training-tab-in-ms-teams.md(6,14)', 'Public-Preview-Version/infrastructure-management/configure-your-platform-infrastructure/customize-the-name-and-icon-of-the-training-tab-in-ms-teams.md(6,14)'.

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.