Merge pull request #7045 from goergenj/jagoerge-privendpointfix+deprecationnote

Update SDK config for private endpoints and move Online Transcription…

Author: v-ccolin

articles/ai-services/speech-service/how-to-custom-speech-transcription-editor.md

@@ -2,17 +2,20 @@
 title: How to use the online transcription editor for custom speech - Speech service
 titleSuffix: Azure AI services
 description: The online transcription editor allows you to create or edit audio + human-labeled transcriptions for custom speech.
-author: PatrickFarley
+author: goergenj
 manager: nitinme
 ms.service: azure-ai-speech
 ms.topic: how-to
-ms.date: 5/19/2025
-ms.author: pafarley
+ms.date: 9/11/2025
+ms.author: jagoerge
 #Customer intent: As a developer, I need to understand how to use the online transcription editor for custom speech so that I can create or edit audio + human-labeled transcriptions for custom speech.
 ---
 
 # How to use the online transcription editor
 
+[!INCLUDE [deprecation notice](./includes/retire-online-transcription-editor.md)]
+
+
 The online transcription editor allows you to create or edit audio + human-labeled transcriptions for custom speech. The main use cases of the editor are as follows: 
 
 * You only have audio data, but want to build accurate audio + human-labeled datasets from scratch to use in model training.

articles/ai-services/speech-service/includes/retire-online-transcription-editor.md

@@ -0,0 +1,13 @@
+---
+author: goergenj
+manager: nitinme
+ms.service: azure-ai-speech
+ms.topic: include
+ms.date: 9/11/2025
+ms.author: jagoerge
+---
+
+> [!IMPORTANT]
+> Online transcription editor in Azure AI Speech will be retired on December 15th 2025. You won't be able to use online transcription editor after this date.
+> 
+> This change doesn't affect other Azure AI Speech capabilities such as [speech to text](../speech-to-text.md) (including no change to speaker diarization), [text to speech](../text-to-speech.md), and [speech translation](../speech-translation.md). 

articles/ai-services/speech-service/speech-services-private-link.md

@@ -2,13 +2,13 @@
 title: How to use private endpoints with Speech service
 titleSuffix: Azure AI services
 description: Learn how to use Speech service with private endpoints provided by Azure Private Link.
-author: PatrickFarley
-ms.author: pafarley
+author: goergenj
+ms.author: jagoerge
 manager: nitinme
 ms.service: azure-ai-speech
 ms.topic: how-to
-ms.date: 08/07/2025
-ms.reviewer: jagoerge
+ms.date: 09/11/2025
+ms.reviewer: pafarley
 ms.custom: devx-track-azurepowershell, devx-track-azurecli
 #Customer intent: As a developer, I want to learn how to use Speech service with private endpoints provided by Azure Private Link.
 ---
@@ -34,7 +34,7 @@ This article describes the usage of the private endpoints with Speech service. U
 
 ## Create a custom domain name
 > [!CAUTION]
-> an AI Foundry resource for Speech with a custom domain name enabled uses a different way to interact with Speech service. You might have to adjust your application code for both of these scenarios: [with private endpoint](#adjust-an-application-to-use-an-ai-foundry-resource-for-speech-with-a-private-endpoint) and [*without* private endpoint](#adjust-an-application-to-use-an-ai-foundry-resource-for-speech-without-private-endpoints).
+> An AI Foundry resource for Speech with a custom domain name enabled uses a different way to interact with Speech service. You might have to adjust your application code for both of these scenarios: [with private endpoint](#adjust-an-application-to-use-an-ai-foundry-resource-for-speech-with-a-private-endpoint) and [*without* private endpoint](#adjust-an-application-to-use-an-ai-foundry-resource-for-speech-without-private-endpoints).
 >
 
 [!INCLUDE [Custom Domain include](includes/how-to/custom-domain.md)]
@@ -113,16 +113,16 @@ If you plan to access the resource by using only a private endpoint, you can ski
 
 ## Adjust an application to use an AI Foundry resource for Speech with a private endpoint
 
-an AI Foundry resource for Speech with a custom domain interacts with the Speech service in a different way.
+An AI Foundry resource for Speech with a custom domain interacts with the Speech service in a different way.
 This is true for a custom-domain-enabled Speech resource both with and without private endpoints.
 Information in this section applies to both scenarios.
 
 Follow instructions in this section to adjust existing applications and solutions to use an AI Foundry resource for Speech with a custom domain name and a private endpoint turned on.
 
-an AI Foundry resource for Speech with a custom domain name and a private endpoint turned on uses a different way to interact with the Speech service. This section explains how to use such a resource with the Speech service REST APIs and the [Speech SDK](speech-sdk.md).
+An AI Foundry resource for Speech with a custom domain name and a private endpoint turned on uses a different way to interact with the Speech service. This section explains how to use such a resource with the Speech service REST APIs and the [Speech SDK](speech-sdk.md).
 
 > [!NOTE]
-> an AI Foundry resource for Speech without private endpoints that uses a custom domain name also has a special way of interacting with the Speech service.
+> An AI Foundry resource for Speech without private endpoints that uses a custom domain name also has a special way of interacting with the Speech service.
 > This way differs from the scenario of an AI Foundry resource for Speech that uses a private endpoint.
 > This is important to consider because you may decide to remove private endpoints later.
 > See [Adjust an application to use an AI Foundry resource for Speech without private endpoints](#adjust-an-application-to-use-an-ai-foundry-resource-for-speech-without-private-endpoints) later in this article.
@@ -242,60 +242,18 @@ Private-endpoint-enabled endpoints communicate with Speech service via a special
 
 A "standard" endpoint URL looks like: <p/>`{region}.{speech service offering}.speech.microsoft.com/{URL path}`
 
-A private endpoint URL looks like: <p/>`{your custom name}.cognitiveservices.azure.com/{speech service offering}/{URL path}`
+A private endpoint URL looks like: <p/>`{your custom name}.cognitiveservices.azure.com/{URL path}`
 
-**Example 1.** An application is communicating by using the following URL (speech recognition using the base model for US English in West Europe):
-
-```
-wss://westeurope.stt.speech.microsoft.com/speech/recognition/conversation/cognitiveservices/v1?language=en-US
-```
-
-To use it in the private-endpoint-enabled scenario when the custom domain name of the Speech resource is `my-private-link-speech.cognitiveservices.azure.com`, you must modify the URL like this:
-
-```
-wss://my-private-link-speech.cognitiveservices.azure.com/stt/speech/recognition/conversation/cognitiveservices/v1?language=en-US
-```
-
-Notice the details:
-
-- The host name `westeurope.stt.speech.microsoft.com` is replaced by the custom domain host name `my-private-link-speech.cognitiveservices.azure.com`.
-- The second element of the original DNS name (`stt`) becomes the first element of the URL path and precedes the original path. So the original URL `/speech/recognition/conversation/cognitiveservices/v1?language=en-US` becomes `/stt/speech/recognition/conversation/cognitiveservices/v1?language=en-US`.
-
-**Example 2.** An application uses the following URL to synthesize speech in West Europe:
-```
-wss://westeurope.tts.speech.microsoft.com/cognitiveservices/websocket/v1
-```
-
-The following equivalent URL uses a private endpoint, where the custom domain name of the Speech resource is `my-private-link-speech.cognitiveservices.azure.com`:
-
-```
-wss://my-private-link-speech.cognitiveservices.azure.com/tts/cognitiveservices/websocket/v1
-```
-
-The same principle in Example 1 is applied, but the key element this time is `tts`.
+The Speech SDK automatically will configure the `/{URL path}` depending on the service used.
+Therefore only the `/{baseURL}` must be configured as described.
 
 #### Modifying applications
 
 Follow these steps to modify your code:
 
-1. Determine the application endpoint URL:
-
-   - [Turn on logging for your application](how-to-use-logging.md) and run it to log activity.
-   - In the log file, search for `SPEECH-ConnectionUrl`. In matching lines, the `value` parameter contains the full URL that your application used to reach the Speech service.
-
-   Example:
-
-   ```
-   (114917): 41ms SPX_DBG_TRACE_VERBOSE:  property_bag_impl.cpp:138 ISpxPropertyBagImpl::LogPropertyAndValue: this=0x0000028FE4809D78; name='SPEECH-ConnectionUrl'; value='wss://westeurope.stt.speech.microsoft.com/speech/recognition/conversation/cognitiveservices/v1?traffictype=spx&language=en-US'
-   ```
-
-   So the URL that the application used in this example is:
-
-   ```
-   wss://westeurope.stt.speech.microsoft.com/speech/recognition/conversation/cognitiveservices/v1?language=en-US
-   ```
+1. Determine the application endpoint URL from the 'Keys and Endpoints' menu of your resource on Azure portal. In this example it would be `my-private-link-speech.cognitiveservices.azure.com`.
 
-2. Create a `SpeechConfig` instance by using a full endpoint URL:
+2. Create a `SpeechConfig` instance by using an endpoint URL:
 
    1. Modify the endpoint that you determined, as described in the earlier [Construct endpoint URL](#construct-endpoint-url) section.
 
@@ -307,9 +265,9 @@ Follow these steps to modify your code:
 
       To make it work, modify how you instantiate the `SpeechConfig` class and use "from endpoint"/"with endpoint" initialization. Suppose we have the following two variables defined:
       - `speechKey` contains the key of the private-endpoint-enabled Speech resource.
-      - `endPoint` contains the full *modified* endpoint URL (using the type required by the corresponding programming language). In our example, this variable should contain:
+      - `endPoint` contains the *modified* endpoint URL (using the type required by the corresponding programming language). In our example, this variable should contain:
         ```
-        wss://my-private-link-speech.cognitiveservices.azure.com/stt/speech/recognition/conversation/cognitiveservices/v1?language=en-US
+        wss://my-private-link-speech.cognitiveservices.azure.com
         ```
 
       Create a `SpeechConfig` instance:
@@ -334,13 +292,13 @@ Follow these steps to modify your code:
       config: sdk.SpeechConfig = sdk.SpeechConfig.fromEndpoint(new URL(endPoint), speechKey);
       ```
 
-> [!TIP]
-> The query parameters specified in the endpoint URI are not changed, even if they're set by other APIs. For example, if the recognition language is defined in the URI as query parameter `language=en-US`, and is also set to `ru-RU` via the corresponding property, the language setting in the URI is used. The effective language is then `en-US`.
->
-> Parameters set in the endpoint URI always take precedence. Other APIs can override only parameters that are not specified in the endpoint URI.
-
 After this modification, your application should work with the private-endpoint-enabled Speech resources. We're working on more seamless support of private endpoint scenarios.
 
+### Speech resource with a custom domain name and without private endpoints: Usage with the Speech SDK
+
+Using the Speech SDK with custom-domain-enabled Speech resources *without* private endpoints is equivalent to the configuration described *with* private endpoints in this document.
+
+
 [!INCLUDE [](includes/speech-studio-vnet.md)]
 
 
@@ -389,22 +347,6 @@ In this case, usage of the Speech to text REST API for short audio and usage of
 >
 > Using an authorization token and passing it to the special endpoint via the `Authorization` header will work *only* if you've turned on the **All networks** access option in the **Networking** section of your Speech resource. In other cases you will get either `Forbidden` or `BadRequest` error when trying to obtain an authorization token.
 
-### Speech resource with a custom domain name and without private endpoints: Usage with the Speech SDK
-
-Using the Speech SDK with custom-domain-enabled Speech resources *without* private endpoints is equivalent to the general case as described in the [Speech SDK documentation](speech-sdk.md).
-
-In case you have modified your code for using with a [private-endpoint-enabled Speech resource](#speech-resource-with-a-custom-domain-name-and-a-private-endpoint-usage-with-the-speech-sdk), consider the following.
-
-In the section on [private-endpoint-enabled Speech resources](#speech-resource-with-a-custom-domain-name-and-a-private-endpoint-usage-with-the-speech-sdk), we explained how to determine the endpoint URL, modify it, and make it work through "from endpoint"/"with endpoint" initialization of the `SpeechConfig` class instance.
-
-However, if you try to run the same application after having all private endpoints removed (allowing some time for the corresponding DNS record reprovisioning), you'll get an internal service error (404). The reason is that the [DNS record](#dns-configuration) now points to the regional Azure AI services endpoint instead of the virtual network proxy, and the URL paths like `/stt/speech/recognition/conversation/cognitiveservices/v1?language=en-US` isn't found there.
-
-You need to roll back your application to the standard instantiation of `SpeechConfig` in the style of the following code:
-
-```csharp
-var config = SpeechConfig.FromSubscription(speechKey, azureRegion);
-```
-
 [!INCLUDE [](includes/speech-vnet-service-enpoints-private-endpoints-simultaneously.md)]
 
 ## Pricing

articles/ai-services/speech-service/toc.yml

@@ -80,8 +80,6 @@ items:
             href: how-to-custom-speech-human-labeled-transcriptions.md
           - name: Structured text phonetic pronunciation
             href: customize-pronunciation.md
-          - name: Online transcription editor
-            href: how-to-custom-speech-transcription-editor.md
           - name: Display text format training data
             href: how-to-custom-speech-display-text-format.md
         - name: Custom speech model lifecycle
@@ -504,6 +502,8 @@ items:
             href: get-started-intent-recognition-clu.md
           - name: Recognize speech intents with LUIS (deprecated)
             href: get-started-intent-recognition.md
+      - name: Online transcription editor
+        href: how-to-custom-speech-transcription-editor.md
   - name: Speech to text REST API migration
     items:
     - name: From Speech to text v3.2 to 2024-11-15