11/04 Publish

[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 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	docs-conceptual\azps-14.6.0\release-notes-azureps.md	whitelist	5788	2	Replacement required	Diversity	Details The term `whitelist` does not appear in the provided context, as there is no instance of the word enclosed in a <target_term> tag. Without a specific instance to review, it is not possible to determine the context or necessity for replacement. If the word is present elsewhere but not tagged, it should be ignored per instructions. Please provide the exact instance for review.
2	docs-conceptual\azps-14.6.0\release-notes-azureps.md	whitelist	8371	2	Replacement required	Diversity	Details The term `whitelist` does not appear in the provided document context, or at least is not clearly marked with a <target_term> tag for review. If it is present but not tagged, or if the context is too broad (such as a changelog or release notes), it is not possible to determine the specific usage scenario or whether it refers to an industry naming convention, a technical property, or a general description. Without a clear, tagged instance and more precise context, it is not possible to make a definitive judgment.
3	docs-conceptual\azps-14.6.0\migrate-az-12.0.0.md	country	2554	2	Replacement required	Geopolitical	Details The term `country` is used as a field/property name in a customer contact detail object for support ticket creation, which is intended to capture the user's country or region. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region` or a similar expression. This aligns with the guidance to use 'country/region' when labeling or collecting country/region information.
4	docs-conceptual\azps-14.6.0\migrate-az-12.0.0.md	country	2556	2	Replacement required	Geopolitical	Details The term `country` is used as a field/property name in a parameter object for a PowerShell cmdlet, specifically to indicate the user's country in support ticket creation. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region` or a similar expression.
5	azps-14.6.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 value. To avoid geopolitical issues and follow inclusive language guidelines, it should be replaced with `country/region`.
6	azps-14.6.0\Az.TrustedSigning\Get-AzTrustedSigningCertificateProfile.md	country	68	2	Replacement required	Geopolitical	Details The term `country` is used as a column header in a table that lists certificate profile details, which likely refers to the country/region associated with the profile. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.
7	azps-14.6.0\Az.TrustedSigning\New-AzTrustedSigningCertificateProfile.md	country	51	2	Replacement required	Geopolitical	Details The term `country` is used as a column header in a table output, representing a location attribute. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.
8	azps-14.6.0\Az.Support\New-AzSupportTicket.md	country	267	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter label to collect user location information, which can refer to either a country or a region. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`. This aligns with industry best practices for labeling user location fields.
9	azps-14.6.0\Az.Site\Update-AzSite.md	country	117	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name to specify the country of an address. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.
10	azps-14.6.0\Az.Site\New-AzSite.md	country	46	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and in documentation to specify the address of a site. In this context, it is labeling a field that may refer to a country or region, and to avoid geopolitical issues, it should be replaced with `country/region` for clarity and inclusivity.
11	azps-14.6.0\Az.Site\New-AzSite.md	country	53	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and in documentation to indicate the geographic location of a site. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region` throughout the documentation and parameter definitions.
12	azps-14.6.0\Az.Site\New-AzSite.md	country	66	2	Replacement required	Geopolitical	Details The term `country` is used as a field name in a JSON object representing address information. According to the rules, when labeling a country/region list or similar resource, it should be replaced to avoid geopolitical issues. The field is not a legacy code or a legal context, so the replacement is needed. Suggest replacing it with `country/region`.
13	azps-14.6.0\Az.Site\New-AzSite.md	country	74	2	Replacement required	Geopolitical	Details The term `country` is used as a label key in a JSON configuration for site address information, which is a scenario where geopolitical sensitivity applies. To avoid issues, it should be replaced with `country/region`.
14	azps-14.6.0\Az.Site\New-AzSite.md	country	125	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter to specify the address of a site, which may refer to a geopolitical entity. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.
15	azps-14.6.0\Az.Security\Get-AzSecurityAdaptiveApplicationControl.md	whitelist	46	2	No action needed	Diversity	Details The term `whitelist` appears as a component of resource type names and IDs, such as 'applicationWhitelistings', which are part of Azure's established naming conventions and resource identifiers. According to the rules, when industry naming conventions or consistency make replacement of the term impractical, it should be left unchanged.
16	azps-14.6.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 in file paths. According to the rules, when the word is a component of other words, file paths, or resource names, it does not need to be replaced or removed.
17	azps-14.6.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, and the description refers to 'country/region' as the intended meaning. To avoid geopolitical issues and ensure inclusivity, it should be replaced with 'country/region'.
18	azps-14.6.0\Az.Peering\Get-AzPeeringServiceLocation.md	country	88	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and description to filter or label a list of locations, which can be interpreted as labeling a country/region list or resource. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region` throughout the documentation and parameter naming.
19	azps-14.6.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.
20	azps-14.6.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 a service, which can raise geopolitical concerns. It should be replaced with `countries/regions` to be more inclusive and accurate.
21	azps-14.6.0\Az.Oracle\Update-AzOracleAutonomousDatabase.md	whitelist	29	2	No action needed	Diversity	Details The term `whitelist` is used as a parameter/property name (`WhitelistedIP`) in a PowerShell cmdlet and as a field in the output. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed, regardless of sensitivity.
22	azps-14.6.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. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
23	azps-14.6.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 locations, which can refer to geopolitical entities. To avoid geopolitical issues, it should be replaced with `country/region`.
24	azps-14.6.0\Az.PaloAltoNetworks\New-AzPaloAltoNetworksLocalRule.md	countries	203	2	Replacement required	Geopolitical	Details The term `countries` is used to label a list of destination countries in a parameter description, which is a scenario where geopolitical sensitivity is relevant. To avoid issues, it should be replaced with `countries/regions`.
25	azps-14.6.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 for filtering or selection, which can raise geopolitical sensitivity. It should be replaced with `countries/regions` to be more inclusive and avoid potential issues.
26	azps-14.6.0\Az.Network\Set-AzFirewallPolicyDraft.md	whitelist	32	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name (`ThreatIntelWhitelist`) and object name (`PSAzureFirewallPolicyThreatIntelWhitelist`), which are field or property names in code and API documentation. According to the rules, when referring to a field or filter name, database name, parameter name, or similar, it does not need to be replaced or removed.
27	azps-14.6.0\Az.Network\Set-AzFirewallPolicyDraft.md	whitelist	43	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter/property name (`ThreatIntelWhitelist`), which is a field name in the API and code. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
28	azps-14.6.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 object name (`PSAzureFirewallPolicyThreatIntelWhitelist`), which are field/property names in code and API documentation. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
29	azps-14.6.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 a PowerShell object name (`PSAzureFirewallPolicyThreatIntelWhitelist`). According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
30	azps-14.6.0\Az.Network\Set-AzFirewallPolicyDraft.md	whitelist	84	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name (`ThreatIntelWhitelist`) and as a component in a PowerShell object name (`PSAzureFirewallPolicyThreatIntelWhitelist`). According to the rules, when the word is used as a field, parameter, or property name, it does not need to be replaced or removed.
31	azps-14.6.0\Az.Network\Set-AzFirewallPolicyDraft.md	whitelist	84	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 referring to a field or parameter name, or when it is a component of other words, it does not need to be replaced or removed.
32	azps-14.6.0\Az.Network\Set-AzFirewall.md	whitelist	218	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 output. According to the rules, when referring to a field or filter name, database name, parameter name, or similar, it does not need to be replaced or removed.
33	azps-14.6.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 code or output. According to the rules, when referring to a field or filter name, it does not need to be replaced or removed.
34	azps-14.6.0\Az.Network\New-AzFirewallPolicy.md	whitelist	51	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name (`ThreatIntelWhitelist`) and type name (`PSAzureFirewallPolicyThreatIntelWhitelist`) in PowerShell cmdlet documentation, which is a field/property name. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
35	azps-14.6.0\Az.Network\New-AzFirewallPolicy.md	whitelist	377	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name (`ThreatIntelWhitelist`) and type name (`PSAzureFirewallPolicyThreatIntelWhitelist`) in PowerShell cmdlet documentation, which is a field/property name. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
36	azps-14.6.0\Az.Network\New-AzFirewallPolicy.md	whitelist	381	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name (`ThreatIntelWhitelist`) and a type name (`PSAzureFirewallPolicyThreatIntelWhitelist`), which are field/property names in code and API documentation. According to the rules, when referring to a field or filter name, database name, parameter name, or similar, it does not need to be replaced or removed.
37	azps-14.6.0\Az.Support\Update-AzSupportTicket.md	country	134	2	Replacement required	Geopolitical	Details The term `country` is used to describe a user attribute in a parameter name and its description, which likely refers to the user's geographic location. To avoid geopolitical issues and be inclusive of regions that may not be recognized as countries, it should be replaced with `country/region`. Specifically, update the parameter description to 'country/region of the user'.
38	azps-14.6.0\Az.Support\New-AzSupportTicketsNoSubscription.md	country	145	2	Replacement required	Geopolitical	Details The term `country` is used to label a parameter that collects the user's country information, which is a scenario where geopolitical sensitivity is relevant. To avoid issues, it should be replaced with `country/region` for inclusivity and accuracy.
39	azps-14.6.0\Az.Security\Get-AzSecurityAdaptiveApplicationControlGroup.md	whitelist	34	2	No action needed	Diversity	Details The term `whitelist` appears as a component of resource type names and property names (e.g., applicationWhitelistings, Microsoft.Security/applicationWhitelistings), which are part of Azure's established naming conventions and technical identifiers. According to the rules, when industry naming conventions or consistency make replacement of the term impractical, it should be left unchanged.
40	azps-14.6.0\Az.Resources\Update-AzADUser.md	country	37	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. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
41	azps-14.6.0\Az.Resources\Update-AzADUser.md	country	69	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. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.
42	azps-14.6.0\Az.Resources\Update-AzADUser.md	country	182	2	No action needed	Geopolitical	Details The term `country` is used as a field/property name in a parameter list for a PowerShell cmdlet, which is an acceptable usage and does not need to be replaced according to the exceptions for field or filter names.
43	azps-14.6.0\Az.Resources\Update-AzADUser.md	countries	771	2	Replacement required	Geopolitical	Details The term `countries` is used to describe the legal requirement for assigning licenses based on service availability in different countries. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `countries/regions`.
44	azps-14.6.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. This matches the rule for describing a list of things that have received approval or are considered to be in good favor. It should be replaced with `allow list` or a more specific term such as `approved IP list`.
45	azps-14.6.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`.
46	azps-14.6.0\Az.Network\Set-AzFirewallPolicy.md	whitelist	20	2	No action needed	Diversity	Details The term `whitelist` is used as a parameter/property name in PowerShell cmdlet documentation and as part of object/class names (e.g., ThreatIntelWhitelist, PSAzureFirewallPolicyThreatIntelWhitelist). According to the rules, when referring to a field, filter name, parameter name, or property name, it does not need to be replaced or removed.
47	azps-14.6.0\Az.Network\Set-AzFirewallPolicy.md	whitelist	33	2	No action needed	Diversity	Details The term `whitelist` is used as part of parameter and property names (e.g., ThreatIntelWhitelist, PSAzureFirewallPolicyThreatIntelWhitelist) in PowerShell cmdlet documentation, which are field or filter names. According to the guidelines, terms used in field, parameter, or property names do not need to be replaced.
48	azps-14.6.0\Az.Network\Set-AzFirewallPolicy.md	whitelist	77	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.
49	azps-14.6.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 (e.g., ThreatIntelWhitelist, PSAzureFirewallPolicyThreatIntelWhitelist), 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.
50	azps-14.6.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 (e.g., ThreatIntelWhitelist, PSAzureFirewallPolicyThreatIntelWhitelist), 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.

This comment lists only the first 50 of 223 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 fb242c7:

⚠️ Validation status: warnings

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

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

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

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

azps-14.6.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.6.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.6.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.6.0/Az.Network/Az.Network.md

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

azps-14.6.0/Az.Search/Az.Search.md

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

azps-14.6.0/Az.SignalR/Az.SignalR.md

• Line 0, Column 0: [Warning: PSMD2Yaml_InconsistentCmdletsInModule] Inconsistent cmdlets found in module: Az.SignalR. 3 cmdlets in the module folder but not listed in the module file: Add-AzSignalRNetworkIpRule, New-AzSignalRNetworkIpRuleObject, Remove-AzSignalRNetworkIpRule.

azps-14.6.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, EnableAutoScaling, Location, MaxCount, MaxPod, MinCount

azps-14.6.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.6.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.6.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.6.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.6.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.