Hello @Harsh Khewal , Thank you again for your time and patience throughout this issue.
The product team is aware of this issue, this fix might roll out with the upcoming release. We don't have any timeline to share with you at this moment.
The temporary workaround is to work with the West Europe region as this error occurs with the East US and West US 2 resource regions. (version: 2024-02-29-preview)
I hope this helps.
Regards,
Vasavi
Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.