Getting error in adaptive custom translation (preview)

Question

Getting error in adaptive custom translation (preview)

Nikolay Yordanov 20

Trying to test the adaptive custom translation in Foundry Tools:
https://learn.microsoft.com/en-us/azure/ai-services/translator/custom-translator/azure-ai-foundry/concepts/adaptive-custom-translation

Created a workspace using the API (as defined on the web).

When trying to upload a file (tmx or tsv), I get error:

params: {'workspaceId': 'removed'}
error_response: {'message': 'The adpative file type not valid for given workspace ..... ', 'display': True, 'errorCode': None}

One more thing -the response has the typo "adpative" instead of adaptive.

Sample TSV:

en	fr
Hello world	Bonjour le monde
Thank you	Merci

Nikolay Yordanov 20 Reputation points

2025-12-19T08:42:22.84+00:00

Also cannot see the created workspace within the portal.
SRILAKSHMI C 12,985 Reputation points Microsoft External Staff Moderator

2025-12-19T12:26:41.2766667+00:00
Hello Nikolay Yordanov,

Welcome to Microsoft Q&A and Thank you for reaching out.

This issue is not caused by your TSV/TMX file. Your sample file format is valid for Adaptive Custom Translation.

What you’re running into is a current limitation of Adaptive Custom Translation while it is still in preview.

Why this is happening

Adaptive Custom Translation workspaces created via API are not fully supported yet

Only workspaces created through the Azure AI Foundry UI are currently supported for:

File upload (TSV / TMX)

Visibility in the Azure portal / Foundry Tools

When a file upload is attempted against an API-created workspace, the backend validation fails and returns a generic error such as:

“adaptive file type not valid for given workspace”

This also explains:

Why the workspace does not appear in the portal

Why valid TSV/TMX files are rejected

Why the error message contains a typo (“adpative”), indicating a preview-stage backend issue

What is supported today

Adaptive Custom Translation (preview) expects workspaces to be created from the Foundry UI

File upload and testing are supported only for UI-created workspaces

API-created workspaces are not yet wired to the upload and portal workflows

Recommended workaround:

For now, please Create the Adaptive Custom Translation workspace directly in Azure AI Foundry

Upload the TSV/TMX file through the Foundry interface

Test adaptive translation from Foundry Tools

Finally, your file format is correct

This is a service-side limitation in preview, not a configuration issue

API-based workspace creation is not fully supported yet for Adaptive Custom Translation

Full API support is expected as the feature progresses toward GA

I Hope this helps. Do let me know if you have any further queries.

Thank you!
Nikolay Yordanov 20 Reputation points

2025-12-19T13:02:25.67+00:00

Is there any documentation explaining where to upload the files?
Can you please confirm that "workspace" and "project" are the same thing within the Foundry resource boundary?
SRILAKSHMI C 12,985 Reputation points Microsoft External Staff Moderator

2025-12-22T10:57:48.7866667+00:00
Hi Nikolay Yordanov,

Thank you for your follow-up questions. I’ll address both points directly and clarify the current behavior in Adaptive Custom Translation (preview).

Where should the files be uploaded?

At this time, there is no separate public documentation page that explicitly calls out the exact UI location for file upload in Adaptive Custom Translation. This is because the feature is still in preview and the workflow is only partially documented.

Current supported workflow (preview):

Files (TSV / TMX) must be uploaded through the Azure AI Foundry portal UI

Upload is done from within the Adaptive Custom Translation experience in Foundry

File upload via API-created workspaces is not supported yet

This aligns with the preview documentation you referenced, but the upload step is implicitly handled in the Foundry UI rather than documented as a standalone API or upload endpoint.

Are “workspace” and “project” the same thing?

No, they are not the same, and this distinction is important.

Workspace

A workspace is the top-level container within the Azure AI Foundry resource

It defines the boundary for:

Storage

Permissions

Feature enablement (such as Adaptive Custom Translation)

The workspace must be created via the Foundry UI for Adaptive Custom Translation to work correctly in preview

Project

A project exists inside a workspace

Projects are used to organize:

Experiments

Datasets

Translation assets

Projects inherit permissions and capabilities from the workspace

Files must be uploaded through the Azure AI Foundry UI, not via API

Adaptive Custom Translation currently supports only UI-created workspaces

Workspace and project are distinct concepts, not interchangeable

The behavior you’re seeing is consistent with preview limitations, not a misconfiguration

As the feature moves toward GA, more explicit documentation and full API support are expected.

Thank you!
SRILAKSHMI C 12,985 Reputation points Microsoft External Staff Moderator

2025-12-23T14:02:26.8033333+00:00

Hi Nikolay Yordanov,

