[Automation] Fixed time zone issue while creating an update deployment schedule (#14565)

* Bug 9534965: New-AzAutomationSoftwareUpdateConfiguration cmdlet is creating schedule by taking the UTC value as the StartTime instead of local time.

* Update ChangeLog.md

Updating ChangeLog.md

Co-authored-by: Debashish Mohanta <[email protected]>

Author: dmohanta

src/Automation/Automation/ChangeLog.md

@@ -22,6 +22,7 @@
 
 ## Version 1.5.2
 * Fixed the issue for starting Python3 runbooks with parameters
+* Fixed time zone issue while creating an update deployment schedule.
 
 ## Version 1.5.1
 * Fixed te issue that complex object cannot be serialized correctly. [#14431]

src/Automation/Automation/Common/AutomationPSClientSoftwareUpdateConfiguration.cs

@@ -81,8 +81,8 @@ public SoftwareUpdateConfiguration CreateSoftwareUpdateConfiguration(string reso
                 {
                     ScheduleInfo = new Sdk.ScheduleProperties()
                     {
-                        StartTime = configuration.ScheduleConfiguration.StartTime.ToUniversalTime(),
-                        ExpiryTime = configuration.ScheduleConfiguration.ExpiryTime.ToUniversalTime(),
+                        StartTime = configuration.ScheduleConfiguration.StartTime,
+                        ExpiryTime = configuration.ScheduleConfiguration.ExpiryTime,
                         Frequency = configuration.ScheduleConfiguration.Frequency.ToString(),
                         Interval = configuration.ScheduleConfiguration.Interval,
                         IsEnabled = true,