Content Understanding Studio: Adding Microsoft Foundry Resource: Defaults have not yet been set Error
Read OriginalThis technical article details a solution for an error encountered when adding a new Microsoft Foundry resource to Azure's Content Understanding Studio. The error 'Defaults have not yet been set' persists even with auto-deployment enabled. The author provides the exact curl command to manually call the PATCH API endpoint, which resolves the issue, and suggests this behavior is a bug in the Studio's automation.
Comments
No comments yet
Be the first to share your thoughts!
Browser Extension
Get instant access to AllDevBlogs from your browser
Top of the Week
No top articles yet