Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into abac-env

Author: pauljewellmsft

.openpublishing.redirection.json

@@ -5707,7 +5707,77 @@
         },
         {
             "source_path_from_root": "/articles/industrial-iot/overview-what-is-industrial-iot-platform.md",
-            "redirect_url": "/azure/industrial-iot/overview-what-is-industrial-iot",
+            "redirect_url": "https://github.com/Azure/Industrial-IoT/blob/main/readme.md",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/industrial-iot/index.yml",
+            "redirect_url": "https://github.com/Azure/Industrial-IoT/blob/main/readme.md",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/industrial-iot/industrial-iot-platform-versions.md",
+            "redirect_url": "https://github.com/Azure/Industrial-IoT/blob/main/readme.md",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/industrial-iot/overview-what-is-industrial-iot.md",
+            "redirect_url": "https://github.com/Azure/Industrial-IoT/blob/main/readme.md",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/industrial-iot/overview-what-is-opc-publisher.md",
+            "redirect_url": "https://github.com/Azure/Industrial-IoT/blob/main/readme.md",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/industrial-iot/reference-command-line-arguments.md",
+            "redirect_url": "https://github.com/Azure/Industrial-IoT/blob/main/readme.md",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/industrial-iot/reference-opc-publisher-telemetry-format.md",
+            "redirect_url": "https://github.com/Azure/Industrial-IoT/blob/main/readme.md",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/industrial-iot/tutorial-configure-industrial-iot-components.md",
+            "redirect_url": "https://github.com/Azure/Industrial-IoT/blob/main/readme.md",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/industrial-iot/tutorial-data-explorer-import.md",
+            "redirect_url": "https://github.com/Azure/Industrial-IoT/blob/main/readme.md",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/industrial-iot/tutorial-deploy-industrial-iot-platform.md",
+            "redirect_url": "https://github.com/Azure/Industrial-IoT/blob/main/readme.md",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/industrial-iot/tutorial-industrial-iot-azure-data-explorer.md",
+            "redirect_url": "https://github.com/Azure/Industrial-IoT/blob/main/readme.md",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/industrial-iot/tutorial-publisher-configure-opc-publisher.md",
+            "redirect_url": "https://github.com/Azure/Industrial-IoT/blob/main/readme.md",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/industrial-iot/tutorial-publisher-deploy-opc-publisher-standalone.md",
+            "redirect_url": "https://github.com/Azure/Industrial-IoT/blob/main/readme.md",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/industrial-iot/tutorial-publisher-performance-memory-tuning-opc-publisher.md",
+            "redirect_url": "https://github.com/Azure/Industrial-IoT/blob/main/readme.md",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/industrial-iot/tutorial-visualize-data-time-series-insights.md",
+            "redirect_url": "https://github.com/Azure/Industrial-IoT/blob/main/readme.md",
             "redirect_document_id": false
         },
         {
@@ -10798,6 +10868,13 @@
             "source_path_from_root": "/articles/azure-health-insights/response-info.md",
             "redirect_url": "/azure/azure-health-insights/overview",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/networking/disaster-recovery-dns-traffic-manager.md",
+            "redirect_url": "/azure/reliability/reliability-traffic-manager",
+            "redirect_document_id": false
         }
+
+        
     ]
 }

articles/active-directory-b2c/media/tutorial-create-tenant/create-a-resource.png

