Merge pull request #268507 from AbhishekMallick-MS/release-files-vaulted-backup

Dirty PR

Author: rmca14

.openpublishing.redirection.app-service.json

@@ -2659,6 +2659,21 @@
             "source_path": "articles/app-service/quickstart-dotnet-framework.md",
             "redirect_url": "/azure/app-service/quickstart-dotnetcore?tabs=netframework48",
             "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/app-service/quickstart-arm-template-uiex.md",
+            "redirect_url": "/azure/app-service/quickstart-arm-template",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/app-service/quickstart-dotnetcore-uiex.md",
+            "redirect_url": "/azure/app-service/quickstart-dotnetcore",
+            "redirect_document_id": true
+        },
+        {
+            "source_path": "articles/app-service/quickstart-java-uiex.md",
+            "redirect_url": "/azure/app-service/quickstart-java",
+            "redirect_document_id": true
         }
     ]
 }

.openpublishing.redirection.json

@@ -6750,6 +6750,11 @@
             "redirect_url": "/azure/scheduler/migrate-from-scheduler-to-logic-apps",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/search/cognitive-search-tutorial-blob-python.md",
+            "redirect_url": "/azure/search/samples-python",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/search/semantic-ranking.md",
             "redirect_url": "/azure/search/semantic-search-overview",

articles/ai-services/cognitive-services-virtual-networks.md

