Add missing ms.topic metadata to group-view-report.md

[Copilot]

Build validation failing due to missing required ms.topic attribute in group-view-report.md.

Changes

• Added ms.topic: conceptual to the YAML front matter in microsoft-community-training/GA-version/analytics/in-built-reports/group-view-report.md

Value chosen for consistency with similar files in the repository (e.g., power-bi-integration.md).

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[test] fix ms-topic-missing</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			ms-topic-missing	microsoft-community-training/GA-version/analytics/in-built-reports/group-view-report.md	Missing required attribute: 'ms.topic'.	2, 1	01/20/2026 11:03:29

ms-topic-missing

Missing attribute: ms.topic. Add a valid value to indicate the article type.

Description

The ms.topic metadata attribute specifies the type of content, such as a conceptual article or an error reference article.

Resolution

Add the ms.topic metadata attribute to the page with a valid value that indicates the article type. ms.topic is required for all markdown conceptual articles.

For valid ms.topic values, see the [ms.topic allowlist] below.

ms.topic

The ms.topic value indicates the type of content.

Valid Values

These values are active and can applied to content or other use cases.

Slug	Definition
archived	Use for archived content only. Archived content lives under the /previous-versions path and has a banner denoting it’s archived.
article	Use for general articles that don’t map to the intent of a pattern in the Content Pattern Library.
best-practice	Use for content that offers recommendations for working with a service or feature.
blog	Use only for the Learn Platform blog. Blog content should be published on one of the Microsoft-sanctioned blog sites and not on the Learn platform.
browse-hub	Use for pages that include a Filter pane for customers to scope results. Content type is “ContentBrowser.”
checklist	Use for content that contains a list of requirements or tasks to complete or to use a product or feature.
concept-article	Use for content that provides an in-depth explanation of functionality related to a service(s) that is fundamental to understanding and use.
contributor-guide	Use for content published in a contributor guide.
design-pattern	Use for content that provides software design patterns used in architecture. The article follows a pattern that must include Context and problem, Solution, Issues and considerations, When to use this pattern, and Example sections.
end-user-help	Use for content aimed at end users that provides a resolution on a specific issue.
episode	Use for individual pages in the Show section of Learn.
error-reference	Use for reference content that documents error codes.
example-scenario	Use for content that describes a solution architecture and suggested best practices for a specific scenario. The guidance is aligned to well-architected design principles. It doesn’t have accompanying code. Customers are expected to use this type as they are starting the design process of the solution.
faq	Use for question-and-answer formatted content. (Has a .yml template.)
feature-availability	Use for an article that contains all service/feature availability for each sovereign cloud (China, US Gov, etc.)
feature-guide	Use for articles that describe a service or product feature.
generated-reference	Use for consistently-structured documentation of a technical artifact, like an API or SDK, that’s written entirely via autogeneration. Files are overwritten by autogeneration so updates are made at source.
get-started	Use for an article pattern that helps users get started using a particular product or service.
glossary	Use for an article pattern that lists relevant terms for understanding and using a product, service, or scenario.
how-to	Use for content that shows the customer how to complete a task.
hub-page	Use for collections of related services, products, languages, and training to quickly guide customers to their area of interest. (Has a .yml template.)
include	Use in [!INCLUDE] files only. It's required so Build, validation, and other tools work correctly.
install-set-up-deploy	Use to provide the basic structure of a Install, set up, deploy article pattern.
integration	Use for an article pattern that shows users how to connect applications, data, products, services, and devices.
interactive-tutorial	Use only for a legacy guided content experience containing interactive elements that prompt customers to continue to the next page, tracking their progress in the TOC (requires a .yml template). This value is no longer valid for training modules, units, or learning paths.
landing-page	Use for content that surfaces the top customer tasks or features w...

• Fixes [test] fix ms-topic-missing #462

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[learn-build-service-prod]

Learn Build status updates of commit 8436607:

⚠️ 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 dec0926:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
microsoft-community-training/GA-version/analytics/in-built-reports/group-view-report.md	⚠️Warning	View	Details

microsoft-community-training/GA-version/analytics/in-built-reports/group-view-report.md

• Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'Group view' is duplicated in: 'GA-version/analytics/in-built-reports/group-view-report.md(2,8), Public-Preview-Version/analytics/in-built-reports/group-view-report.md(2,8)'. Titles must be unique within a docset.
• Line 12, Column 1: [Warning: h1-not-first - See documentation] Markdown content is not allowed before H1 'Group View'.
• 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 'Group admin are responsible to drive engagement and monitor course completion for learners on the ground.' is duplicated in 'GA-version/analytics/in-built-reports/group-view-report.md(6,14)', 'Public-Preview-Version/analytics/in-built-reports/group-view-report.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.