Merge branch 'main' into release-aio-m3

Author: v-alje

articles/app-service/configure-language-dotnetcore.md

@@ -72,6 +72,9 @@ az webapp config set --name <app-name> --resource-group <resource-group-name> --
 
 ## Customize build automation
 
+> [!NOTE]
+> Building .NET 9 (STS) apps with Windows App Service using MSBuild or SCM_DO_BUILD is not yet supported. Support for these build scenarios will come after the initial GA date and by December 4th, 2024. Deployments that build outside of App Service through Visual Studio, Visual Studio Code, GitHub Actions and Azure DevOps are fully supported.
+
 If you deploy your app using Git, or zip packages [with build automation enabled](deploy-zip.md#enable-build-automation-for-zip-deploy), the App Service build automation steps through the following sequence:
 
 1. Run custom script if specified by `PRE_BUILD_SCRIPT_PATH`.

articles/app-service/quickstart-dotnetcore.md

@@ -44,6 +44,9 @@ Alternatively, you can deploy an ASP.NET web app as part of a [Windows or Linux
 > [!TIP]
 > Find GitHub Copilot tips in the Visual Studio, Visual Studio Code, and Azure portal steps.
 
+> [!NOTE]
+> Building .NET 9 (STS) apps with Windows App Service using MSBuild or SCM_DO_BUILD is not yet supported. Support for these build scenarios will come after the initial GA date and by December 4th, 2024. Deployments that build outside of App Service through Visual Studio, Visual Studio Code, GitHub Actions and Azure DevOps are fully supported.
+
 ## Prerequisites
 
 :::zone target="docs" pivot="development-environment-vs"

articles/azure-functions/functions-triggers-bindings.md

@@ -2,9 +2,10 @@
 title: Triggers and bindings in Azure Functions
 description: Learn to use triggers and bindings to connect your Azure Function to online events and cloud-based services.
 ms.topic: conceptual
-ms.date: 09/06/2024
+ms.date: 10/28/2024
 ms.custom: devdivchpfy22, devx-track-extended-java, devx-track-js, devx-track-python, devx-track-ts
 zone_pivot_groups: programming-languages-set-functions
+ai-usage: ai-assisted
 ---
 
 # Azure Functions triggers and bindings concepts
@@ -36,9 +37,9 @@ These examples aren't meant to be exhaustive, but are provided to illustrate how
 
 ##  Trigger and binding definitions
 
-Triggers and bindings are defined differently depending on the development language. Make sure to select your language at the [top](#top) of the article.
+A function has a single trigger and one or more bindings. The type of binding is either input or output. Not all services support both input and output bindings. See your specific binding extension for [specific bindings code examples](#bindings-code-examples).
 
-Bindings can be either input or output bindings. Not all services support both input and output bindings. See your specific binding extension for [specific bindings code examples](#bindings-code-examples).
+Triggers and bindings are defined differently depending on the development language. Make sure to select your language at the [top](#top) of the article.
 
 This example shows an HTTP triggered function with an output binding that writes a message to an Azure Storage queue.
 
@@ -194,10 +195,13 @@ In Python for Functions version 1, this example `function.json` file defines an
 ---
 
 ::: zone-end  
+
 ## Add bindings to a function
 
 You can connect your function to other services by using input or output bindings. Add a binding by adding its specific definitions to your function. To learn how, see [Add bindings to an existing function in Azure Functions](add-bindings-existing-function.md).  
 
+Azure Functions supports multiple bindings, which must be configured correctly. For example, a function can read data from a queue (input binding) and write data to a database (output binding) simultaneously. 
+
 ## Supported bindings
 
 [!INCLUDE [Full bindings table](../../includes/functions-bindings.md)]

articles/defender-for-iot/organizations/TOC.yml

@@ -373,6 +373,8 @@
           href: appliance-catalog/dell-poweredge-r360-e1800.md
       - name: Production line
         items:
+        - name: Heptagon YB3x
+          href: appliance-catalog/heptagon-yb3x.md
         - name: HPE ProLiant DL20 Gen11 Plus (NHP 2LFF)
           href: appliance-catalog/hpe-proliant-dl20-gen-11-nhp-2lff.md
         - name: DELL XE4 SFF

articles/defender-for-iot/organizations/appliance-catalog/heptagon-yb3x.md

@@ -0,0 +1,74 @@
+---
+title: Heptagon YB3x for OT monitoring in L100 deployments - Microsoft Defender for IoT
+description: Learn about the YB3x appliance when used for OT monitoring with Microsoft Defender for IoT in L100 deployments.
+ms.date: 04/01/2024
+ms.topic: reference
+---
+
+# Heptagon YB3x
+
+This article describes the **Heptagon YB3x** appliance deployment and installation for OT sensors.
+
+| Appliance characteristic |Details |
+|---------|---------|
+|**Hardware profile** | L100 |
+|**Performance** | Max bandwidth: 20-25 Mbps <br> Max devices: 200 |
+|**Physical specifications** | Ports: 6 x 1-GbE ports|
+|**Status** | Supported, available as preconfigured |
+
+The following image shows a view of the Heptagon YB3x front panel:
+
+:::image type="content" source="media/yb3x.png" alt-text="Picture of the front view of the Heptagon YB3x." border="false":::
+
+## Specifications
+
+|Component|Technical specifications|
+|----|----|
+|Construction |Fanless cooling  |
+|Dimensions |1U, 209x187x37.5mm  |
+|Weight | 1.1 kg |
+|CPU |Intel C3708 – 8 cores  |
+|Memory |16 GB |
+|Storage |500 GB |
+|Network controller |Intel I210, Intel x553  |
+|Device access | 4x USB 3.0, TPM 2.0, 2x Serial ports |
+|Power Adapter |12 VDC or optional 9-28 VDC with reverse polarity, <br>Over/under voltage protection  |
+|BMC |BMC AST2600, OpenBMC, IPMI 2.0, iKVM, Virtual Media  |
+|Temperature |-40 °C to +75 °C |
+|Humidity |95% @ 40°C (noncondensing)  |
+|Shock & Vibration  | ETSI standard ETS 300 019-1-5, 5M2 |
+|Safety |IEC 60950-1, AS/NZS  |
+|EMC |CE, FCC, AS/NZS |
+
+## Heptagon YB3x - Bill of Materials
+
+|Description| PN|Quantity|
+|--------------|--------------|---------|
+|CPU: Atom-C3708, 8C, 16 MB Cache, 1.7Ghz, 17 W, Embedded/Ind. Temp <br> DRAM - Not installed <br> COMM1: COM-4X1: Quad 1G Base-T <br> COMM2: No Comm Module <br> BMC: BMC, based on Aspeed AST2600, with Display port video  |YB3708-0-4T0B |1|
+|500G NV2 M.2 2280 PCIe 4.0 NVMe SSD  |SNV2S/500G |1 |
+|Intel X710 Dual Port 10 GbE SFP+ Adapter | 540-BDQZ |1|
+|8 GB 2,666 MT/s DDR4 ECC Reg CL19 DIMM 1Rx8 Hynix D IDT  | KSM26RS8/8HDI  | 2|
+|Power supply, 110-220 VAC to 12 VDC, 100 W, IP 67, Industrial temp   | PS100-12-IP67  | 1 |
+
+## Heptagon YB3x software setup
+
+This procedure describes how to install Defender for IoT software on the Heptagon YB3x. The installation process takes about 20 minutes. After the installation, the system restarts several times.
+
+To install Defender for IoT software:
+
+1. Connect the screen and keyboard to the appliance, and then connect to the CLI.
+
+1. Connect an external CD or disk-on-key that contains the software you downloaded from the Azure portal.
+
+1. Start the appliance.
+
+1. Continue by installing your Defender for IoT software. For more information, see [Defender for IoT software installation](../ot-deploy/install-software-ot-sensor.md#install-defender-or-iot-software-on-ot-sensors).
+
+## Next steps
+
+Continue understanding system requirements for physical or virtual appliances. For more information, see [Which appliances do I need?](../ot-appliance-sizing.md)
+
+Then, use any of the following procedures to continue:
+
+- [Download software for an OT sensor](../ot-deploy/install-software-ot-sensor.md#download-software-files-from-the-azure-portal)
+- [Download software files for an on-premises management console](../legacy-central-management/install-software-on-premises-management-console.md#download-software-files-from-the-azure-portal)

articles/defender-for-iot/organizations/appliance-catalog/index.yml

@@ -42,6 +42,8 @@ landingContent:
     linkLists:
       - linkListType: deploy
         links:
+          - text: Heptagon YB3x
+            url: heptagon-yb3x.md
           - text: HPE ProLiant DL20 Gen11 Plus (NHP 2LFF)
             url: hpe-proliant-dl20-gen-11-nhp-2lff.md
           - text: Dell XE4 SFF

articles/defender-for-iot/organizations/appliance-catalog/media/yb3x.png

@@ -77,11 +77,9 @@ sections:
           The feature to buy domain names is tracked in the Azure backlog. Use the feedback site to [register your support for this feature](https://feedback.azure.com/d365community/idea/9e9f97ea-8526-ec11-b6e6-000d3a4f0789).
           
       - question: |
-          Does Azure DNS support DNSSEC?
+          Does Azure DNS support Domain Name System Security Extensions (DNSSEC)?
         answer: |
-          No. Azure DNS doesn't currently support the Domain Name System Security Extensions (DNSSEC).
-          
-          The DNSSEC feature is tracked in the Azure DNS backlog. Use the feedback site to [register your support for this feature](https://feedback.azure.com/d365community/idea/d403899e-8526-ec11-b6e6-000d3a4f0789).
+          Yes. See [DNSSEC overview](dnssec.md).
           
       - question: |
           Does Azure DNS support zone transfers (AXFR/IXFR)?

articles/dns/dns-faq.yml

@@ -79,7 +79,7 @@ Before you sign a zone with DNSSEC, be sure to understand [how DNSSEC works](#ho
 
 If a DNS server is DNSSEC-aware, it can set the DNSSEC OK (DO) flag in a DNS query to a value of `1`. This value tells the responding DNS server to include DNSSEC-related resource records with the response. These DNSSEC records are Resource Record Signature (RRSIG) records that are used to validate that the DNS response is genuine. 
 
-A recursive (non-authoritative) DNS server performs DNSSEC validation on RRSIG records using a trust anchor (DNSKEY). The server uses a DNSKEY to decrypt digital signatures in RRSIG records (and other DNSSEC-related records), and then computes and compares hash values. If hash values are the same, it provides a reply to the DNS client with the DNS data that it requested, such as a host address (A) record. See the following diagram:
+A recursive (non-authoritative) DNS server performs DNSSEC validation on RRSIG records using a [trust anchor](#trust-anchors-and-dnssec-validation) (DNSKEY). The server uses a DNSKEY to decrypt digital signatures in RRSIG records (and other DNSSEC-related records), and then computes and compares hash values. If hash values are the same, it provides a reply to the DNS client with the DNS data that it requested, such as a host address (A) record. See the following diagram:
 
   ![A diagram showing how DNSSEC validation works.](media/dnssec/dnssec-validation.png)
 
@@ -92,7 +92,7 @@ Windows 10 and Windows 11 client devices are [nonvalidating security-aware stub
 > [!NOTE] 
 > DNSSEC response validation is not performed by the default Azure-provided resolver. The information in this section is helpful if you are setting up your own recursive DNS servers for DNSSEC validation or troubleshooting validation issues.
 
-Trust anchors operate based on the DNS namespace hierarchy. A recursive DNS server can have any number of trust anchors, or no trust anchors. Trust anchors can be added for a single child DNS zone, or any parent zone. If a recursive DNS server has a root (.) trust anchor, then it can perform DNSSEC validation on any DNS zone. 
+Trust anchors operate based on the DNS namespace hierarchy. A recursive DNS server can have any number of trust anchors, or no trust anchors. Trust anchors can be added for a single child DNS zone, or any parent zone. If a recursive DNS server has a root (.) trust anchor, then it can perform DNSSEC validation on any DNS zone. For more information, see [Root Zone Operator Information](https://www.iana.org/dnssec).
 
 The DNSSEC validation process works with trust anchors as follows:
   - If a recursive DNS server doesn't have a DNSSEC trust anchor for a zone or the zone's parent hierarchical namespace, it will not perform DNSSEC validation on that zone.

articles/dns/dnssec.md

@@ -33,7 +33,7 @@ For more information, see [How to protect DNS zones and records](dns-protect-zon
 
 ## DNSSEC
 
-Azure Public DNS doesn't currently support DNSSEC. In most cases, you can reduce the need for DNSSEC by consistently using HTTPS/TLS in your applications. If DNSSEC is a critical requirement for your DNS zones, you can host these zones with third-party DNS hosting providers.
+Azure Public DNS supports DNSSEC. For more information, see [DNSSEC overview](dnssec.md).
 
 ## Ease of use