@@ -59,6 +59,7 @@ Virtual networks are supported in [regions where Azure AI services are available
 > - `AzureResourceManager`
 > - `CognitiveServicesManagement`
 > - `CognitiveServicesFrontEnd`
+> - `Storage` (Speech Studio only)
 
 ## Change the default network access rule
 

articles/ai-services/speech-service/includes/language-support/multilingual-voices.md

@@ -17,4 +17,4 @@ ms.author: v-baolianzou
 
 <sup>2</sup> The neural voice is a multilingual voice in Azure AI Speech. All multilingual voices (except `en-US-JennyMultilingualNeural`) can speak in the language in default locale of the input text without [using SSML](../../speech-synthesis-markup-voice.md#adjust-speaking-languages). However, you can still use the `<lang xml:lang>` element to adjust the speaking accent of each language to set preferred accent such as British accent (`en-GB`) for English. Check the [full list](https://speech.microsoft.com/portal/voicegallery) of supported locales through SSML.
 
-<sup>3</sup> The OpenAI text to speech voices in Azure AI Speech are in public preview and only available in North Central US (`northcentralus`) and Sweden Central (`swedencentral`).
+<sup>3</sup> The OpenAI text to speech voices in Azure AI Speech are in public preview and only available in North Central US (`northcentralus`) and Sweden Central (`swedencentral`). Locales not listed for OpenAI voices aren't supported by design.

articles/aks/howto-deploy-java-liberty-app.md

@@ -59,23 +59,23 @@ The following steps guide you to create a Liberty runtime on AKS. After completi
    1. Create a new resource group. Because resource groups must be unique within a subscription, pick a unique name. An easy way to have unique names is to use a combination of your initials, today's date, and some identifier. For example, `ejb0913-java-liberty-project-rg`.
    1. Select *East US* as **Region**.
 
-   Create environment variables in your shell for the resource group names for the cluster and the database.
-
-   ### [Bash](#tab/in-bash)
-
-   ```bash
-   export RESOURCE_GROUP_NAME=<your-resource-group-name>
-   export DB_RESOURCE_GROUP_NAME=<your-resource-group-name>
-   ```
-
-   ### [PowerShell](#tab/in-powershell)
-
-   ```powershell
-   $Env:RESOURCE_GROUP_NAME="<your-resource-group-name>"
-   $Env:DB_RESOURCE_GROUP_NAME="<your-resource-group-name>"
-   ```
-
-   ---
+    Create environment variables in your shell for the resource group names for the cluster and the database.
+ 
+    ### [Bash](#tab/in-bash)
+ 
+    ```bash
+    export RESOURCE_GROUP_NAME=<your-resource-group-name>
+    export DB_RESOURCE_GROUP_NAME=<your-resource-group-name>
+    ```
+ 
+    ### [PowerShell](#tab/in-powershell)
+ 
+    ```powershell
+    $Env:RESOURCE_GROUP_NAME="<your-resource-group-name>"
+    $Env:DB_RESOURCE_GROUP_NAME="<your-resource-group-name>"
+    ```
+ 
+    ---
 
 1. Select **Next**, enter the **AKS** pane. This pane allows you to select an existing AKS cluster and Azure Container Registry (ACR), instead of causing the deployment to create a new one, if desired. This capability enables you to use the sidecar pattern, as shown in the [Azure architecture center](/azure/architecture/patterns/sidecar). You can also adjust the settings for the size and number of the virtual machines in the AKS node pool. The remaining values do not need to be changed from their default values.
 

articles/aks/use-managed-identity.md

@@ -5,7 +5,7 @@ ms.topic: article
 ms.custom:
   - devx-track-azurecli
   - ignite-2023
-ms.date: 02/27/2024
+ms.date: 03/07/2024
 ---
 
 # Use a managed identity in Azure Kubernetes Service (AKS)
@@ -24,12 +24,12 @@ When you deploy an AKS cluster, a system-assigned managed identity is automatica
 
 AKS doesn't automatically create a [service principal](kubernetes-service-principal.md), so you have to create one. Clusters that use a service principal eventually expire, and the service principal must be renewed to avoid impacting cluster authentication with the identity. Managing service principals adds complexity, so it's easier to use managed identities instead. The same permission requirements apply for both service principals and managed identities. Managed identities use certificate-based authentication. Each managed identity's credentials have an expiration of *90 days* and are rolled after *45 days*.
 
-AKS uses both system-assigned and user-assigned managed identity types, and these identities are immutable.
+AKS uses both system-assigned and user-assigned managed identity types, and these identities are immutable. These identity types shouldn't be confused with a [Microsoft Entra Workload identity][workload-identity-overview], which is intended for use by an application running on a pod.
 
 > [!IMPORTANT]
 > The open source [Microsoft Entra pod-managed identity][entra-id-pod-managed-identity] (preview) in Azure Kubernetes Service was deprecated on 10/24/2022, and the project archived in Sept. 2023. For more information, see the [deprecation notice](https://github.com/Azure/aad-pod-identity#-announcement). The AKS Managed add-on begins deprecation in Sept. 2024.
 >
-> We recommend you first review [Microsoft Entra Workload ID][workload-identity-overview] overview. This authentication method replaces Microsoft Entra pod-managed identity (preview) and is the recommended method.
+> We recommend you first review [Microsoft Entra Workload ID][workload-identity-overview] overview. Entra Workload ID authentication replaces Microsoft Entra pod-managed identity (preview) and is the recommended method to enable an application running on a pod to authenticate itself against other Azure services that support it.
 
 ## Before you begin
 
@@ -67,7 +67,7 @@ AKS uses several managed identities for built-in services and add-ons.
 | Add-on | omsagent | Used to send AKS metrics to Azure Monitor. | Monitoring Metrics Publisher role | No
 | Add-on | Virtual-Node (ACIConnector) | Manages required network resources for Azure Container Instances (ACI). | Contributor role for node resource group | No
 | Add-on | Cost analysis | Used to gather cost allocation data | |
-| OSS project | Microsoft Entra ID-pod-identity | Enables applications to access cloud resources securely with Microsoft Entra ID. | N/A | Steps to grant permission at [Microsoft Entra Pod Identity Role Assignment configuration](./use-azure-ad-pod-identity.md).
+| Workload identity | Microsoft Entra workload ID | Enables applications to access cloud resources securely with Microsoft Entra workload ID. | N/A | No |
 
 ## Enable managed identities on a new AKS cluster
 
@@ -103,7 +103,7 @@ To update your existing AKS cluster that's using a service principal to use a sy
 az aks update -g myResourceGroup -n myManagedCluster --enable-managed-identity
 ```
 
-After updating your cluster, the control plane and pods use the managed identity. kubelet continues using a service principal until you upgrade your agentpool. You can use the `az aks nodepool upgrade --resource-group myResourceGroup --cluster-name myAKSCluster --name mynodepool --node-image-only` command on your nodes to update to a managed identity. A node pool upgrade causes downtime for your AKS cluster as the nodes in the node pools are cordoned/drained and reimaged.
+After updating your cluster, the control plane and pods use the managed identity. Kubelet continues using a service principal until you upgrade your agentpool. You can use the `az aks nodepool upgrade --resource-group myResourceGroup --cluster-name myAKSCluster --name mynodepool --node-image-only` command on your nodes to update to a managed identity. A node pool upgrade causes downtime for your AKS cluster as the nodes in the node pools are cordoned/drained and reimaged.
 
 > [!NOTE]
 >

articles/api-management/TOC.yml

@@ -639,6 +639,8 @@
       href: breaking-changes/self-hosted-gateway-v0-v1-retirement-oct-2023.md
     - name: Deprecated (legacy) developer portal (October 2023)
       href: breaking-changes/legacy-portal-retirement-oct-2023.md
+    - name: Workspaces breaking changes (June 2024)
+      href: breaking-changes/workspaces-breaking-changes-june-2024.md
     - name: stv1 compute platform retirement (August 2024)
       href: breaking-changes/stv1-platform-retirement-august-2024.md
     - name: ADAL-based identity provider retirement (September 2025)

articles/api-management/breaking-changes/overview.md

@@ -2,12 +2,12 @@
 title: Upcoming Breaking Changes in Azure API Management | Microsoft Docs
 description: A list of all the upcoming breaking changes for Azure API Management
 services: api-management
-author: adrianhall
+author: dlepow
 
 ms.service: api-management
 ms.topic: reference
-ms.date: 03/15/2023
-ms.author: adhal
+ms.date: 01/25/2024
+ms.author: danlep
 ---
 
 # Upcoming breaking changes
@@ -22,6 +22,7 @@ The following table lists all the upcoming breaking changes and feature retireme
 | [API version retirements][api2023] | September 30, 2023 |
 | [Deprecated (legacy) portal retirement][devportal2023] | October 31, 2023 |
 | [Self-hosted gateway v0/v1 retirement][shgwv0v1] | October 1, 2023 |
+| [Workspaces breaking changes][workspaces2024] | June 14, 2024 |
 | [stv1 platform retirement][stv12024] | August 31, 2024 |
 | [ADAL-based Microsoft Entra ID or Azure AD B2C identity provider retirement][msal2025] | September 30, 2025 |
 | [CAPTCHA endpoint update][captcha2025] | September 30, 2025 |
@@ -36,3 +37,4 @@ The following table lists all the upcoming breaking changes and feature retireme
 [msal2025]: ./identity-provider-adal-retirement-sep-2025.md
 [captcha2025]: ./captcha-endpoint-change-sep-2025.md
 [metrics2023]: ./metrics-retirement-aug-2023.md
+[workspaces2024]: ./workspaces-breaking-changes-june-2024.md

articles/api-management/breaking-changes/workspaces-breaking-changes-june-2024.md

@@ -0,0 +1,71 @@
+---
+title: Azure API Management workspaces - breaking changes (June 2024) | Microsoft Docs
+description: Azure API Management is updating the workspaces (preview) with breaking changes. If your service uses workspaces, you may need to update workspace configurations.
+services: api-management 
+author: dlepow
+ms.service: api-management
+ms.topic: reference
+ms.date: 03/07/2024
+ms.author: danlep
+---
+
+# Workspaces - breaking changes (June 2024)
+
+On 14 June 2024, as part of our development of [workspaces](../workspaces-overview.md) (preview) in Azure API Management, we're introducing several breaking changes. 
+
+These changes will have no effect on the availability of your API Management service. However, you may have to take action to continue using full workspaces functionality beyond 14 June 2024.
+
+## Is my service affected by these changes?
+
+Your service may be affected by these changes if you configured workspaces (preview) in your API Management instance. This feature was introduced in the **Premium**, **Standard**, and **Developer** tiers.
+
+## Breaking changes
+
+Review the following breaking changes to determine if you need to take action:
+
+### Change to supported service tiers
+
+The following service tiers will no longer support workspaces: **Standard** and **Developer**. Workspaces will be available in the **Premium** tier. 
+
+For availability in the v2 tiers, see [Azure API Management v2 tiers](../v2-service-tiers-overview.md).
+
+### Changes to support for assigning service-level entities in workspaces
+
+The following assignments of workspace entities to service-level entities will no longer be supported:
+
+* Assign workspace APIs to service-level products
+* Assign workspace APIs to service-level tags
+* Assign workspace products to service-level tags
+* Assign service-level groups to workspace products for visibility controls
+
+    > [!NOTE]
+    > The built-in Guests and Developer groups will continue to be available in workspaces.
+
+### Changes to supported context objects
+
+The following `context` objects will no longer be supported in workspace policies or in the all-APIs policy on the service level:
+
+* `context.Api.Workspace`
+* `context.Product.Workspace`
+
+The `context.Workspace` object can be used instead.
+
+
+> [!NOTE]
+> You can continue to reference users from the service level in the `context` object in workspace-level policies.
+
+## What is the deadline for the change?
+
+The breaking changes are effective 14 June 2024. We strongly recommend that you make all required changes to the configuration of workspaces before then.
+
+## Help and support
+
+If you have questions, get answers from community experts in [Microsoft Q&A](https://aka.ms/apim/azureqa/change/captcha-2022). If you have a support plan and you need technical help, create a [support request](https://portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview).
+
+## More information
+
+* [Workspaces overview](../workspaces-overview.md)
+
+## Related content
+
+See all [upcoming breaking changes and feature retirements](overview.md).

articles/api-management/v2-service-tiers-overview.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: api-management
 ms.topic: conceptual
-ms.date: 10/02/2023
+ms.date: 01/31/2024
 ms.author: danlep
 ms.custom: references_regions
 ---
@@ -85,7 +85,7 @@ Currently, the following API Management capabilities are unavailable in the v2 t
 * Built-in analytics
 * Inbound connection using a private endpoint
 * Upgrade to v2 tiers from v1 tiers 
-* Workspaces
+* Workspaces (*Standard v2*)
 
 **Developer portal**
 * Delegation of user registration and product subscription