Azure Key Vault: Datetime with no tzinfo will be considered UTC

[progxaker]

Describe the bug

The same issue as in #27052 but with az keyvault secret set-attribute and az keyvault key set-attribute.

Related command

az keyvault secret set-attribute --name "secret-name" --vault-name "keyvault-name" --expires "2028-02-20T00:00:00Z"
az keyvault key set-attribute --name "key-name" --vault-name "keyvault-name" --expires "2028-02-20T00:00:00Z"

Errors

Datetime with no tzinfo will be considered UTC.

Issue script & Debug output

msal.application: Broker enabled? False
azure.keyvault.secrets._generated._serialization: Datetime with no tzinfo will be considered UTC.
urllib3.connection: Starting HTTPS connection (1): ...

msal.application: Broker enabled? False
azure.keyvault.keys._generated._serialization: Datetime with no tzinfo will be considered UTC.
urllib3.connection: Starting HTTPS connection (1): ...

Expected behavior

The message Datetime with no tzinfo will be considered UTC message is disappeared.

Environment Summary

azure-cli 2.55.0
core 2.55.0
telemetry 1.1.0

Extensions:
aks-preview 0.5.173
azure-firewall 1.0.0

Dependencies:
msal 1.24.0b2
azure-mgmt-resource 23.1.0b2

Python location '/opt/az/bin/python3'
Extensions directoty '/root/.azure/cliextensions'

Python (Linux) 3.11.5 (main, Nov 29 2023, 03:41:49) [GCC 10.2.1 20210110]

Legal docs and information: aka.ms/AzureCliLegal


Your CLI is up-to-date.

Additional context

No response

[yonzhan]

Thank you for opening this issue, we will look into it.

[jsntcy]

@evelyn-ys, please help take a look.

[progxaker]

Hello. Could you please tell if there are any updates?

[progxaker]

Thanks for the help :)