The issue you are experiencing, where custom models are visible in Document Intelligence Studio but not accessible via the API, may be related to permissions or configuration settings. Here are some potential reasons:
- Resource Binding: Ensure that the Document Intelligence resource is correctly bound to the project in Document Intelligence Studio. If the resource was deleted or moved, the models may not be accessible via the API.
- Permissions: Check that the user has the necessary permissions to access the Document Intelligence resource and the associated storage account. If permissions are not properly set, it may prevent access to the models via the API.
- API Configuration: Verify that the API endpoint and key are correctly configured in the project settings. If the "Save" button does not persist changes, it could indicate a problem with the configuration or permissions.
- Virtual Networks and Firewalls: If there are any virtual network or firewall constraints on the storage account, it may prevent the project from being shared or accessed via the API.
If these issues persist, consider manually creating a project using the same settings as the project being shared, or re-checking the configurations and permissions.
References: