Merge pull request #294681 from MicrosoftDocs/main

Taojunshen · web-flow · commit 5380854aa39c · 2025-02-15T02:00:25.000+08:00
2/14/2025 AM Publish
diff --git a/articles/azure-functions/functions-create-first-java-gradle.md b/articles/azure-functions/functions-create-first-java-gradle.md
@@ -20,7 +20,7 @@ This article shows you how to build and publish a Java function project to Azure
 
 To develop functions using Java, you must have the following installed:
 
-- [Java Developer Kit](/azure/developer/java/fundamentals/java-support-on-azure), version 8, 11, 17 or 21. (Java 21 is currently supported in preview on Linux only)
+- [Java Developer Kit](/azure/developer/java/fundamentals/java-support-on-azure), version 8, 11, 17 or 21. (Java 21 is currently supported on Linux only)
 - [Azure CLI]
 - [Azure Functions Core Tools](./functions-run-local.md#v2) version 2.6.666 or above
 - [Gradle](https://gradle.org/), version 6.8 and above
diff --git a/articles/azure-functions/functions-create-maven-intellij.md b/articles/azure-functions/functions-create-maven-intellij.md
@@ -24,7 +24,7 @@ Specifically, this article shows you:
 ## Prerequisites
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio).
-- An [Azure supported Java Development Kit (JDK)](/azure/developer/java/fundamentals/java-support-on-azure), version 8, 11, 17 or 21. (Java 21 is currently only supported in preview on Linux only)
+- An [Azure supported Java Development Kit (JDK)](/azure/developer/java/fundamentals/java-support-on-azure), version 8, 11, 17 or 21. (Java 21 is currently supported on Linux only)
 - An [IntelliJ IDEA](https://www.jetbrains.com/idea/download/) Ultimate Edition or Community Edition installed
 - [Maven 3.5.0+](https://maven.apache.org/download.cgi)
 - Latest [Function Core Tools](https://github.com/Azure/azure-functions-core-tools)
diff --git a/articles/azure-resource-manager/bicep/bicep-functions-string.md b/articles/azure-resource-manager/bicep/bicep-functions-string.md
@@ -3,7 +3,7 @@ title: Bicep functions - string
 description: Describes the functions to use in a Bicep file to work with strings.
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 02/14/2025
 ---
 
 # String functions for Bicep
@@ -543,7 +543,7 @@ Unique scoped to deployment for a resource group
 guid(resourceGroup().id, deployment().name)
 ```
 
-The `guid` function implements the algorithm from [RFC 4122 §4.3](https://www.ietf.org/rfc/rfc4122.txt). The original source can be found in [GuidUtility](https://github.com/LogosBible/Logos.Utility/blob/e7fc45123da090b8cf34da194a1161ed6a34d20d/src/Logos.Utility/GuidUtility.cs) with some modifications.
+The `guid` function implements the algorithm from [RFC 4122 §4.3](https://www.ietf.org/rfc/rfc4122.txt). The original source can be found in [GuidUtility](https://github.com/LogosBible/Logos.Utility/blob/e7fc45123da090b8cf34da194a1161ed6a34d20d/src/Logos.Utility/GuidUtility.cs) with some modifications. In the `guid()` function implementation, the `namespaceId` is set to `11fb06fb-712d-4ddd-98c7-e71bbd588830`, and the `version` is set to `5`. The value is generated by converting each parameter of the `guid()` function to a string and concatenating them with `-` as delimiters.
 
 ### Return value
 
diff --git a/articles/azure-resource-manager/templates/template-functions-string.md b/articles/azure-resource-manager/templates/template-functions-string.md
@@ -458,7 +458,7 @@ Unique scoped to deployment for a resource group
 "[guid(resourceGroup().id, deployment().name)]"
 ```
 
-The `guid` function implements the algorithm from [RFC 4122 §4.3](https://www.ietf.org/rfc/rfc4122.txt). The original source can be found in [GuidUtility](https://github.com/LogosBible/Logos.Utility/blob/e7fc45123da090b8cf34da194a1161ed6a34d20d/src/Logos.Utility/GuidUtility.cs) with some modifications.
+The `guid` function implements the algorithm from [RFC 4122 §4.3](https://www.ietf.org/rfc/rfc4122.txt). The original source can be found in [GuidUtility](https://github.com/LogosBible/Logos.Utility/blob/e7fc45123da090b8cf34da194a1161ed6a34d20d/src/Logos.Utility/GuidUtility.cs) with some modifications. In the `guid()` function implementation, the `namespaceId` is set to `11fb06fb-712d-4ddd-98c7-e71bbd588830`, and the `version` is set to `5`. The value is generated by converting each parameter of the `guid()` function to a string and concatenating them with `-` as delimiters.
 
 ### Return value
 
diff --git a/articles/communication-services/concepts/numbers/phone-number-management-for-sweden.md b/articles/communication-services/concepts/numbers/phone-number-management-for-sweden.md
@@ -45,16 +45,19 @@ More details on eligible subscription types are as follows:
 ## Azure subscription billing locations where Sweden phone numbers are available
 | Country/Region |
 | :---------- |
-|Sweden|
+|United States|
+|Canada|
+|United Kingdom|
 |Denmark|
 |Ireland|
 |Italy|
-|Puerto Rico|
-|United States|
-|United Kingdom|
-|Canada|
-|Japan|
+|Sweden|
+|France|
+|Spain|
+|Netherlands|
+|Germany|
 |Australia|
+|Japan|
 
 [!INCLUDE [Azure Prepayment](../../includes/azure-prepayment.md)]
 
diff --git a/articles/iot-central/core/quick-deploy-iot-central.md b/articles/iot-central/core/quick-deploy-iot-central.md
@@ -3,7 +3,7 @@ title: Quickstart - Connect a device to Azure IoT Central
 description: In this quickstart, you learn how to connect your first device to a new IoT Central application. This quickstart uses a smartphone app as an IoT device.
 author: dominicbetts
 ms.author: dobett
-ms.date: 03/01/2024
+ms.date: 02/14/2025
 ms.topic: quickstart
 ms.service: azure-iot-central
 services: iot-central
diff --git a/articles/iot/iot-phone-app-how-to.md b/articles/iot/iot-phone-app-how-to.md
@@ -5,7 +5,7 @@ author: dominicbetts
 ms.service: azure-iot
 services: iot
 ms.topic: how-to
-ms.date: 02/28/2024
+ms.date: 02/14/2025
 ms.author: dobett
 
 ---
@@ -136,7 +136,7 @@ To view the data the device is sending in your IoT Central application:
 1. Sign in to your IoT Central application and navigate to the **Devices** page. Your device is automatically assigned to the **Smartphone** device template.
 
     > [!TIP]
-    > You may need to refresh the page in your web browser to see when the device is assigned to the **Smartphone** device template.
+    > You might need to refresh the page in your web browser to see when the device is assigned to the **Smartphone** device template.
 
 1. On the list of devices, click on the device name and then select **Overview**. The **Overview** page shows the telemetry from the smartphone sensors:
 
diff --git a/articles/iot/iot-sdks.md b/articles/iot/iot-sdks.md
@@ -6,7 +6,7 @@ ms.author: dobett
 ms.service: azure-iot
 services: iot
 ms.topic: conceptual
-ms.date: 02/28/2024
+ms.date: 02/14/2025
 
 ---
 
diff --git a/articles/iot/tutorial-connect-device.md b/articles/iot/tutorial-connect-device.md
@@ -3,7 +3,7 @@ title: Tutorial - Connect IoT Plug and Play sample device code to Azure IoT Hub
 description: Tutorial - Build and run IoT Plug and Play sample device code (C, C#, Java, JavaScript, or Python) on Linux or Windows that connects to an IoT hub. Use the Azure IoT explorer tool to view the information sent by the device to the hub.
 author: dominicbetts
 ms.author: dobett
-ms.date: 1/23/2024
+ms.date: 02/14/2025
 ms.topic: tutorial
 ms.service: azure-iot
 ms.custom: devx-track-extended-java, devx-track-js, devx-track-python, linux-related-content
diff --git a/articles/reliability/availability-zones-overview.md b/articles/reliability/availability-zones-overview.md
@@ -58,6 +58,8 @@ For example, subscription A may have physical zone 1 mapped to logical zone 2, w
 
 To understand the mapping between logical and physical zones for your subscription, use the [List Locations Azure Resource Manager API](/rest/api/resources/subscriptions/list-locations). You can use the [Azure CLI](/cli/azure/install-azure-cli) or [Azure PowerShell](/powershell/azure/what-is-azure-powershell) to retrieve the information from the API.
 
+To compare zone mapping for resilient solutions that span multiple subscriptions, use the dedicated ARM API [checkZonePeers](/rest/api/resources/subscriptions/check-zone-peers). To use the `checkZonePeers` API, the feature "Microsoft.Resources/AvailabilityZonePeering" needs to be enabled. For more information about how to enable features, see [Register features in Azure subscription](/azure/azure-resource-manager/management/preview-features).
+
 # [CLI](#tab/azure-cli)
 
 ```azurecli
diff --git a/articles/sentinel/microsoft-sentinel-defender-portal.md b/articles/sentinel/microsoft-sentinel-defender-portal.md
@@ -32,8 +32,9 @@ The following table describes the new or improved capabilities available in the
 | Capabilities      | Description              |
 | ----------------- | ------------------------ |
 | Advanced hunting  | Query from a single portal across different data sets to make hunting more efficient and remove the need for context-switching. Use Security Copilot to help generate your KQL. View and query all data including data from Microsoft security services and Microsoft Sentinel. Use all your existing Microsoft Sentinel workspace content, including queries and functions.<br><br>  For more information, see the following articles:<br>- [Advanced hunting in the Microsoft Defender portal](https://go.microsoft.com/fwlink/p/?linkid=2264410)<br>- [Security Copilot in advanced hunting](/defender-xdr/advanced-hunting-security-copilot) |
-| SOC optimizations   | Get high-fidelity and actionable recommendations to help you identify areas to:<br>- Reduce costs <br>- Add security controls<br>- Add missing data<br>SOC optimizations are available in the Defender and Azure portals, are tailored to your environment, and are based on your current coverage and threat landscape.  <br><br>For more information, see the following articles:<br>- [Optimize your security operations](soc-optimization/soc-optimization-access.md) <br>- [Use SOC optimizations programmatically](soc-optimization/soc-optimization-api.md)<br>- [SOC optimization reference of recommendations](soc-optimization/soc-optimization-reference.md)  |
+| Case management | Manage SecOps cases natively in the Defender portal without losing security context. Define your own case workflow with custom status values. Assign tasks to collaborators and configure due dates. Handle escalations and complex cases by linking multiple incidents to a case.</br></br>For more information, see [Manage cases natively in Microsoft's unified security operations platform](/unified-secops-platform/cases-overview).
 | Microsoft Copilot in Microsoft Defender | When investigating incidents in the Defender portal, <br>- [Summarize incidents](/defender-xdr/security-copilot-m365d-incident-summary) <br>- [Analyze scripts](/defender-xdr/security-copilot-m365d-script-analysis)<br>- [Analyze files](/defender-xdr/copilot-in-defender-file-analysis)<br>- [Create incident reports](/defender-xdr/security-copilot-m365d-create-incident-report) <br><br>When hunting for threats in advanced hunting, create ready-to-run KQL queries by using the query assistant. For more information, see [Microsoft Security Copilot in advanced hunting](/defender-xdr/advanced-hunting-security-copilot).|
+| SOC optimizations   | Get high-fidelity and actionable recommendations to help you identify areas to:<br>- Reduce costs <br>- Add security controls<br>- Add missing data<br>SOC optimizations are available in the Defender and Azure portals, are tailored to your environment, and are based on your current coverage and threat landscape.  <br><br>For more information, see the following articles:<br>- [Optimize your security operations](soc-optimization/soc-optimization-access.md) <br>- [Use SOC optimizations programmatically](soc-optimization/soc-optimization-api.md)<br>- [SOC optimization reference of recommendations](soc-optimization/soc-optimization-reference.md)  |
 
 The following table describes the additional capabilities available in the Defender portal with the integration of Microsoft Sentinel and Microsoft Defender XDR as part of Microsoft's unified security operations platform. 
 
diff --git a/includes/iot-pnp-clean-resources-short.md b/includes/iot-pnp-clean-resources-short.md
@@ -3,7 +3,7 @@ author: dominicbetts
 ms.author: dominicbetts
 ms.service: azure-iot
 ms.topic: include
-ms.date: 11/17/2022
+ms.date: 02/14/2025
 ---
 
 ## Clean up resources
diff --git a/includes/iot-pnp-connect-device-c.md b/includes/iot-pnp-connect-device-c.md
@@ -3,7 +3,7 @@ author: dominicbetts
 ms.author: dobett
 ms.service: azure-iot
 ms.topic: include
-ms.date: 11/17/2022
+ms.date: 02/14/2025
 ---
 
 This tutorial shows you how to build a sample IoT Plug and Play device application, connect it to your IoT hub, and use the Azure IoT explorer tool to view the telemetry it sends. The sample application is written in C and is included in the Azure IoT device SDK for C. A solution builder can use the Azure IoT explorer tool to understand the capabilities of an IoT Plug and Play device without the need to view any device code.
@@ -14,7 +14,7 @@ This tutorial shows you how to build a sample IoT Plug and Play device applicati
 
 [!INCLUDE [iot-pnp-prerequisites](iot-pnp-prerequisites.md)]
 
-You can run this tutorial on Linux or Windows. The shell commands in this tutorial follow the Linux convention for path separators '`/`', if you're following along on Windows be sure to swap these separators for '`\`'.
+You can run this tutorial on Linux or Windows. The shell commands in this tutorial follow the Linux convention for path separators `/`, if you're following along on Windows be sure to swap these separators for `\`.
 
 The prerequisites differ by operating system:
 
@@ -31,7 +31,7 @@ sudo apt-get update
 sudo apt-get install -y git cmake build-essential curl libcurl4-openssl-dev libssl-dev uuid-dev
 ```
 
-Verify the version of `cmake` is above **2.8.12** and the version of **GCC** is above **4.4.7**.
+Verify the version of `cmake` is **2.8.12** or greater and the version of **GCC** is **4.4.7** or greater.
 
 ```sh
 cmake --version
@@ -96,7 +96,7 @@ You can build and run the code using Visual Studio or `cmake` at the command lin
 1. To trace the code execution in Visual Studio, add a breakpoint to the `main` function in the *pnp_simple_thermostat.c* file.
 1. You can now run and debug the sample from the **Debug** menu.
 
-The device is now ready to receive commands and property updates, and has started sending telemetry data to the hub. Keep the sample running as you complete the next steps.
+The device is now ready to receive commands and property updates, and is sending telemetry data to the hub. Keep the sample running as you complete the next steps.
 
 ### Use cmake to build the code
 
@@ -142,7 +142,7 @@ cd iothub_client\samples\pnp\pnp_simple_thermostat\Debug
 > [!TIP]
 > To trace the code execution in Visual Studio on Windows, add a break point to the `main` function in the _pnp_simple_thermostat.c_ file.
 
-The device is now ready to receive commands and property updates, and has started sending telemetry data to the hub. Keep the sample running as you complete the next steps.
+The device is now ready to receive commands and property updates, and is sending telemetry data to the hub. Keep the sample running as you complete the next steps.
 
 ## Use Azure IoT explorer to validate the code
 
diff --git a/includes/iot-pnp-connect-device-csharp.md b/includes/iot-pnp-connect-device-csharp.md
@@ -3,7 +3,7 @@ author: dominicbetts
 ms.author: dobett
 ms.service: azure-iot
 ms.topic: include
-ms.date: 11/17/2022
+ms.date: 02/14/2025
 ---
 
 This tutorial shows you how to build a sample IoT Plug and Play device application, connect it to your IoT hub, and use the Azure IoT explorer tool to view the telemetry it sends. The sample application is written in C# and is included in the Azure IoT SDK for C#. A solution builder can use the Azure IoT explorer tool to understand the capabilities of an IoT Plug and Play device without the need to view any device code.
@@ -14,7 +14,7 @@ This tutorial shows you how to build a sample IoT Plug and Play device applicati
 
 [!INCLUDE [iot-pnp-prerequisites](iot-pnp-prerequisites.md)]
 
-You can run this tutorial on Linux or Windows. The shell commands in this tutorial follow the Linux convention for path separators '`/`', if you're following along on Windows be sure to swap these separators for '`\`'.
+You can run this tutorial on Linux or Windows. The shell commands in this tutorial follow the Linux convention for path separators `/`, if you're following along on Windows be sure to swap these separators for `\`.
 
 * The latest [.NET SDK](https://dotnet.microsoft.com/download) for your platform.
 * [Git](https://git-scm.com/downloads).
@@ -46,7 +46,7 @@ To run the sample, run the following command:
 dotnet run
 ```
 
-The device is now ready to receive commands and property updates, and has started sending telemetry data to the hub. Keep the sample running as you complete the next steps.
+The device is now ready to receive commands and property updates, and is sending telemetry data to the hub. Keep the sample running as you complete the next steps.
 
 ## Use Azure IoT explorer to validate the code
 
diff --git a/includes/iot-pnp-connect-device-java.md b/includes/iot-pnp-connect-device-java.md
@@ -3,7 +3,7 @@ author: dominicbetts
 ms.author: dobett
 ms.service: azure-iot
 ms.topic: include
-ms.date: 11/17/2022
+ms.date: 02/14/2025
 ---
 
 This tutorial shows you how to build a sample IoT Plug and Play device application, connect it to your IoT hub, and use the Azure IoT explorer tool to view the telemetry it sends. The sample application is written in Java and is included in the Azure IoT device SDK for Java. A solution builder can use the Azure IoT explorer tool to understand the capabilities of an IoT Plug and Play device without the need to view any device code.
@@ -14,7 +14,7 @@ This tutorial shows you how to build a sample IoT Plug and Play device applicati
 
 [!INCLUDE [iot-pnp-prerequisites](iot-pnp-prerequisites.md)]
 
-You can run this tutorial on Linux or Windows. The shell commands in this tutorial follow the Linux convention for path separators '`/`', if you're following along on Windows be sure to swap these separators for '`\`'.
+You can run this tutorial on Linux or Windows. The shell commands in this tutorial follow the Linux convention for path separators `/`, if you're following along on Windows be sure to swap these separators for `\`.
 
 To complete this tutorial, install the following software in your local development environment:
 
@@ -52,7 +52,7 @@ From the */device/iot-device-samples/pnp-device-sample/thermostat-device-sample*
 mvn exec:java -Dexec.mainClass="samples.com.microsoft.azure.sdk.iot.device.Thermostat"
 ```
 
-The device is now ready to receive commands and property updates, and has started sending telemetry data to the hub. Keep the sample running as you complete the next steps.
+The device is now ready to receive commands and property updates, and is sending telemetry data to the hub. Keep the sample running as you complete the next steps.
 
 ## Use Azure IoT explorer to validate the code
 
diff --git a/includes/iot-pnp-connect-device-node.md b/includes/iot-pnp-connect-device-node.md
@@ -3,7 +3,7 @@ author: dominicbetts
 ms.author: dobett
 ms.service: azure-iot
 ms.topic: include
-ms.date: 11/17/2022
+ms.date: 02/14/2025
 ---
 
 This tutorial shows you how to build a sample IoT Plug and Play device application, connect it to your IoT hub, and use the Azure IoT explorer tool to view the telemetry it sends. The sample application is written in Node.js and is included in the Azure IoT device SDK for Node.js. A solution builder can use the Azure IoT explorer tool to understand the capabilities of an IoT Plug and Play device without the need to view any device code.
@@ -14,7 +14,7 @@ This tutorial shows you how to build a sample IoT Plug and Play device applicati
 
 [!INCLUDE [iot-pnp-prerequisites](iot-pnp-prerequisites.md)]
 
-You can run this tutorial on Linux or Windows. The shell commands in this tutorial follow the Linux convention for path separators '`/`', if you're following along on Windows be sure to swap these separators for '`\`'.
+You can run this tutorial on Linux or Windows. The shell commands in this tutorial follow the Linux convention for path separators `/`, if you're following along on Windows be sure to swap these separators for `\`.
 
 To complete this tutorial, you need Node.js on your development machine. You can download the latest recommended version for multiple platforms from [nodejs.org](https://nodejs.org).
 
@@ -74,7 +74,7 @@ Run the sample application to simulate an IoT Plug and Play device that sends te
 node pnp_simple_thermostat.js
 ```
 
-You see the following output, indicating the device has begun sending telemetry data to the hub, and is now ready to receive commands and property updates.
+You see the following output, indicating the device is sending telemetry data to the hub, and is now ready to receive commands and property updates.
 
 ![Device confirmation messages](media/iot-pnp-connect-device-node/device-confirmation-node.png)
 
diff --git a/includes/iot-pnp-connect-device-python.md b/includes/iot-pnp-connect-device-python.md
@@ -3,7 +3,7 @@ author: dominicbetts
 ms.author: dobett
 ms.service: azure-iot
 ms.topic: include
-ms.date: 11/17/2022
+ms.date: 02/14/2025
 ---
 
 This tutorial shows you how to build a sample IoT Plug and Play device application, connect it to your IoT hub, and use the Azure IoT explorer tool to view the telemetry it sends. The sample application is written for Python and is included in the Azure IoT Hub Device SDK for Python. A solution builder can use the Azure IoT explorer tool to understand the capabilities of an IoT Plug and Play device without the need to view any device code.
@@ -28,7 +28,7 @@ In your local Python environment, install the package as follows:
 pip install azure-iot-device
 ```
 
-Clone the Python SDK IoT repository: 
+Clone the Python SDK IoT repository:
 
 ```cmd/sh
 git clone --branch v2 https://github.com/Azure/azure-iot-sdk-python