Did you get any chance to review the above response. Do let me know if you have any further queries.

Thank you!
Nikolay Yordanov 20 Reputation points

2026-01-06T10:31:25.95+00:00

Hi @SRILAKSHMI C I am not sure that I can create a workspace using the Foundry UI and to upload TMX or TSV files. Please share some screenshots if possible.

I can only reach the UI for uploading file for the classic models using the legacy Foundry UI as described here (https://learn.microsoft.com/en-us/azure/ai-services/translator/custom-translator/azure-ai-foundry/how-to/create-project) but cannot find any way to upload tmx or tsv using the UI for "adaptive" custom translation.
https://learn.microsoft.com/en-us/azure/ai-services/translator/custom-translator/azure-ai-foundry/concepts/adaptive-custom-translation

Thanks and Regards!
Sina Salam 26,916 Reputation points Volunteer Moderator

2026-01-06T17:09:57.57+00:00
Hello Nikolay Yordanov,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you are getting error in adaptive custom translation (preview).

This is not a formatting error in your files; it is a technical limitation in the current public preview of the feature. As long as the workspace originates from the API, the platform will reject uploads and hide the workspace from the Azure AI Foundry portal.

Therefore, it is important to know that Adaptive Custom Translation in its preview phase only supports file uploads and portal visibility for workspaces or projects created directly inside the Azure AI Foundry UI. API‑created containers are not fully wired into the backend upload and portal experience yet, which explains both the upload failure and the missing workspace. This is expected behavior during preview and will be resolved by GA.

To fix the issue, the best practice is to first create your Adaptive Custom Translation project/workspace inside the Azure AI Foundry portal. You can follow the Foundry resource creation quickstart here - https://learn.microsoft.com/en-us/azure/ai-services/multi-service-resource. Once created through the UI, the workspace becomes fully supported for TMX/TSV file uploads, portal visibility, and dataset indexing.

After the UI‑based workspace is created, return to the Adaptive Custom Translation interface in the portal and upload your bilingual TMX/TSV dataset. Adaptive CT supports 5–10,000 aligned pairs with up to 512 characters per pair. This ensures your data passes validation and allows the system to build a dataset index suitable for few‑shot adaptation.

If you prefer to automate the process using the API, you can now safely call the document import endpoint using the workspaceId retrieved from the new UI‑created workspace. For example:

curl -X POST \ "https://<your-resource-name>.cognitiveservices.azure.com/translator/customtranslator/api/texttranslator/v1.0/documents/import?workspaceId=<workspaceId>" \ -H "Authorization: Bearer <token>" \ -F 'DocumentDetails=[{"DocumentName":"my-document","DocumentType":"Adaptive","FileDetails":[{"Name":"data.tmx","LanguageCode":"en","OverwriteIfExists":true}]}]' \ -F "FILES=@path/to/data.tmx"

Full API details - https://learn.microsoft.com/en-us/azure/ai-services/translator/custom-translator/azure-ai-foundry/concepts/adaptive-custom-translation

Next, create a dataset index referencing the successfully imported document IDs and use that index in your translation requests via the 2025‑05‑01‑preview Text Translation API. Adaptive CT dynamically selects the most relevant examples during inference, and using the index ensures that your terminology and style guide the translation output.

Finally, because this feature is still in preview, expect minor UI inconsistencies, naming drift (workspace vs. project), and occasional backend quirks. The reliable path is always: create in the UI > upload in the UI > automate with the API only after the workspace exists in the UI. Following this pattern guarantees consistent success until the feature reaches General Availability.

I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.
SRILAKSHMI C 12,985 Reputation points Microsoft External Staff Moderator

2026-01-08T13:19:46.7533333+00:00
Hi Nikolay Yordanov,

To use this capability, you must first create and use an Azure AI Foundry resource. If you haven’t done this yet, follow the steps in Create your first Foundry resource

to set it up and manage it.

Once the resource is ready:

Create Project in Azure AI Foundry.

Import Adaptive Document (TMX or TSV files) into the project.

Create Dataset Index from the imported documents.

After the dataset index is created, you can perform translations using the Use Text Translation API with adaptive custom translation enabled. For detailed steps and examples, please refer to the Foundry Tools adaptive custom translation - Foundry Tools | Microsoft Learn.

Thank you!
Nikolay Yordanov 20 Reputation points

2026-01-09T08:46:42.3933333+00:00

Hi @SRILAKSHMI C

I have created a new project - but still no progress - I cannot pass the second step "Import Adaptive Document) - the link points to a page where only API is mentioned. Can you please check if some other action is required because on this page - it says that the feature is in preview and not available for every Azure Subscription/Tenant
MicrosoftTranslator/adapct4python

Thanks,

Nikolay

Manas Mohanty 13,440 Microsoft External Staff Moderator

Hi Nikolay Yordanov

Good day.

I am able to replicate the issue at my side and have requested subscription info and other details in private message to create support ticket and escalate to product group.

Attached sample tsv file content and commands used for record.

nano sample.tmx

<?xml version="1.0" encoding="UTF-8"?>
<tmx version="1.4">
  <header
    creationtool="manual"
    creationtoolversion="1.0"
    segtype="sentence"
    adminlang="en-us"
    srclang="en"
    datatype="PlainText"/>
  <body>
    <tu>
      <tuv xml:lang="en"><seg>Hello world</seg></tuv>
      <tuv xml:lang="de"><seg>Hallo Welt</seg></tuv>
    </tu>
    <tu>
      <tuv xml:lang="en"><seg>Good morning</seg></tuv>
      <tuv xml:lang="de"><seg>Guten Morgen</seg></tuv>
    </tu>
    <tu>
      <tuv xml:lang="en"><seg>Thank you</seg></tuv>
      <tuv xml:lang="de"><seg>Danke</seg></tuv>
    </tu>
  </body>
</tmx>

Commands used in Azure Cloud CLI

#set env variables
export AZ_TRANSLATOR_RESOURCE="my-translator-foundry"
export AZ_REGION="eastus2"
export BASE_URL="https://${AZ_TRANSLATOR_RESOURCE}.cognitiveservices.azure.com/translator/customtranslator/api/texttranslator/v1.0"

#Get token
TOKEN=$(az account get-access-token \
  --resource https://cognitiveservices.azure.com \
  --query accessToken -o tsv)

echo ${#TOKEN}

#Create a workspace
curl -X POST "${BASE_URL}/workspaces" \
  -H "Authorization: Bearer ${TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "adaptive-ct-demo-workspace"
  }'

#get workspace id
curl -X GET "${BASE_URL}/workspaces" \
  -H "Authorization: Bearer ${TOKEN}"

#export WORKSPACE_ID="<paste-workspace-id>"

#upload documents - fails 
curl -X POST "${BASE_URL}/documents/import?workspaceId=${WORKSPACE_ID}" \
  -H "Authorization: Bearer ${TOKEN}" \
  -F 'DocumentDetails=[
        {
          "DocumentName":"sample-tmx-doc",
          "DocumentType":"Adaptive",
          "FileDetails":[
            {
              "Name":"sample.tmx",
              "LanguageCode":"en",
              "OverwriteIfExists":true
            }
          ]
        }
      ]' \
  -F "FILES=@sample.tmx"

