diff --git a/ee/ucp/user-access/cli.md b/ee/ucp/user-access/cli.md
index afcfcfc78f..e58c2efcb5 100644
--- a/ee/ucp/user-access/cli.md
+++ b/ee/ucp/user-access/cli.md
@@ -85,6 +85,11 @@ and the `DOCKER_CERT_PATH` environment variable to use the client certificates
 that are included in the client bundle you downloaded. The utility scripts also
 run the `kubectl config` command to configure kubectl.
 
+> **Note**: In Docker Enterprise 3.0, new files are contained in the UCP bundle. These changes support 
+the use of `.zip` files with `docker context import` and allow you to directly change your context 
+using the bundle `.zip` file. Refer to [Working with Contexts](/engine/context/working-with-contexts/) 
+for more information.
+
 To confirm that your client tools are now communicating with UCP, run:
 
 <ul class="nav nav-tabs">
diff --git a/engine/context/working-with-contexts.md b/engine/context/working-with-contexts.md
index 33704358ee..e2f83082de 100644
--- a/engine/context/working-with-contexts.md
+++ b/engine/context/working-with-contexts.md
@@ -210,6 +210,8 @@ You can verify that the context was imported with `docker context ls`.
 
 The format of the import command is `docker context import <context-name> <context-file>`.
 
+> **Note**: You can import the client bundle `.zip` file generated from UCP and run a command to set your context to UCP. For example, `docker context import ctx-name ucp-bundle.zip`.
+
 Now, let's look at exporting just the Kubernetes parts of a context.
 
 ### Exporting a Kubernetes context