Merge pull request #271299 from MicrosoftDocs/main

Publish to live, Friday 4 AM PST, 4/5

Author: ttorble

.openpublishing.redirection.iot-develop.json

@@ -574,6 +574,41 @@
       "source_path_from_root": "/articles/iot/concepts-model-repository.md",
       "redirect_url": "/azure/iot/concepts-model-discovery",
       "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/iot-develop/quickstart-send-telemetry-iot-hub.md",
+      "redirect_url": "/azure/iot/tutorial-send-telemetry-iot-hub",
+      "redirect_document_id": true      
+    },
+    {
+      "source_path_from_root": "/articles/iot-develop/tutorial-use-mqtt.md",
+      "redirect_url": "/azure/iot/tutorial-use-mqtt",
+      "redirect_document_id": true      
+    },
+    {
+      "source_path_from_root": "/articles/iot-develop/quickstart-devkit-espressif-esp32-freertos-iot-hub.md",
+      "redirect_url": "/azure/iot/tutorial-devkit-espressif-esp32-freertos-iot-hub",
+      "redirect_document_id": true      
+    },
+    {
+      "source_path_from_root": "/articles/iot-develop/concepts-iot-device-types.md",
+      "redirect_url": "/azure/iot/concepts-iot-device-types",
+      "redirect_document_id": true      
+    },
+    {
+      "source_path_from_root": "/articles/iot-develop/concepts-using-c-sdk-and-embedded-c-sdk.md",
+      "redirect_url": "/azure/iot/concepts-using-c-sdk-and-embedded-c-sdk",
+      "redirect_document_id": true      
+    },
+    {
+      "source_path_from_root": "/articles/iot-develop/concepts-manage-device-reconnections.md",
+      "redirect_url": "/azure/iot/concepts-manage-device-reconnections",
+      "redirect_document_id": true      
+    },
+    {
+      "source_path_from_root": "/articles/iot-develop/iot-device-selection.md",
+      "redirect_url": "/azure/iot/concepts-iot-device-selection",
+      "redirect_document_id": true      
     }
   ]
 }

.openpublishing.redirection.json

@@ -3924,6 +3924,16 @@
             "redirect_url": "/azure/operational-excellence/relocation-storage-account",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/kubernetes-fleet/resource-propagation.md",
+            "redirect_url": "/azure/kubernetes-fleet/concepts-resource-propagation",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/kubernetes-fleet/access-fleet-kubernetes-api.md",
+            "redirect_url": "/azure/kubernetes-fleet/quickstart-access-fleet-kubernetes-api",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/defender-for-iot/organizations/update-legacy-ot-software.md",
             "redirect_url": "/azure/defender-for-iot/organizations/update-ot-software?tabs=portal",

articles/ai-studio/toc.yml

@@ -68,6 +68,7 @@ items:
       href: how-to/create-secure-ai-hub.md
     - name: Create an Azure AI hub resource from template
       href: how-to/create-azure-ai-hub-template.md
+      displayName: ARM, bicep
     - name: Create an Azure AI project
       href: how-to/create-projects.md
     - name: Create and manage compute
@@ -91,6 +92,7 @@ items:
       items:
       - name: Add data to your project
         href: how-to/data-add.md
+        displayName: index
       - name: Use your image data with Azure OpenAI
         href: how-to/data-image-add.md
         displayName: vision, gpt, turbo
@@ -173,6 +175,7 @@ items:
     items:
     - name: Deployments overview
       href: concepts/deployments-overview.md
+      displayName: endpoint
     - name: Deploy Azure OpenAI models
       href: how-to/deploy-models-openai.md
     - name: Deploy Llama 2 family models
@@ -181,10 +184,12 @@ items:
     - name: Deploy Mistral family models
       href: how-to/deploy-models-mistral.md
       displayName: maas, as a service
