10/14 Publish for azps-14.5.0

[huypub]

PR Summary

PR Checklist

• Descriptive Title: This PR's title is a synopsis of the changes it proposes.
• Summary: This PR's summary describes the scope and intent of the change.
• Contributor's Guide: I have read the contributors guide.
• Style: This PR adheres to the style guide.

[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 issues. Other issues are also a high priority. 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	azps-14.5.0\Az.Security\Get-AzSecurityAdaptiveApplicationControl.md	whitelist	34	2	No action needed	Diversity	Details The term `whitelist` appears only as a component of resource type names and file paths, such as 'applicationWhitelistings' in resource IDs and type names. According to the rules, when the word is a component of other words or appears in file paths, it does not need to be replaced or removed.
2	azps-14.5.0\Az.Security\Get-AzSecurityAdaptiveApplicationControl.md	whitelist	36	2	No action needed	Diversity	Details The term `whitelist` appears only as a component of resource type and property names, such as 'applicationWhitelistings' and not as a standalone label or description. According to the rules, when the word is a component of other words (e.g., in resource names, file paths, or property names), it does not need to be replaced or removed.
3	azps-14.5.0\Az.Security\Get-AzSecurityAdaptiveApplicationControl.md	whitelist	40	2	No action needed	Diversity	Details The term `whitelist` appears only as a component of resource type names and file paths, such as 'applicationWhitelistings' in resource IDs and type fields. According to the rules, when the word is a component of other words or appears in file paths, it does not need to be replaced or removed.
4	azps-14.5.0\Az.Security\Get-AzSecurityAdaptiveApplicationControl.md	whitelist	42	2	No action needed	Diversity	Details The term `whitelist` appears as a component of resource type names and property names (such as applicationWhitelistings and Microsoft.Security/applicationWhitelistings), which are part of legacy code and system identifiers. According to the rules, terms used in such contexts do not need to be replaced or removed.
5	azps-14.5.0\Az.Security\Get-AzSecurityAdaptiveApplicationControl.md	whitelist	48	2	No action needed	Diversity	Details The term `whitelist` appears as a component of resource type names and IDs, such as 'applicationWhitelistings' and 'Microsoft.Security/applicationWhitelistings', which are field or filter names and part of legacy code. According to the rules, terms used in resource names, field names, or as part of legacy code do not need to be replaced.
6	azps-14.5.0\Az.Resources\New-AzADUser.md	country	21	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name to indicate the user's location, which can be interpreted as labeling a country/region resource. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.
7	azps-14.5.0\Az.Resources\New-AzADUser.md	country	37	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name to indicate the user's location, and the description refers to 'country/region' as the intended meaning. To avoid geopolitical issues and ensure inclusivity, it should be updated to `country/region` for consistency with best practices.
8	azps-14.5.0\Az.Resources\Update-AzADUser.md	country	37	2	No action needed	Geopolitical	Details The term `country` is used as a field/parameter name in a PowerShell cmdlet, which is a technical property name and not a user-facing label or list. According to the rules, field or parameter names do not need to be replaced/removed.
9	azps-14.5.0\Az.Resources\Update-AzADUser.md	country	53	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name to specify the user's location, which can refer to a geopolitical entity. To avoid geopolitical issues and be inclusive, it should be replaced with `country/region`.
10	azps-14.5.0\Az.Resources\Update-AzADUser.md	country	182	2	No action needed	Geopolitical	Details The term `country` is used as a parameter name in a PowerShell cmdlet, which is a field/property name in code and documentation. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
11	azps-14.5.0\Az.Resources\Update-AzADUser.md	countries	771	2	Replacement required	Geopolitical	Details The term `countries` is used to refer to a list of locations for legal requirements and service availability, which can be interpreted as labeling a country/region list or resource. To avoid geopolitical issues, it should be replaced with `countries/regions`.
12	azps-14.5.0\Az.Network\Set-AzFirewallPolicyDraft.md	whitelist	43	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name and type, specifically `ThreatIntelWhitelist` and `PSAzureFirewallPolicyThreatIntelWhitelist`. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
13	azps-14.5.0\Az.Network\Set-AzFirewallPolicyDraft.md	whitelist	54	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name (`ThreatIntelWhitelist`) and as a component in object names (e.g., `PSAzureFirewallPolicyThreatIntelWhitelist`). According to the rules, when the word is a field, parameter, or property name, it does not need to be replaced or removed.
14	azps-14.5.0\Az.Network\Set-AzFirewallPolicyDraft.md	whitelist	123	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name (`ThreatIntelWhitelist`) and as a component in object names (e.g., `PSAzureFirewallPolicyThreatIntelWhitelist`). According to the rules, when the word is a field, filter, parameter, or component of other words, it does not need to be replaced or removed.
15	azps-14.5.0\Az.Oracle\Update-AzOracleAutonomousDatabase.md	whitelist	58	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name (`WhitelistedIP`) in a PowerShell cmdlet, which is a field/property name in code. According to the guidelines, when the word is used as a field or parameter name, it does not need to be replaced or removed.
16	azps-14.5.0\Az.Oracle\Update-AzOracleAutonomousDatabase.md	whitelist	127	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name (`WhitelistedIP`) in a PowerShell cmdlet, which is a field/property name in code. According to the guidelines, when referring to a field or parameter name, it does not need to be replaced or removed.
17	azps-14.5.0\Az.Oracle\Update-AzOracleAutonomousDatabase.md	whitelist	698	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name (`WhitelistedIP`) in a PowerShell cmdlet, which is a field/property name in code. According to the guidelines, when the word is used as a field or parameter name, it does not need to be replaced or removed.
18	azps-14.5.0\Az.Peering\Get-AzPeeringServiceLocation.md	country	65	2	Replacement required	Geopolitical	Details The term `country` is used to label a column in a table and as a parameter name to filter locations, which is effectively labeling a country/region list or resource. To avoid geopolitical issues, it should be replaced with `country/region` throughout the documentation, including the parameter name and table header.
19	azps-14.5.0\Az.Peering\Get-AzPeeringServiceLocation.md	country	84	2	Replacement required	Geopolitical	Details The term `country` is used to label a filter and describe a location parameter, which is a scenario where geopolitical sensitivity is relevant. To avoid issues, it should be replaced with `country/region` throughout the documentation and parameter descriptions.
20	azps-14.5.0\Az.Peering\Get-AzPeeringServiceLocation.md	country	88	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and in the description to label a geographic location for filtering or listing peering service locations. According to the rules, when labeling a country/region list or similar resource, it should be replaced to avoid geopolitical issues. The recommended change is to replace `country` with `country/region` throughout the documentation and parameter name.
21	azps-14.5.0\Az.Peering\Get-AzPeeringServiceLocation.md	country	89	2	Replacement required	Geopolitical	Details The term `country` is used to label a parameter that filters locations by country, which is a scenario where geopolitical sensitivity is relevant. To avoid issues, it should be replaced with `country/region` for clarity and inclusivity.
22	azps-14.5.0\Az.Support\New-AzSupportTicketsNoSubscription.md	country	145	2	Replacement required	Geopolitical	Details The term `country` is used to label a field describing the user's location, which is a scenario where geopolitical sensitivity is important. It should be replaced with `country/region` to be inclusive and avoid geopolitical issues.
23	azps-14.5.0\Az.SecurityInsights\Get-AzSentinelEnrichment.md	country	72	2	Replacement required	Geopolitical	Details The term `country` is used as a field label in the output of a command, representing a geopolitical entity. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.
24	azps-14.5.0\Az.Purview\Get-AzPurviewScanRuleset.md	Turkey	43	2	Replacement required	Geopolitical	Details The term `Turkey` is used as part of a system classification referring to the country/region, not the bird. To align with current geopolitical naming conventions and avoid sensitivity, it should be replaced with `Türkiye`.
25	azps-14.5.0\Az.Peering\Get-AzPeeringServiceCountry.md	countries	23	2	Replacement required	Geopolitical	Details The term `countries` is used to label a list of geographic locations for a service, which can raise geopolitical sensitivity. It should be replaced with `countries/regions` to be inclusive and avoid issues.
26	azps-14.5.0\Az.Peering\Get-AzPeeringServiceCountry.md	countries	27	2	Replacement required	Geopolitical	Details The term `countries` is used to label a list of geographic locations for a service, which can raise geopolitical sensitivity. It should be replaced with `countries/regions` to be inclusive and avoid issues.
27	azps-14.5.0\Az.Peering\Get-AzPeeringServiceCountry.md	countries	53	2	Replacement required	Geopolitical	Details The term `countries` is used to label a list of geographic locations available for peering service, which can raise geopolitical sensitivity. It should be replaced with `countries/regions` to be inclusive and avoid issues.
28	azps-14.5.0\Az.Peering\Az.Peering.md	countries	50	2	Replacement required	Geopolitical	Details The term `countries` is used to label a list of available countries for peering service, which is a scenario where geopolitical sensitivity is relevant. To avoid issues, it should be replaced with `countries/regions`.
29	azps-14.5.0\Az.Peering\Get-AzPeeringLocation.md	country	35	2	Replacement required	Geopolitical	Details The term `country` is used as a column header to label a list of country codes in a table, which is a scenario where geopolitical sensitivity is relevant. To avoid issues, it should be replaced with `country/region`.
30	azps-14.5.0\Az.PaloAltoNetworks\New-AzPaloAltoNetworksLocalRule.md	countries	474	2	Replacement required	Geopolitical	Details The term `countries` is used to label a list of geographic locations in the parameter description for `SourceCountry`. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `countries/regions`.
31	azps-14.5.0\Az.Oracle\New-AzOracleAutonomousDatabase.md	whitelist	737	2	Replacement required	Diversity	Details The term `whitelist` is used as a parameter name and description for an IP access control list, which is a list of approved IPs. In this context, it is not an industry-mandated term and can be replaced for inclusivity. The recommended replacement is `allow list` or a more specific term such as `approved IP list`.
32	azps-14.5.0\Az.Oracle\Get-AzOracleAutonomousDatabase.md	whitelist	104	2	No action needed	Diversity	Details The term `whitelist` appears as part of the property name `WhitelistedIP`, which is a field name in the output of the cmdlet. According to the rules, when referring to a field or property name, it does not need to be replaced or removed.
33	azps-14.5.0\Az.NewRelic\New-AzNewRelicMonitor.md	country	508	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name to collect user information, which likely refers to the user's country of residence or operation. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.
34	azps-14.5.0\Az.Network\Set-AzFirewallPolicy.md	whitelist	20	2	No action needed	Diversity	Details The term `whitelist` is used as part of parameter and property names (e.g., ThreatIntelWhitelist, PSAzureFirewallPolicyThreatIntelWhitelist), which are field or filter names in code and API documentation. According to the rules, when referring to a field or filter name, it does not need to be replaced or removed.
35	azps-14.5.0\Az.Network\Set-AzFirewallPolicy.md	whitelist	46	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name and type (ThreatIntelWhitelist, PSAzureFirewallPolicyThreatIntelWhitelist) in PowerShell cmdlet documentation, which is a field/property name in code. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
36	azps-14.5.0\Az.Network\Set-AzFirewallPolicy.md	whitelist	77	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name and type in PowerShell cmdlet documentation, specifically `ThreatIntelWhitelist` and `PSAzureFirewallPolicyThreatIntelWhitelist`. This is a field/property name in code and aligns with industry naming conventions and existing API contracts, making replacement impractical.
37	azps-14.5.0\Az.Network\Set-AzFirewallPolicy.md	whitelist	77	2	No action needed	Diversity	Details The term `whitelist` is used as a parameter/property name in PowerShell cmdlet syntax and object definitions, which is a field name in code. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
38	azps-14.5.0\Az.Network\Set-AzFirewallPolicy.md	whitelist	437	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name and type, such as ThreatIntelWhitelist and PSAzureFirewallPolicyThreatIntelWhitelist, which are field or filter names in code and API documentation. According to the rules, when referring to a field or filter name, it does not need to be replaced or removed.
39	azps-14.5.0\Az.Network\Set-AzFirewallPolicy.md	whitelist	441	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name and type, specifically `ThreatIntelWhitelist` and `PSAzureFirewallPolicyThreatIntelWhitelist`. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
40	docs-conceptual\azps-14.5.0\release-notes-azureps.md	whitelist	5709	2	No action needed	Diversity	Details The term `allow-listed` is used in the phrase 'Subscriptions must be allow-listed by the service to use IP/Service Tag ACL features.' This is a release note describing a technical requirement for service access, and the term is used in a context where industry naming conventions and technical consistency make replacement impractical. The context is a changelog for Azure PowerShell modules, which often follows established terminology for compatibility and clarity.
41	docs-conceptual\azps-14.5.0\release-notes-azureps.md	whitelist	8292	2	No action needed	Diversity	Details The term `whitelist` appears in the context of describing Azure PowerShell release notes, specifically in the phrase 'allow-listed by the service to use IP/Service Tag ACL features.' In this context, it is used as a verb to describe a technical process of granting access, and the industry is in a transition period where both 'whitelist' and 'allow list' are sometimes used for clarity. However, in this instance, the term is already replaced with 'allow-listed,' and the only occurrence of `whitelist` is in the context of describing the technical process, not as a label for people or things. Therefore, replacement is not strictly necessary here.
42	azps-14.5.0\Az.TrustedSigning\Get-AzTrustedSigningCertificateProfile.md	country	55	2	Replacement required	Geopolitical	Details The term `country` is used as a column header in a data output table, which labels a country/region field. According to the rules, when used to label a country/region list or similar resource, it should be replaced to avoid geopolitical issues. Suggest replacing `country` with `country/region`.
43	azps-14.5.0\Az.Security\Get-AzSecurityAdaptiveApplicationControlGroup.md	whitelist	34	2	No action needed	Diversity	Details The term `whitelist` appears as a component of resource type and property names such as 'applicationWhitelistings' and 'Microsoft.Security/applicationWhitelistings'. According to the guidelines, when the word is a component of other words, such as in resource names, it does not need to be replaced or removed.
44	azps-14.5.0\Az.Support\Update-AzSupportTicketsNoSubscription.md	country	131	2	Replacement required	Geopolitical	Details The term `country` is used to label a field for user information, which may refer to a country or region. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.
45	azps-14.5.0\Az.Support\Update-AzSupportTicket.md	country	134	2	Replacement required	Geopolitical	Details The term `country` is used to label a field that collects the user's country information. To avoid geopolitical issues and be inclusive of regions, it should be replaced with `country/region`. Specifically, update the field label and description to use `country/region` instead of just `country`.
46	azps-14.5.0\Az.Network\Set-AzFirewall.md	whitelist	217	2	No action needed	Diversity	Details The term `whitelist` appears as part of property names such as ThreatIntelWhitelist and ThreatIntelWhitelistText, which are field or filter names in code or configuration. According to the rules, when referring to a field or filter name, it does not need to be replaced or removed.
47	azps-14.5.0\Az.Network\Set-AzFirewall.md	whitelist	294	2	No action needed	Diversity	Details The term `whitelist` appears as part of property names such as ThreatIntelWhitelist and ThreatIntelWhitelistText, which are field or filter names in the context of Azure Firewall configuration. According to the rules, when referring to a field or filter name, it does not need to be replaced or removed.
48	azps-14.5.0\Az.Network\New-AzFirewallThreatIntelWhitelist.md	whitelist	90	2	No action needed	Diversity	Details The term `whitelist` is used as part of a cmdlet name, parameter name, and output type in PowerShell documentation, which follows industry naming conventions and established API contracts. Changing it would break consistency and potentially existing scripts.
49	azps-14.5.0\Az.Network\New-AzFirewallPolicyThreatIntelWhitelist.md	whitelist	23	2	No action needed	Diversity	Details The term `whitelist` is used as part of a cmdlet name, parameter name, and output type, which are established industry naming conventions in PowerShell and Azure. Changing these names would break consistency and potentially functionality, so replacement is impractical.
50	azps-14.5.0\Az.Network\New-AzFirewallPolicyThreatIntelWhitelist.md	whitelist	90	2	No action needed	Diversity	Details The term `whitelist` is used as part of a cmdlet name, parameter name, and output type in PowerShell documentation, which follows established industry naming conventions and product consistency. Changing it would break existing scripts and references, so replacement is impractical.

This comment lists only the first 50 of 211 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 1622be1:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
azps-14.5.0/Az.Advisor/Get-AzAdvisorRecommendation.md	⚠️Warning	View (azps-14.5.0)	Details
azps-14.5.0/Az.DataLakeStore/Az.DataLakeStore.md	⚠️Warning	View (azps-14.5.0)	Details
azps-14.5.0/Az.KeyVault/Az.KeyVault.md	⚠️Warning	View (azps-14.5.0)	Details
azps-14.5.0/Az.NetAppFiles/Az.NetAppFiles.md	⚠️Warning	View (azps-14.5.0)	Details
azps-14.5.0/Az.Network/Az.Network.md	⚠️Warning	View (azps-14.5.0)	Details
azps-14.5.0/Az.Sql/Az.Sql.md	⚠️Warning	View (azps-14.5.0)	Details
azps-14.5.0/Az.AksArc/New-AzAksArcCluster.md	💡Suggestion	View (azps-14.5.0)	Details
azps-14.5.0/Az.AksArc/Update-AzAksArcCluster.md	💡Suggestion	View (azps-14.5.0)	Details
azps-14.5.0/Az.ApiManagement/Get-AzApiManagementAuthorizationServer.md	💡Suggestion	View (azps-14.5.0)	Details
azps-14.5.0/Az.ApiManagement/Remove-AzApiManagementRegion.md	💡Suggestion	View (azps-14.5.0)	Details
azps-14.5.0/Az.ApplicationInsights/Get-AzApplicationInsights.md	💡Suggestion	View (azps-14.5.0)	Details
azps-14.5.0/Az.ApplicationInsights/Set-AzApplicationInsightsContinuousExport.md	💡Suggestion	View (azps-14.5.0)	Details
azps-14.5.0/Az.Accounts/Add-AzEnvironment.md	✅Succeeded	View (azps-14.5.0)
azps-14.5.0/Az.Accounts/Az.Accounts.md	✅Succeeded	View (azps-14.5.0)
azps-14.5.0/Az.Accounts/Clear-AzConfig.md	✅Succeeded	View (azps-14.5.0)
azps-14.5.0/Az.Accounts/Clear-AzContext.md	✅Succeeded	View (azps-14.5.0)
azps-14.5.0/Az.Accounts/Clear-AzDefault.md	✅Succeeded	View (azps-14.5.0)
azps-14.5.0/Az.Accounts/Connect-AzAccount.md	✅Succeeded	View (azps-14.5.0)
azps-14.5.0/Az.Accounts/Disable-AzContextAutosave.md	✅Succeeded	View (azps-14.5.0)
azps-14.5.0/Az.Accounts/Disable-AzDataCollection.md	✅Succeeded	View (azps-14.5.0)
azps-14.5.0/Az.Accounts/Disable-AzureRmAlias.md	✅Succeeded	View (azps-14.5.0)
azps-14.5.0/Az.Accounts/Disconnect-AzAccount.md	✅Succeeded	View (azps-14.5.0)
azps-14.5.0/Az.Accounts/Enable-AzContextAutosave.md	✅Succeeded	View (azps-14.5.0)
azps-14.5.0/Az.Accounts/Enable-AzDataCollection.md	✅Succeeded	View (azps-14.5.0)
azps-14.5.0/Az.Accounts/Enable-AzureRmAlias.md	✅Succeeded	View (azps-14.5.0)

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

azps-14.5.0/Az.Advisor/Get-AzAdvisorRecommendation.md

• Line 0, Column 0: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#category' in 'azps-14.5.0/Az.Advisor/Get-AzAdvisorRecommendation.yml', did you mean '#-category'?

azps-14.5.0/Az.DataLakeStore/Az.DataLakeStore.md

• Line 0, Column 0: [Warning: PSMD2Yaml_InconsistentCmdletsInModule] Inconsistent cmdlets found in module: Az.DataLakeStore. 1 cmdlets in the module folder but not listed in the module file: Get-AzDataLakeStoreDeletedItemsWithToken.

azps-14.5.0/Az.KeyVault/Az.KeyVault.md

• Line 0, Column 0: [Warning: PSMD2Yaml_InconsistentCmdletsInModule] Inconsistent cmdlets found in module: Az.KeyVault. 4 cmdlets in the module folder but not listed in the module file: Add-AzKeyVaultManagedHsmNetworkRule, New-AzKeyVaultManagedHsmNetworkRuleSetObject, Remove-AzKeyVaultManagedHsmNetworkRule, Update-AzKeyVaultManagedHsmNetworkRuleSet.

azps-14.5.0/Az.NetAppFiles/Az.NetAppFiles.md

• Line 0, Column 0: [Warning: PSMD2Yaml_InconsistentCmdletsInModule] Inconsistent cmdlets found in module: Az.NetAppFiles. 1 cmdlets in the module folder but not listed in the module file: Split-AzNetAppFilesCloneFromParent.

azps-14.5.0/Az.Network/Az.Network.md

• Line 0, Column 0: [Warning: PSMD2Yaml_InconsistentCmdletsInModule] Inconsistent cmdlets found in module: Az.Network. 7 cmdlets in the module folder but not listed in the module file: Get-AzVirtualNetworkGatewayFailoverAllTestsDetail, Get-AzVirtualNetworkGatewayFailoverSingleTestDetail, Get-AzVirtualNetworkGatewayResiliencyInformation, Get-AzVirtualNetworkGatewayRoutesInformation, Invoke-AzFirewallPacketCaptureOperation, Start-AzVirtualNetworkGatewaySiteFailoverTest, Stop-AzVirtualNetworkGatewaySiteFailoverTest.

azps-14.5.0/Az.Sql/Az.Sql.md

• Line 0, Column 0: [Warning: PSMD2Yaml_InconsistentCmdletsInModule] Inconsistent cmdlets found in module: Az.Sql. 1 cmdlets in the module folder but not listed in the module file: Restore-AzSqlServer.

azps-14.5.0/Az.AksArc/New-AzAksArcCluster.md

• Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Az.AksArc.New-AzAksArcCluster cmdlet. Parameters lacking description: AdminGroupObjectID, MaxCount, MaxPod, MinCount

azps-14.5.0/Az.AksArc/Update-AzAksArcCluster.md

• Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Az.AksArc.Update-AzAksArcCluster cmdlet. Parameters lacking description: AdminGroupObjectID

azps-14.5.0/Az.ApiManagement/Get-AzApiManagementAuthorizationServer.md

• Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Az.ApiManagement.Get-AzApiManagementAuthorizationServer cmdlet. Parameters lacking description: Context, ServerId

azps-14.5.0/Az.ApiManagement/Remove-AzApiManagementRegion.md

• Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Az.ApiManagement.Remove-AzApiManagementRegion cmdlet. Parameters lacking description: DefaultProfile

azps-14.5.0/Az.ApplicationInsights/Get-AzApplicationInsights.md

• Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Az.ApplicationInsights.Get-AzApplicationInsights cmdlet. Parameters lacking description: Full

azps-14.5.0/Az.ApplicationInsights/Set-AzApplicationInsightsContinuousExport.md

• Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Az.ApplicationInsights.Set-AzApplicationInsightsContinuousExport cmdlet. Parameters lacking description: DisableConfiguration

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.