Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into WI265678-sql-at-scale

Author: ElazarK

articles/ai-services/speech-service/text-to-speech-avatar/what-is-text-to-speech-avatar.md

@@ -67,9 +67,9 @@ Sample code for text to speech avatar is available on [GitHub](https://github.co
 
 ## Pricing
 
-- When utilizing the text-to-speech avatar feature, charges will be incurred based on the minutes of video output. However, with the real-time avatar, charges are based on the minutes of avatar activation, irrespective of whether the avatar is actively speaking or remaining silent. To optimize costs for real-time avatar usage, refer to the provided tips in the [sample code](https://github.com/Azure-Samples/cognitive-services-speech-sdk/tree/master/samples/js/browser/avatar#chat-sample) (search "Use Local Video for Idle").
 - Throughout an avatar real-time session or batch content creation, the text-to-speech, speech-to-text, Azure OpenAI, or other Azure services are charged separately.
-- For more information, see [Speech service pricing](https://azure.microsoft.com/pricing/details/cognitive-services/speech-services/). Note that avatar pricing will only be visible for service regions where the feature is available, including Southeast Asia, North Europe, West Europe, Sweden Central, South Central US, and West US 2.
+- Refer to [text to speech avatar pricing note](../text-to-speech.md#text-to-speech-avatar) to learn how billing works for the text-to-speech avatar feature.
+- For the detailed pricing, see [Speech service pricing](https://azure.microsoft.com/pricing/details/cognitive-services/speech-services/). Note that avatar pricing will only be visible for service regions where the feature is available, including Southeast Asia, North Europe, West Europe, Sweden Central, South Central US, and West US 2.
 
 ## Available locations
 

articles/ai-services/speech-service/text-to-speech.md

@@ -99,6 +99,17 @@ Custom neural voice (CNV) training time is measured by ‘compute hour’ (a uni
 
 Custom neural voice (CNV) endpoint hosting is measured by the actual time (hour). The hosting time (hours) for each endpoint is calculated at 00:00 UTC every day for the previous 24 hours. For example, if the endpoint has been active for 24 hours on day one, it's billed for 24 hours at 00:00 UTC the second day. If the endpoint is newly created or suspended during the day, it's billed for its accumulated running time until 00:00 UTC the second day. If the endpoint isn't currently hosted, it isn't billed. In addition to the daily calculation at 00:00 UTC each day, the billing is also triggered immediately when an endpoint is deleted or suspended. For example, for an endpoint created at 08:00 UTC on December 1, the hosting hour will be calculated to 16 hours at 00:00 UTC on December 2 and 24 hours at 00:00 UTC on December 3. If the user suspends hosting the endpoint at 16:30 UTC on December 3, the duration (16.5 hours) from 00:00 to 16:30 UTC on December 3 will be calculated for billing.
 
+### Personal voice
+
+When you use the personal voice feature, you're billed for both profile storage and synthesis.
+
+*  **Profile storage**: After a personal voice profile is created, it will be billed until it is removed from the system. The billing unit is per voice per day. If voice storage lasts for a period of less than 24 hours, it will be billed as one full day.
+*  **Synthesis**: Billed per character. For details on billable characters, see the above [billable characters](#billable-characters).
+
+### Text to speech avatar
+
+When using the text-to-speech avatar feature, charges will be incurred based on the length of video output and will be billed per second. However, for the real-time avatar, charges are based on the time when the avatar is active, regardless of whether it is speaking or remaining silent, and will also be billed per second. To optimize costs for real-time avatar usage, refer to the tips provided in the [sample code](https://github.com/Azure-Samples/cognitive-services-speech-sdk/tree/master/samples/js/browser/avatar#chat-sample) (search "Use Local Video for Idle"). Avatar hosting is billed per second per endpoint. You can suspend your endpoint to save costs. If you want to suspend your endpoint, you can delete it directly. To use it again, simply redeploy the endpoint.
+
 ## Reference docs
 
 * [Speech SDK](speech-sdk.md)

articles/azure-arc/system-center-virtual-machine-manager/quickstart-connect-system-center-virtual-machine-manager-to-arc.md

@@ -7,7 +7,7 @@ manager: jsuri
 ms.topic: quickstart
 ms.services: azure-arc
 ms.subservice: azure-arc-scvmm
-ms.date: 07/01/2024
+ms.date: 07/11/2024
 ms.custom: references_regions
 
 # Customer intent: As a VI admin, I want to connect my VMM management server to Azure Arc.
@@ -126,7 +126,10 @@ If for any reason, the appliance creation fails, you need to retry it. Run the c
  ./resource-bridge-onboarding-script.ps1 -Force -Subscription <Subscription> -ResourceGroup <ResourceGroup> -AzLocation <AzLocation> -ApplianceName <ApplianceName> -CustomLocationName <CustomLocationName> -VMMservername <VMMservername>
 ```
 
-### Retry command - Linux
+>[!Note]
+>You can find the values for *Subscription*, *ResourceGroup*, *Azlocation*, *ApplianceName*, *CustomLocationName*, and *VMMservername* parameters from the onboarding script.
+
+ ### Retry command - Linux
 
 If for any reason, the appliance creation fails, you need to retry it. Run the command with ```--force``` to clean up and onboard again.
 

articles/azure-monitor/logs/media/summary-rules/ingestion-flow.png

@@ -159,7 +159,7 @@ After connecting data sources to Microsoft Sentinel, you can create rules to gen
 
 6. On the **Incident settings** tab, enable **Create incidents from alerts triggered by this analytics rule** and select **Next: Automated response**.
  
-    :::image type="content" source="../sentinel/media/detect-threats-custom/general-tab.png" alt-text="Screenshot showing the Analytic rule wizard for creating a new rule in Microsoft Sentinel.":::
+    :::image type="content" source="../sentinel/media/create-analytics-rules/general-tab.png" alt-text="Screenshot showing the Analytic rule wizard for creating a new rule in Microsoft Sentinel.":::
 
 7. Select **Next: Review**.
 

articles/azure-vmware/azure-security-integration.md

@@ -369,6 +369,8 @@
           href: appliance-catalog/hpe-proliant-dl20-gen-11.md
         - name: Dell Edge 5200 (Rugged MIL-STD-810G)
           href: appliance-catalog/dell-edge-5200.md
+        - name: Dell PowerEdge R360
+          href: appliance-catalog/dell-poweredge-r360-e1800.md
         - name: Dell PowerEdge R350
           href: appliance-catalog/dell-poweredge-r350-e1800.md
       - name: Production line

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

@@ -0,0 +1,212 @@
+---
+title: Dell PowerEdge R360 for operational technology (OT) monitoring - Microsoft Defender for IoT
+description: Learn about the Dell PowerEdge R360 appliance's configuration when used for OT monitoring with Microsoft Defender for IoT in enterprise deployments.
+ms.date: 03/14/2024
+ms.topic: reference
+---
+
+# Dell PowerEdge R360
+
+This article describes the Dell PowerEdge R360 appliance, supported for operational technology (OT) sensors in an enterprise deployment.
+The Dell PowerEdge R360 is also available for the on-premises management console.
+
+|Appliance characteristic  | Description|
+|---------|---------|
+|**Hardware profile** | E1800|
+|**Performance** | Max bandwidth: 1 Gbps<br>Max devices: 10,000 |
+|**Physical Specifications** | Mounting: 1U with rail kit<br>Ports: 6x RJ45 1 GbE|
+|**Status** | Supported, available as a preconfigured appliance|
+
+The following image shows a view of the Dell PowerEdge R360 front panel:
+<!-- look up images -->
+:::image type="content" source="../media/tutorial-install-components/r360-front.png" alt-text="Picture of the Dell PowerEdge R360 front panel." border="false":::
+
+The following image shows a view of the Dell PowerEdge R360 back panel:
+<!-- look up images -->
+:::image type="content" source="../media/tutorial-install-components/r360-rear.png" alt-text="Picture of the Dell PowerEdge R360 back panel." border="false":::
+
+## Specifications
+
+|Component| Technical specifications|
+|:----|:----|
+|Chassis| 1U rack server|
+|Dimensions| Height: 1.68 in / 42.8 mm <br>Width: 18.97 in / 482.0 cm<br>Depth: 23.04 in / 585.3 mm (without bezel) 23.57 in / 598.9 mm (with bezel)|
+|Processor| Intel Xeon E-2434 3.4 GHz <br>8M Cache<br> 4C/8T, Turbo, HT (55 W) DDR5-4800|
+|Memory|32 GB |
+|Storage| 2.4 TB Hard Drive |
+|Network controller| - PowerEdge R360 Motherboard with with Broadcom 5720 Dual Port 1Gb On-Board LOM, <br>- PCIe Blank Filler, Low Profile. <br>- Intel Ethernet i350 Quad Port 1GbE BASE-T Adapter, PCIe Low Profile, V2|
+|Management|iDRAC Group Manager, Disabled|
+|Rack support| ReadyRails Sliding Rails With Cable Management Arm|
+
+## Dell PowerEdge R360 - Bill of Materials
+
+|Quantity|PN|Description|
+|----|---|----|
+|1| 210-BJTR | Base PowerEdge R360 Server|
+|1| 461-AAIG | Trusted Platform Module 2.0 V3 |
+|1| 321-BKHP | 2.5" Chassis with up to 8 Hot Plug Hard Drives, Front PERC |
+|1| 338-CMRB | Intel Xeon E-2434 3.4G, 4C/8T, 8M Cache, Turbo, HT (55 W) DDR5-4800 |
+|1| 412-BBHK | Heatsink |
+|1| 370-AAIP | Performance Optimized |
+|1| 370-BBKS | 4800 MT/s UDIMMs |
+|2| 370-BBKF | 16 GB UDIMM, 4800 MT/s ECC |
+|1| 780-BCDQ | RAID 10 |
+|1| 405-ABCQ | PERC H355 Controller Card |
+|1| 750-ACFR | Front PERC Mechanical Parts, front load |
+|4| 400-BEFU | 1.2 TB Hard Drive SAS 12 Gbps 10k 512n 2.5in Hot Plug |
+|1| 384-BBBH | Power Saving BIOS Settings |
+|1| 387-BBEY | No Energy Star |
+|1| 384-BDML | Standard Fan |
+|1| 528-CTIC | iDRAC9, Enterprise 16G |
+|2| 450-AADY | C13 to C14, PDU Style, 10 AMP, 6.5 Feet (2m), Power Cord |
+|1| 330-BCMK | Riser Config 2, Butterfly Gen4 Riser (x8/x8) |
+|1| 329-BJTH | PowerEdge R360 Motherboard with with Broadcom 5720 Dual Port 1Gb On-Board LOM |
+|1| 414-BBJB | PCIe Blank Filler, Low Profile |
+|1| 540-BDII | Intel Ethernet i350 Quad Port 1GbE BASE-T Adapter, PCIe Low Profile, V2, FIRMWARE RESTRICTIONS APPLY |
+|1| 379-BCRG | iDRAC, Factory Generated Password, No OMQR |
+|1| 379-BCQX | iDRAC Service Module (ISM), NOT Installed |
+|1| 325-BEVH | PowerEdge 1U Standard Bezel |
+|1| 350-BCTP | Dell Luggage Tag R360 |
+|1| 379-BCQY | iDRAC Group Manager, Disabled |
+|1| 470-AFBU | BOSS Blank |
+|1| 770-BCWN | ReadyRails Sliding Rails With Cable Management Arm |
+
+## Install Defender for IoT software on the DELL R360
+
+This procedure describes how to install Defender for IoT software on the Dell R360.
+
+The installation process takes about 20 minutes. During 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 with the generic procedure for installing Defender for IoT software. For more information, see [Defender for IoT software installation](../how-to-install-software.md).
+
+<!--
+## Dell PowerEdge R350 installation
+
+This section describes how to install Defender for IoT software on the Dell PowerEdge R350 appliance.
+
+Before installing the software on the Dell appliance, you need to adjust the appliance's BIOS configuration.
+
+> [!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.
+>
+
+### Prerequisites
+
+To install the Dell PowerEdge R350 appliance, you need:
+
+- An Enterprise license for Dell Remote Access Controller (iDrac)
+
+- A BIOS configuration XML
+
+### 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.
+
+Dell BIOS iDRAC is a system management software designed to give administrators control of Dell 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 iDRAC IP address and the management computer's IP address on the same subnet.
+
+**To configure the iDRAC IP address**:
+
+1. Power up the sensor.
+
+1. If the OS is already installed, select the F2 key to enter the BIOS configuration.
+
+1. Select **iDRAC Settings**.
+
+1. Select **Network**.
+
+   > [!NOTE]
+   > During the installation, you must configure the default iDRAC IP address and password mentioned in the following steps. After the installation, you change these definitions.
+
+1. Change the static IPv4 address to **10.100.100.250**.
+
+1. Change the static subnet mask to **255.255.255.0**.
+
+   :::image type="content" source="../media/tutorial-install-components/idrac-network-settings-screen-v2.png" alt-text="Screenshot that shows the static subnet mask in iDRAC settings.":::
+
+1. Select **Back** > **Finish**.
+
+**To configure the Dell BIOS**:
+
+This procedure describes how to update the Dell PowerEdge R350 configuration for your OT deployment.
+
+Configure the appliance BIOS only if you didn't purchase your appliance from Arrow, or if you have an appliance, but don't have access to the XML configuration file.
+
+1. Access the appliance's BIOS directly by using a keyboard and screen, or use iDRAC.
+
+   - If the appliance isn't a Defender for IoT appliance, open a browser and go to the IP address configured beforehand. Sign in with the Dell default administrator privileges. Use **root** for the username and **calvin** for the password.
+
+   - If the appliance is a Defender for IoT appliance, sign in by using **XXX** for the username and **XXX** for the password.
+
+1. After you access the BIOS, go to **Device Settings**.
+
+1. Choose the RAID-controlled configuration by selecting **Integrated RAID controller 1: Dell PERC\<PERC H755 Adapter\> Configuration Utility**.
+
+1. Select **Configuration Management**.
+
+1. Select **Create Virtual Disk**.
+
+1. In the **Select RAID Level** field, select **RAID10**. In the **Virtual Disk Name** field, enter **ROOT** and select **Physical Disks**.
+
+1. Select **Check All** and then select **Apply Changes**
+
+1. Select **Ok**.
+
+1. Scroll down and select **Create Virtual Disk**.
+
+1. Select the **Confirm** check box and select **Yes**.
+
+1. Select **OK**.
+
+1. Return to the main screen and select **System BIOS**.
+
+1. Select **Boot Settings**.
+
+1. For the **Boot Mode** option, select **UEFI**.
+
+1. Select **Back**, and then select **Finish** to exit the BIOS settings.
+
+### Install Defender for IoT software on the Dell PowerEdge R350
+
+This procedure describes how to install Defender for IoT software on the Dell PowerEdge R350.
+
+The installation process takes about 20 minutes. After the installation, the system restarts several times.
+
+**To install the software**:
+
+1. Verify that the version media is mounted to the appliance in one of the following ways:
+
+   - Connect an external CD or disk-on-key that contains the sensor software you downloaded from the Azure portal.
+
+   - Mount the ISO image by using iDRAC. After signing in to iDRAC, select the virtual console, and then select **Virtual Media**.
+
+1. In the **Map CD/DVD** section, select **Choose File**.
+
+1. Choose the version ISO image file for this version from the dialog box that opens.
+
+1. Select the **Map Device** button.
+
+   :::image type="content" source="../media/tutorial-install-components/mapped-device-on-virtual-media-screen-v2.png" alt-text="Screenshot that shows a mapped device.":::
+
+1. The media is mounted. Select **Close**.
+
+1. Start the appliance. When you're using iDRAC, you can restart the servers by selecting the **Console Control** button. Then, on the **Keyboard Macros**, select the **Apply** button, which starts the Ctrl+Alt+Delete sequence.
+
+1. Continue by installing OT sensor or on-premises management software. For more information, see [Defender for IoT software installation](../how-to-install-software.md).
+-->
+## Next steps
+
+Continue learning about the 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/dell-poweredge-r360-e1800.md

@@ -32,6 +32,8 @@ landingContent:
             url: hpe-proliant-dl20-gen-11.md
           - text: Dell Edge 5200 (Rugged MIL-STD-810G)
             url: dell-edge-5200.md
+          - text: Dell PowerEdge R360 
+            url: dell-poweredge-r360-e1800.md
           - text: Dell PowerEdge R350 
             url: dell-poweredge-r350-e1800.md