ci: use microsoft-graph-devx-bot GitHub App instead of PAT by ramsessanchez · Pull Request #802 · MicrosoftDocs/microsoftgraph-docs-powershell

ramsessanchez · 2026-07-14T22:45:34Z

Summary

Migrates the weekly reference docs pipeline off the PAT-backed GITHUB_TOKEN secret and onto the existing microsoft-graph-devx-bot GitHub App identity, for both the branch push and PR creation. Follows the same pattern as microsoftgraph/MSGraph-SDK-Code-Generator#1442.

Changes

scripts/Generate-Github-Token.ps1 (new): signs a JWT from the App ID + private key, resolves the installation, and mints a short-lived installation token (copied from the reference repo).
azure-pipelines/powershell-docs.yml: adds an AzureKeyVault@2 task to fetch microsoft-graph-devx-bot-appid / microsoft-graph-devx-bot-privatekey from akv-prod-eastus; the push step now mints an App installation token (masked via ##vso[task.setsecret]) and pushes with x-access-token instead of the PAT.
azure-pipelines/common-templates/create-pr.yml: mints an App token for gh pr create; drops the redundant PAT-based git push.

Prerequisites

The App requires contents:write and pull_requests:write on this repo (already granted).
The pipeline project must be able to use the Federated AKV Managed Identity Connection service connection.
Once validated, the old GITHUB_TOKEN PAT variable can be removed.

Automated change authored with GitHub Copilot CLI.

learn-build-service-prod · 2026-07-14T23:18:07Z

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.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md	country	3716	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.
2	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.
3	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. To avoid geopolitical issues, it should be replaced with 'country/region'.
4	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md	countries	9368	2	Replacement required	Geopolitical	Details The term `countries` is used in a description for a property that checks for service availability in different regions, and is not part of a code identifier or international standard. To avoid geopolitical issues, it should be replaced with `countries/regions`.
5	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 schema, which is considered a code identifier. According to global exceptions, code identifiers should not be replaced.
6	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 locale information and follows international standards (ISO 3166-1 alpha-2). According to the rules, when used in a legal, international standards, or similar context, the term should be left unchanged.
7	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 language and country component of a user's locale, which is a general reference to a country/region. To avoid geopolitical issues, it should be replaced with 'country/region'.
8	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`.
9	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.
10	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.
11	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 component of a user's locale, following ISO 3166-1 alpha-2 codes. Since this is not a code identifier or part of a URL, but rather documentation describing a user property, it should be updated to `country/region` to avoid geopolitical issues.
12	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md	countries	27575	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`.

13	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 field definition, which falls under the global exception for code identifiers and technical field names. It should not be replaced.
14	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 matches the rule for legal or international standards context. Therefore, it should be left unchanged.
15	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicy.md	country	9309	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 description labeling a country/region concept, so it should be updated to 'country/region' to avoid geopolitical issues.
16	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`.
17	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.
18	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.
19	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicy.md	country	18453	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 not a code identifier or technical field name, but a descriptive label in documentation. To avoid geopolitical issues, it should be replaced with `country/region`.

20	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md	country	3693	2	No action needed	Geopolitical	Details The term `country` is used as a property name in a technical API schema, which qualifies as a code identifier. According to global exceptions, code identifiers should not be replaced.
21	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'.
22	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 schema or API definition, which is considered a code identifier. According to global exceptions, code identifiers should not be replaced.
23	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md	country	15970	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 rules, the term should be left unchanged.
24	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md	countries	18453	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`.
25	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 API schema, which qualifies as a code identifier. According to global exceptions, code identifiers should not be replaced.
26	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 international standards (ISO 3166-1 alpha-2), which is a legal/international standard context. According to the rules, it should be left unchanged.
27	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md	countries	27552	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`.

28	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicy.md	country	6813	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.
29	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 not a code identifier or part of a URL, but a descriptive label in documentation. To avoid geopolitical issues, it should be replaced with `country/region`.
30	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 qualifies as a code identifier. According to global exceptions, code identifiers should not be replaced.
31	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicy.md	country	15937	2	No action needed	Geopolitical	Details The term `country` is used in the context of describing a locale representation, specifically referencing the ISO 3166-1 alpha-2 standard. This is an international standards context, so per the rules, the term should be left unchanged.
32	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 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'.

33	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernance.md	country	6636	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.
34	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernance.md	country	8982	2	Replacement required	Geopolitical	Details The term `country` is used in the description of a user's locale, specifically referencing the ISO 3166-1 alpha-2 country code. Since this is not a code identifier or part of a technical field name, and is used to describe a user's location, it should be updated to `country/region` to avoid geopolitical issues.
35	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernance.md	country	12767	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.
36	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'.
37	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernance.md	countries	27584	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'.

38	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernancePolicyTemplate.md	country	6916	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.
39	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernancePolicyTemplate.md	country	16031	2	No action needed	Geopolitical	Details The term `country` is used in the context of describing 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.

40	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernanceRequest.md	country	9054	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`.
41	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.
42	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernanceRequest.md	country	15854	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.
43	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`.

44	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectory.md	country	28977	2	Replacement required	Geopolitical	Details The term `country` is used in a descriptive context to explain the locale property, referencing language and country codes. To avoid geopolitical issues, it should be replaced with `country/region`.
45	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectory.md	countries	29114	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, which matches the rule for replacing with 'country/region' to avoid geopolitical issues.

46	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 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'.
47	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernanceRequest.md	country	12841	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.
48	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`.

49	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernancePolicyTemplate.md	country	6715	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.

50	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.CloudCommunications\Update-MgBetaCommunicationCallParticipant.md	country	939	2	No action needed	Geopolitical	Details The term `country` is used in a technical documentation context describing a property value for 'Region', 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 · 2026-07-14T23:45:53Z

Learn Build status updates of commit a47262d:

💡 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
azure-pipelines/common-templates/create-pr.yml	✅Succeeded
azure-pipelines/powershell-docs.yml	✅Succeeded
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)

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.

