Weekly PowerShell Microsoft Graph Reference Docs Refresh (part 3 of 3: beta B)

[ramsessanchez]

This pull request was generated locally by running the reference-docs generation script sequence (mirroring the weekly powershell-docs.yml pipeline).

Part 3 of 3 — beta (group B), ~8,014 files.

The weekly refresh exceeds GitHub's changed-file rendering limit, so it is split into three PRs:

• Part 1: v1.0 → Weekly PowerShell Microsoft Graph Reference Docs Refresh (part 1 of 3: v1.0) #798
• Part 2: beta group A → Weekly PowerShell Microsoft Graph Reference Docs Refresh (part 2 of 3: beta A) #800
• Part 3 (this PR): beta group B

Important: Check for unexpected deletions or changes in this PR.

[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.

#	File	Term	Line	Sev	AI Recommendation	Class	AI Review Details
1	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernanceRequest.md	country	6864	2	No action needed	Geopolitical	Details The term `country` is used in the context of describing a locale representation, specifically referencing ISO 3166-1 alpha-2 standards. According to the rules, when used in international standards or similar contexts, the term should be left unchanged.
2	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernanceRequest.md	country	9210	2	Replacement required	Geopolitical	Details The term `country` is used in the context of describing a user's locale, specifically as part of a language and country or region code. To avoid geopolitical issues, it should be replaced with 'country/region'.
3	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernanceRequest.md	countries	9347	2	Replacement required	Geopolitical	Details The term `countries` is used in a description for license assignment and service availability, which refers to a list of regions. To avoid geopolitical issues, it should be replaced with `countries/regions`.
4	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernanceRequest.md	country	16010	2	No action needed	Geopolitical	Details The term `country` is used in the context of describing a locale representation, specifically referencing ISO 3166-1 alpha-2 codes. This is an international standards context, so per the rule, the term should be left unchanged.
5	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernanceRequest.md	countries	18493	2	Replacement required	Geopolitical	Details The term `countries` is used in a description about legal requirements for license assignment and service availability, which refers to a list of regions. To avoid geopolitical issues, it should be replaced with `countries/regions` or `country/region` as per the rule.
6	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicy.md	country	3644	2	No action needed	Geopolitical	Details The term `country` is used as a property name in a technical field definition, which falls under the global exception for code identifiers and technical field names. It should not be replaced.
7	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicy.md	country	9159	2	Replacement required	Geopolitical	Details The term `country` is used to describe a component of a user's locale, specifically referencing ISO 3166-1 alpha-2 codes. This is a general text label describing a country/region, not a code identifier or part of a technical field name, so it should be updated to 'country/region' to avoid geopolitical issues.
8	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicy.md	countries	9296	2	Replacement required	Geopolitical	Details The term `countries` is used in a description about legal requirements for license assignment and service availability, which refers to a list of regions. To avoid geopolitical issues, it should be replaced with `countries/regions`.
9	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicy.md	country	12768	2	No action needed	Geopolitical	Details The term `country` is used as a property name in a technical API schema, which is considered a code identifier. According to global exceptions, code identifiers should not be replaced.
10	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicy.md	country	18283	2	Replacement required	Geopolitical	Details The term `country` is used in the context of describing a user's locale, specifically as part of a language and country or region code. To avoid geopolitical issues, it should be replaced with 'country/region'.
11	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicy.md	countries	18420	2	Replacement required	Geopolitical	Details The term `countries` is used in the context of describing legal requirements for license assignment and service availability, which refers to a list of regions. To avoid geopolitical issues, it should be replaced with `countries/regions`.
12	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernancePolicyTemplate.md	country	9262	2	Replacement required	Geopolitical	Details The term `country` is used to describe the component of a locale, referencing ISO 3166-1 alpha-2 codes. Since this is not a code identifier or part of a URL, but rather documentation text describing a user property, it should be updated to `country/region` to avoid geopolitical issues.
13	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernancePolicyTemplate.md	countries	9399	2	Replacement required	Geopolitical	Details The term `countries` is used in a description about legal requirements for license assignment and service availability, which is not a code identifier or part of a URL. To avoid geopolitical issues, it should be replaced with `countries/regions`.
14	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernancePolicyTemplate.md	country	12862	2	No action needed	Geopolitical	Details The term `country` is used as a property name in a technical schema, specifically as a field label in a data model. According to global exceptions, technical field names and database column identifiers should not be replaced.
15	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernancePolicyTemplate.md	country	18377	2	Replacement required	Geopolitical	Details The term `country` is used to describe a component of a user's locale, specifically referencing ISO 3166-1 alpha-2 codes. Since this is not a code identifier or part of a technical field name, and is used in a descriptive context, it should be replaced with 'country/region' to avoid geopolitical issues.
16	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernancePolicyTemplate.md	countries	18514	2	Replacement required	Geopolitical	Details The term `countries` is used in the context of legal requirements for license assignment and service availability, which refers to a list of regions. To avoid geopolitical issues, it should be replaced with `countries/regions`.
17	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernanceRequest.md	country	6708	2	No action needed	Geopolitical	Details The term `country` is used in the context of describing a locale representation, specifically referencing ISO 3166-1 alpha-2 standards. According to the rules, when used in international standards or similar contexts, the term should be left unchanged.
18	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernanceRequest.md	country	12685	2	No action needed	Geopolitical	Details The term `country` is used as a property name in a technical schema, which is considered a code identifier. According to global exceptions, code identifiers should not be replaced.
19	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernanceRequest.md	country	18200	2	Replacement required	Geopolitical	Details The term `country` is used to describe the component of a user's locale, referencing ISO 3166-1 alpha-2 codes. Since this is not a code identifier or part of a URL, but rather documentation text describing a user property, it should be updated to `country/region` to avoid geopolitical issues.
20	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernanceRequest.md	countries	18337	2	Replacement required	Geopolitical	Details The term `countries` is used in a description about legal requirements for license assignment and service availability, which refers to a list of regions. To avoid geopolitical issues, it should be replaced with `countries/regions`.
21	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernance.md	country	3467	2	No action needed	Geopolitical	Details The term `country` is used as a property name in a technical API schema, which is considered a code identifier. According to global exceptions, code identifiers should not be replaced.
22	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernance.md	countries	9119	2	Replacement required	Geopolitical	Details The term `countries` is used in a description for license assignment and service availability, which refers to a list of regions. To avoid geopolitical issues, it should be replaced with `countries/regions`.
23	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernance.md	country	18282	2	Replacement required	Geopolitical	Details The term `country` is used to describe the language and country component of a user's locale, which is not a technical field name or code identifier. To avoid geopolitical issues, it should be replaced with 'country/region'.
24	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernance.md	country	27447	2	Replacement required	Geopolitical	Details The term `country` is used in the context of describing a user's locale, specifically as part of a language and country or region code. To avoid geopolitical issues, it should be replaced with 'country/region'.
25	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectory.md	country	23462	2	No action needed	Geopolitical	Details The term `country` is used as a property name in a technical API schema, which is considered a code identifier. According to global exceptions, code identifiers should not be replaced.
26	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectory.md	country	26631	2	No action needed	Geopolitical	Details The term `country` is used in the context of describing a locale representation, specifically referencing ISO 3166-1 alpha-2 codes, which is an international standard. According to the rules, when used in international standards or similar contexts, the term should be left unchanged.
27	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md	country	6885	2	No action needed	Geopolitical	Details The term `country` is used in the context of describing a locale representation, specifically referencing ISO 3166-1 alpha-2 standards. According to the rules, when used in international standards or similar contexts, the term should be left unchanged.
28	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md	country	9231	2	Replacement required	Geopolitical	Details The term `country` is used in the context of describing a user's locale, specifically as part of a language and country or region code. This is not a code identifier or part of a technical field name, so it should be updated to `country/region` to avoid geopolitical issues.
29	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md	countries	9368	2	Replacement required	Geopolitical	Details The term `countries` is used in the context of describing legal requirements for service availability, which refers to a list of regions. To avoid geopolitical issues, it should be replaced with `countries/regions`.
30	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md	country	12824	2	No action needed	Geopolitical	Details The term `country` is used as a property name in a technical API schema, which is considered a code identifier. According to global exceptions, code identifiers should not be replaced.
31	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md	country	15993	2	No action needed	Geopolitical	Details The term `country` is used in the context of describing a locale representation, specifically referencing ISO 3166-1 alpha-2 codes. This is an international standard context, so per the rule, the term should be left unchanged.
32	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md	country	18339	2	Replacement required	Geopolitical	Details The term `country` is used to describe the country component of a locale, following ISO 3166-1 alpha-2 codes. In this context, it is not a code identifier or part of a technical field name, but rather explanatory documentation for a user-facing property. To avoid geopolitical issues, it should be replaced with `country/region`.
33	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md	countries	18476	2	Replacement required	Geopolitical	Details The term `countries` is used in the context of checking for availability of services in different regions for licensing purposes. To avoid geopolitical issues, it should be replaced with `countries/regions`.
34	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md	country	21923	2	No action needed	Geopolitical	Details The term `country` is used as a property name in a technical API schema, which is considered a code identifier. According to global exceptions, code identifiers should not be replaced.
35	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md	country	25092	2	No action needed	Geopolitical	Details The term `country` is used in the context of describing a locale representation, specifically referencing ISO 3166-1 alpha-2 codes, which is an international standard. According to the rules, when used in international standards or similar contexts, the term should be left unchanged.
36	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md	country	27438	2	Replacement required	Geopolitical	Details The term `country` is used to describe the country component of a locale, referencing ISO 3166-1 alpha-2 codes. In this context, it is not a code identifier or part of a technical field name, but rather a descriptive label in documentation. To avoid geopolitical issues, it should be replaced with `country/region`.
37	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md	countries	27575	2	Replacement required	Geopolitical	Details The term `countries` is used in the context of checking service availability for users assigned licenses, which refers to a list of regions. To avoid geopolitical issues, it should be replaced with `countries/regions`.
38	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicy.md	country	3794	2	No action needed	Geopolitical	Details The term `country` is used as a property name in a technical schema, which qualifies as a code identifier. According to global exceptions, code identifiers should not be replaced.
39	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicy.md	country	6963	2	No action needed	Geopolitical	Details The term `country` is used in the context of describing international standards (ISO 3166-1 alpha-2), which is a legal or standards-based usage. According to the rules, it should be left unchanged.
40	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicy.md	countries	9446	2	Replacement required	Geopolitical	Details The term `countries` is used in a description about legal requirements for license assignment and service availability, which refers to a list of regions. To avoid geopolitical issues, it should be replaced with `countries/regions`.
41	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicy.md	country	12938	2	No action needed	Geopolitical	Details The term `country` is used as a property name in a technical API schema, which is considered a code identifier. According to global exceptions, code identifiers should not be replaced.
42	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicy.md	country	16107	2	No action needed	Geopolitical	Details The term `country` is used in the context of describing a locale representation, specifically referencing ISO 3166-1 alpha-2 standards. According to the rules, when used in international standards or similar contexts, the term should be left unchanged.
43	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicy.md	countries	18590	2	Replacement required	Geopolitical	Details The term `countries` is used in the phrase 'availability of services in countries' to describe a list of regions where services are available. To avoid geopolitical issues, it should be replaced with 'countries/regions'.
44	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md	country	9208	2	Replacement required	Geopolitical	Details The term `country` is used in the context of describing a user's locale, specifically as part of a language and country or region code. To avoid geopolitical issues, it should be replaced with `country/region`.
45	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md	countries	9345	2	Replacement required	Geopolitical	Details The term `countries` is used in user-facing documentation to describe the availability of services in different geographic areas. To avoid geopolitical issues, it should be replaced with `country/region` as per the guidance.
46	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md	country	12801	2	No action needed	Geopolitical	Details The term `country` is used as a property name in a technical API schema, which is considered a code identifier. According to global exceptions, code identifiers should not be replaced.
47	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md	country	21900	2	No action needed	Geopolitical	Details The term `country` is used as a property name in a technical schema or API definition, which is considered a code identifier. According to global exceptions, code identifiers should not be replaced.
48	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md	country	25069	2	No action needed	Geopolitical	Details The term `country` is used in the context of describing a locale representation, specifically referencing ISO 3166-1 alpha-2 codes, which is an international standard. According to the rules, when used in international standards or similar contexts, the term should be left unchanged.
49	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernancePolicyTemplate.md	country	15830	2	No action needed	Geopolitical	Details The term `country` is used in the context of describing the ISO 3166-1 alpha-2 standard for country codes, which is an international standard. According to the rules, when used in international standards or similar contexts, the term should be left unchanged.
50	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.CloudCommunications\New-MgBetaCommunicationCallParticipant.md	country	910	2	No action needed	Geopolitical	Details The term `country` is used in a technical documentation context to describe a possible value for the `Region` property, which can be a country, continent, or larger geographic region. Since this is part of a property description and not a UI label or general text, and the rules specify to leave unchanged in legacy code or technical contexts, it does not need to be replaced.

This comment lists only the first 50 of 100 issues due to GitHub's comment length limit.

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 9cd86f4:

💡 Validation status: suggestions

File	Status	Preview URL	Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Clear-MgBetaSolutionBusinessScenarioPlannerTaskMessageReaction.md	💡Suggestion	View (graph-powershell-beta)	Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Microsoft.Graph.Beta.BusinessScenario.md	💡Suggestion	View (graph-powershell-beta)	Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/New-MgBetaSolutionBusinessScenarioPlannerTaskMessage.md	💡Suggestion	View (graph-powershell-beta)	Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Set-MgBetaSolutionBusinessScenarioPlannerTaskMessageReaction.md	💡Suggestion	View (graph-powershell-beta)	Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Update-MgBetaSolutionBusinessScenarioPlannerTaskMessage.md	💡Suggestion	View (graph-powershell-beta)	Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Get-MgBetaSolutionBusinessScenario.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Get-MgBetaSolutionBusinessScenarioByUniqueName.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Get-MgBetaSolutionBusinessScenarioCount.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Get-MgBetaSolutionBusinessScenarioPlanner.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Get-MgBetaSolutionBusinessScenarioPlannerPlan.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Get-MgBetaSolutionBusinessScenarioPlannerPlanConfiguration.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Get-MgBetaSolutionBusinessScenarioPlannerPlanConfigurationLocalization.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Get-MgBetaSolutionBusinessScenarioPlannerPlanConfigurationLocalizationCount.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Get-MgBetaSolutionBusinessScenarioPlannerTask.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Get-MgBetaSolutionBusinessScenarioPlannerTaskAssignedToTaskBoardFormat.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Get-MgBetaSolutionBusinessScenarioPlannerTaskBucketTaskBoardFormat.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Get-MgBetaSolutionBusinessScenarioPlannerTaskConfiguration.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Get-MgBetaSolutionBusinessScenarioPlannerTaskCount.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Get-MgBetaSolutionBusinessScenarioPlannerTaskDetail.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Get-MgBetaSolutionBusinessScenarioPlannerTaskMessage.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Get-MgBetaSolutionBusinessScenarioPlannerTaskMessageCount.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Get-MgBetaSolutionBusinessScenarioPlannerTaskProgressTaskBoardFormat.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/New-MgBetaSolutionBusinessScenario.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/New-MgBetaSolutionBusinessScenarioPlannerPlanConfigurationLocalization.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/New-MgBetaSolutionBusinessScenarioPlannerTask.md	✅Succeeded	View (graph-powershell-beta)

This comment lists only the first 25 files in the pull request.

microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Clear-MgBetaSolutionBusinessScenarioPlannerTaskMessageReaction.md

• Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Microsoft.Graph.Beta.BusinessScenario.Clear-MgBetaSolutionBusinessScenarioPlannerTaskMessageReaction cmdlet. Parameters lacking description: ReactionType

microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Microsoft.Graph.Beta.BusinessScenario.md

• Line 0, Column 0: [Suggestion: PSMD2Yaml_UidDuplicated] Duplicate uid found: Microsoft.Graph.Beta.BusinessScenario.Get-MgBetaSolutionBusinessScenario shows more than once in Microsoft.Graph.Beta.BusinessScenario Cmdlets command group in module Microsoft.Graph.Beta.BusinessScenario. Microsoft.Graph.Beta.BusinessScenario.Get-MgBetaSolutionBusinessScenarioPlannerPlanConfigurationLocalization shows more than once in Microsoft.Graph.Beta.BusinessScenario Cmdlets command group in module Microsoft.Graph.Beta.BusinessScenario. Microsoft.Graph.Beta.BusinessScenario.Get-MgBetaSolutionBusinessScenarioPlannerTask shows more than once in Microsoft.Graph.Beta.BusinessScenario Cmdlets command group in module Microsoft.Graph.Beta.BusinessScenario. Microsoft.Graph.Beta.BusinessScenario.Get-MgBetaSolutionBusinessScenarioPlannerTaskMessage shows more than once in Microsoft.Graph.Beta.BusinessScenario Cmdlets command group in module Microsoft.Graph.Beta.BusinessScenario.

microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/New-MgBetaSolutionBusinessScenarioPlannerTaskMessage.md

• Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Microsoft.Graph.Beta.BusinessScenario.New-MgBetaSolutionBusinessScenarioPlannerTaskMessage cmdlet. Parameters lacking description: DeletedDateTime, EditedDateTime

microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Set-MgBetaSolutionBusinessScenarioPlannerTaskMessageReaction.md

• Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Microsoft.Graph.Beta.BusinessScenario.Set-MgBetaSolutionBusinessScenarioPlannerTaskMessageReaction cmdlet. Parameters lacking description: ReactionType

microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.BusinessScenario/Update-MgBetaSolutionBusinessScenarioPlannerTaskMessage.md

• Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Microsoft.Graph.Beta.BusinessScenario.Update-MgBetaSolutionBusinessScenarioPlannerTaskMessage cmdlet. Parameters lacking description: DeletedDateTime, EditedDateTime

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.