diff --git a/backup_and_restore/application_backup_and_restore/backing_up_and_restoring/oadp-about-kopia.adoc b/backup_and_restore/application_backup_and_restore/backing_up_and_restoring/oadp-about-kopia.adoc
index 61b3e0947f5b..e4294e0f4178 100644
--- a/backup_and_restore/application_backup_and_restore/backing_up_and_restoring/oadp-about-kopia.adoc
+++ b/backup_and_restore/application_backup_and_restore/backing_up_and_restoring/oadp-about-kopia.adoc
@@ -26,6 +26,11 @@ Kopia uses content-addressable storage for snapshots:
 
 OADP 1.3 supports Kopia as the backup mechanism for pod volume backup in addition to Restic. You must choose one or the other at installation by setting the `uploaderType` field in the `DataProtectionApplication` custom resource (CR). The possible values are `restic` or `kopia`. If you do not specify an  `uploaderType`, OADP 1.3 defaults to using Kopia as the backup mechanism. The data is written to and read from a unified repository.
 
+[IMPORTANT]
+====
+Using the Kopia client to modify the Kopia backup repositories is not supported and can affect the integrity of Kopia backups. {oadp-short} does not support directly connecting to the Kopia repository and can offer support only on a best-effort basis.
+====
+
 The following example shows a `DataProtectionApplication` CR configured for using Kopia:
 
 [source,yaml]