Merge pull request #280347 from MicrosoftDocs/main

Publish to Live Tuesday 4AM PST 7/9

Author: PMEds28

.openpublishing.redirection.json

@@ -2125,6 +2125,11 @@
             "redirect_url": "/azure/devops/pipelines/get-started-designer?toc=%2Fazure%2Fdevops%2Fuser-guide%2Ftoc.json&bc=%2Fazure%2Fdevops%2Fuser-guide%2Fbreadcrumb%2Ftoc.json&tabs=new-nav",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/devtest/index.md",
+            "redirect_url": "/azure/devtest/offer/",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/devtest-labs/devtest-lab-add-artifact-repo.md",
             "redirect_url": "/azure/devtest-labs/add-artifact-repository",

articles/ai-services/openai/concepts/model-retirements.md

@@ -80,7 +80,7 @@ These models are currently available for use in Azure OpenAI Service.
 
 ## Deprecated models
 
-These models were deprecated on July 6, 2023 and will be retired on June 14, 2024. These models are no longer available for new deployments. Deployments created before July 6, 2023 remain available to customers until June 14, 2024. We recommend customers migrate their applications to deployments of replacement models before the June 14, 2024 retirement.
+These models were deprecated on July 6, 2023 and were retired on June 14, 2024. These models are no longer available for new deployments. Deployments created before July 6, 2023 remain available to customers until June 14, 2024. We recommend customers migrate their applications to deployments of replacement models before the June 14, 2024 retirement.
 
 If you're an existing customer looking for information about these models, see [Legacy models](./legacy-models.md).
 
@@ -144,4 +144,4 @@ The default version of `gpt-4` and `gpt-3-32k` was updated from `0314` to `0613`
 
 ### July 6, 2023
 
-We announced the deprecation of models with upcoming retirement on July 5, 2024.
+We announced the deprecation of models with upcoming retirement on July 5, 2024.

articles/ai-services/speech-service/includes/language-support/personal-voice.md

@@ -10,18 +10,14 @@ ms.author: eur
 
 |Locale (BCP-47)|Language|
 |-----------------|--------------------------------|
-|`af-ZA`<sup>1</sup>|Afrikaans (South Africa)|
 |`am-ET`|Amharic (Ethiopia)|
 |`ar-EG`|Arabic (Egypt)|
 |`ar-SA`|Arabic (Saudi Arabia)|
-|`az-AZ`<sup>1</sup>|Azerbaijani (Latin, Azerbaijan)|
 |`bg-BG`|Bulgarian (Bulgaria)|
-|`bn-BD`<sup>1</sup>|Bangla (Bangladesh)
 |`bn-IN`|Bengali (India)|
 |`bs-BA`|Bosnian (Bosnia and Herzegovina)|
 |`ca-ES`|Catalan|
 |`cs-CZ`|Czech (Czechia)|
-|`cy-GB`<sup>1</sup>|Welsh (United Kingdom)|
 |`da-DK`|Danish (Denmark)|
 |`de-AT`|German (Austria)|
 |`de-CH`|German (Switzerland)|
@@ -37,39 +33,24 @@ ms.author: eur
 |`es-MX`|Spanish (Mexico)|
 |`et-EE`|Estonian (Estonia)|
 |`eu-ES`|Basque|
-|`fa-IR`<sup>1</sup>|Persian (Iran)|
 |`fi-FI`|Finnish (Finland)|
 |`fil-PH`|Filipino (Philippines)|
 |`fr-BE`|French (Belgium)|
 |`fr-CA`|French (Canada)|
 |`fr-CH`|French (Switzerland)|
 |`fr-FR`|French (France)|
-|`ga-IE`<sup>1</sup>|Irish (Ireland)|
 |`gl-ES`|Galician|
 |`he-IL`|Hebrew (Israel)|
 |`hi-IN`|Hindi (India)|
 |`hr-HR`|Croatian (Croatia)|
 |`hu-HU`|Hungarian (Hungary)|
-|`hy-AM`<sup>1</sup>|Armenian (Armenia)|
 |`id-ID`|Indonesian (Indonesia)|
-|`is-IS`<sup>1</sup>|Icelandic (Iceland)|
 |`it-IT`|Italian (Italy)|
 |`ja-JP`|Japanese (Japan)|
 |`jv-ID`|Javanese (Latin, Indonesia)|
-|`ka-GE`<sup>1</sup>|Georgian (Georgia)|
-|`kk-KZ`<sup>1</sup>|Kazakh (Kazakhstan)|
-|`km-KH`<sup>1</sup>|Khmer (Cambodia)|
-|`kn-IN`<sup>1</sup>|Kannada (India)|
 |`ko-KR`|Korean (Korea)|
