11/18 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	azps-15.0.0\Az.Site\New-AzSite.md	country	20	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and in documentation to refer to the address of a site. To avoid geopolitical issues and be inclusive of regions that may not be recognized as countries, it should be replaced with `country/region` throughout the documentation and parameter naming.
2	azps-15.0.0\Az.Site\New-AzSite.md	country	53	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and in example usage to specify the address of a site. In this context, it is labeling a country/region field and should be updated to avoid geopolitical issues. The recommended change is to replace it with `country/region` throughout the documentation, including parameter names and examples.
3	azps-15.0.0\Az.Site\New-AzSite.md	country	66	2	Replacement required	Geopolitical	Details The term `country` is used as a property name in a JSON configuration for a site address, which is labeling a country/region field. To avoid geopolitical issues and align with inclusive language guidance, it should be replaced with `country/region`.
4	azps-15.0.0\Az.Site\New-AzSite.md	country	125	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter label for an address field, which is a resource label scenario. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.
5	azps-15.0.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 and Microsoft.Security/applicationWhitelistings), which are established naming conventions in Azure and cannot be easily changed without breaking compatibility. According to the rules, when industry naming conventions or consistency make replacement of the term impractical, the term should be left unchanged.
6	azps-15.0.0\Az.Security\Get-AzSecurityAdaptiveApplicationControl.md	whitelist	36	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 code structure. According to the rules, when industry naming conventions or consistency make replacement of the term impractical, it should be left unchanged.
7	azps-15.0.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 URLs (such as applicationWhitelistings in resource IDs and types), which are established naming conventions in Azure and cannot be easily changed without breaking compatibility. According to the rules, when industry naming conventions or consistency make replacement of the term impractical, the term should be left unchanged.
8	azps-15.0.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 file paths, such as 'applicationWhitelistings' in the output and resource IDs. According to the rules, when the word is in a file path or is a component of other words, it does not need to be replaced or removed.
9	azps-15.0.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 likely part of legacy code, file paths, or API/resource identifiers. According to the rules, when used in such technical contexts, it does not need to be replaced or removed.
10	azps-15.0.0\Az.Security\Get-AzSecurityAdaptiveApplicationControl.md	whitelist	48	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 used in file paths, it does not need to be replaced or removed.
11	azps-15.0.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`.
12	azps-15.0.0\Az.Peering\Get-AzPeeringServiceLocation.md	country	61	2	No action needed	Geopolitical	Details The term `country` is used as a parameter name in a PowerShell cmdlet, which is considered a field or parameter name. According to the guidelines, when referring to a field or parameter name, it does not need to be replaced or removed.
13	azps-15.0.0\Az.Peering\Get-AzPeeringServiceLocation.md	country	65	2	Replacement required	Geopolitical	Details The term `country` is used as a column header in a table that lists locations, and as a parameter name and description for filtering locations. In this context, it is labeling a country/region list or resource, so to avoid geopolitical issues, it should be replaced with `country/region` throughout the documentation, including the parameter name and table header.
14	azps-15.0.0\Az.Peering\Get-AzPeeringServiceLocation.md	country	89	2	Replacement required	Geopolitical	Details The term `country` is used to label a parameter that specifies a geographic location, and in the context of Azure documentation, this can raise geopolitical sensitivity. It is not a counterexample, forbidden term, or a component of another word, nor is it a field name in a way that is exempted by the rules. Therefore, it should be replaced with `country/region` to avoid geopolitical issues.
15	azps-15.0.0\Az.Network\Set-AzFirewallPolicyDraft.md	whitelist	20	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter/property name (`ThreatIntelWhitelist` and `PSAzureFirewallPolicyThreatIntelWhitelist`) in PowerShell cmdlet documentation, which falls under the rule that when referring to a field or parameter name, it does not need to be replaced or removed.
16	azps-15.0.0\Az.Network\Set-AzFirewallPolicyDraft.md	whitelist	83	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.
17	azps-15.0.0\Az.Network\Set-AzFirewallPolicyDraft.md	whitelist	83	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter/property name (`ThreatIntelWhitelist`) and as a variable name in code examples. According to the guidelines, when the word is used as a field, parameter, or property name, it does not need to be replaced or removed.
18	azps-15.0.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, filter name, parameter name, or as a component of other words, it does not need to be replaced or removed.
19	azps-15.0.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, it does not need to be replaced or removed.
20	azps-15.0.0\Az.Network\Set-AzFirewallPolicy.md	whitelist	33	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter and object name in a PowerShell cmdlet (`ThreatIntelWhitelist`, `PSAzureFirewallPolicyThreatIntelWhitelist`, `$threatIntelWhitelist`). According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed, even if the term is sensitive in other contexts.
21	azps-15.0.0\Az.Network\Set-AzFirewallPolicy.md	whitelist	78	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 reflects existing API and code naming conventions. According to the rules, when industry naming conventions or consistency make replacement of the term impractical, the term should be left unchanged.
22	azps-15.0.0\Az.Network\Set-AzFirewallPolicy.md	whitelist	120	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 reflects existing API and code naming conventions. According to the rules, when industry naming conventions or consistency make replacement of the term impractical, the term should be left unchanged.
23	azps-15.0.0\Az.Network\Set-AzFirewallPolicy.md	whitelist	441	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 reflects established industry naming conventions and code interfaces. According to the rules and exceptions, terms in parameter names or class names do not need to be replaced, especially when changing them would break compatibility or consistency.
24	azps-15.0.0\Az.Network\New-AzFirewallPolicyThreatIntelWhitelist.md	whitelist	10	2	No action needed	Diversity	Details The term `whitelist` is used as part of a cmdlet name, parameter name, and object name in PowerShell, which follows industry naming conventions and is required for consistency and discoverability. Replacing it would break existing scripts and documentation references.
25	azps-15.0.0\Az.Network\New-AzFirewallPolicyThreatIntelWhitelist.md	whitelist	18	2	No action needed	Diversity	Details The term `whitelist` is used in the context of a PowerShell cmdlet name, parameter name, and output type, which are part of established industry naming conventions and code artifacts. According to the rules, when industry naming conventions or consistency make replacement of the term impractical, the term should be left unchanged.
26	azps-15.0.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 documentation. Changing these names would break consistency and potentially functionality, so replacement is impractical.
27	azps-15.0.0\Az.Network\New-AzFirewallPolicyThreatIntelWhitelist.md	whitelist	29	2	No action needed	Diversity	Details The term `whitelist` is used in the context of a PowerShell cmdlet name, parameter names, and output type, which are part of industry naming conventions and established API surface. Changing these names would break backward compatibility and is impractical.
28	azps-15.0.0\Az.Network\New-AzFirewallThreatIntelWhitelist.md	whitelist	7	2	No action needed	Diversity	Details The term `whitelist` is used as part of a PowerShell cmdlet name, parameter name, and object type, which are established industry naming conventions and API identifiers. Changing these would break backward compatibility and is impractical.
29	azps-15.0.0\Az.Network\New-AzFirewallPolicyDraft.md	whitelist	20	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name (`ThreatIntelWhitelist`) and a type 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-15.0.0\Az.Network\New-AzFirewallPolicyDraft.md	whitelist	32	2	No action needed	Diversity	Details The term `whitelist` is used as a parameter/property name (ThreatIntelWhitelist, -ThreatIntelWhitelist) in PowerShell cmdlet documentation, which is a field name and part of the API contract. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
31	azps-15.0.0\Az.Network\New-AzFirewallPolicyDraft.md	whitelist	59	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter/property name (ThreatIntelWhitelist, -ThreatIntelWhitelist) in PowerShell cmdlet documentation and code examples. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
32	azps-15.0.0\Az.Network\New-AzFirewallPolicyDraft.md	whitelist	61	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter and type name (ThreatIntelWhitelist, PSAzureFirewallPolicyThreatIntelWhitelist) in PowerShell cmdlet documentation, which is a case where industry naming conventions and code consistency make replacement impractical. Changing parameter or type names would break existing scripts and APIs.
33	azps-15.0.0\Az.Network\New-AzFirewallPolicyDraft.md	whitelist	62	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name (`ThreatIntelWhitelist`) and a type name (`PSAzureFirewallPolicyThreatIntelWhitelist`). According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
34	azps-15.0.0\Az.Network\New-AzFirewallPolicy.md	whitelist	19	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-15.0.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 type name (`PSAzureFirewallPolicyThreatIntelWhitelist`) in PowerShell cmdlet documentation, which reflects industry naming conventions and code consistency. According to the rules, when industry naming conventions or consistency make replacement of the term impractical, the term should be left unchanged.
36	azps-15.0.0\Az.Network\New-AzFirewall.md	whitelist	25	2	No action needed	Diversity	Details The term `whitelist` appears as part of parameter and type names such as ThreatIntelWhitelist and New-AzFirewallThreatIntelWhitelist, which are established API and PowerShell parameter names. In this context, industry naming conventions and backward compatibility make replacement impractical.
37	azps-15.0.0\Az.Network\New-AzFirewall.md	whitelist	185	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter/property name (`ThreatIntelWhitelist`, `New-AzFirewallThreatIntelWhitelist`) in PowerShell cmdlet documentation, which follows industry naming conventions and established API schemas. Changing it would break consistency and potentially compatibility for users and scripts.
38	azps-15.0.0\Az.Network\New-AzFirewall.md	whitelist	706	2	No action needed	Diversity	Details The term `whitelist` is used as part of parameter and property names such as ThreatIntelWhitelist and New-AzFirewallThreatIntelWhitelist, which are field and 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-15.0.0\Az.Site\Update-AzSite.md	country	20	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`.
40	azps-15.0.0\Az.Site\Update-AzSite.md	country	118	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 be inclusive, it should be replaced with `country/region`.
41	azps-15.0.0\Az.Support\New-AzSupportTicketsNoSubscription.md	country	145	2	Replacement required	Geopolitical	Details The term `country` is used to label a field for user information, specifically as part of a parameter name and description for user contact details. In this context, it is labeling a country/region list or resource, and should be updated to avoid geopolitical issues. It should be replaced with `country/region` for clarity and inclusivity.
42	azps-15.0.0\Az.TrustedSigning\Get-AzTrustedSigningCertificateProfile.md	country	55	2	Replacement required	Geopolitical	Details The term `country` is used as a column header in a table output, which labels a country/region field for certificate profile data. According to the rules, when used to label a country/region list or similar resource, it should be replaced to avoid geopolitical issues. The recommended replacement is `country/region`.
43	azps-15.0.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 description, which likely refers to the user's geographic location. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.
44	azps-15.0.0\Az.Support\Update-AzSupportTicketsNoSubscription.md	country	131	2	Replacement required	Geopolitical	Details The term `country` is used in the parameter description for `ContactDetailCountry` to refer to the user's country, which is a label for a country/region resource. To avoid geopolitical issues, it should be replaced with `country/region`.
45	azps-15.0.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 technical identifiers and not general descriptive text. According to the rules, when the word is a component of other words, such as in resource names or property names, it does not need to be replaced or removed.
46	azps-15.0.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.
47	azps-15.0.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 for a service, which can raise geopolitical sensitivity. It should be replaced with `countries/regions` to be inclusive and avoid issues.
48	azps-15.0.0\Az.Resources\New-AzADUser.md	country	191	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'. To avoid geopolitical issues and ensure inclusivity, the parameter name should be updated to `country/region` to match the recommended terminology.
49	azps-15.0.0\Az.Oracle\Update-AzOracleAutonomousDatabase.md	whitelist	665	2	No action needed	Diversity	Details The term `whitelist` is used as part of the parameter name `WhitelistedIP`, which is a field/property name in the PowerShell cmdlet. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
50	azps-15.0.0\Az.Purview\Get-AzPurviewScanRuleset.md	Turkey	43	2	Replacement required	Geopolitical	Details The term `Turkey` is used as part of a system classification name referring to the country/region, not the bird or another context. According to the rules, when referring to the country/region, it should be replaced with 'Türkiye'. The classification name should be updated to use 'Türkiye' for geopolitical correctness.

This comment lists only the first 50 of 225 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 42f643e:

⚠️ Validation status: warnings

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

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

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

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

azps-15.0.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-15.0.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-15.0.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-15.0.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-15.0.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-15.0.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-15.0.0/Az.Workloads/Az.Workloads.md

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

azps-15.0.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-15.0.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-15.0.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-15.0.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-15.0.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-15.0.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.