Merge pull request #297714 from MicrosoftDocs/main

ttorble · web-flow · commit fba0df0a6169 · 2025-04-07T12:18:44.000+01:00
Publish to live, Monday 4 AM PST, 4/7
diff --git a/articles/automation/automation-linux-hrw-install.md b/articles/automation/automation-linux-hrw-install.md
@@ -4,7 +4,7 @@ description: This article tells how to install an agent-based  Hybrid Runbook Wo
 services: automation
 ms.subservice: process-automation
 ms.custom: linux-related-content
-ms.date: 09/09/2024
+ms.date: 04/07/2025
 ms.topic: how-to
 ms.service: azure-automation
 ---
@@ -73,7 +73,7 @@ The minimum requirements for a Linux system and user Hybrid Runbook Worker are:
 | **Required package** | **Description** | **Minimum version**|
 |--------------------- | --------------------- | -------------------|
 |Glibc |GNU C Library| 2.5-12 |
-|Openssl| OpenSSL Libraries | 1.0 (TLS 1.1 and TLS 1.2 are supported)|
+|OpenSSL| OpenSSL Libraries | 1.0 (TLS 1.1 and TLS 1.2 are supported)|
 |Curl | cURL web client | 7.15.5|
 |Python-ctypes | Foreign function library for Python| Python 2.x or Python 3.x are required |
 |PAM | Pluggable Authentication Modules|
diff --git a/articles/automation/extension-based-hybrid-runbook-worker-install.md b/articles/automation/extension-based-hybrid-runbook-worker-install.md
@@ -4,7 +4,7 @@ description: This article provides information about deploying the extension-bas
 services: automation
 ms.subservice: process-automation
 ms.custom: devx-track-azurepowershell, devx-track-azurecli, devx-track-bicep, linux-related-content
-ms.date: 02/27/2025
+ms.date: 04/07/2025
 ms.topic: how-to
 #Customer intent: As a developer, I want to learn about extension so that I can efficiently deploy Hybrid Runbook Workers.
 ms.service: azure-automation
@@ -52,7 +52,7 @@ Azure Automation stores and manages runbooks and then delivers them to one or mo
 | Required package | Description | Minimum version |
 |--------------------- | --------------------- | ------------------- |
 | Glibc |GNU C Library | 2.5-12 |
-| Openssl | OpenSSL Libraries | 1.0 (TLS 1.1 and TLS 1.2 are supported) |
+| OpenSSL | OpenSSL Libraries | 1.0 (TLS 1.1 and TLS 1.2 are supported) |
 | Curl | cURL web client | 7.15.5 |
 | Python-ctypes | Foreign function library for Python | Python 2.x or Python 3.x are required |
 | PAM | Pluggable Authentication Modules |       |
diff --git a/articles/automation/migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md b/articles/automation/migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md
@@ -3,7 +3,7 @@ title: Migrate an existing agent-based hybrid workers to extension-based-workers
 description: This article provides information on how to migrate an existing agent-based hybrid worker to extension based workers.
 services: automation
 ms.subservice: process-automation
-ms.date: 02/27/2025
+ms.date: 04/07/2025
 ms.custom: devx-track-azurecli, devx-track-bicep, devx-track-azurepowershell
 ms.topic: how-to
 #Customer intent: As a developer, I want to learn about extension so that I can efficiently migrate agent based hybrid workers to extension based workers.
@@ -69,7 +69,7 @@ The purpose of the Extension-based approach is to simplify the installation and
 | Required package | Description | Minimum version |
 |--------------------- | --------------------- | ------------------- |
 | Glibc |GNU C Library | 2.5-12 |
-| Openssl | OpenSSL Libraries | 1.0 (TLS 1.1 and TLS 1.2 are supported) |
+| OpenSSL | OpenSSL Libraries | 1.0 (TLS 1.1 and TLS 1.2 are supported) |
 | Curl | cURL web client | 7.15.5 |
 | Python-ctypes | Foreign function library for Python | Python 2.x or Python 3.x are required |
 | PAM | Pluggable Authentication Modules |       |
diff --git a/articles/azure-maps/release-notes-drawing-tools-module.md b/articles/azure-maps/release-notes-drawing-tools-module.md
@@ -4,7 +4,7 @@ titleSuffix: Microsoft Azure Maps
 description: Release notes for the Azure Maps Drawing Tools Module. 
 author: sinnypan
 ms.author: sipa
-ms.date: 10/25/2023
+ms.date: 11/07/2024
 ms.topic: reference
 ms.service: azure-maps
 ms.subservice: web-sdk
diff --git a/articles/azure-maps/release-notes-indoor-module.md b/articles/azure-maps/release-notes-indoor-module.md
@@ -4,7 +4,7 @@ titleSuffix: Microsoft Azure Maps
 description: Release notes for the Azure Maps Indoor Module. 
 author: sipa
 ms.author: sipa
-ms.date: 3/24/2023
+ms.date: 10/25/2023
 ms.topic: reference
 ms.service: azure-maps
 ms.subservice: web-sdk
diff --git a/articles/azure-maps/release-notes-map-control.md b/articles/azure-maps/release-notes-map-control.md
@@ -4,7 +4,7 @@ titleSuffix: Microsoft Azure Maps
 description: Release notes for the Azure Maps Web SDK. 
 author: sinnypan
 ms.author: sipa
-ms.date: 3/15/2023
+ms.date: 03/24/2025
 ms.topic: reference
 ms.service: azure-maps
 ms.subservice: web-sdk
@@ -16,6 +16,11 @@ This document contains information about new features and other changes to the M
 
 ## v3 (latest)
 
+### [3.6.1] (CDN: April 7, 2025, npm: TBA)
+
+#### Bug fixes
+* Fix the issue where `maxBounds` wasn't included in `map.getCamera()`, causing it to be unset when `setCamera()` is called.
+
 ### [3.6.0] (CDN: February 18, 2025, npm: February 20, 2025)
 
 #### New features
@@ -653,6 +658,7 @@ Stay up to date on Azure Maps:
 > [!div class="nextstepaction"]
 > [Azure Maps Blog]
 
+[3.6.1]: https://www.npmjs.com/package/azure-maps-control/v/3.6.1
 [3.6.0]: https://www.npmjs.com/package/azure-maps-control/v/3.6.0
 [3.5.0]: https://www.npmjs.com/package/azure-maps-control/v/3.5.0
 [3.4.0]: https://www.npmjs.com/package/azure-maps-control/v/3.4.0
diff --git a/articles/azure-maps/release-notes-spatial-module.md b/articles/azure-maps/release-notes-spatial-module.md
@@ -4,7 +4,7 @@ titleSuffix: Microsoft Azure Maps
 description: Release notes for the Azure Maps Spatial IO Module. 
 author: sinnypan
 ms.author: sipa
-ms.date: 5/23/2023
+ms.date: 02/22/2024
 ms.topic: reference
 ms.service: azure-maps
 ms.subservice: web-sdk
diff --git a/articles/backup/backup-azure-database-postgresql-flex.md b/articles/backup/backup-azure-database-postgresql-flex.md
@@ -2,7 +2,7 @@
 title: Configure backup for Azure Database for PostgreSQL - Flexible Server using Azure portal
 description: Learn about how to configure backup for Azure Database for PostgreSQL - Flexible Server using Azure portal. 
 ms.topic: how-to
-ms.date: 02/28/2025
+ms.date: 04/07/2025
 ms.service: azure-backup
 ms.custom:
   - ignite-2024
@@ -36,9 +36,6 @@ To create a backup policy, follow these steps:
 
 4. On the **Schedule + retention** tab, under **Backup schedule**, define the Backup frequency.
 
-   >[!Note]
-   >The **Weekly backup** option is currently available. However, you can schedule the backups on multiple days of the week.
-
 5. Under **Retention rules**, select **Add retention rule**.
 
    :::image type="content" source="./media/backup-azure-database-postgresql-flex/define-backup-schedule.png" alt-text="Screenshot shows how to define the backup schedule in the Backup policy." lightbox="./media/backup-azure-database-postgresql-flex/define-backup-schedule.png":::
diff --git a/articles/backup/quick-backup-postgresql-flexible-server-portal.md b/articles/backup/quick-backup-postgresql-flexible-server-portal.md
@@ -5,7 +5,7 @@ ms.devlang: terraform
 ms.custom:
   - ignite-2024
 ms.topic: quickstart
-ms.date: 02/28/2025
+ms.date: 04/07/2025
 ms.service: azure-backup
 author: jyothisuri
 ms.author: jsuri
@@ -42,9 +42,6 @@ To create a Backup policy for Azure Database for PostgreSQL - Flexible Server, f
 
 4. On the **Schedule + retention** tab, under **Backup schedule**, define the Backup frequency.
 
-   >[!Note]
-   >The **Weekly backup** option is currently available. However, you can schedule the backups on multiple days of the week.
-
 5. Under **Retention rules**, select **Add retention rule**.
 
    :::image type="content" source="./media/backup-azure-database-postgresql-flex/define-backup-schedule.png" alt-text="Screenshot shows how to define the backup schedule in the Backup policy." lightbox="./media/backup-azure-database-postgresql-flex/define-backup-schedule.png":::
diff --git a/articles/business-continuity-center/business-continuity-center-support-matrix.md b/articles/business-continuity-center/business-continuity-center-support-matrix.md
@@ -2,7 +2,7 @@
 title: Azure Business Continuity Center support matrix
 description: Provides a summary of support settings and limitations for the Azure Business Continuity center service.
 ms.topic: reference
-ms.date: 11/19/2024
+ms.date: 04/04/2025
 ms.custom:
   - references_regions
   - ignite-2023
@@ -20,7 +20,7 @@ You can use [Azure Business Continuity Center](business-continuity-center-overvi
 
 ## Supported regions
 
-Azure Business Continuity Center supports all Azure regions.
+Azure Business Continuity Center supports all Azure regions, except Azure Sovereign Clouds (Azure China Cloud and Azure US Government).
 
 ## Supported solutions and datasources
 
diff --git a/articles/cyclecloud/cluster-references/node-nodearray-reference.md b/articles/cyclecloud/cluster-references/node-nodearray-reference.md
@@ -92,7 +92,7 @@ PlacementGroupId | String | If set, this label is used to place this node in a s
 KeyPairLocation | Integer | Where CycleCloud will find a SSH keypair on the local filesystem
 KeepAlive | Boolean | If true, CycleCloud will prevent the termination of this node
 Locker | String | Specify the name of the locker from which to download project specs. See [Use Projects](~/articles/cyclecloud/how-to/projects.md)
-BootDiagnosticsUri | String | Storage URI for boot diagnostics (example: https://mystorageaccount.blob.core.windows.net/), if specified. Storage charges will apply.
+BootDiagnosticsUri | String | Storage URI for boot diagnostics (example: `https://mystorageaccount.blob.core.windows.net/`), if specified. Storage charges will apply.
 HybridBenefit | Boolean | If true, enables "Azure Hybrid Benefit" licensing for Windows VMs
 NetworkSecurityGroupId | String | If given, the full resource id for a Network Security Group to use for this node. Note: this can also be specified as `SecurityGroup` on a [network interface](network-interface-reference.md).
 EnableTerminateNotification (8.2.0+) | Boolean | If true, enables [Terminate Notification](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-terminate-notification) to send events on VM deletion to the VM for local handling. This only applies to scaleset VMs.
diff --git a/articles/defender-for-iot/organizations/alerts.md b/articles/defender-for-iot/organizations/alerts.md
@@ -1,11 +1,11 @@
 ---
 title: Microsoft Defender for IoT alerts
 description: Learn about Microsoft Defender for IoT alerts across the Azure portal and OT network sensors.
-ms.date: 08/06/2023
+ms.date: 04/06/2025
 ms.topic: how-to
 ms.custom: enterprise-iot
 ---
-<!-- should we reassess the order of this article, does it make sesne? Could the flow be better? -->
+
 # Microsoft Defender for IoT alerts
 
 Microsoft Defender for IoT alerts enhance your network security and operations with real-time details about events logged in your network. Alerts are triggered when OT network sensors detect changes or suspicious activity in network traffic that needs your attention.
@@ -34,7 +34,7 @@ While you can view alert details, investigate alert context, and triage and mana
 
 > [!TIP]
 > Any alerts generated from different sensors in the same zone within a 10-minute timeframe, with the same type, status, alert protocol, and associated devices, are listed as a single, unified alert.
-> 
+>
 > - The 10-minute timeframe is based on the alert's *first detection* time. 
 > - The single, unified alert lists all of the sensors that detected the alert. 
 > - Alerts are combined based on the *alert* protocol, and not the device protocol.
diff --git a/articles/defender-for-iot/organizations/release-notes.md b/articles/defender-for-iot/organizations/release-notes.md
@@ -2,7 +2,7 @@
 title: OT monitoring software versions - Microsoft Defender for IoT
 description: This article lists Microsoft Defender for IoT on-premises OT monitoring software versions, including release and support dates and highlights for new features.
 ms.topic: release-notes
-ms.date: 12/19/2023
+ms.date: 04/06/2025
 ---
 
 # OT monitoring software versions
@@ -38,6 +38,7 @@ Cloud features may be dependent on a specific sensor version. Such features are
 | Version / Patch |  Release date | Scope     | Supported until |
 | ------- |  ------------ | ----------- | ------------------- |
 | **25.1** | | | |
+| 25.1.1  |03/2025 | Minor |02/2026 |
 | 25.1.0  |03/2025 | Major |02/2026 |
 | **24.1** | | | |
 | 24.1.9  |03/2025 | Minor |02/2026 |
@@ -96,6 +97,17 @@ To understand whether a feature is supported in your sensor version, check the r
 
 ## Versions 25.1.x
 
+### Version 25.1.1
+
+**Release date**: 04/2025
+
+**Supported until**: 03/2026
+
+This version includes the following updates:
+
+- Bug fixes for stability improvements
+- Enhanced 'Address Scan Detected' alert with port and protocol details for each scanned address, allowing SOC teams to investigate more efficiently without opening the PCAP.
+
 ### Version 25.1.0
 
 **Release date**: 03/2025
diff --git a/articles/expressroute/about-fastpath.md b/articles/expressroute/about-fastpath.md
@@ -111,6 +111,7 @@ The following Azure services are supported:
 > * ExpressRoute FastPath connectivity to Azure Private Link service and Private endpoint deployed in a spoke Virtual Network, peered to the Hub Virtual Network (where the ExpressRoute Virtual Network Gateway is deployed), is supported.
 > * ExpressRoute FastPath supports a maximum of 100-Gbps connectivity to a single availability zone.
 > * Azure Private Link pricing doesn't apply to traffic sent over ExpressRoute FastPath. For more information about pricing, see the [Private Link pricing page](https://azure.microsoft.com/pricing/details/private-link/).
+> * Enabling ExpressRoute FastPath does not prevent access to Azure services on Private Endpoints: reachability remains guaranteed by routing traffic through the ExpressRoute Virtual Network Gateway.
 
 ## Limitations
 
diff --git a/articles/frontdoor/private-link.md b/articles/frontdoor/private-link.md
@@ -66,7 +66,7 @@ The Azure Front Door Private Link feature is region agnostic but for the best la
 
 ### Private endpoint creation
 
-Within a single Azure Front Door profile, if two or more Private Link enabled origins are created with the same set of Private Link, resource ID and group ID, then for all such origins only one private endpoint gets created. Connections to the backend can be enabled using this private endpoint. This setup means you only have to approve the private endpoint once because only one private endpoint gets created. If you create more Private Link enabled origins using the same set of Private Link location, resource ID, and group ID, you don't need to approve anymore private endpoints.
+Within a single Azure Front Door profile, if two or more Private Link enabled origins are created with the same set of resource ID, group ID and region, then for all such origins only one private endpoint gets created. Connections to the backend can be enabled using this private endpoint. This setup means you only have to approve the private endpoint once because only one private endpoint gets created. If you create more Private Link enabled origins using the same set of Private Link location, resource ID, and group ID, you don't need to approve anymore private endpoints.
 
 #### Single private endpoint
 
diff --git a/articles/virtual-desktop/thin-clients.md b/articles/virtual-desktop/thin-clients.md
@@ -30,4 +30,4 @@ The following partners have thin client devices that are approved to use with Az
 
 ## Next steps
 
-Learn more about Windows App at [What is Windows App](/windows-app/overview.md).
+Learn more about Windows App at [What is Windows App](/windows-app/overview).
