Skip to content

Weekly PowerShell Microsoft Graph Reference Docs Refresh - #826

Closed
microsoft-graph-devx-bot[bot] wants to merge 16 commits into
mainfrom
WeeklyReferenceDocsUpdate_202607291924
Closed

Weekly PowerShell Microsoft Graph Reference Docs Refresh#826
microsoft-graph-devx-bot[bot] wants to merge 16 commits into
mainfrom
WeeklyReferenceDocsUpdate_202607291924

Conversation

@microsoft-graph-devx-bot

Copy link
Copy Markdown
Contributor

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

Microsoft Graph DevX Tooling and others added 16 commits July 22, 2026 13:38
Guard GenerateMarkDown.ps1 so a module's docs are only deleted when the
module is available to regenerate them. Skip-and-preserve per workload
module, and abort if Authentication is unavailable, avoiding refresh PRs
that delete thousands of docs after a failed module install.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 4d27d82f-3809-40d2-b4e7-6623436ff2ef
EscapeDisallowedHtmlTags.ps1 and RemoveInvalidFullStops.ps1 hardcoded a
personal git identity, so their stage commits in the weekly refresh PRs
were attributed to an individual instead of the tooling bot. Align both
with the other generation scripts.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 4d27d82f-3809-40d2-b4e7-6623436ff2ef
- UpdateLinks.ps1: only insert the beta/v1 '[!NOTE]' link when it is not
  already present, so weekly runs stop stacking duplicate note blocks.
- GeneratePermissionsTable.ps1: skip files that already contain a
  '**Permissions**' table instead of prepending another copy each run.
- GenerateMarkDown.ps1: write PlatyPS output as UTF-8 without BOM so every
  regenerated file no longer diffs on a leading BOM.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 4d27d82f-3809-40d2-b4e7-6623436ff2ef
Add '*.md text eol=lf' to .gitattributes so PlatyPS/transform scripts,
which run on Windows and emit CRLF, no longer produce line-ending churn
in the weekly refresh PRs. Index blobs are already LF, so this only
pins the working-tree checkout and future writes to LF.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 4d27d82f-3809-40d2-b4e7-6623436ff2ef
…rphans

Bulk-deleting a module's docs before regenerating meant any transient import failure (installed but unimportable module, e.g. Authentication version conflict) wiped docs that were never regenerated, producing refresh PRs with thousands of missing files. Now: verify the module truly imports and exposes commands before processing (skip-and-preserve otherwise), overwrite each doc in place, and remove only genuine orphans whose command is no longer in the metadata.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 4d27d82f-3809-40d2-b4e7-6623436ff2ef
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

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
DetailsThe 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
DetailsThe 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
DetailsThe 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.
4 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md country 12824 2 No action needed Geopolitical
DetailsThe 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.
5 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md country 15993 2 No action needed Geopolitical
DetailsThe 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\Update-MgBetaWindowsUpdatesPolicyRing.md country 18339 2 Replacement required Geopolitical
DetailsThe term `country` is used to describe the component of a user's locale, following ISO 3166-1 alpha-2 codes. Since it is not a code identifier or part of a URL, and is labeling a country/region concept in documentation, it should be replaced with 'country/region' to avoid geopolitical issues.
7 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md countries 18476 2 Replacement required Geopolitical
DetailsThe 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`.
8 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md country 21923 2 No action needed Geopolitical
DetailsThe 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.
9 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md country 25092 2 No action needed Geopolitical
DetailsThe 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.
10 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md country 27438 2 Replacement required Geopolitical
DetailsThe term `country` is used to describe the locale component for a user in Microsoft Teams, 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.
11 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\Update-MgBetaWindowsUpdatesPolicyRing.md countries 27575 2 Replacement required Geopolitical
DetailsThe 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`.
 
12 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md country 3693 2 No action needed Geopolitical
DetailsThe 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.
13 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md country 6862 2 No action needed Geopolitical
DetailsThe 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.
14 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md country 9208 2 Replacement required Geopolitical
DetailsThe 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'.
15 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md countries 9345 2 Replacement required Geopolitical
DetailsThe 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`.
16 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md country 12801 2 No action needed Geopolitical
DetailsThe 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.
17 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md country 15970 2 No action needed Geopolitical
DetailsThe term `country` is used in the context of describing a locale representation, specifically referencing ISO 3166-1 alpha-2 standards. Since this is an international standard context, the rule recommends leaving the term unchanged.
18 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md country 18316 2 Replacement required Geopolitical
DetailsThe 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.
19 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md countries 18453 2 Replacement required Geopolitical
DetailsThe 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`.
20 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md country 21900 2 No action needed Geopolitical
DetailsThe 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.
21 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md country 25069 2 No action needed Geopolitical
DetailsThe term `country` is used in the context of describing locale information, 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.
22 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.WindowsUpdates\New-MgBetaWindowsUpdatesPolicyRing.md countries 27552 2 Replacement required Geopolitical
DetailsThe 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`.
 
23 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernanceRequest.md country 3695 2 No action needed Geopolitical
DetailsThe 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.
24 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernanceRequest.md country 6864 2 No action needed Geopolitical
DetailsThe 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.
25 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernanceRequest.md country 9210 2 Replacement required Geopolitical
DetailsThe 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'.
26 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernanceRequest.md countries 9347 2 Replacement required Geopolitical
DetailsThe 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`.
27 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernanceRequest.md country 12841 2 No action needed Geopolitical
DetailsThe 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.
28 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernanceRequest.md countries 18493 2 Replacement required Geopolitical
DetailsThe 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-MgBetaDirectoryTenantGovernancePolicyTemplate.md country 3747 2 No action needed Geopolitical
DetailsThe 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.
30 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernancePolicyTemplate.md country 6916 2 No action needed Geopolitical
DetailsThe 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.
31 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernancePolicyTemplate.md country 9262 2 Replacement required Geopolitical
DetailsThe term `country` is used to describe a component of a user's locale, specifically referencing ISO 3166-1 alpha-2 codes. This is a general text label describing a country/region, not a code identifier or part of a technical field name, so it should be updated to 'country/region' to avoid geopolitical issues.
32 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernancePolicyTemplate.md countries 9399 2 Replacement required Geopolitical
DetailsThe 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`.
33 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernancePolicyTemplate.md country 12862 2 No action needed Geopolitical
DetailsThe term `country` is used as a property name in a technical schema, specifically as a field label in a data model. According to global exceptions, technical field names and database column identifiers should not be replaced.
34 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernancePolicyTemplate.md country 16031 2 No action needed Geopolitical
DetailsThe 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.
 
35 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.SignIns\Test-MgBetaIdentityConditionalAccess.md country 84 2 No action needed Geopolitical
DetailsThe term `country` is used as a property name in a PowerShell code example, specifically as a key in a hashtable representing sign-in conditions. According to global exceptions, technical field names and code identifiers should not be replaced.
36 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.SignIns\Test-MgBetaIdentityConditionalAccess.md country 122 2 No action needed Geopolitical
DetailsThe 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. It should not be replaced.
37 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.SignIns\Test-MgBetaIdentityConditionalAccess.md country 161 2 No action needed Geopolitical
DetailsThe term `country` is used as a property name in a code snippet, which falls under the global exception for technical field names and code identifiers. It should not be replaced.
38 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.SignIns\Test-MgBetaIdentityConditionalAccess.md country 198 2 No action needed Geopolitical
DetailsThe 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.
 
39 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernance.md country 3467 2 No action needed Geopolitical
DetailsThe 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.
40 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernance.md country 18282 2 Replacement required Geopolitical
DetailsThe 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.
41 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernance.md country 21932 2 No action needed Geopolitical
DetailsThe term `country` is used as a property name in a technical API schema, which is considered a code identifier. According to global exceptions, code identifiers should not be replaced.
42 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernance.md country 25101 2 No action needed Geopolitical
DetailsThe 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 rules, the term should be left unchanged.
43 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\Update-MgBetaDirectoryTenantGovernance.md countries 27584 2 Replacement required Geopolitical
DetailsThe term `countries` is used in the phrase 'availability of services in countries' to describe a list of regions where services are available. To avoid geopolitical issues, it should be replaced with 'countries/regions'.
 
44 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernanceRequest.md country 3539 2 No action needed Geopolitical
DetailsThe 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.
45 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernanceRequest.md countries 9191 2 Replacement required Geopolitical
DetailsThe 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'.
46 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernanceRequest.md countries 18337 2 Replacement required Geopolitical
DetailsThe 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.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernancePolicyTemplate.md country 3546 2 No action needed Geopolitical
DetailsThe 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.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernancePolicyTemplate.md country 9061 2 Replacement required Geopolitical
DetailsThe term `country` is used to describe the language and country code component of a user's locale, 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`.
49 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernancePolicyTemplate.md country 12661 2 No action needed Geopolitical
DetailsThe term `country` is used as a property name in a technical API schema, specifically as a field label in a resource definition. According to global exceptions, technical field names and database column identifiers should not be replaced.
50 microsoftgraph\graph-powershell-beta\Microsoft.Graph.Beta.Identity.DirectoryManagement\New-MgBetaDirectoryTenantGovernancePolicyTemplate.md country 15830 2 No action needed Geopolitical
DetailsThe 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.
This comment lists only the first 50 of 72 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

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 1e17ca8:

