[BUG] Unsupported DateTime format "6/1/2023 12:00:00 AM +00:00"

[ejf-ibm]

Describe the bug
azure-resourcemanager-billing 1.0.0 throws exception on billing account get operation due to startDate format for enrollment accounts. The start date in the latest version of https://learn.microsoft.com/en-us/rest/api/billing/billing-accounts/get?view=rest-billing-2024-04-01&tabs=HTTP has changed from 2018-05-01T17:32:28Z to 6/1/2023 12:00:00 AM +00:00. CoreUtils::parseBestOffsetDateTime is not able to handle this new format.

Exception or Stack Trace

To Reproduce

1. Invoke BillingManager.billingAccounts().get("[enrollment_id]");

Expected behavior
Correct deserialization of the start and end dates for the enrollment.

Setup (please complete the following information):

• OS: Ubuntu 24.04.5 LTS
• Library/Libraries: com.azure:azure-core:1.54.1, com.azure.resourcemanager:azure-resourcemanager-billing:1.0.0
• Java version: 17

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

• Bug Description Added
• Repro Steps Added
• Setup information Added

[github-actions]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[alzimmermsft]

Thanks for reporting this @ejf-ibm, I can say I've never seen this datetime format.

@weidongxu-microsoft I did a quick litmus test to see if the old Jackson-based serialization would handled 6/1/2023 12:00:00 AM +00:00 -> OffsetDateTime and it doesn't support it either.

[weidongxu-microsoft]

Thanks @ejf-ibm @alzimmermsft .

I think this be a mistake in billing backend.

And their example in learn site is still the RFC3339 format.

Let me see if I can get service to check.
I've raised an issue in specs repo Azure/azure-rest-api-specs#31625
Let's see whether we can get service response there.