-|`lo-LA`<sup>1</sup>|Lao (Laos)|
-|`lt-LT`<sup>1</sup>|Lithuanian (Lithuania)|
-|`lv-LV`<sup>1</sup>|Latvian (Latvia)|
 |`mk-MK`|Macedonian (North Macedonia)|
-|`ml-IN`<sup>1</sup>|Malayalam (India)|
-|`mn-MN`<sup>1</sup>|Mongolian (Mongolia)|
 |`ms-MY`|Malay (Malaysia)|
-|`mt-MT`<sup>1</sup>|Maltese (Malta)|
-|`my-MM`<sup>1</sup>|Burmese (Myanmar)|
 |`nb-NO`|Norwegian Bokmål (Norway)|
 |`ne-NP`|Nepali (Nepal)|
 |`nl-BE`|Dutch (Belgium)|
@@ -80,26 +61,17 @@ ms.author: eur
 |`pt-PT`|Portuguese (Portugal)|
 |`ro-RO`|Romanian (Romania)|
 |`ru-RU`|Russian (Russia)|
-|`si-LK`<sup>1</sup>|Sinhala (Sri Lanka)|
 |`sk-SK`| Slovak (Slovakia)|
 |`sl-SI`|Slovenian (Slovenia)|
-|`so-SO`<sup>1</sup>|Somali (Somalia)|
-|`sq-AL`<sup>1</sup>|Albanian (Albania)|
-|`sr-RS`<sup>1</sup>|Serbian (Cyrillic, Serbia)|
-|`su-ID`<sup>1</sup>|Sundanese (Indonesia)|
 |`sv-SE`|Swedish (Sweden)|
 |`sw-KE`|Swahili (Kenya)|
 |`ta-IN`|Tamil (India)|
 |`te-IN`|Telugu (India)|
 |`th-TH`|Thai (Thailand)|
 |`tr-TR`|Turkish (Türkiye)|
 |`uk-UA`|Ukrainian (Ukraine)|
-|`ur-PK`<sup>1</sup>|Urdu (Pakistan)|
-|`uz-UZ`<sup>1</sup>|Uzbek (Latin, Uzbekistan)|
 |`vi-VN`|Vietnamese (Vietnam)|
 |`zh-CN`|Chinese (Mandarin, Simplified)|
 |`zh-HK`|Chinese (Cantonese, Traditional)|
 |`zh-TW`|Chinese (Taiwanese Mandarin, Traditional)|
 |`zu-ZA`|Zulu (South Africa)|
-
-<sup>1</sup> The language is in public preview for personal voice.

articles/azure-monitor/logs/summary-rules.md

@@ -98,7 +98,7 @@ Instead of logging hundreds of similar entries within an hour, the destination t
 
 ## Pricing model
 
-There is no direct cost for Summary rules, and you only pay for the query on the source table and the results ingestion to the destination table:
+There is no additional cost for Summary rules. You only pay for the query and the ingestion of results to the destination table, based on the table plan used in query:
 
 | Source table plan | Query cost | Summary results ingestion cost |
 | --- | --- | --- |

articles/connectors/connectors-native-reqres.md

@@ -463,7 +463,9 @@ When you use the Request trigger to receive inbound requests, you can model the
 
 ## Test your workflow
 
