Merge branch 'main' into release-aio-ga

Author: v-alje

articles/azure-vmware/azure-vmware-solution-platform-updates.md

@@ -4,20 +4,26 @@ description: Learn about the platform updates to Azure VMware Solution.
 ms.topic: reference
 ms.custom: "references_regions, engagement-fy23"
 ms.service: azure-vmware
-ms.date: 8/20/2024
+ms.date: 11/6/2024
 ---
 
 # What's new in Azure VMware Solution
 
 Microsoft regularly applies important updates to the Azure VMware Solution for new features and software lifecycle management. You should receive a notification through Azure Service Health that includes the timeline of the maintenance. For more information, see [Host maintenance and lifecycle management](architecture-private-clouds.md#host-maintenance-and-lifecycle-management).
 
+## November 2024
+
+Azure VMware Solution is now ready to update all existing Azure Commercial customers from vSphere 7 to vSphere 8 (Stretched Clusters & Azure Government still pending). Over the coming months, all customers will receive a scheduling notice for this upgrade. If you want to prioritize your vSphere 8 upgrade, open a [Service Request](https://rc.portal.azure.com/#create/Microsoft.Support) with Microsoft requesting a "Priority vSphere 8 upgrade" for your private cloud. [Learn more](architecture-private-clouds.md#vmware-software-versions)
+
+All new Azure VMware Solution private clouds are being deployed with VMware vSphere 8.0 version in [Microsoft Azure Government](https://azure.microsoft.com/explore/global-infrastructure/government/#why-azure). [Learn more](architecture-private-clouds.md#vmware-software-versions)
+
 ## October 2024
 
-The VMware Cloud Foundations (VCF) license portability feature on Azure VMware Solution is to modernize your VMware workload by bringing your VCF entitlements to Azure VMware Solution and take advantage of incredible cost savings.
+The VMware Cloud Foundations (VCF) license portability feature on Azure VMware Solution allows you to bring your VCF entitlement to Azure VMware Solution and take advantage of potential cost savings.
 
 ## August 2024
 
-All new Azure VMware Solution private clouds are being deployed with VMware vSphere 8.0 version in Azure Commercial. [Learn more](architecture-private-clouds.md#vmware-software-versions)
+All new Azure VMware Solution private clouds are being deployed with VMware vSphere 8.0 version in Azure Commercial (Stretched Clusters excluded). [Learn more](architecture-private-clouds.md#vmware-software-versions)
 
 Azure VMware Solution was approved to be added as a service within the [DoD SRG Impact Level 4 (IL4)](/azure/azure-government/compliance/azure-services-in-fedramp-auditscope#azure-government-services-by-audit-scope) Provisional Authorization (PA) in [Microsoft Azure Government](https://azure.microsoft.com/explore/global-infrastructure/government/#why-azure).
 

articles/data-factory/connector-deprecation-plan.md

@@ -1,18 +1,18 @@
 ---
-title: Planned connector deprecations for Azure Data Factory
-description: This page describes future deprecations for some connectors of Azure Data Factory.
+title: Upgrade plan for Azure Data Factory connectors
+description: This article describes future upgrades for some connectors of Azure Data Factory.
 author: jianleishen
 ms.author: jianleishen
 ms.service: azure-data-factory
 ms.subservice: data-movement
 ms.topic: concept-article
 ms.custom: references_regions
-ms.date: 10/16/2024
+ms.date: 11/06/2024
 ---
 
-# Planned connector deprecations for Azure Data Factory
+# Upgrade plan for Azure Data Factory connectors
 
-This article describes future deprecations for some connectors of Azure Data Factory.
+This article describes future upgrades for some connectors of Azure Data Factory.
 
 > [!NOTE]
 > "Deprecated" means we intend to remove the connector from a future release. Unless they are in *Preview*, connectors remain fully supported until they are officially deprecated. This deprecation notification can span a few months or longer. After removal, the connector will no longer work. This notice is to allow you sufficient time to plan and update your code before the connector is deprecated.

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

@@ -359,6 +359,8 @@
         href: /legal/defender-for-iot/hardware-support-policy?toc=/azure/defender-for-iot/organizations/toc.json&bc=/azure/defender-for-iot/breadcrumb/toc.json
       - name: Corporate environments
         items:
+        - name: HPE ProLiant DL360 Gen11
+          href: appliance-catalog/hpe-proliant-dl360-gen11.md
         - name: HPE ProLiant DL360
           href: appliance-catalog/hpe-proliant-dl360.md
         - name: Dell PowerEdge R660

articles/defender-for-iot/organizations/appliance-catalog/hpe-proliant-dl360-gen11.md

@@ -0,0 +1,153 @@
+---
+title: HPE ProLiant DL360 Gen 11 OT monitoring - Microsoft Defender for IoT
+description: Learn about the HPE ProLiant DL360 Gen 11 appliance when used for OT monitoring with Microsoft Defender for IoT.
+ms.date: 03/14/2024
+ms.topic: reference
+---
+
+# HPE ProLiant DL360 Gen 11
+
+This article describes the **HPE ProLiant DL360 Gen 11** appliance for OT sensors, customized for use with Microsoft Defender for IoT.
+
+| Appliance characteristic |Details |
+|---------|---------|
+|**Hardware profile** | C5600  |
+|**Performance** | Max bandwidth: 3 Gbps <br> Max devices: 12,000 |
+|**Physical specifications** | Mounting: 1U|
+|**Status** | Supported, available preconfigured|
+
+The following image displays the hardware elements on the HPE ProLiant DL360 Gen11 that are used by Defender for IoT:
+
+:::image type="content" source="media/hpe-proliant-dl360-gen11/hpe-proliant-dl360-gen11.png" alt-text="Photo of the HPE ProLiant DL360 gen11." border="false":::
+
+## Specifications
+
+|Component  |Specifications|
+|---------|---------|
+|**Chassis**    |1U rack server         |
+|**Physical Characteristics** | HPE DL360 Gen11 8SFF  |
+|**Processor** | INT Xeon-S 4510 CPU for HPE OEM  |
+|**Chipset** | Intel C262|
+|**Memory** | 4 HPE 32GB (1x32GB) Dual Rank x8 DDR5-5600 CAS-46-45-45 EC8 Registered Smart Memory Kit |
+|**Storage**| 6 HPE 2.4TB SAS 12G Mission Critical 10K SFF BC 3-year Warranty 512e Multi Vendor HDD |
+|**Network controller**| On-board: 8 x 1 Gb |
+|**Management**     | HPE iLO Advanced         |
+|**Power**            |HPE 800W Flex Slot Titanium Hot Plug Low Halogen Power Supply Kit |
+|**Rack support**     | HPE 1U Rail 3 kit        |
+
+## HPE DL360 Gen 11 Plus (NHP 4SFF) - Bill of materials
+
+|PN |Description |Quantity|
+|-------------- | --------------| --------- |
+|**P55428-B21** | HPE OEM ProLiant DL360 Gen11 SFF NC Configure-to-order Server |1|
+|**P55428-B21#B19** | HPE OEM ProLiant DL360 Gen11 SFF NC Configure-to-order Server |1|
+|**P67824-B21** | INT Xeon-S 4510 CPU for HPE OEM |2|
+|**P64706-B21** | HPE 32GB (1x32GB) Dual Rank x8 DDR5-5600 CAS-46-45-45 EC8 Registered Smart Memory Kit |4|
+|**P48896-B21** | HPE ProLiant DL360 Gen11 8SFF x4 U.3 Tri-Mode Backplane Kit |1|
+|**P28352-B21** | HPE 2.4TB SAS 12G Mission Critical 10K SFF BC 3-year Warranty 512e Multi Vendor HDD |6|
+|**P48901-B21** | HPE ProLiant DL360 Gen11 x16 Full Height Riser Kit |1|
+|**P51178-B21** | Broadcom BCM5719 Ethernet 1Gb 4-port BASE-T Adapter for HPE |1|
+|**P47789-B21** | HPE MR216i-o Gen11 x16 Lanes without Cache OCP SPDM Storage Controller |1|
+|**P10097-B21** | Broadcom BCM57416 Ethernet 10Gb 2-port BASE-T OCP3 Adapter for HPE |1|
+|**P48907-B21** | HPE ProLiant DL3X0 Gen11 1U Standard Fan Kit |1|
+|**P54697-B21** | HPE ProLiant DL3X0 Gen11 1U 2P Standard Fan Kit |1|
+|**865438-B21** | HPE 800W Flex Slot Titanium Hot Plug Low Halogen Power Supply Kit |2|
+|**AF573A** | HPE C13 - C14 WW 250V 10Amp Flint Gray 2.0m Jumper Cord |2|
+|**P48830-B21** | HPE ProLiant DL3XX Gen11 CPU2 to OCP2 x8 Enablement Kit  |1|
+|**P52416-B21** | HPE ProLiant DL360 Gen11 OROC Tri-Mode Cable Kit |1|
+|**BD505A** | HPE iLO Advanced 1-server License with 3yr Support on iLO Licensed Features |1|
+|**P48904-B21** | HPE ProLiant DL3X0 Gen11 1U Standard Heat Sink Kit |2|
+|**P52341-B21** | HPE ProLiant DL3XX Gen11 Easy Install Rail 3 Kit |1|
+
+## HPE ProLiant DL360 Gen 11 installation
+
+This section describes how to install OT sensor software on the HPE ProLiant DL360 Gen 11 appliance and includes adjusting the appliance's BIOS configuration.
+
+During this procedure, you configure the iLO port. We recommend that you also change the default password provided for the administrative user.
+
+> [!NOTE]
+> Installation procedures are only relevant if you need to re-install software on a pre-configured device, or if you buy your own hardware and configure the appliance yourself.
+>
+
+### Enable remote access and update the password
+
+Use the following procedure to set up network options and update the default password.
+
+**To enable and update the password**:
+
+1. Connect a screen and a keyboard to the HP appliance, turn on the appliance, and press **F9**.
+
+    :::image type="content" source="../media/tutorial-install-components/hpe-proliant-screen-v2.png" alt-text="Screenshot that shows the HPE ProLiant window.":::
+
+1. Go to **System Utilities** > **System Configuration** > **iLO 5 Configuration Utility** > **Network Options**.
+
+    :::image type="content" source="../media/tutorial-install-components/system-configuration-window-v2.png" alt-text="Screenshot that shows the System Configuration window.":::
+
+    1. Select **Shared Network Port-LOM** from the **Network Interface Adapter** field.
+
+    1. Set **Enable DHCP** to **Off**.
+
+    1. Enter the IP address, subnet mask, and gateway IP address.
+
+1. Select **F10: Save**.
+
+1. Select **Esc** to get back to the **iLO 5 Configuration Utility**, and then select **User Management**.
+
+1. Select **Edit/Remove User**. The administrator is the only default user defined.
+
+1. Change the default password and select **F10: Save**.
+
+### Set up the BIOS and RAID array
+
+This procedure describes how to configure the BIOS configuration for an unconfigured sensor appliance.
+If any of the steps below are missing in the BIOS, make sure that the hardware matches the specifications above.
+
+HPE BIOS iLO is a system management software designed to give administrators control of HPE hardware remotely. It allows administrators to monitor system performance, configure settings, and troubleshoot hardware issues from a web browser. It can also be used to update system BIOS and firmware. The BIOS can be set up locally or remotely. To set up the BIOS remotely from a management computer, you need to define the HPE IP address and the management computer's IP address on the same subnet.
+
+**To configure the HPE BIOS**:
+
+> [!IMPORTANT]
+> Please make sure your server is using the HPE SPP 2022.03.1 (BIOS version U32 v2.6.2) or later.
+
+1. Select **System Utilities** > **System Configuration** > **BIOS/Platform Configuration (RBSU)**.
+
+1. In the **BIOS/Ethernet Adapter/NIC Configuration**, disable LLDP Agent for all NIC cards.
+
+1. In the **BIOS/Platform Configuration (RBSU)** form, select **Boot Options**.
+
+1. Change **Boot Mode** to **UEFI BIOS Mode**, and then select **F10: Save**.
+
+1. Select **Esc** twice to close the **System Configuration** form.
+
+1. Select **Embedded RAID1: HPE Smart Array P408i-a SR Gen 10** > **Array Configuration** > **Create Array**.
+
+1. In the **Create Array** form, select all the drives, and enable RAID Level 5.
+
+> [!NOTE]
+> For **Data-at-Rest** encryption, see the HPE guidance for activating RAID Secure Encryption or using Self-Encrypting-Drives (SED).
+>
+
+[!INCLUDE [install iLO remotely from virtual drive and change timeout settings](../includes/ilo-remote-install-hpe.md)]
+
+### Install OT sensor software on the HPE DL360
+
+This procedure describes how to install OT sensor software on the HPE DL360.
+
+The installation process takes about 20 minutes. After the installation, the system is restarted several times.
+
+**To install OT sensor software**:
+
+1. Connect a screen and keyboard to the appliance, and then connect to the CLI.
+
+1. Connect an external CD or disk-on-key that contains the sensor software you downloaded from the Azure portal.
+
+1. Continue with the generic procedure for installing OT sensor software. For more information, see [Defender for IoT software installation](../how-to-install-software.md).
+
+## 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

@@ -24,6 +24,8 @@ landingContent:
           url: dell-poweredge-r660.md
         - text: HPE ProLiant DL360
           url: hpe-proliant-dl360.md
+        - text: HPE ProLiant DL360 Gen11
+          url: hpe-proliant-dl360-gen11.md
 
   # Card
   - title: Large enterprises

articles/defender-for-iot/organizations/appliance-catalog/media/hpe-proliant-dl360-gen11/hpe-proliant-dl360-gen11.png

@@ -312,23 +312,23 @@
         items:
         - name: Connect to an internal load balancer
           href: standard-premium/how-to-enable-private-link-internal-load-balancer.md
-        - name: Connect to a storage account
+        - name: Connect to Azure Storage Account
           items:
           - name: Azure portal
             href: standard-premium/how-to-enable-private-link-storage-account.md
           - name: Azure CLI
             href: standard-premium/how-to-enable-private-link-storage-account-cli.md
-        - name: Connect to a storage static website
+        - name: Connect to Azure Storage static website
           href: how-to-enable-private-link-storage-static-website.md
-        - name: Connect to an App service
+        - name: Connect to Azure App Service
           items:
           - name: Azure portal
             href: standard-premium/how-to-enable-private-link-web-app.md
           - name: Azure CLI
             href: standard-premium/how-to-enable-private-link-web-app-cli.md
-        - name: Connect to an application gateway
+        - name: Connect to Azure Application Gateway
           href: how-to-enable-private-link-application-gateway.md
-        - name: Connect to an API management
+        - name: Connect to Azure API Management
           href: standard-premium/how-to-enable-private-link-apim.md
       - name: Monitor and reports
         items:

articles/frontdoor/TOC.yml

@@ -12,6 +12,9 @@ zone_pivot_groups: front-door-tiers
 
 # End-to-end TLS with Azure Front Door
 
+> [!IMPORTANT]
+> Support for TLS 1.0 and 1.1 will be discontinued on March 1, 2025.
+
 Transport Layer Security (TLS), previously known as Secure Sockets Layer (SSL), is the standard security technology for establishing an encrypted link between a web server and a client, like a web browser. This link ensures that all data passed between the server and the client remain private and encrypted.
 
 To meet your security or compliance requirements, Azure Front Door supports end-to-end TLS encryption. Front Door TLS/SSL offload terminates the TLS connection, decrypts the traffic at the Azure Front Door, and re-encrypts the traffic before forwarding it to the origin. When connections to the origin use the origin's public IP address, it's a good security practice to configure HTTPS as the forwarding protocol on your Azure Front Door. By using HTTPS as the forwarding protocol, you can enforce end-to-end TLS encryption for the entire processing of the request from the client to the origin. TLS/SSL offload is also supported if you deploy a private origin with Azure Front Door Premium using the [Private Link](private-link.md) feature.
@@ -30,11 +33,11 @@ Azure Front Door offloads the TLS sessions at the edge and decrypts client reque
 
 ## Supported TLS versions
 
-Azure Front Door supports four versions of the TLS protocol: TLS versions 1.0, 1.1, 1.2 and 1.3. All Azure Front Door profiles created after September 2019 use TLS 1.2 as the default minimum with TLS 1.3 enabled, but TLS 1.0 and TLS 1.1 are still supported for backward compatibility.
+Azure Front Door currently supports four versions of the TLS protocol: TLS versions 1.0, 1.1, 1.2 and 1.3. All Azure Front Door profiles created after September 2019 use TLS 1.2 as the default minimum with TLS 1.3 enabled, but TLS 1.0 and TLS 1.1 are still supported for backward compatibility. Support for TLS 1.0 and 1.1 will be discontinued on March 1, 2025.
 
 Although Azure Front Door supports TLS 1.2, which introduced client/mutual authentication in RFC 5246, currently, Azure Front Door doesn't support client/mutual authentication (mTLS) yet.
 
-You can configure the minimum TLS version in Azure Front Door in the custom domain HTTPS settings using the Azure portal or the [Azure REST API](/rest/api/frontdoorservice/frontdoor/frontdoors/createorupdate#minimumtlsversion). Currently, you can choose between 1.0 and 1.2. As such, specifying TLS 1.2 as the minimum version controls the minimum acceptable TLS version Azure Front Door will accept from a client. For minimum TLS version 1.2 the negotiation will attempt to establish TLS 1.3 and then TLS 1.2, while for minimum TLS version 1.0 all four versions will be attempted. When Azure Front Door initiates TLS traffic to the origin, it will attempt to negotiate the best TLS version that the origin can reliably and consistently accept. Supported TLS versions for origin connections are TLS 1.0, TLS 1.1, TLS 1.2 and TLS 1.3.
+You can configure the minimum TLS version in Azure Front Door in the custom domain HTTPS settings using the Azure portal or the [Azure REST API](/rest/api/frontdoorservice/frontdoor/frontdoors/createorupdate#minimumtlsversion). Currently, you can choose between 1.0 and 1.2. As such, specifying TLS 1.2 as the minimum version controls the minimum acceptable TLS version Azure Front Door will accept from a client. For minimum TLS version 1.2 the negotiation will attempt to establish TLS 1.3 and then TLS 1.2, while for minimum TLS version 1.0 all four versions will be attempted. When Azure Front Door initiates TLS traffic to the origin, it will attempt to negotiate the best TLS version that the origin can reliably and consistently accept. Supported TLS versions for origin connections are TLS 1.0, TLS 1.1, TLS 1.2 and TLS 1.3. Support for TLS 1.0 and 1.1 will be discontinued on March 1, 2025.
 
 > [!NOTE]
 > * Clients with TLS 1.3 enabled are required to support one of the Microsoft SDL compliant EC Curves, including Secp384r1, Secp256r1, and Secp521, in order to successfully make requests with Azure Front Door using TLS 1.3.

articles/frontdoor/end-to-end-tls.md

@@ -8,7 +8,7 @@ ms.subservice: fhir
 ms.custom: devx-track-python
 ms.topic: conceptual
 ms.date: 04/29/2024
-ms.author: jasteppe
+ms.author: kesheth
 ---
 
 # Access Azure Health Data Services

articles/healthcare-apis/access-healthcare-apis.md

@@ -8,7 +8,7 @@ ms.subservice: fhir
 ms.custom: devx-track-python
 ms.topic: conceptual
 ms.date: 10/15/2024
-ms.author: jasteppe
+ms.author: kesheth
 ---
 
 # Availability Zones for Azure Health Data Services