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

[ramsessanchez]

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

Part 2 of 2 — beta only (microsoftgraph/graph-powershell-beta, ~16,027 files).

The weekly refresh exceeds GitHub's ~25k changed-file limit, so it is split into two PRs by profile:

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

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

[ramsessanchez]

Superseded: splitting beta into two smaller PRs (part 2 and part 3 of 3) so GitHub can render each diff. v1.0 is #798.

[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\New-MgBetaWindowsUpdatesPolicyRing.md	country	3693	2	Replacement required	Geopolitical	Details The term `country` is used as a property label to indicate the user's country or region, which matches the rule for labeling a country/region list or similar resource. It should be replaced with `country/region` to avoid geopolitical issues.
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 standards. This is an international standard context, so per the rule, the term should be left unchanged.
3	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 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 labeling a country/region concept in user-facing documentation, it should be replaced with `country/region` to avoid geopolitical issues.
4	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md	countries	9345	2	Replacement required	Geopolitical	Details The term `countries` is used in user-facing documentation to describe the availability of services in different geographic areas. To avoid geopolitical issues, it should be replaced with `country/region`.
5	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, which is an international standard. According to the rules, when used in international standards or similar contexts, the term should be left unchanged.
6	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 language and country component of a user's locale, referencing ISO 3166-1 alpha-2 codes. This is a general descriptive context, not a code identifier or legacy code, so it should be updated to `country/region` to avoid geopolitical issues.
7	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.
8	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md	country	25069	2	No action needed	Geopolitical	Details The term `country` is used in the context of describing a locale representation, specifically referencing ISO 3166-1 alpha-2 codes, which is an international standard. According to the rules, when used in international standards or similar contexts, the term should be left unchanged.
9	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` or `country/region` as per the rule.
10	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.
11	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. This is an international standards context, so per the rule, the term should be left unchanged.
12	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'.
13	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md	countries	9368	2	Replacement required	Geopolitical	Details The term `countries` is used in the context of describing legal requirements for license assignment and service availability, which refers to a list of regions. To avoid geopolitical issues, it should be replaced with `countries/regions`.
14	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md	country	12824	2	No action needed	Geopolitical	Details The term `country` is used as a property name in a technical API schema, which qualifies as a code identifier. According to global exceptions, code identifiers should not be replaced.
15	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md	country	15993	2	No action needed	Geopolitical	Details The term `country` is used in the context of describing a locale representation, specifically referencing ISO 3166-1 alpha-2 codes. This is an international standard context, so per the rules, the term should be left unchanged.
16	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 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 global exception, and it labels a country/region concept, it should be replaced with 'country/region' to avoid geopolitical issues.
17	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 is not a code identifier or part of a technical field name. To avoid geopolitical issues, it should be replaced with `countries/regions`.
18	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 schema, which qualifies as a code identifier (field/property name). According to global exceptions, code identifiers should not be replaced.
19	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 locale codes as defined by international standards (ISO 3166-1 alpha-2), which matches the rule for legal or international standards context. Therefore, it should be left unchanged.
20	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 language and country component of a user's locale, which is not a technical identifier or code field. To avoid geopolitical issues, it should be replaced with `country/region`.
21	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`.
22	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.
23	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 technical field name, but rather a descriptive label in documentation. To avoid geopolitical issues, it should be replaced with `country/region`.
24	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'.
25	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.SignIns\Test-MgBetaIdentityConditionalAccess.md	country	122	2	No action needed	Geopolitical	Details The term `country` is used as a property name in a PowerShell code snippet, which falls under the global exception for technical field names and code identifiers. According to the priority logic, it should not be replaced.
26	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'.
27	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 to describe the country component of a locale code, specifically referencing the ISO 3166-1 alpha-2 standard. This is an international standards context, so the term should be left unchanged according to the rules.
28	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`.
29	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernance.md	country	3467	2	No action needed	Geopolitical	Details The term `country` is used as a property name in a technical API schema, which is a code identifier. According to global exceptions, code identifiers should not be replaced.
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	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`.
32	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 context of describing legal requirements for service availability, which refers to a list of regions. To avoid geopolitical issues, it should be replaced with `countries/regions`.
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	25101	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.
35	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.
36	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`.
37	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernanceRequest.md	countries	9191	2	Replacement required	Geopolitical	Details The term `countries` is used in a description for license assignment and service availability, which refers to a list of regions. To avoid geopolitical issues, it should be replaced with `countries/regions`.
38	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 country component of a locale, following ISO 3166-1 alpha-2 codes. In this context, it is not a code identifier or part of a technical field name, but rather explanatory documentation for a property that refers to a user's country or region. To avoid geopolitical issues, it should be replaced with `country/region`.
39	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 is not a code identifier or part of a standard. To avoid geopolitical issues, it should be replaced with `countries/regions`.
40	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicy.md	country	6963	2	No action needed	Geopolitical	Details The term `country` is used in the context of describing international standards (ISO 3166-1 alpha-2), which is a legal or standards-based usage. According to the rules, when used in international standards context, the term should be left unchanged.
41	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`.
42	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.
43	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`.
44	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 refer to geographic regions where services are available. To avoid geopolitical issues, it should be replaced with 'countries/regions' as per the rule for labeling country/region lists.
45	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernancePolicyTemplate.md	country	3747	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.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 a descriptive label in documentation, it should be updated to `country/region` to avoid geopolitical issues.
47	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 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`.
48	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 a description for license assignment and service availability, which refers to a list of regions. To avoid geopolitical issues, it should be replaced with `countries/regions`.
49	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 a field (`Region`) that can be a country, continent, or larger geographic region. Since this is documentation for a code property and describes a technical field, it falls under the global exception for technical field names and property descriptions, so it should not be replaced.
50	microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernancePolicyTemplate.md	countries	18313	2	Replacement required	Geopolitical	Details The term `countries` is used in the context of describing legal requirements for license availability, which refers to a list of regions. 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 c6691f4:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Preview URL	Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.DeviceManagement/Update-MgBetaDeviceManagement.md	❌Error		Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Add-MgBetaServicePrincipalTokenSigningCertificate.md	💡Suggestion		Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Confirm-MgBetaApplicationMemberGroup.md	💡Suggestion		Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Confirm-MgBetaApplicationMemberObject.md	💡Suggestion		Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Confirm-MgBetaServicePrincipalMemberGroup.md	💡Suggestion		Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Confirm-MgBetaServicePrincipalMemberObject.md	💡Suggestion		Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Get-MgBetaApplicationById.md	💡Suggestion		Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Get-MgBetaApplicationMemberGroup.md	💡Suggestion		Details
microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.Applications/Get-MgBetaApplicationMemberObject.md	💡Suggestion		Details

microsoftgraph/graph-powershell-beta/Microsoft.Graph.Beta.DeviceManagement/Update-MgBetaDeviceManagement.md

• Line 0, Column 0: [Error: PSMD2Yaml_FileProcessFailed] Failed to process file: Failed to convert Update-MgBetaDeviceManagement.md to YAML file by PlatyPS, need to check the content, can execute Measure-PlatyPSMarkdown to obtain diagnostics.

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.