Thank you.

Your answer

Nikolay Yordanov 20 Reputation points

2025-12-19T08:42:22.84+00:00

Also cannot see the created workspace within the portal.
SRILAKSHMI C 12,985 Reputation points Microsoft External Staff Moderator

2025-12-19T12:26:41.2766667+00:00

Hello Nikolay Yordanov,

Welcome to Microsoft Q&A and Thank you for reaching out.

This issue is not caused by your TSV/TMX file. Your sample file format is valid for Adaptive Custom Translation.

What you’re running into is a current limitation of Adaptive Custom Translation while it is still in preview.

Why this is happening

Adaptive Custom Translation workspaces created via API are not fully supported yet

Only workspaces created through the Azure AI Foundry UI are currently supported for:

File upload (TSV / TMX)

Visibility in the Azure portal / Foundry Tools

When a file upload is attempted against an API-created workspace, the backend validation fails and returns a generic error such as:

“adaptive file type not valid for given workspace”

This also explains:

Why the workspace does not appear in the portal

Why valid TSV/TMX files are rejected

Why the error message contains a typo (“adpative”), indicating a preview-stage backend issue

What is supported today

Adaptive Custom Translation (preview) expects workspaces to be created from the Foundry UI

File upload and testing are supported only for UI-created workspaces

API-created workspaces are not yet wired to the upload and portal workflows

Recommended workaround:

For now, please Create the Adaptive Custom Translation workspace directly in Azure AI Foundry

Upload the TSV/TMX file through the Foundry interface

Test adaptive translation from Foundry Tools

Finally, your file format is correct

This is a service-side limitation in preview, not a configuration issue

API-based workspace creation is not fully supported yet for Adaptive Custom Translation

Full API support is expected as the feature progresses toward GA

I Hope this helps. Do let me know if you have any further queries.

Thank you!
Nikolay Yordanov 20 Reputation points

2025-12-19T13:02:25.67+00:00

Is there any documentation explaining where to upload the files?
Can you please confirm that "workspace" and "project" are the same thing within the Foundry resource boundary?
SRILAKSHMI C 12,985 Reputation points Microsoft External Staff Moderator

