CI of azps-15.1.0

[Albertyang0]

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.1.0\Az.Site\New-AzSite.md	country	33	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.
2	azps-15.1.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 indicate the location of a site, which can be interpreted as labeling a country/region resource. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region` throughout the documentation and parameter naming.
3	azps-15.1.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 labels a country/region field. To avoid geopolitical issues and align with inclusive language guidance, it should be replaced with `country/region`.
4	azps-15.1.0\Az.Site\New-AzSite.md	country	74	2	Replacement required	Geopolitical	Details The term `country` is used as a label in a JSON configuration for site address information, which is a scenario where geopolitical sensitivity is relevant. To avoid issues, it should be replaced with `country/region`.
5	azps-15.1.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 property names (such as applicationWhitelistings and Microsoft.Security/applicationWhitelistings), which are established identifiers in code, APIs, and resource paths. According to the guidelines, terms used in resource names, file paths, or as part of technical identifiers do not need to be replaced.
6	azps-15.1.0\Az.Security\Get-AzSecurityAdaptiveApplicationControl.md	whitelist	46	2	No action needed	Diversity	Details The term `whitelist` appears only as a component of resource type names, such as 'applicationWhitelistings' and 'Microsoft.Security/applicationWhitelistings', which are field or resource names in Azure. According to the guidelines, when the word is part of a field, resource, or parameter name, it does not need to be replaced.
7	azps-15.1.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 URLs, such as 'applicationWhitelistings' and not as a standalone descriptive term. According to the guidelines, when the word is a component of other words (e.g., in resource names, file paths, or URLs), it does not need to be replaced or removed.
8	azps-15.1.0\Az.Security\Get-AzSecurityAdaptiveApplicationControlGroup.md	whitelist	36	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 rules, when the word is a component of other words, such as in a file path, resource name, or property name, it does not need to be replaced or removed.
9	azps-15.1.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 refer to either a country or a region. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.
10	azps-15.1.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 considered a field or parameter name. According to the additional rules, when referring to a field or parameter name, it does not need to be replaced or removed.
11	azps-15.1.0\Az.Resources\Update-AzADUser.md	countries	771	2	Replacement required	Geopolitical	Details The term `countries` is used to describe the availability of services in different geographic locations for licensing purposes. To avoid geopolitical issues, it should be replaced with `countries/regions`.
12	azps-15.1.0\Az.Resources\New-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 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.
13	azps-15.1.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` or similar. This aligns with the guidance to replace such terms when labeling a country/region field.
14	azps-15.1.0\Az.Peering\Get-AzPeeringServiceLocation.md	country	33	2	Replacement required	Geopolitical	Details The term `country` is used as a column header in a table that lists locations, and as a parameter to filter results, both of which are labeling a country/region resource. To avoid geopolitical issues, it should be replaced with `country/region` throughout the documentation, including the parameter name and table header.
15	azps-15.1.0\Az.Peering\Get-AzPeeringServiceLocation.md	country	84	2	Replacement required	Geopolitical	Details The term `country` is used to label a country/region list or resource in both the parameter description and output table. To avoid geopolitical issues, it should be replaced with `country/region` throughout the documentation and parameter names.
16	azps-15.1.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`.
17	azps-15.1.0\Az.Oracle\New-AzOracleAutonomousDatabase.md	whitelist	29	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter/property name (`WhitelistedIP`) in a PowerShell cmdlet and its output. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
18	azps-15.1.0\Az.Oracle\New-AzOracleAutonomousDatabase.md	whitelist	122	2	No action needed	Diversity	Details The term `whitelist` appears as part of a parameter name (`WhitelistedIP`) and a property name in the PowerShell cmdlet documentation. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
19	azps-15.1.0\Az.Peering\Get-AzPeeringServiceCountry.md	countries	13	2	Replacement required	Geopolitical	Details The term `countries` is used to label a list of geographic locations for a service, which can include both countries and regions. To avoid geopolitical issues and be inclusive, it should be replaced with `countries/regions` or a similar expression.
20	azps-15.1.0\Az.Peering\Get-AzPeeringServiceCountry.md	countries	27	2	Replacement required	Geopolitical	Details The term `countries` is used to label a list of geographic entities available for a service, which can include both countries and regions. To avoid geopolitical issues and be inclusive, it should be replaced with `countries/regions`.
21	azps-15.1.0\Az.Peering\Get-AzPeeringServiceCountry.md	Hong Kong	43	2	Replacement required	Geopolitical	Details The term `Hong Kong` is used as an entry in a list of countries for a service, which is a formal context. To avoid geopolitical issues and ensure accuracy, it should be replaced with `Hong Kong SAR` or `Hong Kong Special Administrative Region`.
22	azps-15.1.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 issues. It should be replaced with `countries/regions` to be more inclusive and accurate.
23	azps-15.1.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 applies. It should be replaced with `country/region` to be inclusive and avoid potential issues.
24	azps-15.1.0\Az.Oracle\Get-AzOracleAutonomousDatabase.md	whitelist	102	2	No action needed	Diversity	Details The term `whitelist` appears as part of the property name `WhitelistedIP` in the output of a PowerShell cmdlet. Since it is used as a field/property name, it does not need to be replaced according to the guidelines.
25	azps-15.1.0\Az.Oracle\Invoke-AzOracleActionAutonomousDatabase.md	whitelist	170	2	No action needed	Diversity	Details The term `whitelist` appears as part of the property name `WhitelistedIP` in the output of a PowerShell cmdlet. According to the rules, when the word is used as a field or property name, it does not need to be replaced or removed.
26	azps-15.1.0\Az.Network\Set-AzFirewallPolicyDraft.md	whitelist	20	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.
27	azps-15.1.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 (`ThreatIntelWhitelist`) and object name (`PSAzureFirewallPolicyThreatIntelWhitelist`) in PowerShell cmdlet documentation. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
28	azps-15.1.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 used as a field, parameter, or property name, it does not need to be replaced or removed.
29	azps-15.1.0\Az.Network\Set-AzFirewallPolicyDraft.md	whitelist	84	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter and object name (e.g., ThreatIntelWhitelist, PSAzureFirewallPolicyThreatIntelWhitelist) in PowerShell cmdlet documentation, which reflects existing API and parameter naming conventions. According to the rules, when industry naming conventions or consistency make replacement of the term impractical, the term should be left unchanged.
30	azps-15.1.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, $threatIntelWhitelist), which are field or filter names in code and command-line interfaces. According to the guidelines, when the word is used as a field or parameter name, it does not need to be replaced or removed.
31	azps-15.1.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 (e.g., ThreatIntelWhitelist, PSAzureFirewallPolicyThreatIntelWhitelist) in PowerShell cmdlet documentation. 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.
32	azps-15.1.0\Az.Network\Set-AzFirewallPolicy.md	whitelist	46	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter/property name (`ThreatIntelWhitelist`, `PSAzureFirewallPolicyThreatIntelWhitelist`, `$threatIntelWhitelist`) in PowerShell cmdlet documentation. According to the rules, when referring to a field, filter name, parameter name, property name, or similar, it does not need to be replaced or removed.
33	azps-15.1.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.
34	azps-15.1.0\Az.Network\New-AzNetworkManagerSecurityAdminConfiguration.md	nip	95	2	No action needed	Diversity	Details The term `nip` is used as an acronym or abbreviation for 'Network Intent Policy' in a technical context, not as a reference to a person or in an offensive way. It is not being used in a sensitive or inappropriate context.
35	azps-15.1.0\Az.Network\New-AzFirewallPolicy.md	whitelist	48	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-15.1.0\Az.Network\New-AzFirewallPolicy.md	whitelist	50	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-15.1.0\Az.Network\New-AzFirewallPolicy.md	whitelist	51	2	No action needed	Diversity	Details The term `whitelist` is used as part of parameter and type names (e.g., ThreatIntelWhitelist, PSAzureFirewallPolicyThreatIntelWhitelist) in PowerShell cmdlet documentation, which reflects existing API and industry naming conventions. Changing these names would break consistency and potentially functionality for users referencing these parameters.
38	azps-15.1.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 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.
39	azps-15.1.0\Az.Network\New-AzFirewall.md	whitelist	186	2	No action needed	Diversity	Details The term `whitelist` is used as part of the parameter and object names (e.g., ThreatIntelWhitelist, New-AzFirewallThreatIntelWhitelist), 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.
40	azps-15.1.0\Az.Network\New-AzFirewall.md	whitelist	186	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 or filter names in code and API documentation. According to the rules, when referring to a field or filter name, database name, parameter name, panel name, property name, file name or some other names, it does not need to be replaced or removed.
41	azps-15.1.0\Az.Network\Get-AzNetworkWatcherReachabilityReport.md	country	56	2	No action needed	Geopolitical	Details The term `country` is used as a parameter name in a PowerShell cmdlet and as a field name in output, which falls under the exception for field, filter, or parameter names. According to the provided guidance, terms used in field or parameter names do not need to be replaced.
42	azps-15.1.0\Az.Network\Get-AzNetworkWatcherReachabilityReport.md	country	60	2	No action needed	Geopolitical	Details The term `country` is used as a field name in a JSON output example, specifically as a property in an object (e.g., 'aggregationLevel' : 'country'). According to the guidelines, when the word is used as a field or property name, it does not need to be replaced or removed.
43	azps-15.1.0\Az.Network\Get-AzNetworkWatcherReachabilityReport.md	country	62	2	Replacement required	Geopolitical	Details The term `country` is used as a property name in a JSON output and as a parameter in a command, both of which label a country/region resource. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.
44	azps-15.1.0\Az.Network\Get-AzNetworkWatcherReachabilityReport.md	country	131	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and description to specify a geographic location, which may refer to a country or region. To avoid geopolitical issues and be inclusive, it should be replaced with `country/region`.
45	azps-15.1.0\Az.Network\Get-AzNetworkWatcherReachabilityReport.md	country	132	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and description for user input, which refers to a geographic location. To avoid geopolitical issues and be inclusive of regions that are not countries, it should be updated to `country/region`. This aligns with guidance to use 'country/region' in user-facing documentation and parameter descriptions.
46	azps-15.1.0\Az.Network\Az.Network.md	whitelist	1233	2	No action needed	Diversity	Details The term `whitelist` appears only as a component of PowerShell cmdlet names (e.g., New-AzFirewallPolicyThreatIntelWhitelist, New-AzFirewallThreatIntelWhitelist), which are field or parameter names and part of established API or command naming conventions. According to the rules, when used as a field, filter, or parameter name, or when industry naming conventions make replacement impractical, it does not need to be replaced.
47	azps-15.1.0\Az.NeonPostgres\New-AzNeonPostgresOrganization.md	country	152	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter description for CompanyDetailCountry, which is a field representing the country name of the company. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.
48	azps-15.1.0\Az.DataBoxEdge\New-AzDataBoxEdgeOrder.md	country	20	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and label for user input, specifically to collect address information. In this context, it is labeling a country/region field and should be updated to avoid geopolitical issues. The recommended replacement is `country/region`.
49	azps-15.1.0\Az.DataBox\Update-AzDataBoxJob.md	country	108	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter in a PowerShell command to specify the country for a shipping address. In this context, it is labeling a country/region field or resource, and to avoid geopolitical issues, it should be updated to `country/region` or a similar expression.
50	azps-15.1.0\Az.DataBox\New-AzDataBoxJob.md	country	242	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter/property name in a code example for specifying a shipping address. In this context, it is labeling a country/region field for user input, which can raise geopolitical concerns. It should be replaced with `country/region` to ensure inclusivity and avoid geopolitical issues.

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 fcfdaf3:

⚠️ Validation status: warnings

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

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

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

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

azps-15.1.0/Az.CosmosDB/Az.CosmosDB.md

• Line 0, Column 0: [Warning: PSMD2Yaml_InconsistentCmdletsInModule] Inconsistent cmdlets found in module: Az.CosmosDB. 11 cmdlets in the module folder but not listed in the module file: Add-AzCosmosDBFleetspaceAccount, Get-AzCosmosDBFleet, Get-AzCosmosDBFleetspace, Get-AzCosmosDBFleetspaceAccount, New-AzCosmosDBFleet, New-AzCosmosDBFleetspace, Remove-AzCosmosDBFleet, Remove-AzCosmosDBFleetspace, Remove-AzCosmosDBFleetspaceAccount, Update-AzCosmosDBFleet, Update-AzCosmosDBFleetspace.

azps-15.1.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.1.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.1.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.1.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.1.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.1.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.

docs-conceptual/azps-15.1.0/migrate-az-15.0.0.md

• Line 15, Column 130: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/azure/batch/batch-certificate-migration-guide' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
• Line 26, Column 130: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/azure/batch/batch-certificate-migration-guide' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
• Line 37, Column 130: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/azure/batch/batch-certificate-migration-guide' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
• Line 49, Column 130: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/azure/batch/batch-certificate-migration-guide' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
• Line 15, Column 130: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/azure/batch/batch-certificate-migration-guide' will be broken in isolated environments. Replace with a relative link.
• Line 26, Column 130: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/azure/batch/batch-certificate-migration-guide' will be broken in isolated environments. Replace with a relative link.
• Line 37, Column 130: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/azure/batch/batch-certificate-migration-guide' will be broken in isolated environments. Replace with a relative link.
• Line 49, Column 130: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/azure/batch/batch-certificate-migration-guide' will be broken in isolated environments. Replace with a relative link.

azps-15.1.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.1.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.1.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.1.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.1.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.1.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.