Hi Amulya Sharma,
This behavior is a documented limitation of the Azure Translator service when processing PDFs that contain borderless tables. In such cases, the service may not correctly identify the table structure during translation, which can cause formatting issues in the translated output. As per the current known issues for Translator, the recommended workaround is to modify the source file so that the tables have visible borders before running the translation. Bordered tables are detected more reliably by the document translation pipeline, which helps preserve their layout in the output.
At present, there is no configuration or API parameter that can automatically correct formatting for borderless tables. If updating the source document is not feasible, you could consider preprocessing it programmatically to add faint borders around tables or extracting the table data and translating it using the Translator text API, then reassembling it into a PDF with proper formatting. However, these are manual or custom workflow solutions, and the only officially supported method to mitigate this issue is to ensure tables have borders prior to translation.