Hi @hiaga the reason we put that breaking change warning, I believe, is that we preferred to remove the alias, becuase it was against our design guideline.

For the same reason, rather than keeping the alias, I still hope it can be removed in next breaking change release (~April 2021). What do you think?

@isra-fel : Thanks for the clarification. Can you please summarize what is the end result for the customer? Apologies, but I didn't understand the exact problem by reading the design guidelines.

By removing the alias, the end result would be that customers can only use "Get-AzRecoveryServicesBackupJobDetail" to call the command. If they use "Get-AzRecoveryServicesBackupJobDetails" PowerShell won't recognize it.

The design guideline simply needs cmdlet name to be singular. It's a powershell convention that we'd like all our cmdlets to follow.

@isra-fel I'll modify the breaking change warning instead and make it singular in upcoming breaking change release.

Do we have any next breaking change release version ? I want to modify the warning message.