2025-12-23T14:02:26.8033333+00:00

Hi Nikolay Yordanov,

Did you get any chance to review the above response. Do let me know if you have any further queries.

Thank you!
Nikolay Yordanov 20 Reputation points

2026-01-06T10:31:25.95+00:00

Hi @SRILAKSHMI C I am not sure that I can create a workspace using the Foundry UI and to upload TMX or TSV files. Please share some screenshots if possible.

I can only reach the UI for uploading file for the classic models using the legacy Foundry UI as described here (https://learn.microsoft.com/en-us/azure/ai-services/translator/custom-translator/azure-ai-foundry/how-to/create-project) but cannot find any way to upload tmx or tsv using the UI for "adaptive" custom translation.
https://learn.microsoft.com/en-us/azure/ai-services/translator/custom-translator/azure-ai-foundry/concepts/adaptive-custom-translation

Thanks and Regards!
SRILAKSHMI C 12,985 Reputation points Microsoft External Staff Moderator

2026-01-08T13:19:46.7533333+00:00

Hi Nikolay Yordanov,

To use this capability, you must first create and use an Azure AI Foundry resource. If you haven’t done this yet, follow the steps in Create your first Foundry resource

to set it up and manage it.

Once the resource is ready:

Create Project in Azure AI Foundry.

Import Adaptive Document (TMX or TSV files) into the project.

Create Dataset Index from the imported documents.

After the dataset index is created, you can perform translations using the Use Text Translation API with adaptive custom translation enabled. For detailed steps and examples, please refer to the Foundry Tools adaptive custom translation - Foundry Tools | Microsoft Learn.

Thank you!
Nikolay Yordanov 20 Reputation points

2026-01-09T08:46:42.3933333+00:00

Hi @SRILAKSHMI C

I have created a new project - but still no progress - I cannot pass the second step "Import Adaptive Document) - the link points to a page where only API is mentioned. Can you please check if some other action is required because on this page - it says that the feature is in preview and not available for every Azure Subscription/Tenant
MicrosoftTranslator/adapct4python

Thanks,

Nikolay
Manas Mohanty 13,440 Reputation points Microsoft External Staff Moderator

2026-01-13T09:13:02.92+00:00

Hi Nikolay Yordanov

Good day.

I am able to replicate the issue at my side and have requested subscription info and other details in private message to create support ticket and escalate to product group.

Attached sample tsv file content and commands used for record.

nano sample.tmx <?xml version="1.0" encoding="UTF-8"?> <tmx version="1.4"> <header creationtool="manual" creationtoolversion="1.0" segtype="sentence" adminlang="en-us" srclang="en" datatype="PlainText"/> <body> <tu> <tuv xml:lang="en"><seg>Hello world</seg></tuv> <tuv xml:lang="de"><seg>Hallo Welt</seg></tuv> </tu> <tu> <tuv xml:lang="en"><seg>Good morning</seg></tuv> <tuv xml:lang="de"><seg>Guten Morgen</seg></tuv> </tu> <tu> <tuv xml:lang="en"><seg>Thank you</seg></tuv> <tuv xml:lang="de"><seg>Danke</seg></tuv> </tu> </body> </tmx>

Commands used in Azure Cloud CLI

#set env variables export AZ_TRANSLATOR_RESOURCE="my-translator-foundry" export AZ_REGION="eastus2" export BASE_URL="https://${AZ_TRANSLATOR_RESOURCE}.cognitiveservices.azure.com/translator/customtranslator/api/texttranslator/v1.0" #Get token TOKEN=$(az account get-access-token \ --resource https://cognitiveservices.azure.com \ --query accessToken -o tsv) echo ${#TOKEN} #Create a workspace curl -X POST "${BASE_URL}/workspaces" \ -H "Authorization: Bearer ${TOKEN}" \ -H "Content-Type: application/json" \ -d '{ "name": "adaptive-ct-demo-workspace" }' #get workspace id curl -X GET "${BASE_URL}/workspaces" \ -H "Authorization: Bearer ${TOKEN}" #export WORKSPACE_ID="<paste-workspace-id>" #upload documents - fails curl -X POST "${BASE_URL}/documents/import?workspaceId=${WORKSPACE_ID}" \ -H "Authorization: Bearer ${TOKEN}" \ -F 'DocumentDetails=[ { "DocumentName":"sample-tmx-doc", "DocumentType":"Adaptive", "FileDetails":[ { "Name":"sample.tmx", "LanguageCode":"en", "OverwriteIfExists":true } ] } ]' \ -F "FILES=@sample.tmx"

Thank you.

Share via

Getting error in adaptive custom translation (preview)

Your answer