An Azure service that turns documents into usable data. Previously known as Azure Form Recognizer.
Thanks for the question.
This issue usually happens when using the Document Intelligence Studio and expecting a separate endpoint and key for each custom model.
- The important point is that Azure does not create a unique endpoint or key for every model. The endpoint and key are always at the resource level. So even if you train many models inside the same resource, they all use the same endpoint and key.
- To get the correct endpoint and key, open the Azure Portal → go to your Document Intelligence (Form Recognizer) resource → click Keys and Endpoint. You will find your resource endpoint and two access keys there. These are the ones you must use when calling your custom model.
- Once you have the endpoint and key, you just need to include your model ID in the request URL. That’s how the API knows which custom model to run. The Studio shows you the model name/ID, and that is what you pass in your API call.
- If the model still doesn’t work, check a few things:
- The model is in “Ready” state.
- You are using the same region as your resource.
- The API version matches what your resource supports.
- Your keys are active and not regenerated.
Nothing is wrong with your setup. You just need to use the resource endpoint and key, then call your custom model by its model ID. Please let me know if there are any remaining questions or additional details.