Swagger Spec for Microsoft.ADHybridHealthService

[gamitra]

This Pull Request contains the Swagger specification for Microsoft.ADHybridHealthService RP.
This RP is for Azure Active Directory Connect Health service, which has been GA-ed for last 2 years.
Azure Active Directory (Azure AD) Connect Health helps you monitor and gain insights into your on-premises identity infrastructure and the synchronization services. It enables you to maintain a reliable connection to Office 365 and Microsoft Online Services by providing monitoring capabilities for your key identity components such as Active Directory Federation Services (AD FS) servers, Azure AD Connect servers (also known as Sync Engine), Active Directory domain controllers, etc. It also makes the key data points about these components easily accessible so that you can get usage and other important insights to make informed decisions.
The information is presented in the Azure AD Connect Health portal. In the Azure AD Connect Health portal, you can view alerts, performance monitoring, usage analytics, and other information. Azure AD Connect Health enables the single lens of health for your key identity components in one place.
More details about this RP can be found at:
https://docs.microsoft.com/en-us/azure/active-directory/connect-health/active-directory-aadconnect-health

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.

PR information

• The title of the PR is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
• Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
• If applicable, the PR references the bug/issue that it fixes.
• Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

• I have read the contribution guidelines.
• My spec meets the review criteria:
  • The spec conforms to the Swagger 2.0 specification.
  • The spec follows the guidelines described in the Swagger checklist document.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.

[azuresdkciprbot]

AutoRest linter results for ARM Related Validation Errors/Warnings

These errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns.

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[azuresdkciprbot]

AutoRest linter results for SDK Related Validation Errors/Warnings

These errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns.

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[AutorestCI]

Automation for azure-sdk-for-go

A PR has been created for you:
Azure/azure-sdk-for-go#1750

[AutorestCI]

Automation for azure-sdk-for-python

A PR has been created for you:
Azure/azure-sdk-for-python#2504

[AutorestCI]

Automation for azure-libraries-for-java

A PR has been created for you:
AutorestCI/azure-libraries-for-java#129

[AutorestCI]

Automation for azure-sdk-for-node

Nothing to generate for azure-sdk-for-node

[annatisch]

@gamitra - please add a readme file for this spec into the resource-manager directory.
You can see here for an example:
https://github.com/Azure/azure-rest-api-specs/tree/master/specification/cognitiveservices/resource-manager

Please also include the sections and/or files for the various language SDK generation.

[azuresdkciprbot]

AutoRest linter results for ARM Related Validation Errors/Warnings

These errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns.

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[azuresdkciprbot]

AutoRest linter results for SDK Related Validation Errors/Warnings

These errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns.

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[azuresdkciprbot]

AutoRest linter results for ARM Related Validation Errors/Warnings

These errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns.

File: specification/adhybridhealthservice/resource-manager/readme.md

⚠️48 new Warnings.(48 total)

Code	Id	Source	Message
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isGroupbySite
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: perfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isGroupbySite
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: schema
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: perfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: schema
GuidUsage	R3017	Link	Guid used in model definition 'Alert' for property 'alertId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'ExportStatus' for property 'serviceId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'MergedExportError' for property 'runStepResultId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'ReplicationSummary' for property 'serviceId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'TabularExportError' for property 'serviceId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: gcReachable
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: pdcReachable
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: sysvolState
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: consentedToShare
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: multiValued
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: trucated
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: attributeMultiValue
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: passwordSyncEnabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: idSet
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: invisibleForUi
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDefault
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isPerfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDevOps
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: attributeMultiValues
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDomain
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDefault
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: requiresSecureConnection
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: unlockAccount
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailEnabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailEnabledForGlobalAdmins
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: originalDisabledState
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: aadPremium
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: agentAutoUpdate
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: consentedToMicrosoftDevOps
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: onboarded
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: privatePreviewTenant
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: tenantInQuarantine
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: tenantOnboarded

❌0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[azuresdkciprbot]

AutoRest linter results for SDK Related Validation Errors/Warnings

These errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns.

File: specification/adhybridhealthservice/resource-manager/readme.md

⚠️100 new Warnings.(100 total)

