Merge pull request #272022 from rcdun/release-preview-voice-protect

[Operator Call Protection] Dirty PR for release branch merge conflict with upstream main

Author: Court72

articles/ai-services/translator/containers/configuration.md

@@ -75,10 +75,6 @@ If you need to configure an HTTP proxy for making outbound requests, use these t
 | Name | Data type | Description |
 |--|--|--|
 |HTTPS_PROXY|string|The proxy to use, for example, `https://proxy:8888`<br>`<proxy-url>`|
-|HTTP_PROXY_CREDS|string|Any credentials needed to authenticate against the proxy, for example, `username:password`. This value **must be in lower-case**. |
-|`<proxy-user>`|string|The user for the proxy.|
-|`<proxy-password>`|string|The password associated with `<proxy-user>` for the proxy.|
-||||
 
 ```bash
 docker run --rm -it -p 5000:5000 \
@@ -89,7 +85,6 @@ Eula=accept \
 Billing=<endpoint> \
 ApiKey=<api-key> \
 HTTPS_PROXY=<proxy-url> \
-HTTP_PROXY_CREDS=<proxy-user>:<proxy-password> \
 ```
 
 ## Logging settings

articles/ai-services/translator/containers/install-run.md

@@ -29,9 +29,9 @@ In this article, learn how to install and run the Translator container online wi
 
 * **Text Translation**. Translate the contextual meaning of words or phrases from supported `source` to supported `target` language in real time. For more information, *see* [**Container: translate text**](translator-container-supported-parameters.md).
 
-* **Text Transliteration**. Convert text from one language script or writing system to another language script or writing system in real time. For more information, *see* [Container: transliterate text](transliterate-text-parameters.md).
+* **🆕 Text Transliteration**. Convert text from one language script or writing system to another language script or writing system in real time. For more information, *see* [Container: transliterate text](transliterate-text-parameters.md).
 
-* **Document translation**. Synchronously translate documents while preserving structure and format in real time. For more information, *see* [Container:translate documents](translate-document-parameters.md).
+* **🆕 Document translation (preview)**. Synchronously translate documents while preserving structure and format in real time. For more information, *see* [Container:translate documents](translate-document-parameters.md).
 
 ## Prerequisites
 

articles/ai-services/translator/containers/translate-document-parameters.md

@@ -12,7 +12,12 @@ ms.date: 04/08/2024
 ms.author: lajanuar
 ---
 
-# Container: Translate Documents
+# Container: Translate Documents (preview)
+
+> [!IMPORTANT]
+>
+> * Azure AI Translator public preview releases provide early access to features that are in active development.
+> * Features, approaches, and processes may change, prior to General Availability (GA), based on user feedback.
 
 **Translate document with source language specified**.
 

articles/ai-services/translator/toc.yml

@@ -187,7 +187,7 @@ items:
     href: containers/overview.md
   - name: Install and run containers
     displayName: docker,docker-run,run,pull,swagger,c#,python,import,cpu,EULA,billing
-    href: containers/translator-how-to-install-container.md
+    href: containers/install-run.md
   - name: Container configuration guide
     displayName: docker,docker-run,billing,settings,key,logging,EULA,telemetry,proxy
     href: containers/configuration.md
@@ -199,10 +199,10 @@ items:
       - name: "Container: Translate text"
         displayName: docker,docker-run,run,pull,swagger,c#,python,import,cpu,EULA,billing
         href: containers/translate-text-parameters.md
-      - name: "Container: Transliterate text"
+      - name: "🆕 Container: Transliterate text"
         displayName: docker,docker-run,run,pull,swagger,c#,python,import,cpu,EULA,billing
         href: containers/transliterate-text-parameters.md
-      - name: "Container: Translate documents"
+      - name: "🆕 Container: Translate documents (preview)"
         displayName: docker,docker-run,run,pull,swagger,c#,python,import,cpu,EULA,billing
         href: containers/translate-document-parameters.md
   - name: Translator container FAQ

articles/aks/media/howto-deploy-java-wls-app/marketplace-search-results.png

@@ -9,7 +9,7 @@ ms.author: nickoman
 
 # Supported Kubernetes versions in Azure Kubernetes Service (AKS)
 
-The Kubernetes community releases minor versions roughly every three months. Recently, the Kubernetes community has [increased the support window for each version from nine months to one year](https://kubernetes.io/blog/2020/08/31/kubernetes-1-19-feature-one-year-support/), starting with version 1.19.
+The Kubernetes community [releases minor versions](https://kubernetes.io/releases/) roughly every four months. 
 
 Minor version releases include new features and improvements. Patch releases are more frequent (sometimes weekly) and are intended for critical bug fixes within a minor version. Patch releases include fixes for security vulnerabilities or major bugs.
 
@@ -21,8 +21,8 @@ Kubernetes uses the standard [Semantic Versioning](https://semver.org/) versioni
 [major].[minor].[patch]
 
 Examples:
-  1.17.7
-  1.17.8
+  1.29.2
+  1.29.1
 ```
 
 Each number in the version indicates general compatibility with the previous version:
@@ -31,7 +31,7 @@ Each number in the version indicates general compatibility with the previous ver
 * **Minor versions** change when functionality updates are made that are backwards compatible to the other minor releases.
 * **Patch versions** change when backwards-compatible bug fixes are made.
 
-Aim to run the latest patch release of the minor version you're running. For example, if your production cluster is on **`1.17.7`**, **`1.17.8`** is the latest available patch version available for the *1.17* series. You should upgrade to **`1.17.8`** as soon as possible to ensure your cluster is fully patched and supported.
+Aim to run the latest patch release of the minor version you're running. For example, if your production cluster is on **`1.29.1`** and **`1.29.2`** is the latest available patch version available for the *1.29* minor version, you should upgrade to **`1.29.2`** as soon as possible to ensure your cluster is fully patched and supported.
 
 ## AKS Kubernetes release calendar
 
@@ -73,7 +73,7 @@ Note the following important changes before you upgrade to any of the available
 > [!NOTE]
 > Alias minor version requires Azure CLI version 2.37 or above as well as API version 20220401 or above. Use `az upgrade` to install the latest version of the CLI.
 
-AKS allows you to create a cluster without specifying the exact patch version. When you create a cluster without designating a patch, the cluster runs the minor version's latest GA patch. For example, if you create a cluster with **`1.21`**, your cluster runs **`1.21.7`**, which is the latest GA patch version of *1.21*. If you want to upgrade your patch version in the same minor version, please use [auto-upgrade](./auto-upgrade-cluster.md).
+AKS allows you to create a cluster without specifying the exact patch version. When you create a cluster without designating a patch, the cluster runs the minor version's latest GA patch. For example, if you create a cluster with **`1.29`** and **`1.29.2`** is the latest GA'd patch available, your cluster will be created with **`1.29.2`**. If you want to upgrade your patch version in the same minor version, please use [auto-upgrade](./auto-upgrade-cluster.md).
 
 To see what patch you're on, run the `az aks show --resource-group myResourceGroup --name myAKSCluster` command. The `currentKubernetesVersion` property shows the whole Kubernetes version.
 
@@ -83,7 +83,7 @@ To see what patch you're on, run the `az aks show --resource-group myResourceGro
   "autoScalerProfile": null,
   "autoUpgradeProfile": null,
   "azurePortalFqdn": "myaksclust-myresourcegroup.portal.hcp.eastus.azmk8s.io",
-  "currentKubernetesVersion": "1.21.7",
+  "currentKubernetesVersion": "1.29.2",
 }
 ```
 
@@ -102,41 +102,38 @@ AKS provides platform support only for one GA minor version of Kubernetes after
 > [!NOTE]
 > AKS uses safe deployment practices which involve gradual region deployment. This means it might take up to 10 business days for a new release or a new version to be available in all regions.
 
-The supported window of Kubernetes versions on AKS is known as "N-2": (N (Latest release) - 2 (minor versions)), and ".letter" is representative of patch versions.
+The supported window of Kubernetes minor versions on AKS is known as "N-2", where N refers to the latest release, meaning that two previous minor releases are also supported.
 
-For example, if AKS introduces *1.17.a* today, support is provided for the following versions:
+For example, on the day that AKS introduces version 1.29, support is provided for the following versions:
 
-New minor version    |    Supported Version List
+New minor version    |    Supported Minor Version List
 -----------------    |    ----------------------
-1.17.a               |    1.17.a, 1.17.b, 1.16.c, 1.16.d, 1.15.e, 1.15.f
+1.29                 |    1.29, 1.28, 1.27
 
-When a new minor version is introduced, the oldest minor version and patch releases supported are deprecated and removed. For example, let's say the current supported version list is:
+When a new minor version is introduced, the oldest minor version is deprecated and removed. For example, let's say the current supported minor version list is:
 
 ```
-1.17.a
-1.17.b
-1.16.c
-1.16.d
-1.15.e
-1.15.f
+1.29
+1.28
+1.27
 ```
 
-When AKS releases 1.18.\*, all the 1.15.\* versions go out of support 30 days later.
+When AKS releases 1.30, all the 1.27 versions go out of support 30 days later.
 
 AKS also supports a maximum of two **patch** releases of a given minor version. For example, given the following supported versions:
 
 ```
 Current Supported Version List
 ------------------------------
-1.17.8, 1.17.7, 1.16.10, 1.16.9
+1.29.2, 1.29.1, 1.28.7, 1.28.6, 1.27.11, 1.27.10
 ```
 
-If AKS releases `1.17.9` and `1.16.11`, the oldest patch versions are deprecated and removed, and the supported version list becomes:
+If AKS releases `1.29.3` and `1.28.8`, the oldest patch versions are deprecated and removed, and the supported version list becomes:
 
 ```
 New Supported Version List
 ----------------------
-1.17.*9*, 1.17.*8*, 1.16.*11*, 1.16.*10*
+1.29.3, 1.29.2, 1.28.8, 1.28.7, 1.27.11, 1.27.10
 ```
 
 ## Platform support policy
@@ -178,7 +175,7 @@ This table outlines support guidelines for Community Support compared to Platfor
 
 You can use one minor version older or newer of `kubectl` relative to your *kube-apiserver* version, consistent with the [Kubernetes support policy for kubectl](https://kubernetes.io/docs/setup/release/version-skew-policy/#kubectl).
 
-For example, if your *kube-apiserver* is at *1.17*, then you can use versions *1.16* to *1.18* of `kubectl` with that *kube-apiserver*.
+For example, if your *kube-apiserver* is at *1.28*, then you can use versions *1.27* to *1.29* of `kubectl` with that *kube-apiserver*.
 
 To install or update `kubectl` to the latest version, run:
 
@@ -229,7 +226,7 @@ Specific patch releases might be skipped or rollout accelerated, depending on th
 
 ## Azure portal and CLI versions
 
-When you deploy an AKS cluster with Azure portal, Azure CLI, Azure PowerShell, the cluster defaults to the N-1 minor version and latest patch. For example, if AKS supports *1.17.a*, *1.17.b*, *1.16.c*, *1.16.d*, *1.15.e*, and *1.15.f*, the default version selected is *1.16.c*.
+When you deploy an AKS cluster with Azure portal, Azure CLI, Azure PowerShell, the cluster defaults to the N-1 minor version and latest patch. For example, if AKS supports *1.29.2*, *1.29.1*, *1.28.7*, *1.28.6*, *1.27.11*, and *1.27.10*, the default version selected is *1.28.7*.
 
 ### [Azure CLI](#tab/azure-cli)
 
@@ -265,8 +262,8 @@ Starting with Kubernetes 1.19, the [open source community has expanded support t
 
 If you're on the *n-3* version or older, it means you're outside of support and will be asked to upgrade. When your upgrade from version n-3 to n-2 succeeds, you're back within our support policies. For example:
 
-* If the oldest supported AKS version is *1.15.a* and you're on *1.14.b* or older, you're outside of support.
-* When you successfully upgrade from *1.14.b* to *1.15.a* or higher, you're back within our support policies.
+* If the oldest supported AKS minor version is *1.27* and you're on *1.26* or older, you're outside of support.
+* When you successfully upgrade from *1.26* to *1.27* or higher, you're back within our support policies.
 
 Downgrades aren't supported.
 
@@ -302,16 +299,16 @@ The [version skew policy](https://kubernetes.io/releases/version-skew-policy/) n
 
 When you upgrade a supported AKS cluster, Kubernetes minor versions can't be skipped. Kubernetes control planes [version skew policy](https://kubernetes.io/releases/version-skew-policy/) doesn't support minor version skipping. For example, upgrades between:
 
-* *1.12.x* -> *1.13.x*: allowed.
-* *1.13.x* -> *1.14.x*: allowed.
-* *1.12.x* -> *1.14.x*: not allowed.
+* *1.28.x* -> *1.29.x*: allowed.
+* *1.27.x* -> *1.28.x*: allowed.
+* *1.27.x* -> *1.29.x*: not allowed.
 
-To upgrade from *1.12.x* -> *1.14.x*:
+To upgrade from *1.27.x* -> *1.29.x*:
 
-1. Upgrade from *1.12.x* -> *1.13.x*.
-2. Upgrade from *1.13.x* -> *1.14.x*.
+1. Upgrade from *1.27.x* -> *1.28.x*.
+2. Upgrade from *1.28.x* -> *1.29.x*.
 
-Skipping multiple versions can only be done when upgrading from an unsupported version back into the minimum supported version. For example, you can upgrade from an unsupported *1.10.x* to a supported *1.15.x* if *1.15* is the minimum supported minor version.
+Skipping multiple versions can only be done when upgrading from an unsupported version back into the minimum supported version. For example, you can upgrade from an unsupported *1.25.x* to a supported *1.27.x* if *1.27* is the minimum supported minor version.
 
 When performing an upgrade from an _unsupported version_ that skips two or more minor versions, the upgrade is performed without any guarantee of functionality and is excluded from the service-level agreements and limited warranty.Clusters running _unsupported version_ has the flexibility of decoupling control plane upgrades with node pool upgrades. However if your version is significantly out of date, we recommend that you re-create the cluster.
 

articles/aks/supported-kubernetes-versions.md

@@ -11,7 +11,7 @@ ms.author: danlep
 
 # Workspaces - breaking changes (June 2024)
 
-[!INCLUDE [api-management-availability-premium](../../../includes/api-management-availability-premium.md)]
+[!INCLUDE [api-management-availability-premium-dev-standard](../../../includes/api-management-availability-premium-dev-standard.md)]
 
 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. 
 
@@ -70,4 +70,4 @@ If you have questions, get answers from community experts in [Microsoft Q&A](htt
 
 ## Related content
 
-See all [upcoming breaking changes and feature retirements](overview.md).
+See all [upcoming breaking changes and feature retirements](overview.md).

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

@@ -262,7 +262,7 @@
                   href: change-tracking/extension-version-details.md
             - name: Supported regions
               href: change-tracking/region-mappings-monitoring-agent.md
-            - name: Enable change tracking from portal
+            - name: Enable change tracking and inventory
               href: change-tracking/enable-vms-monitoring-agent.md
             - name: Manage change tracking and inventory
               href: change-tracking/manage-change-tracking-monitoring-agent.md

articles/automation/TOC.yml

@@ -3,7 +3,7 @@ title: Enable Azure Automation Change Tracking for single machine and multiple m
 description: This article tells how to enable the Change Tracking feature for single machine and multiple machines at scale from the Azure portal.
 services: automation
 ms.subservice: change-inventory-management
-ms.date: 06/28/2023
+ms.date: 04/10/2024
 ms.topic: conceptual
 ---
 
@@ -23,7 +23,7 @@ This article describes how you can enable [Change Tracking and Inventory](overvi
 
 This section provides detailed procedure on how you can enable change tracking on a single VM and multiple VMs.
 
-#### [For a single VM](#tab/singlevm)
+#### [Single Azure VM -portal](#tab/singlevm)
 
 1. Sign in to [Azure portal](https://portal.azure.com) and navigate to **Virtual machines**.
 
@@ -41,7 +41,7 @@ This section provides detailed procedure on how you can enable change tracking o
    :::image type="content" source="media/enable-vms-monitoring-agent/deployment-success-inline.png" alt-text="Screenshot showing the notification of deployment." lightbox="media/enable-vms-monitoring-agent/deployment-success-expanded.png":::
 
 
-#### [For multiple VMs](#tab/multiplevms)
+#### [Multiple Azure VMs - portal](#tab/multiplevms)
 
 1. Sign in to [Azure portal](https://portal.azure.com) and navigate to **Virtual machines**.
 
@@ -64,6 +64,40 @@ This section provides detailed procedure on how you can enable change tracking o
 
 1. Select **Enable** to initiate the deployment.
 1. A notification appears on the top right corner of the screen indicating the status of deployment.
+
+#### [Arc-enabled VMs - portal/CLI](#tab/arcvms)
+
+To enable the Change Tracking and Inventory on Arc-enabled servers, ensure that the custom Change Tracking Data collection rule is associated to the Arc-enabled VMs. 
+
+Follow these steps to associate the data collection rule to the Arc-enabled VMs:
+
+1. [Create Change Tracking Data collection rule](#create-data-collection-rule).
+1. Sign in to [Azure portal](https://portal.azure.com) and go to **Monitor** and under **Settings**, select **Data Collection Rules**.
+      
+   :::image type="content" source="media/enable-vms-monitoring-agent/monitor-menu-data-collection-rules.png" alt-text="Screenshot showing the menu option to access data collection rules from Azure Monitor." lightbox="media/enable-vms-monitoring-agent/monitor-menu-data-collection-rules.png":::
+
+1. Select the data collection rule that you have created in Step 1 from the listing page.
+1. In the data collection rule page, under **Configurations**, select **Resources** and then select **Add**.
+    
+   :::image type="content" source="media/enable-vms-monitoring-agent/select-resources.png" alt-text="Screenshot showing the menu option to select resources from the data collection rule page." lightbox="media/enable-vms-monitoring-agent/select-resources.png":::
+    
+1. In the **Select a scope**, from **Resource types**, select *Machines-Azure Arc* that is connected to the subscription and then select **Apply** to associate the *ctdcr* created in Step 1 to the Arc-enabled machine and it will also install the Azure Monitoring Agent extension.
+    
+   :::image type="content" source="media/enable-vms-monitoring-agent/scope-select-arc-machines.png" alt-text="Screenshot showing the selection of Arc-enabled machines from the scope." lightbox="media/enable-vms-monitoring-agent/scope-select-arc-machines.png":::
+    
+1. Install the Change Tracking extension as per the OS type for the Arc-enabled VM.
+    
+   **Linux**
+       
+   ```azurecli
+   az connectedmachine extension create  --name ChangeTracking-Linux  --publisher Microsoft.Azure.ChangeTrackingAndInventory --type-handler-version 2.20  --type ChangeTracking-Linux  --machine-name XYZ --resource-group XYZ-RG  --location X --enable-auto-upgrade
+   ```
+
+   **Windows**
+
+   ```azurecli
+   az connectedmachine extension create  --name ChangeTracking-windows  --publisher Microsoft.Azure.ChangeTrackingAndInventory --type-handler-version 2.20  --type ChangeTracking-Windows  --machine-name XYZ --resource-group XYZ-RG  --location X --enable-auto-upgrade
+   ```   
 --- 
 
 >[!NOTE]