An Azure service that integrates speech processing into apps and services.
Thanks for sharing the details. I understand you are still facing the issue even after trying the earlier steps.
Let’s go a bit deeper and check a few important areas that usually cause this kind of problem.
From your scenario, this looks like a backend or configuration level issue, most commonly related to permissions, storage setup, or project configuration in Azure AI Foundry.
Please go through the below checks one by one:
First, check storage account connection Evaluation in Foundry requires a storage account to be linked with the project. If the storage is not connected properly, the evaluation cannot read or write data and can fail silently or with errors. You can refer here for details: Evaluation troubleshooting guide [learn.microsoft.com]
Next, verify role permissions Even if you have Contributor or Owner, evaluation features need specific permissions. The Foundry project identity or your user should have proper access like Storage Blob Data Contributor on the storage account. If this role is missing, it can result in 403 or forbidden type errors.
Check if the deployment and project are in healthy state Make sure:
- Model deployment is active and not in failed or bad state
- Project does not have any backend errors Sometimes deployments fail due to quota, region capacity, or dependency issues. [azureossd.github.io]
Validate region and quota Some Foundry features depend on region availability and quota. If the region has limited capacity or quota is not assigned, operations may fail even if configuration looks correct. [opentools.ai]
Check for permission or access related blocking. A 403 error usually means access is being blocked either by:
- Missing RBAC role
- Conditional access or policy restriction
- Network or firewall settings
In many cases, even if setup looks correct, missing data plane permissions or policies can block the action. [learn.microsoft.com]
Try one quick isolation step. Create a brand-new project with:
- New storage connection
- Small test dataset
- Same region
If the issue still happens, it helps confirm that the issue is not with your configuration but something outside your control.
If you can share whether your storage is connected and what roles are assigned, it will help narrow this down faster.
I Hope this helps. Do let me know if you have any further queries.
Thankyou!