diff --git a/platform_versioned_docs/version-23.3.0/faqs.mdx b/platform_versioned_docs/version-23.3.0/faqs.mdx
index 78da6902..5de39129 100644
--- a/platform_versioned_docs/version-23.3.0/faqs.mdx
+++ b/platform_versioned_docs/version-23.3.0/faqs.mdx
@@ -807,6 +807,7 @@ The default Azure Batch implementation in Seqera Platform uses a single pool for
 1. Create two Batch pools in Azure:
     - One Dedicated
     - One [Low priority](https://learn.microsoft.com/en-us/azure/batch/batch-spot-vms#differences-between-spot-and-low-priority-vms).
+    - **Note**: Both pools must meet the requirements of a pre-existing pool as detailed in the [Nextflow documentation](https://www.nextflow.io/docs/latest/azure.html#requirements-on-pre-existing-named-pools).
 2. Create a manual [Azure Batch](./compute-envs/azure-batch.mdx#manual) compute environment in Seqera Platform.
 3. In **Compute pool name** (step 10 in the guide linked above), specify your dedicated Batch pool.
 4. Specify the Low priority pool using the `process.queue` [directive](https://www.nextflow.io/docs/latest/process.html#queue) in your `nextflow.config` file (either via the launch form, or your pipeline repository's `nextflow.config` file).
diff --git a/platform_versioned_docs/version-23.4.0/faqs.mdx b/platform_versioned_docs/version-23.4.0/faqs.mdx
index 362eaa33..c5d0f5ab 100644
--- a/platform_versioned_docs/version-23.4.0/faqs.mdx
+++ b/platform_versioned_docs/version-23.4.0/faqs.mdx
@@ -807,6 +807,7 @@ The default Azure Batch implementation in Seqera Platform uses a single pool for
 1. Create two Batch pools in Azure:
     - One Dedicated
     - One [Low priority](https://learn.microsoft.com/en-us/azure/batch/batch-spot-vms#differences-between-spot-and-low-priority-vms).
+    - **Note**: Both pools must meet the requirements of a pre-existing pool as detailed in the [Nextflow documentation](https://www.nextflow.io/docs/latest/azure.html#requirements-on-pre-existing-named-pools).
 2. Create a manual [Azure Batch](./compute-envs/azure-batch.mdx#manual) compute environment in Seqera Platform.
 3. In **Compute pool name** (step 10 in the guide linked above), specify your dedicated Batch pool.
 4. Specify the Low priority pool using the `process.queue` [directive](https://www.nextflow.io/docs/latest/process.html#queue) in your `nextflow.config` file (either via the launch form, or your pipeline repository's `nextflow.config` file).
diff --git a/platform_versioned_docs/version-24.1.1/faqs.mdx b/platform_versioned_docs/version-24.1.1/faqs.mdx
index 362eaa33..c5d0f5ab 100644
--- a/platform_versioned_docs/version-24.1.1/faqs.mdx
+++ b/platform_versioned_docs/version-24.1.1/faqs.mdx
@@ -807,6 +807,7 @@ The default Azure Batch implementation in Seqera Platform uses a single pool for
 1. Create two Batch pools in Azure:
     - One Dedicated
     - One [Low priority](https://learn.microsoft.com/en-us/azure/batch/batch-spot-vms#differences-between-spot-and-low-priority-vms).
+    - **Note**: Both pools must meet the requirements of a pre-existing pool as detailed in the [Nextflow documentation](https://www.nextflow.io/docs/latest/azure.html#requirements-on-pre-existing-named-pools).
 2. Create a manual [Azure Batch](./compute-envs/azure-batch.mdx#manual) compute environment in Seqera Platform.
 3. In **Compute pool name** (step 10 in the guide linked above), specify your dedicated Batch pool.
 4. Specify the Low priority pool using the `process.queue` [directive](https://www.nextflow.io/docs/latest/process.html#queue) in your `nextflow.config` file (either via the launch form, or your pipeline repository's `nextflow.config` file).