Merge branch 'MicrosoftDocs:main' into cosmos-retire-table-ruby-php

Author: seesharprun

articles/ai-services/speech-service/includes/how-to/professional-voice/create-consent/rest.md

@@ -11,7 +11,7 @@
 
 With the professional voice feature, it's required that every voice be created with explicit consent from the user. A recorded statement from the user is required acknowledging that the customer (Azure AI Speech resource owner) will create and use their voice.
 
-To add voice talent consent to the professional voice project, you get the prerecorded consent audio file from a publicly accessible URL (`Consents_Create`) or upload the audio file (`Consents_Post`). In this article, you add consent from a URL. 
+To add voice talent consent to the professional voice project, you get the prerecorded consent audio file from a publicly accessible URL ([Consents_Create](/rest/api/speechapi/consents/create)) or upload the audio file ([Consents_Post](/rest/api/speechapi/consents/post)). In this article, you add consent from a URL. 
 
 ## Consent statement
 
@@ -25,15 +25,15 @@ You can get the consent statement text for each locale from the text to speech G
 
 ## Add consent from a URL
 
-To add consent to a professional voice project from the URL of an audio file, use the `Consents_Create` operation of the custom voice API. Construct the request body according to the following instructions:
+To add consent to a professional voice project from the URL of an audio file, use the [Consents_Create](/rest/api/speechapi/consents/create) operation of the custom voice API. Construct the request body according to the following instructions:
 
 - Set the required `projectId` property. See [create a project](../../../../professional-voice-create-project.md).
 - Set the required `voiceTalentName` property. The voice talent name can't be changed later.
 - Set the required `companyName` property. The company name can't be changed later.
 - Set the required `audioUrl` property. The URL of the voice talent consent audio file. Use a URI with the [shared access signatures (SAS)](/azure/storage/common/storage-sas-overview) token.
 - Set the required `locale` property. This should be the locale of the consent. The locale can't be changed later. You can find the text to speech locale list [here](/azure/ai-services/speech-service/language-support?tabs=tts).
 
-Make an HTTP PUT request using the URI as shown in the following `Consents_Create` example. 
+Make an HTTP PUT request using the URI as shown in the following [Consents_Create](/rest/api/speechapi/consents/create) example. 
 - Replace `YourResourceKey` with your Speech resource key.
 - Replace `YourResourceRegion` with your Speech resource region.
 - Replace `JessicaConsentId` with a consent ID of your choice. The case sensitive ID will be used in the consent's URI and can't be changed later. 
@@ -65,7 +65,7 @@ You should receive a response body in the following format:
 }
 ```
 
-The response header contains the `Operation-Location` property. Use this URI to get details about the `Consents_Create` operation. Here's an example of the response header:
+The response header contains the `Operation-Location` property. Use this URI to get details about the [Consents_Create](/rest/api/speechapi/consents/create) operation. Here's an example of the response header:
 
 ```HTTP 201
 Operation-Location: https://eastus.api.cognitive.microsoft.com/customvoice/operations/070f7986-ef17-41d0-ba2b-907f0f28e314?api-version=2023-12-01-preview

articles/ai-services/speech-service/includes/how-to/professional-voice/create-project/rest.md

@@ -15,12 +15,12 @@ Each project is specific to a country/region and language, and the gender of the
 
 ## Create a project
 
-To create a professional voice project, use the `Projects_Create` operation of the custom voice API. Construct the request body according to the following instructions:
+To create a professional voice project, use the [Projects_Create](/rest/api/speechapi/projects/create) operation of the custom voice API. Construct the request body according to the following instructions:
 
 - Set the required `kind` property to `ProfessionalVoice`. The kind can't be changed later.
 - Optionally, set the `description` property for the project description. The project description can be changed later.
 
-Make an HTTP PUT request using the URI as shown in the following `Projects_Create` example. 
+Make an HTTP PUT request using the URI as shown in the following [Projects_Create](/rest/api/speechapi/projects/create) example. 
 - Replace `YourResourceKey` with your Speech resource key.
 - Replace `YourResourceRegion` with your Speech resource region.
 - Replace `ProjectId` with a project ID of your choice. The case sensitive ID must be unique within your Speech resource. The ID will be used in the project's URI and can't be changed later. 

articles/ai-services/speech-service/includes/how-to/professional-voice/create-training-set/rest.md

