New-AzResourceGroupDeployment changes Time field value

[MayankBargali-MSFT]

While deploying the ARM template using Templates option in Azure portal the logic app is created successfully and I can see that the timeZone and startTime is correctly set to my recurrence trigger.

But when I deploy the same template using New-AzResourceGroupDeployment command then I observe that it adds Z at the end of the startTime parameter despite the ARM template doesn’t have Z added to the startTime value.

New-AzResourceGroupDeployment
-Name LOGIC_APP_NAME
-ResourceGroupName RESOURCE_GROUP
-Mode Incremental
-TemplateFile "C:\Users\USER\Downloads\arm.txt"

As Z is added therefor the logic app does not take consider the timeZone option. Can you please confirm if this is issue with the New-AzResourceGroupDeployment as the same template works when deploying ARM template using portal option

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @armleads-azure.

Issue Details

---

While deploying the ARM template using Templates option in Azure portal the logic app is created successfully and I can see that the timeZone and startTime is correctly set to my recurrence trigger.

But when I deploy the same template using New-AzResourceGroupDeployment command then I observe that it adds Z at the end of the startTime parameter despite the ARM template doesn’t have Z added to the startTime value.

New-AzResourceGroupDeployment
-Name LOGIC_APP_NAME
-ResourceGroupName RESOURCE_GROUP
-Mode Incremental
-TemplateFile "C:\Users\USER\Downloads\arm.txt"

As Z is added therefor the logic app does not take consider the timeZone option. Can you please confirm if this is issue with the New-AzResourceGroupDeployment as the same template works when deploying ARM template using portal option

Author:	MayankBargali-MSFT
Assignees:	-
Labels:	Service Attention, ARM - Templates
Milestone:	Aug 2021 (2021-09-07)

[dingmeng-xue]

This issue should be addressed by #15552

[MayankBargali-MSFT]

@dingmeng-xue Thanks for the update. Will test it in the next release targeting on 7th September.

[MayankBargali-MSFT]

@armleads-azure @dingmeng-xue can you please confirm if this issue is fixed in the latest release as I can still observe the issue in v6.4.0

[jorgecotillo]

Can you please verify that you are using Resources module 4.3.1? See changelog here: https://github.com/Azure/azure-powershell/blob/main/src/Resources/Resources/ChangeLog.md#version-431

PR #15552 should fix for both parameters and template content serialization, here's the updated code:

azure-powershell/src/Resources/ResourceManager/SdkClient/ResourceManagerSdkClient.cs

Line 454 in 9d62943

if (!string.IsNullOrEmpty(parameters.TemplateFile))

[dingmeng-xue]

I close this issue now and let's open it if the issue is not fixed.

[ojintoad]

Is there any possibility that there's still a bug involving times about triggers that include timezone info?

After upgrading from Az 6.3.0 -> Az 6.4.0 I'm seeing error messages like:

{
    "status": "Failed",
    "error": {
        "code": "InvalidWorkflowTriggerRecurrence",
        "message": "The recurrence of trigger 'recurrence' has an invalid start time '2017-04-04T17:15:00.0000000+00:00' zone designator for time zone 'Eastern Standard Time'. Expected start time format with zone designator is 'yyyy-MM-ddTHH:mm:ss'."
    }
}

However, my template has the following:

 "triggers": {
                        "recurrence": {
                            "type": "recurrence",
                            "recurrence": {
                                "frequency": "Day",
                                "interval": 1,
                                "timeZone": "Eastern Standard Time",
                                "startTime": "2017-04-04T12:15:00-05:00"
                            }
                        }
                    },

The template is working with Az 6.3.0 and this date issue feels related. I also don't see any unit tests in #15552 of dates that contain additional timezone information. If you prefer that I open up another bug feel free to let me know.