> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/library-preparation/dna-enrichment-based-library-prep/library-preparation-dna-enrichment-based-library-prep-reference_material-list/000007483.md).

# Illumina DNA Prep with Enrichment third-party probe panel requirements

Illumina DNA Prep with Enrichment (formerly Nextera Flex for Enrichment) is a targeted enrichment workflow that is compatible with both Illumina and third-party enrichment panels.

**Third-Party DNA Probe Panel Requirements**

If using third-party biotinylated DNA probe panels with the Illumina DNA Prep with Enrichment workflow, the enrichment panels must meet the following criteria.

* 80 bp or 120 bp probe length
* Between 500 and 675,000 probes
* Single-stranded or double-stranded DNA probes
* Total probe input of ≥ 3 pmols for enrichment at plexities from 1-plex to 12-plex

Follow the [Illumina DNA Prep with Enrichment Reference Guide](https://support.illumina.com/sequencing/sequencing_kits/illumina-dna-prep-with-enrichment/documentation.html) when using DNA probes.

The use of third-party probe panels with Illumina DNA Prep with Enrichment may require additional optimization and validation, because third-party probe panels have not been validated by Illumina.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                              |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #7483), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000007483%20-%20Library%20Preparation%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledge.illumina.com/library-preparation/dna-enrichment-based-library-prep/library-preparation-dna-enrichment-based-library-prep-reference_material-list/000007483.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