learn-build-service-prod · 2026-07-15T00:04:02Z

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.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md	country	3693	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.
2	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md	country	6862	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.
3	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md	country	15970	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.
4	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md	country	18316	2	Replacement required	Geopolitical	Details The term `country` is used to describe the locale component in a user setting, referencing ISO 3166-1 alpha-2 codes. This is not a code identifier or part of a URL, but a descriptive label in documentation. To avoid geopolitical issues, it should be replaced with `country/region`.
5	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.
6	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md	country	27415	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 describing a user property, it should be updated to `country/region` to avoid geopolitical issues.

7	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 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.
8	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicy.md	country	9309	2	Replacement required	Geopolitical	Details The term `country` is used to describe a component of a user's locale, specifically referencing the ISO 3166-1 alpha-2 country codes. Since this is not a code identifier or part of a technical field name, and is labeling a country/region concept, it should be replaced with `country/region` to avoid geopolitical issues.
9	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.
10	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 codes, which is an international standard. According to the rules, when used in international standards or similar contexts, the term should be left unchanged.
11	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicy.md	country	18453	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'.

12	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 schema, which qualifies as a code identifier. According to global exceptions, code identifiers should not be replaced.
13	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicy.md	country	6813	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, when used in international standards context, the term should be left unchanged.
14	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicy.md	country	15937	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.

15	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. This is an international standard context, so per the rules, the term should be left unchanged.
16	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernanceRequest.md	country	12841	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.

17	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernancePolicyTemplate.md	country	6916	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.
18	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernancePolicyTemplate.md	country	16031	2	No action needed	Geopolitical	Details The term `country` is used in the context of describing international standards (ISO 3166-1 alpha-2) for locale representation, which is a legal/international standards context. According to the rule, it should be left unchanged.
19	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 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\Update-MgBetaDirectoryTenantGovernance.md	country	6636	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.
21	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernance.md	country	8982	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'.
22	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernance.md	country	12767	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.
23	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernance.md	country	15936	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.
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.CloudCommunications\Update-MgBetaCommunicationCallParticipant.md	country	939	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 it is not labeling a list or UI element, and is part of a property description, it fits the exception for technical field/property descriptions and does not need to be replaced.