@@ -15,14 +15,14 @@ In this article, you [create a training set](#create-a-training-set) and get its
 
 ## Create a training set
 
-To create a training set, use the `TrainingSets_Create` operation of the custom voice API. Construct the request body according to the following instructions:
+To create a training set, use the [TrainingSets_Create](/rest/api/speechapi/training-sets/create) operation of the custom voice API. Construct the request body according to the following instructions:
 
 - Set the required `projectId` property. See [create a project](../../../../professional-voice-create-project.md).
 - Set the required `voiceKind` property to `Male` or `Female`. The kind can't be changed later. 
 - Set the required `locale` property. This should be the locale of the training set data. The locale of the training set should be the same as the locale of the [consent statement](../../../../professional-voice-create-consent.md). The locale can't be changed later. You can find the text to speech locale list [here](/azure/ai-services/speech-service/language-support?tabs=tts).
 - Optionally, set the `description` property for the training set description. The training set description can be changed later.
 
-Make an HTTP PUT request using the URI as shown in the following `TrainingSets_Create` example. 
+Make an HTTP PUT request using the URI as shown in the following [TrainingSets_Create](/rest/api/speechapi/training-sets/create) example. 
 - Replace `YourResourceKey` with your Speech resource key.
 - Replace `YourResourceRegion` with your Speech resource region.
 - Replace `JessicaTrainingSetId` with a training set ID of your choice. The case sensitive ID will be used in the training set's URI and can't be changed later. 
@@ -53,7 +53,7 @@ You should receive a response body in the following format:
 
 ## Upload training set data
 
-To upload a training set of audio and scripts, use the `TrainingSets_UploadData` operation of the custom voice API.
+To upload a training set of audio and scripts, use the [TrainingSets_UploadData](/rest/api/speechapi/training-sets/upload-data) operation of the custom voice API.
 
 Before calling this API, please store recording and script files in Azure Blob. In the example below, recording files are https://contoso.blob.core.windows.net/voicecontainer/jessica300/*.wav, script files are
 https://contoso.blob.core.windows.net/voicecontainer/jessica300/*.txt. 
@@ -70,7 +70,7 @@ Construct the request body according to the following instructions:
   - Set the required `extensions` property to the extensions of the script files.
   - Optionally, set the `prefix` property to set a prefix for the blob name.
 
-Make an HTTP POST request using the URI as shown in the following `TrainingSets_UploadData` example. 
+Make an HTTP POST request using the URI as shown in the following [TrainingSets_UploadData](/rest/api/speechapi/training-sets/upload-data) example. 
 - Replace `YourResourceKey` with your Speech resource key.
 - Replace `YourResourceRegion` with your Speech resource region.
 - Replace `JessicaTrainingSetId` if you specified a different training set ID in the previous step.
@@ -95,7 +95,7 @@ curl -v -X POST -H "Ocp-Apim-Subscription-Key: YourResourceKey" -H "Content-Type
 } '  "https://YourResourceRegion.api.cognitive.microsoft.com/customvoice/trainingsets/JessicaTrainingSetId:upload?api-version=2023-12-01-preview"
 ```
 
-The response header contains the `Operation-Location` property. Use this URI to get details about the `TrainingSets_UploadData` operation. Here's an example of the response header:
+The response header contains the `Operation-Location` property. Use this URI to get details about the [TrainingSets_UploadData](/rest/api/speechapi/training-sets/upload-data) operation. Here's an example of the response header:
 
 ```HTTP 201
 Operation-Location: https://eastus.api.cognitive.microsoft.com/customvoice/operations/284b7e37-f42d-4054-8fa9-08523c3de345?api-version=2023-12-01-preview

articles/ai-services/speech-service/includes/how-to/professional-voice/deploy-endpoint/rest.md

@@ -16,13 +16,13 @@ After you've successfully created and [trained](../../../../professional-voice-t
 
 ## Add a deployment endpoint
 
-To create an endpoint, use the `Endpoints_Create` operation of the custom voice API. Construct the request body according to the following instructions:
+To create an endpoint, use the [Endpoints_Create](/rest/api/speechapi/endpoints/create) operation of the custom voice API. Construct the request body according to the following instructions:
 
 - Set the required `projectId` property. See [create a project](../../../../professional-voice-create-project.md).
 - Set the required `modelId` property. See [train a voice model](../../../../professional-voice-train-voice.md).
 - Set the required `description` property. The description can be changed later.
 
-Make an HTTP PUT request using the URI as shown in the following `Endpoints_Create` example. 
+Make an HTTP PUT request using the URI as shown in the following [Endpoints_Create](/rest/api/speechapi/endpoints/create) example. 
 - Replace `YourResourceKey` with your Speech resource key.
 - Replace `YourResourceRegion` with your Speech resource region.
 - Replace `EndpointId` with an endpoint ID of your choice. The ID must be a GUID and must be unique within your Speech resource. The ID will be used in the project's URI and can't be changed later. 
