Document Translator in Azure OpenAI

Question

We have the below queries regarding the Document Translator creation in Azure OpenAI. Please help for selecting the correct configuration while creating the Document Translator:

• For using the Document Translator in Azure OpenAI, is it necessary or recommended to use Hierarchical namespace storage account (data lake storage gen2)?
• What are the key benefits that Hierarchical namespace provides over Flat namespace for Document Translator?
• Is Hierarchical namespace storage account (data lake storage gen2) supports table storage and page blobs?
• How to enable the connectivity between Document Translator and storage account (data lake storage gen2) with firewall enabled?

Answer 1

Thanks for posting your question in the Microsoft Q&A forum.

When choosing between Hierarchical Namespace Storage (HNS) and Flat Namespace Storage for Azure OpenAI's Document Translator, it’s important to weigh the benefits and limitations of HNS. HNS enhances performance for large document sets, provides a structured hierarchy for easier management, and allows for detailed access control, making it compatible with big data analytics tools. It also streamlines directory operations like renaming and moving. However, HNS lacks support for some Azure Blob Storage features and primarily accommodates block and append blobs, excluding table and page blobs. Consider the type of workload—HNS is ideal for frequent directory operations or analytics integration—as well as project scale, feature needs, and potential future requirements for big data integrations. Overall, HNS offers significant advantages for specific use cases, particularly in large-scale document processing scenarios.

---

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful

Answer 2

Hello, thanks for reaching out to us, to answer your question generally -

1. Is it necessary or recommended to use Hierarchical namespace storage account (data lake storage gen2)?

While it's not strictly necessary to use a Hierarchical namespace storage account (Data Lake Storage Gen2) for the Document Translator, it is recommended. Hierarchical namespaces provide better organization and management of data, especially for large datasets or structured data.

2. What are the key benefits that Hierarchical namespace provides over Flat namespace for Document Translator?

• Folder Structure: Hierarchical namespaces allow you to create a folder structure, which can simplify data organization and management.
• Performance: Operations like renaming or deleting directories can be performed more efficiently compared to a flat namespace.
• Access Control: Fine-grained access control can be implemented at the folder level, allowing better security and governance.
• Enhanced Features: Hierarchical namespaces support features such as data lifecycle management and better integration with analytics services.

Please refer to the below documents -

https://learn.microsoft.com/en-us/azure/storage/blobs/upgrade-to-data-lake-storage-gen2

https://learn.microsoft.com/en-us/azure/storage/blobs/data-lake-storage-namespace

I hope this helps, feel free to let me know if you have any questions.

Regards,

Yutong

-Please kindly accept the answer if you feel helpful to support the community, thanks a lot.