From 205997d86dc7a77bdac0f87e3848d55df5279c3a Mon Sep 17 00:00:00 2001 From: AlexRothwell <7465195+AlexRothwell@users.noreply.github.com> Date: Thu, 20 Nov 2025 18:19:22 +1100 Subject: [PATCH 1/2] Update the DW section of the IP address allow list page --- src/pages/docs/octopus-cloud/ip-address-allow-list.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/src/pages/docs/octopus-cloud/ip-address-allow-list.md b/src/pages/docs/octopus-cloud/ip-address-allow-list.md index 36bd28f660..fb6b6f7a31 100644 --- a/src/pages/docs/octopus-cloud/ip-address-allow-list.md +++ b/src/pages/docs/octopus-cloud/ip-address-allow-list.md @@ -44,15 +44,14 @@ You can import a CSV file of IP addresses or ranges, with optional descriptions, Dynamic workers leased by your Octopus Cloud are not protected by your IP address allow list. -If you require a dynamic worker to have access to your Octopus Cloud instance when IP address allow list is activated, you need to include the IP address used for egress from the dynamic worker in your allow list. +These dynamic workers do not bypass your IP address allow list, either. -You can determine the egress IP address of a dynamic worker by running a script on it like `curl -s https://api.ipify.org`. +We do not support adding your leased dynamic workers to the allow list. -Please note: +If you need to access your Octopus Cloud instance from a dynamic worker, consider provisioning your own [external worker](/docs/infrastructure/workers#external-workers-external-workers). + +If using an IP address allow list on your Octopus Cloud instance is important to you and you must use a dynamic worker which initiates communication with your instance, please let us know by leaving a comment on our public [roadmap card](https://roadmap.octopus.com/c/189-higher-resourced-more-secure-dynamic-workers-for-octopus-cloud). -- Dynamic workers do not have static IP addresses -- You may need to adjust your allow list if a dynamic worker's IP address changes -- Dynamic workers in your Octopus Cloud Azure region can be leased by any customer in that region ## Azure Private Links From f863a3b9100a09fe5e3a79f15a96613af10bd9ca Mon Sep 17 00:00:00 2001 From: Alex Rothwell <7465195+AlexRothwell@users.noreply.github.com> Date: Wed, 26 Nov 2025 10:21:45 +1100 Subject: [PATCH 2/2] Update src/pages/docs/octopus-cloud/ip-address-allow-list.md Co-authored-by: Steve Fenton <99181436+steve-fenton-octopus@users.noreply.github.com> --- src/pages/docs/octopus-cloud/ip-address-allow-list.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/docs/octopus-cloud/ip-address-allow-list.md b/src/pages/docs/octopus-cloud/ip-address-allow-list.md index fb6b6f7a31..19f3b99066 100644 --- a/src/pages/docs/octopus-cloud/ip-address-allow-list.md +++ b/src/pages/docs/octopus-cloud/ip-address-allow-list.md @@ -50,7 +50,7 @@ We do not support adding your leased dynamic workers to the allow list. If you need to access your Octopus Cloud instance from a dynamic worker, consider provisioning your own [external worker](/docs/infrastructure/workers#external-workers-external-workers). -If using an IP address allow list on your Octopus Cloud instance is important to you and you must use a dynamic worker which initiates communication with your instance, please let us know by leaving a comment on our public [roadmap card](https://roadmap.octopus.com/c/189-higher-resourced-more-secure-dynamic-workers-for-octopus-cloud). +If you're using Octopus Cloud and would like to combine an IP address allow list with a dynamic worker that initiates communication with your instance, please let us know by leaving a comment on our public [roadmap card](https://roadmap.octopus.com/c/189-higher-resourced-more-secure-dynamic-workers-for-octopus-cloud). ## Azure Private Links