Code	Id	Source	Message
ListInOperationName	R1003	Link	Since operation 'addsservices_GetServices' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'alerts_GetAddsServicesAlerts' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'addsservicemembers_GetServiceMembers' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'addomainservicemembers_GetServiceMembersV2' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'metrics_GetAddsServiceMetricsAverage' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'addsservices_GetAddsServiceMetricsSum' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'metricmetadata_GetMetricMetadata' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'metricmetadata_GetMetricsForService' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'alerts_GetAddsServiceMemberAlerts' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'addsservices_GetServicesPremiumCheck' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services_GetServices' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'premiumCheck_GetServicesPremiumCheck' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'alerts_GetAlerts' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services_GetLatestAadExportErrorCount' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services_GetLatestAadExportErrorsV2' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services_GetExportStatus' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services_GetPeralertfeedback' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services_GetMetricsAverage' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services_GetMetricsSum' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services_GetMetricMetadata' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services_GetMetricsForService' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services_GetServiceMonitoringConfigurations' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services-GetBadPwdUserReport' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services_GetServiceMembers' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services_GetServiceMemberAlerts' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services_GetConnectors' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services_GetServiceMemberExportStatus' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services_GetMetricsForServiceMember' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounVerb	R1001	Link	Per the Noun_Verb convention for Operation Ids, the noun 'addsservices' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'alertsModel'. Consider using the plural form of 'alerts' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'addsservicemembersModel'. Consider using the plural form of 'addsservicemembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'forestsummaryModel'. Consider using the plural form of 'forestsummary' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
PatchInOperationName	R1007	Link	'PATCH' operation 'configuration_PatchTenant' should use method name 'Update'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'metricmetadataModel'. Consider using the plural form of 'metricmetadata' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'metricmetadataModel'. Consider using the plural form of 'metricmetadata' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'metricmetadataModel'. Consider using the plural form of 'metricmetadata' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'replicationstatusModel'. Consider using the plural form of 'replicationstatus' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'replicationsummaryModel'. Consider using the plural form of 'replicationsummary' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
GetInOperationName	R1005	Link	'GET' operation 'services_CheckServiceFeatureAvailibility' should use method name 'Get' or Method name start with 'List'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'alertsModel'. Consider using the plural form of 'alerts' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounVerb	R1001	Link	Per the Noun_Verb convention for Operation Ids, the noun 'Feedback' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
GetInOperationName	R1005	Link	'GET' operation 'services-GetBadPwdUserReport' should use method name 'Get' or Method name start with 'List'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'alertsModel'. Consider using the plural form of 'alerts' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
GetInOperationName	R1005	Link	'GET' operation 'services_CheckTenantWhitelistingForFeature' should use method name 'Get' or Method name start with 'List'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
XmsEnumValidation	R2018	Link	The enum types should have x-ms-enum type extension set with appropriate options. Property name: state
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
DescriptionAndTitleMissing	R4000	Link	'value' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.
DescriptionAndTitleMissing	R4000	Link	'value' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.
DescriptionAndTitleMissing	R4000	Link	'value' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.
DescriptionAndTitleMissing	R4000	Link	'value' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.
DescriptionAndTitleMissing	R4000	Link	'value' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.
DescriptionAndTitleMissing	R4000	Link	'value' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.
DescriptionAndTitleMissing	R4000	Link	'value' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.
DescriptionAndTitleMissing	R4000	Link	'value' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.
DescriptionAndTitleMissing	R4000	Link	'value' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.
DescriptionAndTitleMissing	R4000	Link	'value' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.
DescriptionAndTitleMissing	R4000	Link	'value' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.
DescriptionAndTitleMissing	R4000	Link	'value' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.
DescriptionAndTitleMissing	R4000	Link	'value' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.
DescriptionAndTitleMissing	R4000	Link	'value' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.
DescriptionAndTitleMissing	R4000	Link	'value' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.
DescriptionAndTitleMissing	R4000	Link	'value' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
DescriptionAndTitleMissing	R4000	Link	'value' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.
DescriptionAndTitleMissing	R4000	Link	'value' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.
DescriptionAndTitleMissing	R4000	Link	'value' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.
DescriptionAndTitleMissing	R4000	Link	'value' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
DescriptionAndTitleMissing	R4000	Link	'value' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.