-    - name: Deploy Cohere Command models
-      href: how-to/deploy-models-cohere-command.md
-    - name: Deploy Cohere Embed models
-      href: how-to/deploy-models-cohere-embed.md
+    - name: Deploy Cohere models
+      items:
+      - name: Deploy Cohere Command models
+        href: how-to/deploy-models-cohere-command.md
+      - name: Deploy Cohere Embed models
+        href: how-to/deploy-models-cohere-embed.md
     - name: Deploy open models
       href: how-to/deploy-models-open.md
       displayName: oss, open source
@@ -196,6 +201,7 @@ items:
     items:
     - name: Plan and manage costs
       href: how-to/costs-plan-manage.md
+      displayName: pricing, budget, estimate
     - name: Manage quotas
       href: how-to/quota.md
     - name: Increase rate limit

articles/aks/deploy-marketplace.md

@@ -61,10 +61,9 @@ Kubernetes application-based container offers can't be deployed on AKS for Azure
 1. You can search for an offer or publisher directly by name, or you can browse all offers. To find Kubernetes application offers, on the left side under **Categories** select **Containers**.
 
    :::image type="content" source="./media/deploy-marketplace/containers-inline.png" alt-text="Screenshot of Azure Marketplace offers in the Azure portal, with the container category on the left side highlighted." lightbox="./media/deploy-marketplace/containers.png":::
-
+   
    > [!IMPORTANT]
-   > The **Containers** category includes both Kubernetes applications and standalone container images. This walkthrough is specific to Kubernetes applications. If you find that the steps to deploy an offer differ in some way, you're most likely trying to deploy a container image-based offer instead of a Kubernetes application-based offer.
-
+   > The **Containers** category includes Kubernetes applications. This walkthrough is specific to Kubernetes applications. 
 1. You'll see several Kubernetes application offers displayed on the page. To view all of the Kubernetes application offers, select **See more**.
 
    :::image type="content" source="./media/deploy-marketplace/see-more-inline.png" alt-text="Screenshot of Azure Marketplace K8s offers in the Azure portal. 'See More' is highlighted." lightbox="./media/deploy-marketplace/see-more.png":::
@@ -183,6 +182,7 @@ If you experience issues, see the [troubleshooting checklist for failed deployme
 
 - Learn more about [exploring and analyzing costs][billing].
 - Learn more about [deploying a Kubernetes application programmatically using Azure CLI](/azure/aks/deploy-application-az-cli)
+
 - Learn more about [deploying a Kubernetes application through an ARM template](/azure/aks/deploy-application-template)
 
 <!-- LINKS -->

articles/api-management/validate-azure-ad-token-policy.md

@@ -73,7 +73,7 @@ The `validate-azure-ad-token` policy enforces the existence and validity of a JS
 | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
 | audiences           | Contains a list of acceptable audience claims that can be present on the token. If multiple `audience` values are present, then each value is tried until either all are exhausted (in which case validation fails) or until one succeeds. Policy expressions are allowed.                                                                    | No       |
 | backend-application-ids | Contains a list of acceptable backend application IDs.  This is only required in advanced cases for the configuration of options and can generally be removed. Policy expressions aren't allowed. | No |
-| client-application-ids | Contains a list of acceptable client application IDs. If multiple `application-id` elements are present, then each value is tried until either all are exhausted (in which case validation fails) or until one succeeds. If a client application ID isn't provided, one or more `audience` claims should be specified. Policy expressions aren't allowed. | No |
+| client-application-ids | Contains a list of acceptable client application IDs. If multiple `application-id` elements are present, then each value is tried until either all are exhausted (in which case validation fails) or until one succeeds. If a client application ID isn't provided, one or more `audience` claims should be specified. Policy expressions aren't allowed. | Yes |
 | required-claims     | Contains a list of `claim` elements for claim values expected to be present on the token for it to be considered valid. When the `match` attribute is set to `all`, every claim value in the policy must be present in the token for validation to succeed. When the `match` attribute is set to `any`, at least one claim must be present in the token for validation to succeed. Policy expressions are allowed. | No       |
 
 ### claim attributes