💡 Validation status: suggestions

File Status Preview URL Details
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Add-MgServicePrincipalTokenSigningCertificate.md 💡Suggestion View (graph-powershell-1.0) Details
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Confirm-MgApplicationMemberGroup.md 💡Suggestion View (graph-powershell-1.0) Details
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Confirm-MgApplicationMemberObject.md 💡Suggestion View (graph-powershell-1.0) Details
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Confirm-MgServicePrincipalMemberGroup.md 💡Suggestion View (graph-powershell-1.0) Details
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Confirm-MgServicePrincipalMemberObject.md 💡Suggestion View (graph-powershell-1.0) Details
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Get-MgApplicationById.md 💡Suggestion View (graph-powershell-1.0) Details
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Get-MgApplicationMemberGroup.md 💡Suggestion View (graph-powershell-1.0) Details
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Get-MgApplicationMemberObject.md 💡Suggestion View (graph-powershell-1.0) Details
.gitattributes ✅Succeeded
azure-pipelines/powershell-docs.yml ✅Succeeded
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Add-MgApplicationKey.md ✅Succeeded View (graph-powershell-1.0)
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Add-MgApplicationPassword.md ✅Succeeded View (graph-powershell-1.0)
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Add-MgServicePrincipalKey.md ✅Succeeded View (graph-powershell-1.0)
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Add-MgServicePrincipalPassword.md ✅Succeeded View (graph-powershell-1.0)
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Clear-MgApplicationVerifiedPublisher.md ✅Succeeded View (graph-powershell-1.0)
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Find-MgApplicationSynchronizationJobSchemaDirectory.md ✅Succeeded View (graph-powershell-1.0)
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Find-MgApplicationSynchronizationTemplateSchemaDirectory.md ✅Succeeded View (graph-powershell-1.0)
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Find-MgServicePrincipalSynchronizationJobSchemaDirectory.md ✅Succeeded View (graph-powershell-1.0)
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Find-MgServicePrincipalSynchronizationTemplateSchemaDirectory.md ✅Succeeded View (graph-powershell-1.0)
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Get-MgApplication.md ✅Succeeded View (graph-powershell-1.0)
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Get-MgApplicationAppManagementPolicy.md ✅Succeeded View (graph-powershell-1.0)
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Get-MgApplicationAppManagementPolicyByRef.md ✅Succeeded View (graph-powershell-1.0)
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Get-MgApplicationAppManagementPolicyCount.md ✅Succeeded View (graph-powershell-1.0)
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Get-MgApplicationByAppId.md ✅Succeeded View (graph-powershell-1.0)
microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Get-MgApplicationByUniqueName.md ✅Succeeded View (graph-powershell-1.0)

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

microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Add-MgServicePrincipalTokenSigningCertificate.md

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

microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Confirm-MgApplicationMemberGroup.md

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

microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Confirm-MgApplicationMemberObject.md

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

microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Confirm-MgServicePrincipalMemberGroup.md

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

microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Confirm-MgServicePrincipalMemberObject.md

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

microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Get-MgApplicationById.md

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

microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Get-MgApplicationMemberGroup.md

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

microsoftgraph/graph-powershell-1.0/Microsoft.Graph.Applications/Get-MgApplicationMemberObject.md

  • Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Microsoft.Graph.Applications.Get-MgApplicationMemberObject 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant