Issues using SAS URL for Batch Transcription in Azure Speech-to-Text

Question

Issues using SAS URL for Batch Transcription in Azure Speech-to-Text

saeide dana 0

Hello,

I'm currently working with the Azure Speech-to-Text service (batch transcription via REST API) and using a SAS URL for my audio file located in blob storage.

Although the SAS URL works in the browser, I get the following error in my code:

Fehlerdetails: {'code': 'InvalidUri', 'message': 'The recordings URI is invalid.'}

I created the SAS URL as follows:

Container: audiotest

File: test.flac

Permissions: Read

Signing: Account Key

Time window: valid at the time of the request

Format: https://mytranscription.blob.core.windows.net/audiotest/GermanTestAudio.flac?

SriLakshmi C 4,705 Reputation points Microsoft External Staff

2025-03-25T07:17:47.8033333+00:00
Hello saeide dana,

I understand that like you're encountering an issue with the format or permissions of your SAS URL. Here are a few things to check and try:

The SAS URL must include the complete file path along with the SAS token. It should be properly formatted as follows:

{ "contentContainerUrl": "https://<storage_account_name>.blob.core.windows.net/<container_name>?SAS_TOKEN" }

Kindly refer this SAS URL for batch transcription.

Ensure that the SAS token has the necessary permissions to access the file. While "Read" permission is required, you may also need "List" permissions if applicable. Additionally, verify that the SAS token is still valid at the time of the request if expired, generate a new one.

Double-check that the file name in the SAS URL matches exactly with the file in Azure Blob Storage, including case sensitivity. If using the Trusted Azure services security mechanism, ensure that the Speech resource managed identity has the correct access role (e.g., Storage Blob Data Reader) for the container.

Confirm that the blob container is not private and is accessible using the provided SAS token. Also, make sure the SAS URL is passed as a properly formatted string and follows the correct API request structure.

To troubleshoot, test the SAS URL in an incognito browser window or Postman to verify accessibility.

Also Please refer this Use the Bring your own storage (BYOS) Speech resource for speech to text, Trusted Azure services security mechanism.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
SriLakshmi C 4,705 Reputation points Microsoft External Staff

2025-03-26T09:53:28.0866667+00:00

@saeide dana

Following up to see if the above suggestion was helpful. And, if you have any further query do let us know.

Thank you!
SriLakshmi C 4,705 Reputation points Microsoft External Staff

2025-03-27T10:49:27.0166667+00:00

@saeide dana

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Thank you!

Your answer

SriLakshmi C 4,705 Reputation points Microsoft External Staff

2025-03-25T07:17:47.8033333+00:00

Hello saeide dana,

I understand that like you're encountering an issue with the format or permissions of your SAS URL. Here are a few things to check and try:

The SAS URL must include the complete file path along with the SAS token. It should be properly formatted as follows:

{ "contentContainerUrl": "https://<storage_account_name>.blob.core.windows.net/<container_name>?SAS_TOKEN" }

Kindly refer this SAS URL for batch transcription.

Ensure that the SAS token has the necessary permissions to access the file. While "Read" permission is required, you may also need "List" permissions if applicable. Additionally, verify that the SAS token is still valid at the time of the request if expired, generate a new one.

Double-check that the file name in the SAS URL matches exactly with the file in Azure Blob Storage, including case sensitivity. If using the Trusted Azure services security mechanism, ensure that the Speech resource managed identity has the correct access role (e.g., Storage Blob Data Reader) for the container.

Confirm that the blob container is not private and is accessible using the provided SAS token. Also, make sure the SAS URL is passed as a properly formatted string and follows the correct API request structure.

To troubleshoot, test the SAS URL in an incognito browser window or Postman to verify accessibility.

Also Please refer this Use the Bring your own storage (BYOS) Speech resource for speech to text, Trusted Azure services security mechanism.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
SriLakshmi C 4,705 Reputation points Microsoft External Staff

2025-03-26T09:53:28.0866667+00:00

@saeide dana

Following up to see if the above suggestion was helpful. And, if you have any further query do let us know.

Thank you!
SriLakshmi C 4,705 Reputation points Microsoft External Staff

2025-03-27T10:49:27.0166667+00:00

@saeide dana

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Thank you!

Share via

Issues using SAS URL for Batch Transcription in Azure Speech-to-Text

Your answer