Azure PowerShell cmdlet changes for ShouldProcess, ShouldContinue, and Force (Azure#2594)

Author: Hovsep

ChangeLog.md

@@ -1,4 +1,15 @@
 ##2016.07.11 version 1.6.0
+* **Behavioral change for -Force, –Confirm and $ConfirmPreference parameters for all cmdlets. We are changing this implementation to be in line with PowerShell guidelines. For most cmdlets, this means removing the Force parameter and to skip the ShouldProcess prompt, users will need to include the parameter: ‘-Confirm:$false’ in their PowerShell scripts.** This changes are addressing following issues:
+  * Correct implementation of –WhatIf functionality, allowing a user to determine the effects of a cmdlet or script without making any actual changes
+  * Control over prompting using a session-wide $ConfirmPreference, so that the user is prompted based on the impact of a prospective change (as reported in the ConfirmImpact setting in the cmdlet)
+  * Cmdlet-specific control over confirmation prompts using the –Confirm parameter
+  * Consistent use of ShouldContinue and the –Force parameter across cmdlets, for only those actions that would require prompting from the user due to the special nature of the changes (for example, deleting hidden files)
+  * Consistency with other PowerShell cmdlets, so that PowerShell scripting knowledge from other cmdlets is immediately applicable to the Azure PowerShell cmdlets.
+
+**Notice that now to *automatically skip all Prompts in all Circumstances* Azure PowerShell cmdlets require the user to supply two parameters:**
+```
+My-CmdletWithConfirmation –Confirm:$false -Force
+```
 * Azure Compute
   * Set-AzureRmVMADDomainExtension
   * Get-AzureRmVMADDomainExtension