@Mullika Phanhong Thank you for reaching out regarding Thai support within OCR built-in.
Historically the process is to have Azure AI Vision API (to be used with custom skillsets) release their update. In this instance, the current production version is 3.2, which does not include support for Thai. Version 4.0 is currently in preview but does include support for Thai. Version 4.0 is expected to be moved to production very soon in the coming weeks.
The OCR built-in team verified though that they cannot consider adopting a new version until Azure AI Vision has released their version into production. So once 4.0 releases as an API in the coming weeks, they will then need to research, agree to adopt 4.0, and if they agree, develop, test, and likely have a preview and only then a production version. All of this to say, if 4.0 gets accepted into the built-in OCR skillset, it could be a long time until it's available for consumption.
I am aware that your customer does not want to develop a custom skill set and use an API due to the management tasks that are associated with this approach. If they are wanting Thai support they will likely need to open up to this approach though depending on their project timeline. They can immediately move forward with Azure Document Intelligence read, which has support for Thai printed text, available today or they can wait a few weeks more for Azure AI Vision API 4.0, which will also include support for Thai printed text.