26	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.CloudCommunications\New-MgBetaCommunicationCall.md	country	1622	2	No action needed	Geopolitical	Details The term `country` is used in a technical property description for an API object, specifically as part of the explanation for the `Region` property. According to global exceptions, technical field names or property descriptions do not require replacement.
27	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.CloudCommunications\New-MgBetaCommunicationCall.md	country	1663	2	No action needed	Geopolitical	Details The term `country` is used in a technical property description, specifically as part of the explanation for the `Region` property, which can be a country, continent, or larger geographic region. Since this is documentation for a technical API property and not a UI label or general text, it falls under the global exception for technical field/property names and should not be replaced.
28	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.CloudCommunications\New-MgBetaCommunicationCall.md	country	1905	2	Replacement required	Geopolitical	Details The term `country` is used in a descriptive context to indicate that a region can be a country, continent, or larger geographic area. To avoid geopolitical issues, it should be replaced with 'country/region'.
29	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.CloudCommunications\New-MgBetaCommunicationCall.md	country	1962	2	No action needed	Geopolitical	Details The term `country` is used in a technical API property description, specifically as part of a field explaining the possible values for `Region`. According to global exceptions, technical field names and their descriptions do not require replacement, and rule #2 also applies for legacy code or technical resources.

30	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.CloudCommunications\Move-MgBetaCommunicationCall.md	country	697	2	No action needed	Geopolitical	Details The term `country` is used in a technical property description for an object model, specifically as part of the explanation for the `Region` property. According to global exceptions, technical field/property names and their documentation do not require replacement.

31	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernancePolicyTemplate.md	country	3546	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.
32	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernancePolicyTemplate.md	country	6715	2	No action needed	Geopolitical	Details The term `country` is used in the context of describing locale information and follows international standards (ISO 3166-1 alpha-2). According to the rules, when used in international standards or similar contexts, the term should be left unchanged.
33	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernancePolicyTemplate.md	country	9061	2	Replacement required	Geopolitical	Details The term `country` is used to describe the language and country component of a user's locale, which is a general reference to a country/region. To avoid geopolitical issues, it should be replaced with 'country/region'.
34	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernancePolicyTemplate.md	country	18176	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 URL, but rather a descriptive label in documentation, it should be updated to `country/region` to avoid geopolitical issues.

35	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.
36	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectory.md	country	26631	2	Replacement required	Geopolitical	Details The term `country` is used to describe a component of a locale representation, referencing ISO 3166-1 alpha-2 codes. To avoid geopolitical issues, it should be replaced with `country/region`.

