Merge pull request #279347 from MicrosoftDocs/main

6/26/2024 AM Publish

Author: Taojunshen

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

@@ -4,7 +4,7 @@ titleSuffix: Azure OpenAI
 description: Learn about the different model capabilities that are available with Azure OpenAI.
 ms.service: azure-ai-openai
 ms.topic: conceptual
-ms.date: 06/19/2024
+ms.date: 06/25/2024
 ms.custom: references_regions, build-2023, build-2023-dataai, refefences_regions
 manager: nitinme
 author: mrbullwinkle #ChrisHMSFT
@@ -297,18 +297,18 @@ The following Embeddings models are available with [Azure Government](/azure/azu
 
 For Assistants you need a combination of a supported model, and a supported region. Certain tools and capabilities require the latest models. The following models are available in the Assistants API, SDK, Azure AI Studio and Azure OpenAI Studio. The following table is for pay-as-you-go. For information on Provisioned Throughput Unit (PTU) availability, see [provisioned throughput](./provisioned-throughput.md). 
 
-| Region | `gpt-35-turbo (0613)` | `gpt-35-turbo (1106)`| `fine tuned gpt-3.5-turbo-0125` | `gpt-4 (0613)` | `gpt-4 (1106)` | `gpt-4 (0125)` |
-|-----|---|---|---|---|---|---|
-| Australia East | ✅ | ✅ | | ✅ |✅ | |
-| East US  | ✅ | | | | | ✅ |
-| East US 2 | ✅ |  | ✅ | ✅ |✅ | |
-| France Central  | ✅ | ✅ | | ✅ |✅ |  |
-| Japan East | ✅ |  | | | | | 
-| Norway East | |  | | | ✅ |  |
-| Sweden Central  | ✅ |✅ | ✅ |✅ |✅| |
-| UK South | ✅  | ✅ | | | ✅ | ✅ |  
-| West US |  | ✅ | | | ✅ | | 
-| West US 3 |  |  | | |✅ | | 
+| Region | `gpt-35-turbo (0613)` | `gpt-35-turbo (1106)`| `fine tuned gpt-3.5-turbo-0125` | `gpt-4 (0613)` | `gpt-4 (1106)` | `gpt-4 (0125)` | `gpt-4o (2024-05-13)` |
+|-----|:---:|:---:|:---:|:---:|:---:|:---:|:---:|
+| Australia East | ✅ | ✅ | | ✅ |✅ | | |
+| East US  | ✅ | | | | | ✅ | ✅ |
+| East US 2 | ✅ |  | ✅ | ✅ |✅ | |✅|
+| France Central  | ✅ | ✅ | | ✅ |✅ |  | |
+| Japan East | ✅ |  | | | | | |
+| Norway East | |  | | | ✅ |  | |
+| Sweden Central | ✅ |✅ | ✅ |✅ |✅| |✅|
+| UK South | ✅  | ✅ | | | ✅ | ✅ |  |
+| West US |  | ✅ | | | ✅ | |✅|
+| West US 3 |  |  | | |✅ | |✅|
 
 ## Model retirement
 

articles/ai-services/speech-service/includes/cognitive-services-speech-service-rest-auth.md

@@ -13,13 +13,15 @@ Each request requires an authorization header. This table illustrates which head
 | `Ocp-Apim-Subscription-Key` | Yes | Yes |
 | `Authorization: Bearer` | Yes | Yes |
 
-When you're using the `Ocp-Apim-Subscription-Key` header, you're only required to provide your resource key. For example:
+When you're using the `Ocp-Apim-Subscription-Key` header, only your resource key must be provided. For example:
 
 ```http
 'Ocp-Apim-Subscription-Key': 'YOUR_SUBSCRIPTION_KEY'
 ```
 
-When you're using the `Authorization: Bearer` header, you're required to make a request to the `issueToken` endpoint. In this request, you exchange your resource key for an access token that's valid for 10 minutes.
+When you're using the `Authorization: Bearer` header, you need to make a request to the `issueToken` endpoint. In this request, you exchange your resource key for an access token that's valid for 10 minutes.
+
+Another option is to use Microsoft Entra authentication that also uses the `Authorization: Bearer` header, but with a token issued via Microsoft Entra ID. See [Use Microsoft Entra authentication](#use-microsoft-entra-authentication).
 
 ### How to get an access token
 
@@ -154,3 +156,42 @@ Connection: Keep-Alive
 
 // Message body here...
 ```
+
+### Use Microsoft Entra authentication
+
+To use Microsoft Entra authentication with the Speech to text REST API for short audio, you need to create an access token.
+The steps to obtain the access token consisting of Resource ID and  Microsoft Entra access token are the same as when using the Speech SDK.
+Follow the steps here [Use Microsoft Entra authentication](../how-to-configure-azure-ad-auth.md)
+
+> [!div class="checklist"]
+>
+> - Create a Speech resource
+> - Configure the Speech resource for Microsoft Entra authentication
+> - Get a Microsoft Entra access token
+> - Get the Speech resource ID
+
+After the resource ID and the Microsoft Entra access token were obtained, the actual access token can be constructed following this format:
+```http
+"aad#YOUR_RESOURCE_ID#YOUR_MICROSOFT_ENTRA_ACCESS_TOKEN";
+```
+You need to include the "aad#" prefix and the "#" (hash) separator between resource ID and the access token.
+
+Here's a sample HTTP request to the Speech to text REST API for short audio:
+
+```http
+POST /cognitiveservices/v1 HTTP/1.1
+Authorization: Bearer YOUR_ACCESS_TOKEN
+Host: westus.stt.speech.microsoft.com
+Content-type: application/ssml+xml
+Content-Length: 199
+Connection: Keep-Alive
+
+// Message body here...
+```
+
+To learn more about Microsoft Entra access tokens, including token lifetime, visit [Access tokens in the Microsoft identity platform](/azure/active-directory/develop/access-tokens).
+
+
+
+
+

articles/aks/long-term-support.md

@@ -127,9 +127,6 @@ To carry out an in-place upgrade to the latest LTS version, you need to specify
 ```azurecli
 az aks upgrade --resource-group myResourceGroup --name myAKSCluster --kubernetes-version 1.32.2
 ```
-> [!NOTE]
->If you use any programming/scripting logic to list and select a minor version of Kubernetes before creating clusters with the `ListKubernetesVersions` API, note that starting from Kubernetes v1.27, the API returns `SupportPlan` as `[KubernetesOfficial, AKSLongTermSupport]`. Please ensure you update any logic to exclude `AKSLongTermSupport` versions to avoid any breaks and choose `KubernetesOfficial` support plan versions.  Otherwise, if LTS is indeed your path forward please first opt-into the Premium tier and the `AKSLongTermSupport` support plan versions from the `ListKubernetesVersions` API before creating clusters.
-
 > [!NOTE]
 > The next Long Term Support Version after 1.27 is to be determined. However Customers will get a minimum 6 months of overlap between 1.27 LTS and the next LTS version to plan upgrades.  
 > Kubernetes 1.32.2 is used as an example version in this article. Check the [AKS release tracker](release-tracker.md) for available Kubernetes releases.

articles/automation/quickstarts/dsc-configuration.md

@@ -14,6 +14,9 @@ ms.custom: mvc, mode-other
 > [!CAUTION]
 > This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly. For more information, see the [CentOS End Of Life guidance](~/articles/virtual-machines/workloads/centos/centos-end-of-life.md).
 
+> [!NOTE]
+> Before you enable Azure Automation DSC, we would like you to know that a newer version of DSC is now generally available, managed by a feature of Azure Policy named [Azure Machine Configuration](../../governance/machine-configuration/overview.md). The Azure Machine Configuration service combines features of DSC Extension, Azure Automation State Configuration, and the most commonly requested features from customer feedback. Azure Machine Configuration also includes hybrid machine support through [Arc-enabled servers](../../azure-arc/servers/overview.md).
+
 By enabling Azure Automation State Configuration, you can manage and monitor the configurations of your Windows and Linux servers using Desired State Configuration (DSC). Configurations that drift from a desired configuration can be identified or auto-corrected. This quickstart steps through enabling an Azure Linux VM and deploying a LAMP stack using Azure Automation State Configuration.
 
 ## Prerequisites

articles/azure-arc/kubernetes/extensions-release.md

@@ -116,7 +116,18 @@ For more information, see [Tutorial: Deploy applications using GitOps with Flux
 The most recent version of the Flux v2 extension and the two previous versions (N-2) are supported. We generally recommend that you use the most recent version of the extension.
 
 > [!IMPORTANT]
-> Eventually, a major version update (v2.x.x) for the `microsoft.flux` extension will be released. When this happens, clusters won't be auto-upgraded to this version, since [auto-upgrade is only supported for minor version releases](extensions.md#upgrade-extension-instance). If you're still using an older API version when the next major version is released, you'll need to update your manifests to the latest API versions, perform any necessary testing, then upgrade your extension manually. For more information about the new API versions (breaking changes) and how to update your manifests, see the [Flux v2 release notes](https://github.com/fluxcd/flux2/releases/tag/v2.0.0).
+> The [Flux v2.3.0 release](https://fluxcd.io/blog/2024/05/flux-v2.3.0/) includes API changes to the HelmRelease and HelmChart APIs, with deprecated fields removed. An upcoming minor version update of Microsoft's Flux extension will include these changes, consistent with the upstream OSS Flux project.
+>
+> The [HelmRelease](https://fluxcd.io/flux/components/helm/helmreleases/) kind will be promoted from `v2beta1` to `v2` (GA). The `v2` API is backwards compatible with `v2beta1`, with the exception of these deprecated fields, which will be removed:
+>
+> - `.spec.chart.spec.valuesFile`: replaced by `.spec.chart.spec.valuesFiles`
+> - `.spec.postRenderers.kustomize.patchesJson6902`: replaced by `.spec.postRenderers.kustomize.patches`
+> - `.spec.postRenderers.kustomize.patchesStrategicMerge`: replaced by `.spec.postRenderers.kustomize.patches`
+> - `.status.lastAppliedRevision`: replaced by `.status.history.chartVersion`
+>
+> The [HelmChart](https://fluxcd.io/flux/components/source/helmcharts/) kind will be promoted from `v1beta2` to `v1` (GA). The `v1` API is backwards compatible with `v1beta2`, with the exception of the `.spec.valuesFile` field, which will be replaced by `.spec.valuesFiles`.
+>
+> To avoid issues due to breaking changes, we recommend updating your deployments by July 22, 2024, so that they stop using the fields that will be removed and use the replacement fields instead. These new fields are already available in the current version of the APIs.
 
 > [!NOTE]
 > When a new version of the `microsoft.flux` extension is released, it may take several days for the new version to become available in all regions.

articles/azure-arc/servers/prepare-extended-security-updates.md

@@ -39,10 +39,7 @@ Other Azure services through Azure Arc-enabled servers are available as well, wi
 
 * [Microsoft Defender for Cloud](../../defender-for-cloud/defender-for-cloud-introduction.md) - As part of the cloud security posture management (CSPM) pillar, it provides server protections through [Microsoft Defender for Servers](../../defender-for-cloud/plan-defender-for-servers.md) to help protect you from various cyber threats and vulnerabilities.
 * [Microsoft Sentinel](scenario-onboard-azure-sentinel.md) - Collect security-related events and correlate them with other data sources.
-
-    >[!NOTE]
-    >Activation of ESU is planned for the third quarter of 2023. Using Azure services such as Azure Update Manager and Azure Policy to support managing ESU-eligible Windows Server 2012/2012 R2 machines are also planned for the third quarter.
-
+   
 ## Prepare delivery of ESUs
 
 Plan and prepare to onboard your machines to Azure Arc-enabled servers through the installation of the [Azure Connected Machine agent](agent-overview.md) (version 1.34 or higher) to establish a connection to Azure. Windows Server 2012 Extended Security Updates supports Windows Server 2012 and R2 Standard and Datacenter editions. Windows Server 2012 Storage is not supported.

articles/azure-monitor/app/opentelemetry-enable.md

@@ -218,7 +218,7 @@ Point the Java virtual machine (JVM) to the jar file by adding `-javaagent:"path
 > If you develop a Spring Boot application, you can optionally replace the JVM argument by a programmatic configuration. For more information, see [Using Azure Monitor Application Insights with Spring Boot](./java-spring-boot.md).
 
 
-##### [Java-Native](#tab/java-native)
+##### [Java Native](#tab/java-native)
 
 Several automatic instrumentations are enabled through configuration changes; no code changes are required
 

articles/azure-monitor/insights/code-optimizations-troubleshoot.md

@@ -0,0 +1,58 @@
+---
+title: Troubleshoot Code Optimizations (Preview)
+description: Learn how to use Application Insights Code Optimizations on Azure. View a checklist of troubleshooting steps.
+author: rkahng 
+ms.author: ryankahng
+editor: v-jsitser
+ms.reviewer: hannahhunter, v-leedennis
+ms.service: azure-monitor
+ms.topic: troubleshooting
+ms.date: 06/25/2024
+ms.custom: sap:Availability Tests
+---
+
+# Troubleshoot Code Optimizations (Preview)
+
+This article provides troubleshooting steps and information to use Application Insights Code Optimizations for Microsoft Azure.
+
+## Troubleshooting checklist
+
+### Step 1: View a video about Code Optimizations setup
+
+View the following demonstration video to learn how to set up Code Optimizations correctly.
+
+> [!VIDEO https://www.youtube-nocookie.com/embed/vbi9YQgIgC8]
+
+### Step 2: Make sure that your app is connected to an Application Insights resource
+
+[Create an Application Insights resource](/azure/azure-monitor/app/create-workspace-resource) and verify that it's connected to the correct app.
+
+### Step 3: Verify that Application Insights Profiler is enabled
+
+[Enable Application Insights Profiler](/azure/azure-monitor/profiler/profiler-overview).
+
+### Step 4: Verify that Application Insights Profiler is collecting profiles
+
+To make sure that profiles are uploaded to your Application Insights resource, follow these steps：
+
+1. In the [Azure portal](https://portal.azure.com), search for and select **Application Insights**.
+1. In the list of Application Insights resources, select the name of your resource.
+1. In the navigation pane of your Application Insights resource, locate the **Investigate** heading, and then select **Performance**.
+1. On the **Performance** page of your Application Insights resource, select **Profiler**:
+
+   :::image type="content" source="./media/code-optimizations-troubleshoot/performance-page.png" alt-text="Azure portal screenshot that shows how to navigate to the Application Insights Profiler.":::
+
+1. On the **Application Insights Profiler** page, view the **Recent profiling sessions** section.
+
+   :::image type="content" source="./media/code-optimizations-troubleshoot/profiling-sessions.png" alt-text="Azure portal screenshot of the Application Insights Profiler page." lightbox="./media/code-optimizations-troubleshoot/profiling-sessions.png":::
+
+   > [!NOTE]  
+   > If you don't see any profiling sessions, see [Troubleshoot Application Insights Profiler](../profiler/profiler-troubleshooting.md).
+
+### Step 5: Regularly check the Profiler
+
+After you successfully complete the previous steps, keep checking the Profiler for insights. Meanwhile, the service continues to analyze your profiles and provide insights as soon as it detects any issues in your code. After you enable the Application Insights Profiler, several hours might be required for you to generate profiles and for the service to analyze them. If the service detects no issues in your code, a message appears that confirms that no insights were found.
+
+## Contact us for help
+
+If you have questions or need help, [create a support request](https://ms.portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview?DMC=troubleshoot), or ask [Azure community support](https://azure.microsoft.com/support/community). You can also submit product feedback to [Azure feedback community](https://feedback.azure.com/d365community).

articles/azure-monitor/insights/code-optimizations.md

@@ -6,7 +6,7 @@ ms.service: azure-monitor
 ms.subservice: optimization-insights
 author: hhunter-ms
 ms.author: hannahhunter
-ms.date: 03/08/2024
+ms.date: 06/25/2024
 ms.reviewer: ryankahng
 ---
 
@@ -73,4 +73,4 @@ Get started with Code Optimizations by enabling the following features on your a
 - [Application Insights](../app/create-workspace-resource.md)
 - [Application Insights Profiler](../profiler/profiler-overview.md)
 
-Running into issues? Check the [Troubleshooting guide](/troubleshoot/azure/azure-monitor/app-insights/code-optimizations-troubleshooting)
+Running into issues? Check the [Troubleshooting guide](./code-optimizations-troubleshoot.md)