@@ -52,7 +52,7 @@ You should receive a response body in the following format:
 }
 ```
 
-The response header contains the `Operation-Location` property. Use this URI to get details about the `Endpoints_Create` operation. Here's an example of the response header:
+The response header contains the `Operation-Location` property. Use this URI to get details about the [Endpoints_Create](/rest/api/speechapi/endpoints/create) operation. Here's an example of the response header:
 
 ```HTTP 201
 Operation-Location: https://eastus.api.cognitive.microsoft.com/customvoice/operations/284b7e37-f42d-4054-8fa9-08523c3de345?api-version=2023-12-01-preview
@@ -83,9 +83,9 @@ To use a custom voice via [Speech Synthesis Markup Language (SSML)](../../../../
 
 You can suspend or resume an endpoint, to limit spend and conserve resources that aren't in use. You won't be charged while the endpoint is suspended. When you resume an endpoint, you can continue to use the same endpoint URL in your application to synthesize speech. 
 
-To suspend an endpoint, use the `Endpoints_Suspend` operation of the custom voice API. 
+To suspend an endpoint, use the [Endpoints_Suspend](/rest/api/speechapi/endpoints/suspend) operation of the custom voice API. 
 
-Make an HTTP POST request using the URI as shown in the following `Endpoints_Suspend` example. 
+Make an HTTP POST request using the URI as shown in the following [Endpoints_Suspend](/rest/api/speechapi/endpoints/suspend) example. 
 - Replace `YourResourceKey` with your Speech resource key.
 - Replace `YourResourceRegion` with your Speech resource region.
 - Replace `YourEndpointId` with the endpoint ID that you received when you created the endpoint.
@@ -113,9 +113,9 @@ You should receive a response body in the following format:
 
 ## Resume an endpoint
 
-To suspend an endpoint, use the `Endpoints_Resume` operation of the custom voice API. 
+To suspend an endpoint, use the [Endpoints_Resume](/rest/api/speechapi/endpoints/resume) operation of the custom voice API. 
 
-Make an HTTP POST request using the URI as shown in the following `Endpoints_Resume` example. 
+Make an HTTP POST request using the URI as shown in the following [Endpoints_Resume](/rest/api/speechapi/endpoints/resume) example. 
 - Replace `YourResourceKey` with your Speech resource key.
 - Replace `YourResourceRegion` with your Speech resource region.
 - Replace `YourEndpointId` with the endpoint ID that you received when you created the endpoint.
@@ -143,9 +143,9 @@ You should receive a response body in the following format:
 
 ## Delete an endpoint
 
-To delete an endpoint, use the `Endpoints_Delete` operation of the custom voice API. 
+To delete an endpoint, use the [Endpoints_Delete](/rest/api/speechapi/endpoints/delete) operation of the custom voice API. 
 
-Make an HTTP DELETE request using the URI as shown in the following `Endpoints_Delete` example. 
+Make an HTTP DELETE request using the URI as shown in the following [Endpoints_Delete](/rest/api/speechapi/endpoints/delete) example. 
 - Replace `YourResourceKey` with your Speech resource key.
 - Replace `YourResourceRegion` with your Speech resource region.
 - Replace `YourEndpointId` with the endpoint ID that you received when you created the endpoint.

articles/ai-services/speech-service/includes/how-to/professional-voice/train-voice/rest.md

@@ -40,7 +40,7 @@ The language of the training data must be one of the [languages that are support
 
 # [Neural](#tab/neural)
 
-To create a neural voice, use the `Models_Create` operation of the custom voice API. Construct the request body according to the following instructions:
+To create a neural voice, use the [Models_Create](/rest/api/speechapi/models/create) operation of the custom voice API. Construct the request body according to the following instructions:
 
 - Set the required `projectId` property. See [create a project](../../../../professional-voice-create-project.md).
 - Set the required `consentId` property. See [add voice talent consent](../../../../professional-voice-create-consent.md).
@@ -49,7 +49,7 @@ To create a neural voice, use the `Models_Create` operation of the custom voice
 - Set the required `voiceName` property. The voice name must end with "Neural" and can't be changed later. Choose a name carefully. The voice name is used in your [speech synthesis request](../../../../professional-voice-deploy-endpoint.md#use-your-custom-voice) by the SDK and SSML input. Only letters, numbers, and a few punctuation characters are allowed. Use different names for different neural voice models.
 - Optionally, set the `description` property for the voice description. The voice description can be changed later.
 
-Make an HTTP PUT request using the URI as shown in the following `Models_Create` example. 
+Make an HTTP PUT request using the URI as shown in the following [Models_Create](/rest/api/speechapi/models/create) example. 
 - Replace `YourResourceKey` with your Speech resource key.
 - Replace `YourResourceRegion` with your Speech resource region.
 - Replace `JessicaModelId` with a model ID of your choice. The case sensitive ID will be used in the model's URI and can't be changed later. 
@@ -93,7 +93,7 @@ You should receive a response body in the following format:
 
 # [Neural - cross lingual](#tab/crosslingual)
 
-To create a cross lingual neural voice, use the `Models_Create` operation of the custom voice API. Construct the request body according to the following instructions:
+To create a cross lingual neural voice, use the [Models_Create](/rest/api/speechapi/models/create) operation of the custom voice API. Construct the request body according to the following instructions:
 
 - Set the required `projectId` property. See [create a project](../../../../professional-voice-create-project.md).
 - Set the required `consentId` property. See [add voice talent consent](../../../../professional-voice-create-consent.md).
@@ -103,7 +103,7 @@ To create a cross lingual neural voice, use the `Models_Create` operation of the
 - Set the required `locale` property for the language that your voice speaks. The voice speaks a different language from your training data. You can specify only one target language for a voice model.
 - Optionally, set the `description` property for the voice description. The voice description can be changed later.
 
-Make an HTTP PUT request using the URI as shown in the following `Models_Create` example. 
+Make an HTTP PUT request using the URI as shown in the following [Models_Create](/rest/api/speechapi/models/create) example. 
 - Replace `YourResourceKey` with your Speech resource key.
 - Replace `YourResourceRegion` with your Speech resource region.
 - Replace `JessicaModelId` with a model ID of your choice. The case sensitive ID will be used in the model's URI and can't be changed later. 
@@ -146,7 +146,7 @@ You should receive a response body in the following format:
 
 # [Neural - multi style](#tab/multistyle)
 
-To create a multi-style neural voice, use the `Models_Create` operation of the custom voice API. Construct the request body according to the following instructions:
+To create a multi-style neural voice, use the [Models_Create](/rest/api/speechapi/models/create) operation of the custom voice API. Construct the request body according to the following instructions:
 
 - Set the required `projectId` property. See [create a project](../../../../professional-voice-create-project.md).
 - Set the required `consentId` property. See [add voice talent consent](../../../../professional-voice-create-consent.md).
@@ -161,7 +161,7 @@ To create a multi-style neural voice, use the `Models_Create` operation of the c
     - For each dictionary value, specify the ID of a training set that you [already created](../../../../professional-voice-create-training-set.md#add-a-professional-voice-training-dataset) for the same voice model. The training set must contain at least 100 utterances for each style.
 - Optionally, set the `description` property for the voice description. The voice description can be changed later.
 
-Make an HTTP PUT request using the URI as shown in the following `Models_Create` example. 
+Make an HTTP PUT request using the URI as shown in the following [Models_Create](/rest/api/speechapi/models/create) example. 
 - Replace `YourResourceKey` with your Speech resource key.
 - Replace `YourResourceRegion` with your Speech resource region.
 - Replace `JessicaModelId` with a model ID of your choice. The case sensitive ID will be used in the model's URI and can't be changed later. 
@@ -237,9 +237,9 @@ The following table summarizes the different preset styles according to differen
 
 ## Get training status
 
-To get the training status of a voice model, use the `Models_Get` operation of the custom voice API. Construct the request URI according to the following instructions:
+To get the training status of a voice model, use the [Models_Get](/rest/api/speechapi/models/get) operation of the custom voice API. Construct the request URI according to the following instructions:
 
-Make an HTTP GET request using the URI as shown in the following `Models_Get` example. 
+Make an HTTP GET request using the URI as shown in the following [Models_Get](/rest/api/speechapi/models/get) example. 
 - Replace `YourResourceKey` with your Speech resource key.
 - Replace `YourResourceRegion` with your Speech resource region.
 - Replace `JessicaModelId` if you specified a different model ID in the previous step.

articles/ai-services/speech-service/includes/release-notes/release-notes-tts.md

@@ -2,7 +2,7 @@
 author: eric-urban
 ms.service: azure-ai-speech
 ms.topic: include
-ms.date: 1/18/2024
+ms.date: 2/7/2024
 ms.author: eur
 ms.custom: references_regions
 ---
@@ -16,6 +16,10 @@ The Azure AI Speech service supports OpenAI text to speech voices in the followi
 > [!NOTE]
 > OpenAI text to speech voices are also available in [Azure OpenAI Service](../../../openai/reference.md#text-to-speech). 
 
+#### Personal voice
+
+The personal voice feature now supports `DragonLatestNeural` and `PhoenixLatestNeural` models. These new models enhance the naturalness of synthesized voices, better resembling the speech characteristics of the voice in the prompt. For more details, refer to [Integrate personal voice in your application](../../personal-voice-how-to-use.md#integrate-personal-voice-in-your-application).
+
 ### December 2023 release
 
 #### Custom voice API