diff --git a/docs/pipelines/release/artifacts.md b/docs/pipelines/release/artifacts.md
index 70a71f0bec5..92bc42ad56c 100644
--- a/docs/pipelines/release/artifacts.md
+++ b/docs/pipelines/release/artifacts.md
@@ -157,6 +157,12 @@ The following features are available when using Azure Artifacts as an artifact s
 | Work items and commits | Link work items to see them displayed in the release details. Commits will be shown when using Git or TFVC.|
 | [Artifact download](#artifact-download) | By default, pipeline artifacts are downloaded to the agent running the pipeline. You can also configure a step in your stage to [skip downloading](/azure/devops/pipelines/yaml-schema/steps-download) the artifact if needed. |
 
+
+> [!NOTE]
+> When using a **Feed** with 1,000 packages or more, the packages listed in the **Package** dropdown for the Azure Artifacts source might be truncated.
+> To work around this issue, create a new custom view and [promote](../../artifacts/feeds/views.md) packages to that view. Then, in the release pipeline, specify the view in the Azure Artifacts source.
+> Alternatively, you can provide the package ID. For instructions, see [Get Packages - Artifact Details](/rest/api/azure/devops/artifacts/artifact-details/get-packages).
+
 #### Handling Maven snapshots
 
 When using Maven snapshots, multiple versions can be downloaded at once (example `myApplication-2.1.0.BUILD-20190920.220048-3.jar`, `myApplication-2.1.0.BUILD-20190820.221046-2.jar`, `myApplication-2.1.0.BUILD-20190820.220331-1.jar`). You might need to remove the old versions and only keep the latest artifact before deployment.