[Account] Adding warning message to discourage username/password (#25435)

* adding warning message to discourage username/password

* adding warning message to discourage username/password

* update changelog

* use Resources.UsernamePasswordDiscourageWarningMessage to output warning message and update changelog

* use Resources.UsernamePasswordDeprecateWarningMessage to output warning message and update changelog

* update changelog

Author: lijinpei2008

src/Accounts/Accounts/Account/ConnectAzureRmAccount.cs

@@ -337,6 +337,11 @@ public override void ExecuteCmdlet()
                 AzConfigReader.Instance?.UpdateConfig(ConfigKeys.EnableLoginByWam, false, ConfigScope.CurrentUser);
             }
 
+            if (ParameterSetName.Equals(UserWithCredentialParameterSet))
+            {
+                WriteWarning(Resources.UsernamePasswordDeprecateWarningMessage);
+            }
+
             if (MyInvocation.BoundParameters.ContainsKey(nameof(Subscription)))
             {
                 if (Guid.TryParse(Subscription, out subscriptionIdGuid))

src/Accounts/Accounts/ChangeLog.md

@@ -19,6 +19,8 @@
 -->
 
 ## Upcoming Release
+* Added a warning message in `Connect-AzAccount` to discourage the use of the username/password (a.k.a ROPC) login flow.
+* Preannounced a breaking change in `Get-AzAccessToken` to change `Token` property from `String` to `SecureString`.
 * Disable WAM when the customers login with device code flow or username password (ROPC) flow to prevent a potential issue with token cache.
 * Fixed [CVE-2024-35255](https://github.com/advisories/GHSA-m5vv-6r4h-3vj9)
 * Updated `Microsoft.Identity.Client.NativeInterop` to fix the WAM pop window issue in elevated mode [#24967]

src/Accounts/Accounts/Properties/Resources.Designer.cs

@@ -631,4 +631,7 @@
   <data name="ReportIssue" xml:space="preserve">
     <value>If you encounter any problem, please open an issue at: https://aka.ms/azpsissue</value>
   </data>
+  <data name="UsernamePasswordDeprecateWarningMessage" xml:space="preserve">
+    <value>Authentication with a username and password at the command line is strongly discouraged. Use one of the recommended authentication methods based on your requirements. For additional information, visit https://go.microsoft.com/fwlink/?linkid=2276971.</value>
+  </data>
 </root>