Custom document extractor has phantom entries

Question

Custom document extractor has phantom entries

Walter H 0

I created some custom document extractors that I can't delete. Even if I delete the entire resource group and create a new document intelligence service the extractors I want to delete are still in there. What is going on and how can I get them deleted?

Prashanth Veeragoni 4,515 Reputation points Microsoft External Staff Moderator

2025-04-25T00:00:19.6366667+00:00
Hi Walter H,

I understand that you’re observing that Custom Extractors persist even after deleting and recreating the Document Intelligence resource or the entire Resource Group. This is due to how Document Intelligence manages model metadata — it's sometimes stored at the tenant or subscription level, not strictly tied to the resource.

Unfortunately, there's no way to delete phantom models (extractors) through the Azure Portal or SDK once they get "orphaned." But here’s your workaround options:

Option1: Use the REST API to force delete the extractor

Try using the Document Models - Delete Model - REST API to delete the extractor by its modelId.

·       First, list your models:

GET https://<your-resource-name>.cognitiveservices.azure.com/formrecognizer/documentModels?api-version=2023-07-31

·       Then try to delete a specific model:

DELETE https://<your-resource-name>.cognitiveservices.azure.com/formrecognizer/documentModels/{modelId}?api-version=2023-07-31

Make sure to include headers:

Ocp-Apim-Subscription-Key: <your-key>

Option2: Use a new region or subscription (as a last resort)

·       Since the model metadata is region + subscription-specific, creating the service in a different region or under a new subscription will not carry over the phantom extractors.

·       This is useful if you're blocked and need a clean slate immediately.

Hope this helps, do let me know if you have any further queries.

Thank you!
Prashanth Veeragoni 4,515 Reputation points Microsoft External Staff Moderator

2025-04-25T23:18:29.6+00:00

Hi Walter H,

Following up to see if the above suggestion was helpful.

And also, just to better understand your issue, could you please clarify what you mean by “phantom entries” or extractors?

Are these models showing up in your Custom Document Models list even after deletion?

If possible, could you share a screenshot of where you're seeing these entries?

Thanks.
Prashanth Veeragoni 4,515 Reputation points Microsoft External Staff Moderator

2025-04-28T16:45:08.0833333+00:00

Hi Walter H,

Just following up again to see if you had a chance to review my earlier message.

Could you kindly confirm if the suggestion helped, or share a bit more detail (such as a screenshot) so we can better assist you with the "phantom entries" or extractors you mentioned?

If you've already resolved the issue, feel free to let me know as well — happy to close this out if everything's working fine.

Thanks again for your time and looking forward to hearing from you!

Your answer

Prashanth Veeragoni 4,515 Reputation points Microsoft External Staff Moderator

2025-04-25T00:00:19.6366667+00:00

Hi Walter H,

I understand that you’re observing that Custom Extractors persist even after deleting and recreating the Document Intelligence resource or the entire Resource Group. This is due to how Document Intelligence manages model metadata — it's sometimes stored at the tenant or subscription level, not strictly tied to the resource.

Unfortunately, there's no way to delete phantom models (extractors) through the Azure Portal or SDK once they get "orphaned." But here’s your workaround options:

Option1: Use the REST API to force delete the extractor

Try using the Document Models - Delete Model - REST API to delete the extractor by its modelId.

· First, list your models:

GET https://<your-resource-name>.cognitiveservices.azure.com/formrecognizer/documentModels?api-version=2023-07-31

· Then try to delete a specific model:

DELETE https://<your-resource-name>.cognitiveservices.azure.com/formrecognizer/documentModels/{modelId}?api-version=2023-07-31

Make sure to include headers:

Ocp-Apim-Subscription-Key: <your-key>

Option2: Use a new region or subscription (as a last resort)

· Since the model metadata is region + subscription-specific, creating the service in a different region or under a new subscription will not carry over the phantom extractors.

· This is useful if you're blocked and need a clean slate immediately.

Hope this helps, do let me know if you have any further queries.

Thank you!
Prashanth Veeragoni 4,515 Reputation points Microsoft External Staff Moderator

2025-04-25T23:18:29.6+00:00

Hi Walter H,

Following up to see if the above suggestion was helpful.

And also, just to better understand your issue, could you please clarify what you mean by “phantom entries” or extractors?

Are these models showing up in your Custom Document Models list even after deletion?

If possible, could you share a screenshot of where you're seeing these entries?

Thanks.
Prashanth Veeragoni 4,515 Reputation points Microsoft External Staff Moderator

2025-04-28T16:45:08.0833333+00:00

Hi Walter H,

Just following up again to see if you had a chance to review my earlier message.

Could you kindly confirm if the suggestion helped, or share a bit more detail (such as a screenshot) so we can better assist you with the "phantom entries" or extractors you mentioned?

If you've already resolved the issue, feel free to let me know as well — happy to close this out if everything's working fine.

Thanks again for your time and looking forward to hearing from you!

Share via

Custom document extractor has phantom entries

Your answer