❌0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[annatisch]

Thanks @gamitra!
So am I understanding correctly that this spec is for an API that is already public? i.e. - there's no new APIs here that require ARM review?

[annatisch]

This is actually a list operation - so should probably be renamed accordingly and use the x-ms-pageable extension:
https://github.com/Azure/autorest/tree/master/docs/extensions#x-ms-pageable

[annatisch]

Additionally, the name of the operation group ("services") is usually not repeated in the operation name. So this should be renamed to just "services_list" rather than "services_listServices"

[annatisch]

Operations shouldn't be named after the HTTP request type - this should use a verb describes the action, usually "add" or "create". So the new name should be something like "services_create"/"services_add"

[annatisch]

@gamitra
Before I go any further with the review - there's a couple of larger things across the spec that need a look at.

• It looks like many of the operation ID's need to be tweaked. We generally don't repeat the noun when that operation is an action on the operation group, e.g.:
  services_getService => service_get
  services_deleteService => service_delete
• It looks like "serviceMember" needs to be it's own operation group:
  "serviceMember_getDataFreshness"
  "serviceMember_getExportStatus"
  "serviceMember_getMetrics"
• Take a look at the paging extension for array response bodies. There are a couple of areas where it could be applied (anything with a single array in the response or anything the uses a "nextlink" field). This ensures that the SDK generators will automatically handle a next link returned by the service, and wrap the response according to each language.
• Avoid using 'post' in an operation name - replace with a more human friendly verb. Use of 'get' and 'patch' is generally okay though.
• Some capitalization could be looked at, as this affects language specific code generation e.g.:
  forestsummary -> forestSummary
  metricmetadata -> metricMetadata
  replicationstatus -> replicationStatus

[gamitra]

@annatisch , Yes you are right.This RP has been there since 2014. We were missing a swagger spec for our RP and this pull request is about adding the swagger spec for all our Rest APIs. There is no new api for review.

[gamitra]

@annatisch , Thank You for these great suggestions. I am modifying the json file using your suggestion. Below are the formats I am using:

