Deployed scheduled trigger has wrong time due to timezone

[timtransport]

Describe the bug
Scheduled trigger for different timezone is not converted in the deployed environment

To Reproduce

1. Make a scheduled trigger with a particular start time and timezone that is +10
2. Deploy to new environment using following settings

param
(
    [parameter(Mandatory = $true)] [String] $rootFolder,
    [parameter(Mandatory = $true)] [String] $dataFactoryName,
    [parameter(Mandatory = $true)] [String] $resourceGroupName,
    [parameter(Mandatory = $true)] [String] $location,
    [parameter(Mandatory = $true)] [String] $configPath,
    [parameter(Mandatory = $true)] [String] $folderName,
    [parameter(Mandatory = $true)] [String] $triggerName
)
$opt = New-AdfPublishOption
$opt.Includes.Add("trigger.*", "")

$opt.CreateNewInstance = $false
$opt.DeleteNotInSource = $true
$opt.DoNotDeleteExcludedObjects = $false

Publish-AdfV2FromJson -RootFolder "$rootFolder" -ResourceGroupName "$resourceGroupName" -DataFactoryName "$dataFactoryName" -Location "$location" -Option $opt -Stage "$configPath"

Expected behaviour
The deployed trigger should have a start time, end time and schedule execution time that matches the original trigger configuration. Instead the times are shifted by the timezone and no longer matches

Screenshots
Source

Target

Version of PowerShell module of:

• ver 1.9.1

Provide all files to reproduce the issue