Azure Speech to Text payload - Batch Transcription

Ulhas Hulyal, Nilesh 35 Reputation points
2025-01-16T10:50:27.1466667+00:00

We were using below payload for Azure Speech to Text Batch transcription till 15th Jan. It was working fine as expected.

{ "displayName": "TranscriptionDemo1",

"locale": "en-US",

"properties": {

"diarizationEnabled": true,

"wordLevelTimestampsEnabled": true,

"timeToLive": "PT3H3M",

"destinationContainerUrl": "https://StorageAccount.blob.core.windows.net/ContainerName?sp=racwdl&st=2024-10-22T09:42:04Z&se=2025-01-30T17:42:04Z&spr=https&sv=2022-11-02&sr=c&sig=Nu%2Fv9JfUoFwo%2BrPN8kT8nccHoHbc%2FXwIYQOfOvHyxE4%3D"},

"contentUrls": ["https://www.signalogic.com/melp/EngSamples/Orig/male.wav"],

"contentContainerUrl": "",

"customProperties": {

"diarizationV3Enabled": true,

"diarizationMinSpeakers": 1,

"diarizationMaxSpeakers": 10

}

}

but we started getting below error,

{

"code": "InvalidPayload",

"message": "$.customProperties.diarizationV3Enabled: The supplied value is invalid."

}

When checked document as per the link https://learn.microsoft.com/en-us/rest/api/speechtotext/transcriptions/create?view=rest-speechtotext-v3.2-preview.2&tabs=HTTP#create-a-transcription-with-multispeaker-diarization there seems to be change in payload.

Below payload is working as expected and providing results.

{ "displayName": "TranscriptionDemo1",

"locale": "en-US",

"properties": {

"diarizationEnabled": true,

"wordLevelTimestampsEnabled": true,

"diarization": {

"speakers": {

"minCount": 3,

"maxCount": 5

}},

"timeToLive": "PT3H3M",

"destinationContainerUrl": "https://stsvinpklewersttstorev2.blob.core.windows.net/klewer-nonprod-container?sp=racwdl&st=2024-10-22T09:42:04Z&se=2025-01-30T17:42:04Z&spr=https&sv=2022-11-02&sr=c&sig=Nu%2Fv9JfUoFwo%2BrPN8kT8nccHoHbc%2FXwIYQOfOvHyxE4%3D"

},

"contentUrls": [

"https://www.signalogic.com/melp/EngSamples/Orig/male.wav"

]

}

Can anyone please advise when was this payload changes implemented for Azure batch transcription?

Azure AI Speech
Azure AI Speech
An Azure service that integrates speech processing into apps and services.
2,069 questions
{count} votes

1 answer

Sort by: Most helpful
  1. santoshkc 15,355 Reputation points Microsoft External Staff Moderator
    2025-01-16T13:01:19.07+00:00

    Hi @Ulhas Hulyal, Nilesh,

    Thank you for reaching out to Microsoft Q&A forum!

    The error you're encountering is due to recent updates in the Azure Speech to Text Batch Transcription API. Specifically, the diarizationV3Enabled property in the customProperties section has been deprecated. The new structure now requires the diarization settings to be specified within a diarization object inside the properties section. The second payload format you're using is correct and follows the latest API guidelines.

    This change was implemented in the API starting 2024 as part of the API's ongoing evolution. You can review the most recent documentation and release notes for official details, but these updates align with the changes introduced in version v3.2-preview.2 and subsequent updates.

    For further specifics, you can check the Azure Speech to Text documentation and keep an eye on What's new in Azure AI Speech for latest updates.

    I hope you understand! Thank you.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.