Merge branch 'MicrosoftDocs:main' into krkutser-latam-launch-feb13

Author: krkutser

.openpublishing.publish.config.json

@@ -1215,17 +1215,18 @@
   ".openpublishing.redirection.container-service.json",
   ".openpublishing.redirection.defender-for-cloud.json",
   ".openpublishing.redirection.defender-for-iot.json",
+  ".openpublishing.redirection.devops-project.json",
   ".openpublishing.redirection.guidance.json",
   ".openpublishing.redirection.iot-hub-device-update.json",
   ".openpublishing.redirection.key-vault.json",
   ".openpublishing.redirection.machine-configuration.json",
   ".openpublishing.redirection.marketplace.json",
   ".openpublishing.redirection.openshift.json",
   ".openpublishing.redirection.security-benchmark.json",
+  ".openpublishing.redirection.sentinel.json",
+  ".openpublishing.redirection.spring-cloud.json",
   ".openpublishing.redirection.sql-database.json",
   ".openpublishing.redirection.virtual-desktop.json",
-  ".openpublishing.redirection.devops-project.json",
-  ".openpublishing.redirection.sentinel.json",
   "articles/active-directory-b2c/.openpublishing.redirection.active-directory-b2c.json",
   "articles/ai-services/.openpublishing.redirection.ai-services-from-applied.json",
   "articles/ai-services/.openpublishing.redirection.ai-services-from-cog.json",
@@ -1290,7 +1291,6 @@
   "articles/site-recovery/.openpublishing.redirection.site-recovery.json",
   "articles/spatial-anchors/.openpublishing.redirection.spatial-anchors.json",
   "articles/spring-apps/.openpublishing.redirection.spring-apps.json",
-  "articles/spring-cloud/.openpublishing.redirection.spring-cloud.json",
   "articles/static-web-apps/.openpublishing.redirection.static-web-apps.json",
   "articles/storsimple/.openpublishing.redirection.storsimple.json",
   "articles/stream-analytics/.openpublishing.redirection.stream-analytics.json",

articles/spring-cloud/.openpublishing.redirection.spring-cloud.json renamed to .openpublishing.redirection.spring-cloud.json

@@ -185,6 +185,11 @@
             "redirect_url": "/azure/ai-services/language-service/conversational-language-understanding/how-to/migrate-from-luis",
             "redirect_document_id": false
           },
+          {
+            "source_path_from_root": "/articles/ai-services/luis/luis-migration-api-v3.md",
+            "redirect_url": "/azure/ai-services/language-service/conversational-language-understanding/how-to/migrate-from-luis",
+            "redirect_document_id": false
+          },
           {
             "source_path_from_root": "/articles/ai-services/custom-vision-service/update-application-to-3.0-sdk.md",
             "redirect_url": "/azure/ai-services/custom-vision-service/overview",

articles/ai-services/.openpublishing.redirection.applied-ai-services.json

@@ -38,8 +38,6 @@ The Language Understanding service is accessed from an Azure resource you need t
 * Use the **authoring** resource for training to create, edit, train, and publish.
 * Use the **prediction** for runtime to send user's text and receive a prediction.
 
-Learn about the [V3 prediction endpoint](luis-migration-api-v3.md).
-
 Use [Azure AI services sample code](https://github.com/Azure-Samples/cognitive-services-quickstart-code) to learn and use the most common tasks.
 
 ### REST specifications

articles/ai-services/LUIS/developer-reference-resource.md

@@ -23,7 +23,7 @@ You can edit your application name, and description. You can copy your App ID. T
 
 1. Sign into the [LUIS portal](https://www.luis.ai).
 1. Select an app from the **My apps** list.
-.
+
 1. Select **Manage** from the top navigation bar, then **Settings** from the left navigation bar.
 
 > [!div class="mx-imgBorder"]

articles/ai-services/LUIS/how-to-application-settings-portal.md

@@ -82,7 +82,7 @@ When a LUIS app uses the prebuilt [datetimeV2](luis-reference-prebuilt-datetimev
 
 ### V3 prediction API to alter timezone
 
-In V3, the `datetimeReference` determines the timezone offset. Learn more about [V3 predictions](luis-migration-api-v3.md#v3-post-body).
+In V3, the `datetimeReference` determines the timezone offset.
 
 ### V2 prediction API to alter timezone
 The timezone is corrected by adding the user's timezone to the endpoint using the `timezoneOffset` parameter based on the API version. The value of the parameter should be the positive or negative number, in minutes, to alter the time.

articles/ai-services/LUIS/luis-concept-data-alteration.md

@@ -67,7 +67,7 @@ The primary data is the top scoring **intent name**. The endpoint response is:
 }
 ```
 
-Learn more about the [V3 prediction endpoint](luis-migration-api-v3.md).
+
 
 * * *
 
@@ -127,7 +127,7 @@ Set the querystring parameter, `show-all-intents=true`. The endpoint response is
 }
 ```
 
-Learn more about the [V3 prediction endpoint](luis-migration-api-v3.md).
+
 
 * * *
 
@@ -190,7 +190,7 @@ If you add prebuilt domains, the intent name indicates the domain, such as `Util
 }
 ```
 
-Learn more about the [V3 prediction endpoint](luis-migration-api-v3.md).
+
 
 * * *
 

articles/ai-services/LUIS/luis-concept-data-extraction.md

@@ -74,7 +74,7 @@ This workflow should:
 * Train and publish the LUIS app version.
 
   > [!NOTE]
-  > As explained in [Running tests in an automated build workflow](luis-concept-devops-testing.md#running-tests-in-an-automated-build-workflow) you must publish the LUIS app version under test so that tools such as NLU.DevOps can access it. LUIS only supports two named publication slots, *staging* and *production* for a LUIS app, but you can also [publish a version directly](https://github.com/microsoft/botframework-cli/blob/master/packages/luis/README.md#bf-luisapplicationpublish) and [query by version](./luis-migration-api-v3.md#changes-by-slot-name-and-version-name). Use direct version publishing in your automation workflows to avoid being limited to using the named publishing slots.
+  > As explained in [Running tests in an automated build workflow](luis-concept-devops-testing.md#running-tests-in-an-automated-build-workflow) you must publish the LUIS app version under test so that tools such as NLU.DevOps can access it. LUIS only supports two named publication slots, *staging* and *production* for a LUIS app, but you can also [publish a version directly](https://github.com/microsoft/botframework-cli/blob/master/packages/luis/README.md#bf-luisapplicationpublish) and query by version. Use direct version publishing in your automation workflows to avoid being limited to using the named publishing slots.
 
 * Run all the [unit tests](luis-concept-devops-testing.md).
 

articles/ai-services/LUIS/luis-concept-devops-automation.md

@@ -256,7 +256,7 @@ More [examples](luis-container-configuration.md#example-docker-run-commands) of
 
 ## Endpoint APIs supported by the container
 
-Both V2 and [V3](luis-migration-api-v3.md) versions of the API are available with the container.
+Both V2 and V3 versions of the API are available with the container.
 
 ## Query the container's prediction endpoint
 

articles/ai-services/LUIS/luis-container-howto.md

@@ -252,7 +252,7 @@ To create a Prediction resource from the LUIS portal
     }
     ```
 
-Learn more about the [V3 prediction endpoint](luis-migration-api-v3.md).
+
 
 
 ## Clean up resources