37	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernanceRequest.md	country	3539	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.
38	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernanceRequest.md	country	9054	2	Replacement required	Geopolitical	Details The term `country` is used to describe a component of a locale setting, specifically referencing ISO 3166-1 alpha-2 codes. This 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`.
39	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernanceRequest.md	country	15854	2	No action needed	Geopolitical	Details The term `country` is used in the context of describing international standards (ISO 3166-1 alpha-2), which matches the rule for legal or international standards context. Therefore, it should be left unchanged.
40	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 locale component in user settings, referencing ISO 3166-1 alpha-2 codes. This is a general label for a country/region and should be updated to 'country/region' to avoid geopolitical issues.

41	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.CloudCommunications\New-MgBetaCommunicationCallParticipant.md	country	847	2	Replacement required	Geopolitical	Details The term `country` is used in a descriptive context to explain that a region can be a country, continent, or larger geographic region. To avoid geopolitical issues, it should be replaced with `country/region`.
42	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.CloudCommunications\New-MgBetaCommunicationCallParticipant.md	country	910	2	Replacement required	Geopolitical	Details The term `country` is used in a description of a participant's home region, which can be a country, continent, or larger geographic region. To avoid geopolitical issues, it should be replaced with 'country/region'.

43	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md	country	3716	2	No action needed	Geopolitical	Details The term `country` is used as a property name in a technical API schema, which qualifies as a code identifier. According to global exceptions, code identifiers should not be replaced.
44	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 the ISO 3166-1 alpha-2 standard. This is an international standard context, so per the rule, the term should be left unchanged.
45	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 schema, which is considered a code identifier. According to global exceptions, code identifiers should not be replaced.
46	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, which is an international standard. According to the rules, when used in international standards or similar contexts, the term should be left unchanged.
47	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 component of a user's locale, referencing ISO 3166-1 alpha-2 codes. Since this is not a code identifier or part of a technical field name, and it is labeling a country/region concept, it should be replaced with 'country/region' to avoid geopolitical issues.
48	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.
49	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md	country	25092	2	Replacement required	Geopolitical	Details The term `country` is used to describe a component of a locale representation, referencing ISO 3166-1 alpha-2 codes. Since this is not a code identifier or part of a URL, and it is labeling a country/region concept, it should be updated to `country/region` to avoid geopolitical issues.
50	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 a component of a user's locale, specifically referencing ISO 3166-1 alpha-2 codes. This is a general label for a country/region and should be updated to `country/region` to avoid geopolitical issues.

This comment lists only the first 50 of 78 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 · 2026-07-15T00:29:41Z

Learn Build status updates of commit 1a834de:

💡 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
azure-pipelines/common-templates/create-pr.yml	✅Succeeded
azure-pipelines/powershell-docs.yml	✅Succeeded
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)

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.

Pivots the weekly reference docs pipeline off the PAT-backed GITHUB_TOKEN secret and onto the existing microsoft-graph-devx-bot GitHub App identity for both the branch push and PR creation. - scripts/Generate-Github-Token.ps1 (new): mints a short-lived App installation token from the App ID + private key. - powershell-docs.yml: fetch App secrets from Key Vault and push using an App installation token (masked) instead of the PAT. - create-pr.yml: mint an App token for gh pr create; drop the redundant PAT-based git push. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

learn-build-service-prod · 2026-07-15T18:32:58Z

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 · 2026-07-15T19:17:11Z

Learn Build status updates of commit 247ca93:

✅ Validation status: passed

File	Status	Preview URL	Details
azure-pipelines/common-templates/create-pr.yml	✅Succeeded
azure-pipelines/powershell-docs.yml	✅Succeeded
scripts/Generate-Github-Token.ps1	✅Succeeded

For more details, please refer to the build report.

The push URL in the weekly docs pipeline had been corrupted to a literal '******github.com/...' (a masked log value pasted into source) since #802, so 'git push' failed silently while the step still reported success because 'git status' ran last. The branch never reached GitHub, so 'gh pr create' failed with 'No commits between main and <branch>'. - generate-docs-steps.yml: fix push URL to https://x-access-token:$token@github.com/..., throw on non-zero 'git push' exit code, and detect real changes by comparing the branch tip to the recorded base commit (the generation scripts pre-commit their output, so the working tree is clean at push time). - create-pr.yml: add a Condition parameter so PR creation is skipped cleanly when there are no changes instead of erroring. - GenerateMarkDown.ps1: track generated file count and fail if generation produces zero files, so a silent generation failure surfaces immediately. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: f3873c6c-209b-4bd2-b1a7-e96a27d4834a

ramsessanchez requested review from gavinbarron, msewaweru and peombwa as code owners July 14, 2026 22:45

ramsessanchez force-pushed the ramsessanchez/migrate-pipeline-to-app-auth branch from 1a834de to 247ca93 Compare July 15, 2026 18:17

peombwa approved these changes Jul 15, 2026

View reviewed changes

ramsessanchez merged commit 9c004d3 into main Jul 15, 2026
3 checks passed

ramsessanchez deleted the ramsessanchez/migrate-pipeline-to-app-auth branch July 15, 2026 21:13

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

ci: use microsoft-graph-devx-bot GitHub App instead of PAT#802

ci: use microsoft-graph-devx-bot GitHub App instead of PAT#802
ramsessanchez merged 1 commit into
mainfrom
ramsessanchez/migrate-pipeline-to-app-auth

ramsessanchez commented Jul 14, 2026

Uh oh!

learn-build-service-prod Bot commented Jul 14, 2026

Uh oh!

learn-build-service-prod Bot commented Jul 14, 2026

Uh oh!

learn-build-service-prod Bot commented Jul 15, 2026

Uh oh!

learn-build-service-prod Bot commented Jul 15, 2026

Uh oh!

learn-build-service-prod Bot commented Jul 15, 2026

Uh oh!

learn-build-service-prod Bot commented Jul 15, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

ramsessanchez commented Jul 14, 2026

Summary

Changes

Prerequisites

Uh oh!

learn-build-service-prod Bot commented Jul 14, 2026

PoliCheck Scan Report

More information about PoliCheck

Uh oh!

learn-build-service-prod Bot commented Jul 14, 2026

💡 Validation status: suggestions

Uh oh!

learn-build-service-prod Bot commented Jul 15, 2026

PoliCheck Scan Report

More information about PoliCheck

Uh oh!

learn-build-service-prod Bot commented Jul 15, 2026

💡 Validation status: suggestions

Uh oh!

learn-build-service-prod Bot commented Jul 15, 2026

PoliCheck Scan Report

✅ No issues found

More information about PoliCheck

Uh oh!

learn-build-service-prod Bot commented Jul 15, 2026

✅ Validation status: passed

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants