Weekly PowerShell Microsoft Graph beta Reference Docs Refresh

[microsoft-graph-devx-bot]

This pull request was automatically created by Azure Pipelines. Important Check for unexpected deletions or changes in this PR.

[microsoft-github-policy-service]

@microsoft-graph-devx-bot[bot] please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

1. Definitions.
   “Code” means the computer software code, whether in human-readable or machine-executable form,
   that is delivered by You to Microsoft under this Agreement.
   “Project” means any of the projects owned or managed by Microsoft and offered under a license
   approved by the Open Source Initiative (www.opensource.org).
   “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
   Project, including but not limited to communication on electronic mailing lists, source code control
   systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
   discussing and improving that Project, but excluding communication that is conspicuously marked or
   otherwise designated in writing by You as “Not a Submission.”
   “Submission” means the Code and any other copyrightable material Submitted by You, including any
   associated comments and documentation.
2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
   Project. This Agreement covers any and all Submissions that You, now or in the future (except as
   described in Section 4 below), Submit to any Project.
3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
   Should You wish to Submit materials that are not Your original work, You may Submit them separately
   to the Project if You (a) retain all copyright and license information that was in the materials as You
   received them, (b) in the description accompanying Your Submission, include the phrase “Submission
   containing materials of a third party:” followed by the names of the third party and any licenses or other
   restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
   guidelines concerning Submissions.
4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
   for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
   Submission is made in the course of Your work for an employer or Your employer has intellectual
   property rights in Your Submission by contract or applicable law, You must secure permission from Your
   employer to make the Submission before signing this Agreement. In that case, the term “You” in this
   Agreement will refer to You and the employer collectively. If You change employers in the future and
   desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
   and secure permission from the new employer before Submitting those Submissions.
5. Licenses.

• Copyright License. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
  Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
  the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
  parties.
• Patent License. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
  Your patent claims that are necessarily infringed by the Submission or the combination of the
  Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
  import or otherwise dispose of the Submission alone or with the Project.
• Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
  No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
  granted by implication, exhaustion, estoppel or otherwise.

6. Representations and Warranties. You represent that You are legally entitled to grant the above
   licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
   have disclosed under Section 3). You represent that You have secured permission from Your employer to
   make the Submission in cases where Your Submission is made in the course of Your work for Your
   employer or Your employer has intellectual property rights in Your Submission by contract or applicable
   law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
   have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
   You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
   REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
   EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
   PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
   NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
7. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
   You later become aware that would make Your representations in this Agreement inaccurate in any
   respect.
8. Information about Submissions. You agree that contributions to Projects and information about
   contributions may be maintained indefinitely and disclosed publicly, including Your name and other
   information that You submit with Your Submission.
9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
   the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
   Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
   exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
   defenses of lack of personal jurisdiction and forum non-conveniens.
10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

[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.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.
2	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`.
3	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.
4	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.
5	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'.
6	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md	country	9208	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'.
7	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, which is considered a code identifier. According to global exceptions, code identifiers should not be replaced.
8	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md	country	15970	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 legacy code or a legal/international standards context, and it labels a country/region element, it should be replaced with `country/region` to avoid geopolitical issues.
9	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md	countries	18453	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`.
10	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.
11	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md	country	25069	2	Replacement required	Geopolitical	Details The term `country` is used in a descriptive context to explain the locale representation for a user, specifically referencing the ISO 3166-1 alpha-2 country codes. To avoid geopolitical issues, it should be replaced with `country/region`.
12	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 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 technical field name or code identifier, so it should be updated to 'country/region' to avoid geopolitical issues.
13	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.SignIns\Test-MgBetaIdentityConditionalAccess.md	country	84	2	No action needed	Geopolitical	Details The term `country` is used as a property name within a PowerShell hashtable in a code example, which qualifies as a technical field name. According to global exceptions, technical field names and code identifiers should not be replaced.
14	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.SignIns\Test-MgBetaIdentityConditionalAccess.md	country	198	2	No action needed	Geopolitical	Details The term `country` is used as a property name in a PowerShell hash table, which is a technical field name/code identifier. According to global exceptions, code identifiers should not be replaced.
15	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 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.
16	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`.
17	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.
18	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.
19	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'.
20	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicy.md	countries	18420	2	Replacement required	Geopolitical	Details The term `countries` is used in a description for legal requirements to check for availability of services in different regions. To avoid geopolitical issues, it should be replaced with `countries/regions`.
21	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernanceRequest.md	country	3695	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 and falls under the global exception for technical field names. It should not be replaced.
22	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`.
23	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'.
24	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 international standards (ISO 3166-1 alpha-2), which is a legal/international standards context. According to the rules, it should be left unchanged.
25	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernanceRequest.md	country	18356	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 element, so it should be updated to 'country/region' to avoid geopolitical issues.
26	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 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.
27	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 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` or `country/region` as per the rule.
28	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.
29	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 a description about legal requirements for license 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.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.
31	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 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'.
32	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 locale component in user settings, referencing ISO 3166-1 alpha-2 codes. This is a general label for a country/region, not a technical field name or code identifier, so it should be updated to 'country/region' to avoid geopolitical issues.
33	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernance.md	country	21932	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.
34	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernance.md	country	27447	2	Replacement required	Geopolitical	Details The term `country` is used to describe the locale component in a user profile, 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'.
35	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernancePolicyTemplate.md	country	12661	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\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.
37	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.
38	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 schema, specifically as a field label in an API or data model. According to global exceptions, technical field names and database columns should not be replaced.
39	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, following ISO 3166-1 alpha-2 codes. Since this is not a code identifier or part of a URL, and is used in a descriptive context, it should be replaced with `country/region` to avoid geopolitical issues.
40	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`.
41	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.CloudCommunications\New-MgBetaCommunicationCallParticipant.md	country	907	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 the term unchanged in legacy code or technical contexts, no replacement is needed.
42	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.
43	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.
44	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 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'.
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	countries	18476	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`.
47	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.
48	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.
49	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 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`.
50	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 for availability of services in different locations for licensing purposes. To avoid geopolitical issues, it should be replaced with `countries/regions`.

This comment lists only the first 50 of 104 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 2becd2e:

💡 Validation status: suggestions

File	Status	Preview URL	Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Add-MgBetaServicePrincipalTokenSigningCertificate.md	💡Suggestion	View (graph-powershell-beta)	Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Confirm-MgBetaApplicationMemberGroup.md	💡Suggestion	View (graph-powershell-beta)	Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Confirm-MgBetaApplicationMemberObject.md	💡Suggestion	View (graph-powershell-beta)	Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Confirm-MgBetaServicePrincipalMemberGroup.md	💡Suggestion	View (graph-powershell-beta)	Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Confirm-MgBetaServicePrincipalMemberObject.md	💡Suggestion	View (graph-powershell-beta)	Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Get-MgBetaApplicationById.md	💡Suggestion	View (graph-powershell-beta)	Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Get-MgBetaApplicationMemberGroup.md	💡Suggestion	View (graph-powershell-beta)	Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Get-MgBetaApplicationMemberObject.md	💡Suggestion	View (graph-powershell-beta)	Details
azure-pipelines/common-templates/create-pr.yml	✅Succeeded
azure-pipelines/common-templates/generate-docs-steps.yml	✅Succeeded
azure-pipelines/powershell-docs.yml	✅Succeeded
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Add-MgBetaApplicationKey.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Add-MgBetaApplicationPassword.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Clear-MgBetaApplicationVerifiedPublisher.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Find-MgBetaApplicationSynchronizationJobSchemaDirectory.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Find-MgBetaApplicationSynchronizationTemplateSchemaDirectory.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Find-MgBetaServicePrincipalSynchronizationJobSchemaDirectory.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Find-MgBetaServicePrincipalSynchronizationTemplateSchemaDirectory.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Get-MgBetaApplication.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Get-MgBetaApplicationAppManagementPolicy.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Get-MgBetaApplicationAppManagementPolicyByRef.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Get-MgBetaApplicationAppManagementPolicyCount.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Get-MgBetaApplicationByAppId.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Get-MgBetaApplicationByUniqueName.md	✅Succeeded	View (graph-powershell-beta)
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Get-MgBetaApplicationConnectorGroup.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.Applications/Add-MgBetaServicePrincipalTokenSigningCertificate.md

• Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Microsoft.Graph.Beta.Applications.Add-MgBetaServicePrincipalTokenSigningCertificate cmdlet. Parameters lacking description: DisplayName, EndDateTime

microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Confirm-MgBetaApplicationMemberGroup.md

• Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Microsoft.Graph.Beta.Applications.Confirm-MgBetaApplicationMemberGroup cmdlet. Parameters lacking description: GroupIds

microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Confirm-MgBetaApplicationMemberObject.md

• Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Microsoft.Graph.Beta.Applications.Confirm-MgBetaApplicationMemberObject cmdlet. Parameters lacking description: Ids

microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Confirm-MgBetaServicePrincipalMemberGroup.md

• Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Microsoft.Graph.Beta.Applications.Confirm-MgBetaServicePrincipalMemberGroup cmdlet. Parameters lacking description: GroupIds

microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Confirm-MgBetaServicePrincipalMemberObject.md

• Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Microsoft.Graph.Beta.Applications.Confirm-MgBetaServicePrincipalMemberObject cmdlet. Parameters lacking description: Ids

microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Get-MgBetaApplicationById.md

• Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Microsoft.Graph.Beta.Applications.Get-MgBetaApplicationById cmdlet. Parameters lacking description: Ids, Types

microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Get-MgBetaApplicationMemberGroup.md

• Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Microsoft.Graph.Beta.Applications.Get-MgBetaApplicationMemberGroup cmdlet. Parameters lacking description: SecurityEnabledOnly

microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Get-MgBetaApplicationMemberObject.md

• Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Microsoft.Graph.Beta.Applications.Get-MgBetaApplicationMemberObject cmdlet. Parameters lacking description: SecurityEnabledOnly

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.