1. For routes containing addsservices, the naming convention for operationId: addsservice_get/list/update/add* . I cant combine them with /servicemembers because they are dedicated to a specific set of Service monitoring(Active Directory Domain Service.)
2. For routes containing /services, I am using the naming convention services_get/list/patch/add*, etc.
3. For routes containing /servicemembers( which are not a part of addsservices route), I am using the naming convention servicemembers_get/ad/patch/*
4. I am adding x-ms-pageable, where the response has a nextLink.

Let me know if this looks fine to you.

[annatisch]

Thanks @gamitra - looks good.
One thing I would add is that the response does not need a nextlink in order to use x-ms-pageable. This should be used anywhere where the response is a list (then in the spec you can just set "nextLinkName" to null)

[azuresdkciprbot]

AutoRest linter results for ARM Related Validation Errors/Warnings

These errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns.

File: specification/adhybridhealthservice/resource-manager/readme.md

⚠️50 new Warnings.(50 total)

Code	Id	Source	Message
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isGroupbySite
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: perfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isGroupbySite
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: perfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
GuidUsage	R3017	Link	Guid used in model definition 'Alert' for property 'alertId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'ExportStatus' for property 'serviceId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'MergedExportError' for property 'runStepResultId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'TabularExportError' for property 'serviceId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: hasProperties
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: gcReachable
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isAdvertising
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: pdcReachable
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: sysvolState
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: consentedToShare
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: multiValued
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: truncated
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: attributeMultiValue
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: passwordSyncEnabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: invisibleForUi
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDefault
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isPerfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDevOps
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: attributeMultiValues
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDomain
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDefault
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: requiresSecureConnection
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: unlockAccount
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: value
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailEnabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailEnabledForGlobalAdmins
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailsEnabledForGlobalAdmins
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: originalDisabledState
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: aadPremium
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: agentAutoUpdate
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: consentedToMicrosoftDevOps
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: onboardingAllowed
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: onboarded
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: privatePreviewTenant
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: tenantInQuarantine
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: tenantOnboarded

❌0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[azuresdkciprbot]

AutoRest linter results for SDK Related Validation Errors/Warnings

These errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns.

File: specification/adhybridhealthservice/resource-manager/readme.md

⚠️49 new Warnings.(49 total)

Code	Id	Source	Message
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'addsservices' in:'addsServices_add'. Consider updating the operationId
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'configuration' in:'configuration_add'. Consider updating the operationId
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'services' in:'services_add'. Consider updating the operationId
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'servicemembers' in:'serviceMembers_add'. Consider updating the operationId
ListInOperationName	R1003	Link	Since operation 'addsServices_getMetricMetadataForGroup' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'addsServices_getReplicationSummary' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services_getMetricMetadataForGroup' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'alertsModel'. Consider using the plural form of 'alerts' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'dimensionsModel'. Consider using the plural form of 'dimensions' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'addsServiceMembersModel'. Consider using the plural form of 'addsServiceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience

❌0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[azuresdkciprbot]

AutoRest linter results for SDK Related Validation Errors/Warnings

These errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns.

File: specification/adhybridhealthservice/resource-manager/readme.md

⚠️49 new Warnings.(49 total)

Code	Id	Source	Message
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'addsservices' in:'addsServices_add'. Consider updating the operationId
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'configuration' in:'configuration_add'. Consider updating the operationId
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'services' in:'services_add'. Consider updating the operationId
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'servicemembers' in:'serviceMembers_add'. Consider updating the operationId
ListInOperationName	R1003	Link	Since operation 'addsServices_getMetricMetadataForGroup' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'addsServices_getReplicationSummary' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services_getMetricMetadataForGroup' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'alertsModel'. Consider using the plural form of 'alerts' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'dimensionsModel'. Consider using the plural form of 'dimensions' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'addsServiceMembersModel'. Consider using the plural form of 'addsServiceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience

❌0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[azuresdkciprbot]

AutoRest linter results for ARM Related Validation Errors/Warnings

These errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns.

File: specification/adhybridhealthservice/resource-manager/readme.md

⚠️50 new Warnings.(50 total)

Code	Id	Source	Message
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isGroupbySite
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: perfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isGroupbySite
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: perfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
GuidUsage	R3017	Link	Guid used in model definition 'Alert' for property 'alertId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'ExportStatus' for property 'serviceId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'MergedExportError' for property 'runStepResultId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'TabularExportError' for property 'serviceId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: hasProperties
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: gcReachable
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isAdvertising
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: pdcReachable
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: sysvolState
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: consentedToShare
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: multiValued
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: truncated
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: attributeMultiValue
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: passwordSyncEnabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: invisibleForUi
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDefault
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isPerfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDevOps
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: attributeMultiValues
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDomain
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDefault
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: requiresSecureConnection
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: unlockAccount
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: value
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailEnabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailEnabledForGlobalAdmins
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailsEnabledForGlobalAdmins
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: originalDisabledState
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: aadPremium
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: agentAutoUpdate
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: consentedToMicrosoftDevOps
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: onboardingAllowed
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: onboarded
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: privatePreviewTenant
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: tenantInQuarantine
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: tenantOnboarded

❌0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[azuresdkciprbot]

AutoRest linter results for ARM Related Validation Errors/Warnings

These errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns.

File: specification/adhybridhealthservice/resource-manager/readme.md

⚠️50 new Warnings.(50 total)

Code	Id	Source	Message
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isGroupbySite
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: perfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isGroupbySite
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: perfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
GuidUsage	R3017	Link	Guid used in model definition 'Alert' for property 'alertId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'ExportStatus' for property 'serviceId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'MergedExportError' for property 'runStepResultId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'TabularExportError' for property 'serviceId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: hasProperties
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: gcReachable
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isAdvertising
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: pdcReachable
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: sysvolState
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: consentedToShare
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: multiValued
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: truncated
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: attributeMultiValue
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: passwordSyncEnabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: invisibleForUi
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDefault
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isPerfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDevOps
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: attributeMultiValues
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDomain
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDefault
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: requiresSecureConnection
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: unlockAccount
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: value
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailEnabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailEnabledForGlobalAdmins
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailsEnabledForGlobalAdmins
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: originalDisabledState
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: aadPremium
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: agentAutoUpdate
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: consentedToMicrosoftDevOps
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: onboardingAllowed
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: onboarded
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: privatePreviewTenant
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: tenantInQuarantine
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: tenantOnboarded

❌0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[azuresdkciprbot]

AutoRest linter results for SDK Related Validation Errors/Warnings

These errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns.

File: specification/adhybridhealthservice/resource-manager/readme.md

⚠️49 new Warnings.(49 total)

Code	Id	Source	Message
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'addsservices' in:'addsServices_add'. Consider updating the operationId
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'configuration' in:'configuration_add'. Consider updating the operationId
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'services' in:'services_add'. Consider updating the operationId
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'servicemembers' in:'serviceMembers_add'. Consider updating the operationId
ListInOperationName	R1003	Link	Since operation 'addsServices_getMetricMetadataForGroup' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'addsServices_getReplicationSummary' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services_getMetricMetadataForGroup' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'alertsModel'. Consider using the plural form of 'alerts' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'dimensionsModel'. Consider using the plural form of 'dimensions' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'addsServiceMembersModel'. Consider using the plural form of 'addsServiceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience

❌0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[azuresdkciprbot]

AutoRest linter results for SDK Related Validation Errors/Warnings

These errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns.

File: specification/adhybridhealthservice/resource-manager/readme.md

⚠️49 new Warnings.(49 total)

Code	Id	Source	Message
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'addsservices' in:'addsServices_add'. Consider updating the operationId
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'configuration' in:'configuration_add'. Consider updating the operationId
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'services' in:'services_add'. Consider updating the operationId
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'servicemembers' in:'serviceMembers_add'. Consider updating the operationId
ListInOperationName	R1003	Link	Since operation 'addsServices_getMetricMetadataForGroup' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'addsServices_getReplicationSummary' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services_getMetricMetadataForGroup' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'alertsModel'. Consider using the plural form of 'alerts' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'dimensionsModel'. Consider using the plural form of 'dimensions' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'addsServiceMembersModel'. Consider using the plural form of 'addsServiceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience

❌0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[azuresdkciprbot]

AutoRest linter results for ARM Related Validation Errors/Warnings

These errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns.

File: specification/adhybridhealthservice/resource-manager/readme.md

⚠️50 new Warnings.(50 total)

Code	Id	Source	Message
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isGroupbySite
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: perfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isGroupbySite
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: perfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
GuidUsage	R3017	Link	Guid used in model definition 'Alert' for property 'alertId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'ExportStatus' for property 'serviceId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'MergedExportError' for property 'runStepResultId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'TabularExportError' for property 'serviceId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: hasProperties
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: gcReachable
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isAdvertising
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: pdcReachable
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: sysvolState
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: consentedToShare
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: multiValued
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: truncated
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: attributeMultiValue
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: passwordSyncEnabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: invisibleForUi
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDefault
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isPerfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDevOps
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: attributeMultiValues
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDomain
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDefault
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: requiresSecureConnection
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: unlockAccount
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: value
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailEnabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailEnabledForGlobalAdmins
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailsEnabledForGlobalAdmins
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: originalDisabledState
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: aadPremium
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: agentAutoUpdate
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: consentedToMicrosoftDevOps
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: onboardingAllowed
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: onboarded
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: privatePreviewTenant
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: tenantInQuarantine
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: tenantOnboarded

❌0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[azuresdkciprbot]

AutoRest linter results for ARM Related Validation Errors/Warnings

These errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns.

File: specification/adhybridhealthservice/resource-manager/readme.md

⚠️50 new Warnings.(50 total)

Code	Id	Source	Message
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isGroupbySite
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: perfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isGroupbySite
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: perfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
GuidUsage	R3017	Link	Guid used in model definition 'Alert' for property 'alertId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'ExportStatus' for property 'serviceId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'MergedExportError' for property 'runStepResultId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'TabularExportError' for property 'serviceId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: hasProperties
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: gcReachable
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isAdvertising
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: pdcReachable
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: sysvolState
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: consentedToShare
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: multiValued
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: truncated
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: attributeMultiValue
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: passwordSyncEnabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: invisibleForUi
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDefault
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isPerfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDevOps
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: attributeMultiValues
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDomain
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDefault
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: requiresSecureConnection
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: unlockAccount
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: value
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailEnabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailEnabledForGlobalAdmins
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailsEnabledForGlobalAdmins
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: originalDisabledState
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: aadPremium
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: agentAutoUpdate
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: consentedToMicrosoftDevOps
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: onboardingAllowed
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: onboarded
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: privatePreviewTenant
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: tenantInQuarantine
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: tenantOnboarded

❌0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[azuresdkciprbot]

AutoRest linter results for SDK Related Validation Errors/Warnings

These errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns.

File: specification/adhybridhealthservice/resource-manager/readme.md

⚠️49 new Warnings.(49 total)

Code	Id	Source	Message
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'addsservices' in:'addsServices_add'. Consider updating the operationId
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'configuration' in:'configuration_add'. Consider updating the operationId
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'services' in:'services_add'. Consider updating the operationId
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'servicemembers' in:'serviceMembers_add'. Consider updating the operationId
ListInOperationName	R1003	Link	Since operation 'addsServices_getMetricMetadataForGroup' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'addsServices_getReplicationSummary' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services_getMetricMetadataForGroup' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'alertsModel'. Consider using the plural form of 'alerts' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'dimensionsModel'. Consider using the plural form of 'dimensions' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'addsServiceMembersModel'. Consider using the plural form of 'addsServiceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience

❌0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[gamitra]

@annatisch , I resolved all the issues for .12. I till see . 9, .10 and .15 failing but the errors does not look related to me. So I am not sure if I am supposed to fix them. If yes, I need help understanding how to fix them ,because the errors are quite cryptic .

Please let me know if there is any thing pending on me. Thank You

[annatisch]

Thanks @gamitra! The build looks good now. I'll take a last look over today but we should be good to go :)

[gamitra]

@annatisch , Thanks for your help. Looking forward to get this in :)

[annatisch]

@gamitra - last couple of questions

[annatisch]

Looks like this should be x-ms-pageable

[gamitra]

I have it as pageable. See line 2039. Am I missing something here?

[annatisch]

@gamitra - sorry that comment somehow ended up on completely the wrong line - let me find the correct one...

[annatisch]

@gamitra it should be "serviceMembers_listConnectors":
https://github.com/gamitra/azure-rest-api-specs/blob/adhybridhhealth_swagger/specification/adhybridhealthservice/resource-manager/Microsoft.ADHybridHealthService/stable/2014-01-01/ADHybridHealthService.json#L2303

[annatisch]

Should this be listReplicationSummary and use x-ms-pageable?

[gamitra]

You are right.Changing it.

[azuresdkciprbot]

AutoRest linter results for ARM Related Validation Errors/Warnings

These errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns.

File: specification/adhybridhealthservice/resource-manager/readme.md

⚠️50 new Warnings.(50 total)

Code	Id	Source	Message
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isGroupbySite
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: perfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isGroupbySite
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: perfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
GuidUsage	R3017	Link	Guid used in model definition 'Alert' for property 'alertId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'ExportStatus' for property 'serviceId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'MergedExportError' for property 'runStepResultId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'TabularExportError' for property 'serviceId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: hasProperties
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: gcReachable
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isAdvertising
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: pdcReachable
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: sysvolState
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: consentedToShare
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: multiValued
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: truncated
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: attributeMultiValue
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: passwordSyncEnabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: invisibleForUi
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDefault
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isPerfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDevOps
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: attributeMultiValues
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDomain
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDefault
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: requiresSecureConnection
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: unlockAccount
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: value
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailEnabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailEnabledForGlobalAdmins
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailsEnabledForGlobalAdmins
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: originalDisabledState
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: aadPremium
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: agentAutoUpdate
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: consentedToMicrosoftDevOps
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: onboardingAllowed
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: onboarded
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: privatePreviewTenant
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: tenantInQuarantine
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: tenantOnboarded

❌0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[azuresdkciprbot]

AutoRest linter results for SDK Related Validation Errors/Warnings

These errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns.

File: specification/adhybridhealthservice/resource-manager/readme.md

⚠️48 new Warnings.(48 total)

Code	Id	Source	Message
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'addsservices' in:'addsServices_add'. Consider updating the operationId
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'configuration' in:'configuration_add'. Consider updating the operationId
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'services' in:'services_add'. Consider updating the operationId
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'servicemembers' in:'serviceMembers_add'. Consider updating the operationId
ListInOperationName	R1003	Link	Since operation 'addsServices_getMetricMetadataForGroup' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services_getMetricMetadataForGroup' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'alertsModel'. Consider using the plural form of 'alerts' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'dimensionsModel'. Consider using the plural form of 'dimensions' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'addsServiceMembersModel'. Consider using the plural form of 'addsServiceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience

❌0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[gamitra]

@annatisch , I did the change to get_replicationSummary, But I did not quite get the comment for "services_listUserBadPasswordReport". I have it marked pageable. Can you help me understand the comment please?

[annatisch]

@gamitra - sorry for some reason the comment ended up referencing the wrong line number in the spec - the operation I meant to tag was "serviceMembers_listConnectors":
https://github.com/gamitra/azure-rest-api-specs/blob/adhybridhhealth_swagger/specification/adhybridhealthservice/resource-manager/Microsoft.ADHybridHealthService/stable/2014-01-01/ADHybridHealthService.json#L2303

[azuresdkciprbot]

AutoRest linter results for ARM Related Validation Errors/Warnings

These errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns.

File: specification/adhybridhealthservice/resource-manager/readme.md

⚠️50 new Warnings.(50 total)

Code	Id	Source	Message
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isGroupbySite
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: perfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isGroupbySite
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: perfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: confirm
GuidUsage	R3017	Link	Guid used in model definition 'Alert' for property 'alertId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'ExportStatus' for property 'serviceId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'MergedExportError' for property 'runStepResultId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
GuidUsage	R3017	Link	Guid used in model definition 'TabularExportError' for property 'serviceId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: hasProperties
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: gcReachable
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isAdvertising
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: pdcReachable
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: sysvolState
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: consentedToShare
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: multiValued
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: truncated
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: attributeMultiValue
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: passwordSyncEnabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: invisibleForUi
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDefault
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isPerfCounter
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDevOps
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: attributeMultiValues
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDomain
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDefault
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: requiresSecureConnection
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: unlockAccount
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: value
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailEnabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailEnabledForGlobalAdmins
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: notificationEmailsEnabledForGlobalAdmins
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: originalDisabledState
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: aadPremium
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: agentAutoUpdate
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: consentedToMicrosoftDevOps
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disabled
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: onboardingAllowed
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: onboarded
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: privatePreviewTenant
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: tenantInQuarantine
EnumInsteadOfBoolean	R3018	Link	Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: tenantOnboarded

❌0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[azuresdkciprbot]

AutoRest linter results for SDK Related Validation Errors/Warnings

These errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns.

File: specification/adhybridhealthservice/resource-manager/readme.md

⚠️48 new Warnings.(48 total)

Code	Id	Source	Message
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'addsservices' in:'addsServices_add'. Consider updating the operationId
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'configuration' in:'configuration_add'. Consider updating the operationId
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'services' in:'services_add'. Consider updating the operationId
PostOperationIdContainsUrlVerb	R2066	Link	OperationId should contain the verb: 'servicemembers' in:'serviceMembers_add'. Consider updating the operationId
ListInOperationName	R1003	Link	Since operation 'addsServices_getMetricMetadataForGroup' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
ListInOperationName	R1003	Link	Since operation 'services_getMetricMetadataForGroup' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'alertsModel'. Consider using the plural form of 'alerts' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'dimensionsModel'. Consider using the plural form of 'dimensions' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'addsServiceMembersModel'. Consider using the plural form of 'addsServiceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'serviceMembersModel'. Consider using the plural form of 'serviceMembers' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
OperationIdNounConflictingModelNames	R2063	Link	OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'servicesModel'. Consider using the plural form of 'services' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience
AvoidNestedProperties	R2001	Link	Consider using x-ms-client-flatten to provide a better end user experience

❌0 new Errors.(0 total)

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[gamitra]

@annatisch sent a new iteration with the changes

[gamitra]

@annatisch,

Thanks a lot for reviewing and guiding through this PR. :)

[annatisch]

@gamitra - you're welcome - thanks for your patience :)