@@ -520,6 +520,14 @@ sections:
 
           Yes. The labeling experience from Studio is open sourced in the [Toolkit repo](https://github.com/microsoft/Form-Recognizer-Toolkit)
 
+      - question: |
+          Why am I receiving 'Form Recognizer Not Found' error when opening my custom project?
+        answer: |
+          Your Document Intelligence resource bound to this custom project may have been deleted or moved to another resource group.  There are two ways to resolve this issue:
+          
+            - Re-create the Document Intelligence resource under the same subscription/resource group with the same name.
+          
+            - Re-create a custom project with the migrated Document Intelligence resource and specify the very same storage account.
 
   - name: Containers
     questions:

articles/active-directory-b2c/media/tutorial-create-tenant/portal-02-create-tenant.png

@@ -88,7 +88,7 @@ See [model versions](../concepts/model-versions.md) to learn about how Azure Ope
 > Version `0314` of `gpt-4` and `gpt-4-32k` will be retired no earlier than July 5, 2024.  Version `0613` of `gpt-4` and `gpt-4-32k` will be retired no earlier than September 30, 2024.  See [model updates](../how-to/working-with-models.md#model-updates) for model upgrade behavior.
 
 
-GPT-4 version 0125-preview is an updated version of the GPT-4 Turbo preview previously released as version 1106-preview.  GPT-4 versio 0125-preview completes tasks such as code generation more completely compared to gpt-4-1106-preview.  Because of this, depending on the task, customers may find that GPT-4-0125-preview generates more output compared to the gpt-4-1106-preview.  We recommend customers compare the outputs of the new model.  GPT-4-0125-preview also addresses bugs in gpt-4-1106-preview with UTF-8 handling for non-English languages. 
+GPT-4 version 0125-preview is an updated version of the GPT-4 Turbo preview previously released as version 1106-preview.  GPT-4 version 0125-preview completes tasks such as code generation more completely compared to gpt-4-1106-preview.  Because of this, depending on the task, customers may find that GPT-4-0125-preview generates more output compared to the gpt-4-1106-preview.  We recommend customers compare the outputs of the new model.  GPT-4-0125-preview also addresses bugs in gpt-4-1106-preview with UTF-8 handling for non-English languages. 
 
 > [!IMPORTANT]
 >
@@ -144,7 +144,7 @@ GPT-3.5 Turbo version 0301 is the first version of the model released.  Version
 See [model versions](../concepts/model-versions.md) to learn about how Azure OpenAI Service handles model version upgrades, and [working with models](../how-to/working-with-models.md) to learn how to view and configure the model version settings of your GPT-3.5 Turbo deployments.
 
 > [!NOTE]
-> Version `0613` of `gpt-35-turbo` and `gpt-35-turbo-16k` will be retired on June 13, 2024. Version `0301` of `gpt-35-turbo` will be retired on July 5, 2024.  See [model updates](../how-to/working-with-models.md#model-updates) for model upgrade behavior.
+> Version `0613` of `gpt-35-turbo` and `gpt-35-turbo-16k` will be retired no earlier than June 13, 2024. Version `0301` of `gpt-35-turbo` will be retired no earlier than July 5, 2024.  See [model updates](../how-to/working-with-models.md#model-updates) for model upgrade behavior.
 
 ### GPT-3.5-Turbo model availability
 

articles/ai-services/document-intelligence/faq.yml

@@ -18,6 +18,12 @@ recommendations: false
 
 ## February 2024
 
+### GPT-4-0125-preview model available
+
+The `gpt-4` model version `0125-preview` is now available on Azure OpenAI Service in the East US, North Central US, and South Central US regions.  Customers with deployments of `gpt-4` version `1106-preview` will be automatically upgraded to `0125-preview` in the coming weeks.  
+
+For information on model regional availability and upgrades refer to the [models page](./concepts/models.md).
+
 ### Assistants API public preview
 
 Azure OpenAI now supports the API that powers OpenAI's GPTs. Azure OpenAI Assistants (Preview) allows you to create AI assistants tailored to your needs through custom instructions and advanced tools like code interpreter, and custom functions. To learn more, see:

articles/ai-services/openai/concepts/models.md

@@ -48,6 +48,11 @@ Here's an overview of the steps to create a custom neural voice in Speech Studio
 
 You can tune, adjust, and use your custom voice, similarly as you would use a prebuilt neural voice. Convert text into speech in real-time, or generate audio content offline with text input. You use the [REST API](./rest-text-to-speech.md), the [Speech SDK](./get-started-text-to-speech.md), or the [Speech Studio](https://speech.microsoft.com/audiocontentcreation).
 
+> [!TIP]
+> You can also use the Speech SDK and custom voice REST API to train a custom neural voice.
+> 
+> Check out the code samples in the [Speech SDK repository on GitHub](https://github.com/Azure-Samples/cognitive-services-speech-sdk/blob/master/samples/custom-voice/README.md) to see how to use personal voice in your application.
+
 The style and the characteristics of the trained voice model depend on the style and the quality of the recordings from the voice talent used for training. However, you can make several adjustments by using [SSML (Speech Synthesis Markup Language)](./speech-synthesis-markup.md?tabs=csharp) when you make the API calls to your voice model to generate synthetic speech. SSML is the markup language used to communicate with the text to speech service to convert text into audio. The adjustments you can make include change of pitch, rate, intonation, and pronunciation correction. If the voice model is built with multiple styles, you can also use SSML to switch the styles.
 
 ## Components sequence

articles/ai-services/openai/whats-new.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/custom-neural-voice.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-consent/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