-To test your workflow, send an HTTP request to the generated URL. For example, you can use a tool such as [Postman](https://www.getpostman.com/) to send the HTTP request. For more information about the trigger's underlying JSON definition and how to call this trigger, see these topics, [Request trigger type](../logic-apps/logic-apps-workflow-actions-triggers.md#request-trigger) and [Call, trigger, or nest workflows with HTTP endpoints in Azure Logic Apps](../logic-apps/logic-apps-http-endpoint.md).
+To test your workflow, send an HTTP request to the generated URL. For example, you can use local tools or apps such as [Insomnia](https://insomnia.rest/) or [Bruno](https://www.usebruno.com/) to send the HTTP request.
+
+For more information about the trigger's underlying JSON definition and how to call this trigger, see these topics, [Request trigger type](../logic-apps/logic-apps-workflow-actions-triggers.md#request-trigger) and [Call, trigger, or nest workflows with HTTP endpoints in Azure Logic Apps](../logic-apps/logic-apps-http-endpoint.md).
 
 ## Security and authentication
 

articles/defender-for-iot/organizations/release-notes.md

@@ -116,6 +116,8 @@ To understand whether a feature is supported in your sensor version, check the r
 This version includes the following updates and enhancements:
 
 - [Malicious URL path alert](whats-new.md#malicious-url-path-alert)
+- The following CVE is resolved in this version:
+  - CVE-2024-38089
 
 ### Version 24.1.3
 

articles/defender-for-iot/organizations/whats-new.md

@@ -15,27 +15,41 @@ Features released earlier than nine months ago are described in the [What's new
 > [!NOTE]
 > Noted features listed below are in PREVIEW. The [Azure Preview Supplemental Terms](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include other legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
 >
+## July 2024
+
+|Service area  |Updates  |
+|---------|---------|
+| **OT networks** | - [Security update](#security-update)  |
+
+### Security update
+
+This update resolves a CVE, which is listed in [software version 24.1.4 feature documentation](release-notes.md#version-2414).
+
 ## June 2024
 
 |Service area  |Updates  |
 |---------|---------|
-| **OT networks** | - [Malicious URL path alert](#malicious-url-path-alert)<br> |
+| **OT networks** | - [Malicious URL path alert](#malicious-url-path-alert)<br> - [Newly supported protocols](#newly-supported-protocols)|
 
 ### Malicious URL path alert
 
 The new alert, Malicious URL path, allows users to identify malicious paths in legitimate URLs. The Malicious URL path alert expands Defender for IoT's threat identification to include generic URL signatures, crucial for countering a wide range of cyber threats.
 
 For more information, this alert is described in the [Malware engine alerts table](alert-engine-messages.md#malware-engine-alerts).  
 
+### Newly supported protocols
+
+We now support the Open protocol. [See the updated protocol list](concept-supported-protocols.md).
+
 ## April 2024
 
 |Service area  |Updates  |
 |---------|---------|
-| **OT networks** | - [Single sign-on for the sensor console](#single-sign-on-for-the-sensor-console)<br>- [Sensor time drift detection](#sensor-time-drift-detection)<br>- [Security update](#security-update) |
+| **OT networks** | - [Single sign-on for the sensor console](#single-sign-on-for-the-sensor-console)<br>- [Sensor time drift detection](#sensor-time-drift-detection)<br>- [Security update](#security-update-1) |
 
 ### Single sign-on for the sensor console
 
-You can set up single sign-on (SSO) for the Defender for IoT sensor console using Microsoft Entra ID. SSO allows simple sign in for your organization's users, allows your organization to meet regulation standards, and increases your security posture. With SSO, your users don't need multiple login credentials across different sensors and sites. 
+You can set up single sign-on (SSO) for the Defender for IoT sensor console using Microsoft Entra ID. SSO allows simple sign in for your organization's users, allows your organization to meet regulation standards, and increases your security posture. With SSO, your users don't need multiple login credentials across different sensors and sites.
 
 Using Microsoft Entra ID simplifies the onboarding and offboarding processes, reduces administrative overhead, and ensures consistent access controls across the organization.
 
@@ -57,7 +71,7 @@ This update resolves six CVEs, which are listed in [software version 24.1.3 feat
 
 |Service area  |Updates  |
 |---------|---------|
-| **OT networks** | **Version 24.1.2**:<br> - [Alert suppression rules from the Azure portal (Public preview)](#alert-suppression-rules-from-the-azure-portal-public-preview)<br>- [Focused alerts in OT/IT environments](#focused-alerts-in-otit-environments)<br>- [Alert ID now aligned on the Azure portal and sensor console](#alert-id-now-aligned-on-the-azure-portal-and-sensor-console)<br>- [Newly supported protocols](#newly-supported-protocols)<br><br>**Cloud features**<br>- [New license renewal reminder in the Azure portal](#new-license-renewal-reminder-in-the-azure-portal) <br><br>- [New OT appliance hardware profile](#new-ot-appliance-hardware-profile) <br><br>- [New fields for SNMP MIB OIDs](#new-fields-for-snmp-mib-oids)|
+| **OT networks** | **Version 24.1.2**:<br> - [Alert suppression rules from the Azure portal (Public preview)](#alert-suppression-rules-from-the-azure-portal-public-preview)<br>- [Focused alerts in OT/IT environments](#focused-alerts-in-otit-environments)<br>- [Alert ID now aligned on the Azure portal and sensor console](#alert-id-now-aligned-on-the-azure-portal-and-sensor-console)<br>- [Newly supported protocols](#newly-supported-protocols-1)<br><br>**Cloud features**<br>- [New license renewal reminder in the Azure portal](#new-license-renewal-reminder-in-the-azure-portal) <br><br>- [New OT appliance hardware profile](#new-ot-appliance-hardware-profile) <br><br>- [New fields for SNMP MIB OIDs](#new-fields-for-snmp-mib-oids)|
 
 ### Alert suppression rules from the Azure portal (Public preview)
 

articles/logic-apps/connectors/sap-create-example-scenario-workflows.md

@@ -16,7 +16,7 @@ ms.date: 12/12/2023
 
 This how-to guide shows how to create example logic app workflows for some common SAP integration scenarios using Azure Logic Apps and the SAP connector.
 
-Both Standard and Consumption logic app workflows offer the SAP *managed* connector that's hosted and run in multi-tenant Azure. Standard workflows also offer the SAP *built-in service provider* connector that's hosted and run in single-tenant Azure Logic Apps. If you create and host a Consumption workflow in an integration service environment (ISE), you can also use the SAP connector's ISE-native version. For more information, see [Connector technical reference](sap.md#connector-technical-reference).
+Both Standard and Consumption logic app workflows offer the SAP *managed* connector that's hosted and run in multitenant Azure. Standard workflows also offer the SAP *built-in service provider* connector that's hosted and run in single-tenant Azure Logic Apps. If you create and host a Consumption workflow in an integration service environment (ISE), you can also use the SAP connector's ISE-native version. For more information, see [Connector technical reference](sap.md#connector-technical-reference).
 
 ## Prerequisites
 
@@ -32,7 +32,7 @@ The following example logic app workflow triggers when the workflow's SAP trigge
 
 ### Add an SAP trigger
 
-Based on whether you have a Consumption workflow in multi-tenant Azure Logic Apps or a Standard workflow in single-tenant Azure Logic Apps, follow the corresponding steps:
+Based on whether you have a Consumption workflow in multitenant Azure Logic Apps or a Standard workflow in single-tenant Azure Logic Apps, follow the corresponding steps:
 
 ### [Consumption](#tab/consumption)
 
@@ -294,7 +294,7 @@ To have your workflow receive IDocs from SAP over XML HTTP, you can use the [Req
 
 To receive IDocs over Common Programming Interface Communication (CPIC) as plain XML or as a flat file, review the section, [Receive message from SAP](#receive-messages-sap).
 
-Based on whether you have a Consumption workflow in multi-tenant Azure Logic Apps or a Standard workflow in single-tenant Azure Logic Apps, follow the corresponding steps:
+Based on whether you have a Consumption workflow in multitenant Azure Logic Apps or a Standard workflow in single-tenant Azure Logic Apps, follow the corresponding steps:
 
 ### [Consumption](#tab/consumption)
 
@@ -330,7 +330,7 @@ Based on whether you have a Consumption workflow in multi-tenant Azure Logic App
 
 ### Add an SAP action to send an IDoc
 
-Next, create an action to send your IDoc to SAP when the workflow's request trigger fires. Based on whether you have a Consumption workflow in multi-tenant Azure Logic Apps or a Standard workflow in single-tenant Azure Logic Apps, follow the corresponding steps:
+Next, create an action to send your IDoc to SAP when the workflow's request trigger fires. Based on whether you have a Consumption workflow in multitenant Azure Logic Apps or a Standard workflow in single-tenant Azure Logic Apps, follow the corresponding steps:
 
 ### [Consumption](#tab/consumption)
 
@@ -662,7 +662,7 @@ In the following example, the `STFC_CONNECTION` RFC module generates a request a
 
 1. On the designer toolbar, select **Run Trigger** > **Run** to manually start your workflow.
 
-1. To simulate a webhook trigger payload, send an HTTP POST request to the endpoint URL that's specified by your workflow's Request trigger. Make sure to include your message content with your request. To send the request, use a tool such as the [Postman API client](https://www.postman.com/api-platform/api-client/).
+1. To simulate a webhook trigger payload, send an HTTP POST request to the endpoint URL that's specified by your workflow's Request trigger. Make sure to include your message content with your request. To send the request, use a local tool or app tool such as [Insomnia](https://insomnia.rest/) or [Bruno](https://www.usebruno.com/).
 
    For this example, the HTTP POST request sends an IDoc file, which must be in XML format and include the namespace for the SAP action that you selected, for example:
 
@@ -690,7 +690,7 @@ You've now created a workflow that can communicate with your SAP server. Now tha
 
 1. Return to the workflow level. On the workflow menu, select **Overview**. On the toolbar, select **Run** > **Run** to manually start your workflow.
 
-1. To simulate a webhook trigger payload, send an HTTP POST request to the endpoint URL that's specified by your workflow's Request trigger. Make sure to your message content with your request. To send the request, use a tool such as the [Postman API client](https://www.postman.com/api-platform/api-client/).
+1. To simulate a webhook trigger payload, send an HTTP POST request to the endpoint URL that's specified by your workflow's Request trigger. Make sure to your message content with your request. To send the request, use a local tool or app such as [Insomnia](https://insomnia.rest/) or [Bruno](https://www.usebruno.com/).
 
    For this example, the HTTP POST request sends an IDoc file, which must be in XML format and include the namespace for the SAP action that you selected, for example: