Merge pull request #302132 from MicrosoftDocs/main

Merged by Learn.Build PR Management system

Author: learn-build-service-prod[bot]

articles/active-directory-b2c/partner-cloudflare.md

@@ -7,7 +7,7 @@ manager: martinco
 ms.reviewer: kengaderdus
 ms.service: azure-active-directory
 ms.topic: how-to
-ms.date: 01/26/2024
+ms.date: 06/30/2025
 ms.author: gasinh
 ms.subservice: b2c
 
@@ -21,20 +21,19 @@ In this article, you can learn how to configure the [Cloudflare Web Application
 
 ## Prerequisites
 
-To get started, you'll need:
+To get started, you need:
 
-- An Azure subscription 
-  - If you don't have one, you can get an [Azure free account](https://azure.microsoft.com/free/)
-- [An Azure AD B2C tenant](tutorial-create-tenant.md) linked to your Azure subscription
-- A [Cloudflare](https://dash.cloudflare.com/sign-up) account
+- An Azure subscription. If you don't have one, you can get an [Azure free account](https://azure.microsoft.com/free/).
+- [An Azure AD B2C tenant](tutorial-create-tenant.md) linked to your Azure subscription.
+- A [Cloudflare](https://dash.cloudflare.com/sign-up) account.
 
 ## Scenario description
 
 Cloudflare WAF integration includes the following components:
 
-- **Azure AD B2C tenant** – The authorization server that verifies user credentials using the custom policies defined in the tenant. It's known as the identity provider
+- **Azure AD B2C tenant** – The authorization server that verifies user credentials using the custom policies defined in the tenant, known as the identity provider.
 - [**Azure Front Door**](../frontdoor/front-door-overview.md) – Enables custom domains for Azure B2C tenant. Traffic from Cloudflare WAF is routed to Azure Front Door before arriving at Azure AD B2C tenant.
-- **Cloudflare** – The web application firewall that manages traffic sent to the authorization server
+- **Cloudflare** – The web application firewall that manages traffic sent to the authorization server.
 
 ## Integrate with Azure AD B2C
 
@@ -58,6 +57,9 @@ The settings appear in the following image.
 
    ![Screenshot of proxied status.](./media/partner-cloudflare/select-proxied.png)
 
+> [!NOTE]
+> Azure Front Door-managed certificates aren't automatically renewed if your custom domain’s CNAME record points to a DNS record other than the Azure Front Door endpoint’s domain (for example, when using a third-party DNS service like Cloudflare). To renew the certificate in such cases, follow the instructions in the [Renew Azure Front Door-managed certificates](../frontdoor/domain.md#renew-azure-front-door-managed-certificates) article.
+
 ### Configure the Web Application Firewall
 
 Go to your Cloudflare settings, and use the Cloudflare content to [configure the WAF](https://www.cloudflare.com/application-services/products/waf/) and learn about other security tools. 

articles/backup/backup-azure-troubleshoot-blob-backup.md

@@ -2,7 +2,7 @@
 title: Troubleshoot Blob backup and restore issues
 description: In this article, learn about symptoms, causes, and resolutions of Azure Backup failures related to the Azure Blob backups and restore.
 ms.topic: troubleshooting
-ms.date: 06/13/2025
+ms.date: 07/02/2025
 ms.service: azure-backup
 ms.reviewer: geg
 author: jyothisuri
@@ -30,7 +30,7 @@ This article provides troubleshooting information to address issues you encounte
 
 **Error message**: The storage account type isn't supported for backup.
 
-**Recommendation**: Ensure that the storage account you've selected for backup is supported. [Learn more](blob-backup-support-matrix.md?tabs=vaulted-backup#limitations).
+**Recommendation**: Ensure that the storage account you've selected for backup is supported. [Learn more](blob-backup-support-matrix.md?tabs=vaulted-backup#supported-and-unsupported-scenarios-for-azure-blob-backup).
 
 ### UserErrorMaxOrsPolicyExistOnStorageAccount
 **Error code**: `UserErrorMaxOrsPolicyExistOnStorageAccount`

articles/backup/blob-backup-support-matrix.md

@@ -2,7 +2,7 @@
 title: Support matrix for Azure Blobs backup
 description: Provides a summary of support settings and limitations when backing up Azure Blobs.
 ms.topic: reference
-ms.date: 05/12/2025
+ms.date: 07/02/2025
 ms.custom: references_regions, engagement-fy24
 ms.service: azure-backup
 author: jyothisuri
@@ -28,7 +28,7 @@ Vaulted backup for blobs is available in all public cloud regions.
 
 ---
 
-## Limitations
+## Supported and unsupported scenarios for Azure Blob backup
 
 **Choose a backup type**
 
@@ -45,6 +45,7 @@ Operational backup of blobs uses blob point-in-time restore, blob versioning, so
 **Other limitations**:
 
 - If you've deleted a container during the retention period, that container won't be restored with the point-in-time restore operation. If you attempt to restore a range of blobs that includes blobs in a deleted container, the point-in-time restore operation will fail. For more information about protecting containers from deletion, see [Soft delete for containers](../storage/blobs/soft-delete-container-overview.md).
+- Containers with **legal hold** enabled aren't supported.
 - If a blob has moved between the hot and cool tiers in the period between the present moment and the restore point, the blob is restored to its previous tier. Restoring block blobs in the archive tier isn't supported. For example, if a blob in the hot tier was moved to the archive tier two days ago, and a restore operation restores to a point three days ago, the blob isn't restored to the hot tier. To restore an archived blob, first move it out of the archive tier. For more information, see [Rehydrate blob data from the archive tier](../storage/blobs/archive-rehydrate-overview.md).
 - A block that has been uploaded via [Put Block](/rest/api/storageservices/put-block) or [Put Block from URL](/rest/api/storageservices/put-block-from-url), but not committed via [`Put Block List`](/rest/api/storageservices/put-block-list), isn't part of a blob and so isn't restored as part of a restore operation.
 - A blob with an active lease can't be restored. If a blob with an active lease is included in the range of blobs to restore, the restore operation will fail automatically. Break any active leases before starting the restore operation.
@@ -55,6 +56,7 @@ Operational backup of blobs uses blob point-in-time restore, blob versioning, so
 # [Vaulted backup](#tab/vaulted-backup)
 
 - You can back up only block blobs in a *standard general-purpose v2 storage account* using the vaulted backup solution for blobs.
+- Blob vaulted backup is also supported when the storage account has private endpoints.
 - HNS-enabled storage accounts are currently not supported. This includes *ADLS Gen2 accounts*, *accounts using NFS 3.0*, and *SFTP protocols* for blobs.
 - You can take up to five backups per storage account in a day.
 - You can back up storage accounts with *up to 100 containers*, there is no limit on the number of blobs within those containers. You can also select a subset of containers to back up (up to 100 containers).
@@ -72,6 +74,7 @@ Operational backup of blobs uses blob point-in-time restore, blob versioning, so
 
 - Enabling backups isn't supported for the blob container that are configured with native replication using data factory.
 - The protection of  a container that is part of any object replication isn't supported, either as a source or destination. Attempting to back up such a container will result in backup failure.
+- Containers with **legal hold** enabled aren't supported.
 
 
 ---

articles/backup/quick-blob-vaulted-backup-cli.md

@@ -3,7 +3,7 @@ title: Quickstart - Configure vaulted backup for Azure Blobs using Azure CLI
 description: In this Quickstart, learn how to configure vaulted backup for Azure Blobs using Azure CLI.
 ms.devlang: azurecli
 ms.topic: quickstart
-ms.date: 06/17/2025
+ms.date: 07/02/2025
 ms.custom: mvc, devx-track-azurepowershell, mode-api
 author: jyothisuri
 ms.author: jsuri

articles/iot-operations/deploy-iot-ops/howto-upgrade.md

@@ -112,3 +112,7 @@ To ensure zero data loss and high availability during deployment upgrades, the M
 If a failure occurs during the upgrade process, the health manager pod automatically restarts the upgrade process while ensuring no loss of data or connectivity.
 
 Rolling updates can only occur if the MQTT broker is deployed with two or more backend replicas. MQTT broker upgrades aren't supported for single-replica deployments. When you deploy Azure IoT Operations, you specify the number of backend replicas to create in the [az iot ops create](/cli/azure/iot/ops#az-iot-ops-create) command with the `--broker-backend-rf` parameter.
+
+## Supported versions
+
+[!INCLUDE [supported-versions](../includes/supported-versions.md)]

articles/iot-operations/includes/supported-versions.md

@@ -0,0 +1,20 @@
+---
+title: include file
+description: include file with details of currently supported versions
+author: dominicbetts
+ms.topic: include
+ms.date: 06/16/2025
+ms.author: dobett
+---
+
+Microsoft always supports three generally available (GA) versions of Azure IoT Operations at any one time: the latest version, and the two previous minor versions.
+
+Currently, there are only two minor versions available. [Azure support](https://azure.microsoft.com/support/plans) is currently available for the following versions:
+
+- [1.1.x](https://github.com/Azure/azure-iot-operations/releases/tag/v1.1.19) (latest GA version)
+- [1.0.x](https://github.com/Azure/azure-iot-operations/releases/tag/v1.0.9) (previous minor GA version)
+
+> [!IMPORTANT]
+> Previous minor versions don't receive security patches. Always upgrade to the latest version to ensure you have the latest security updates and features.
+
+To verify your current version, see the overview page for your Azure IoT Operations instance in the Azure portal or use the Azure IoT Operations CLI [az iot ops instance show](/cli/azure/iot/ops#az-iot-ops-show) command.

articles/iot-operations/overview-iot-operations.md

@@ -121,6 +121,10 @@ To visualize and analyze sensor data and messages from your devices and assets,
 
 To secure communication between devices and the cloud through isolated network environments based on the ISA-95/Purdue Network architecture, use the Azure IoT Layered Network Management (preview) component.
 
+## Supported versions
+
+[!INCLUDE [supported-versions](includes/supported-versions.md)]
+
 ## Supported environments
 
 [!INCLUDE [supported-environments-table](includes/supported-environments-table.md)]

articles/iot-operations/troubleshoot/iot-operations-faq.yml

@@ -48,6 +48,9 @@ sections:
     - question: |
          Does Azure IoT Operations support connecting via proxy servers? 
       answer: Azure IoT Operations supports connecting via passthrough proxies that don't require proxy authentication. Proxies that require authentication or can inspect encrypted traffic are currently not supported. 
+    - question: |
+         What versions of Azure IoT Operations are supported? 
+      answer: Microsoft supports the three most recent minor versions of Azure IoT Operations. To learn more, see [Supported versions](../overview-iot-operations.md#supported-versions).
     - question: |
          Does Azure IoT Operations support Azure Private Link and private endpoints? 
       answer: Azure IoT Operations currently does not support Azure Private Link and private endpoints. 

articles/storage-mover/TOC.yml

@@ -7,6 +7,8 @@ items:
     href: service-overview.md
   - name: Cloud migration basics
     href: migration-basics.md
+  - name: Get started with cloud-to-cloud migration
+    href: cloud-to-cloud-migration.md
   expanded: true
 - name: Concepts
   items: