[Eng]: New-AzPolicyDefinition converts string value in policyRule to date, in a format that is not compatible with Azure Machine Learning Scheduler

[RezaMadi]

Description

When we are passing a json file which has a date as string in yyyy-MM-ddTHH:mm:ss format in policyRule, the New-AzPolicyDefinition is converting it to date object with yyyy-MM-ddTHH:mm:ssZ format. This policy is supposed to append a shutdown scheduler to Azure machine learning VMs. The scheduler does not recognize this new format.

Expected behavior: Leave the content of the json file as it is, without parsing the string as date.

Here is example of PolicyRule, where startDate is being converted to date with 'Z' at the end:

"policyRule": { "if": { "allOf": [ { "field": "Microsoft.MachineLearningServices/workspaces/computes/computeType", "equals": "ComputeInstance" }, { "field": "Microsoft.MachineLearningServices/workspaces/computes/schedules", "exists": "false" } ] }, "then": { "effect": "append", "details": [ { "field": "Microsoft.MachineLearningServices/workspaces/computes/schedules", "value": { "computeStartStop": [ { "triggerType": "Cron", "cron": { "startTime": "2022-05-02T00:00:00", "timeZone": "UTC", "expression": "[parameters('cronExpression')]" }, "action": "Stop", "status": "Enabled" } ] } } ] } }

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @aperezcloud, @kenieva.

Issue Details

---

### Description When we are passing a json file which has a date as string in yyyy-MM-ddTHH:mm:ss format in policyRule, the New-AzPolicyDefinition is converting it to date object with yyyy-MM-ddTHH:mm:ss**Z** format. This policy is supposed to append a shutdown scheduler to Azure machine learning VMs. The scheduler does not recognize this new format. Expected behavior: Leave the content of the json file as it is, without parsing the string as date. Here is example of PolicyRule, where startDate is being converted to date with 'Z' at the end: "policyRule": { "if": { "allOf": [ { "field": "Microsoft.MachineLearningServices/workspaces/computes/computeType", "equals": "ComputeInstance" }, { "field": "Microsoft.MachineLearningServices/workspaces/computes/schedules", "exists": "false" } ] }, "then": { "effect": "append", "details": [ { "field": "Microsoft.MachineLearningServices/workspaces/computes/schedules", "value": { "computeStartStop": [ { "triggerType": "Cron", "cron": { **"startTime": "2022-05-02T00:00:00",** "timeZone": "UTC", "expression": "[parameters('cronExpression')]" }, "action": "Stop", "status": "Enabled" } ] } } ] } }

Author:	RezaMadi
Assignees:	-
Labels:	`Policy`, `Service Attention`, `question`, `customer-reported`, `CXP Attention`
Milestone:	-

[RakeshMohanMSFT]

@RezaMadi Thank you for reaching out, we are looking into it.

[RezaMadi]

@RakeshMohanMSFT Is there any update on this thread?

[RakeshMohanMSFT]

@RezaMadi Unfortunately no update on this yet, let me push it to product team.

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @aperezcloud, @kenieva.

Issue Details

---

### Description When we are passing a json file which has a date as string in yyyy-MM-ddTHH:mm:ss format in policyRule, the New-AzPolicyDefinition is converting it to date object with yyyy-MM-ddTHH:mm:ss**Z** format. This policy is supposed to append a shutdown scheduler to Azure machine learning VMs. The scheduler does not recognize this new format. Expected behavior: Leave the content of the json file as it is, without parsing the string as date. Here is example of PolicyRule, where startDate is being converted to date with 'Z' at the end: "policyRule": { "if": { "allOf": [ { "field": "Microsoft.MachineLearningServices/workspaces/computes/computeType", "equals": "ComputeInstance" }, { "field": "Microsoft.MachineLearningServices/workspaces/computes/schedules", "exists": "false" } ] }, "then": { "effect": "append", "details": [ { "field": "Microsoft.MachineLearningServices/workspaces/computes/schedules", "value": { "computeStartStop": [ { "triggerType": "Cron", "cron": { **"startTime": "2022-05-02T00:00:00",** "timeZone": "UTC", "expression": "[parameters('cronExpression')]" }, "action": "Stop", "status": "Enabled" } ] } } ] } }

Author:	RezaMadi
Assignees:	-
Labels:	`Policy`, `Service Attention`, `question`, `customer-reported`
Milestone:	-

[kenieva]

Azure Policy only supports the Universal ISO 8601 DateTime format.

[RezaMadi]

Thanks @kenieva for the update. Then, clearly there is a mismatch between DateTime format in Azure Policy and AzureML compute instance schedulers. How should we proceed?