From 631075d68675ea6be0365c91b5bce10c5f7f503f Mon Sep 17 00:00:00 2001 From: mvm Date: Mon, 12 Oct 2026 13:45:03 -0500 Subject: [PATCH 1/5] docs: fix broken internal links --- public/__redirects | 5 +++++ .../ai-gateway/2026-10-05-provider-credential-errors.mdx | 2 +- src/content/changelog/basin/2026-10-01-basin-ga.mdx | 2 +- .../cloudflare-one-client/2024-06-16-cloudflare-one.mdx | 2 +- .../cloudflare-one/2026-07-28-gateway-maximum-dns-ttl.mdx | 2 +- .../d1/2026-09-01-d1-free-tier-limit-enforcement.mdx | 2 +- .../directories/manage-integrated-directories/index.mdx | 2 +- .../mdm-deployment/windows-no-auth-no-internet.mdx | 2 +- .../cloudflare-one-client/download/support-lifecycle.mdx | 2 +- .../devices/cloudflare-one-client/download/update.mdx | 2 +- .../traffic-policies/dns-policies/maximum-dns-ttl.mdx | 2 +- .../configure-email-security/active-directory-sync.mdx | 6 +++--- .../configure-email-security/report-phish.mdx | 2 +- .../monitor-your-inbox/phish-submissions.mdx | 2 +- src/content/docs/realtime/realtimekit/ui-kit/chat-panel.mdx | 2 +- .../content-types/tutorial.mdx | 2 +- .../http-status-codes/cloudflare-1xxx-errors/error-1034.mdx | 2 +- src/content/partials/style-guide/link-in-props.mdx | 2 ++ 18 files changed, 25 insertions(+), 18 deletions(-) diff --git a/public/__redirects b/public/__redirects index 49844e7f130..1d13eeaaf47 100644 --- a/public/__redirects +++ b/public/__redirects @@ -2751,9 +2751,14 @@ /cloudflare-one/email-security/outbound-dlp/ /cloudflare-one/email-security/policies/outbound/outbound-dlp/ 301 /cloudflare-one/email-security/settings/auto-moves/ /cloudflare-one/email-security/settings/detection-settings/auto-moves/ 301 /cloudflare-one/email-security/directories/ /cloudflare-one/email-security/settings/domains-and-directories/directories/ 301 +/cloudflare-one/email-security/directories/manage-es-directories/ /cloudflare-one/email-security/settings/domains-and-directories/directories/manage-es-directories/ 301 +/cloudflare-one/email-security/directories/manage-integrated-directories/ /cloudflare-one/email-security/settings/domains-and-directories/directories/manage-integrated-directories/ 301 +/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory/ /cloudflare-one/email-security/settings/domains-and-directories/directories/manage-integrated-directories/manage-groups-directory/ 301 +/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory/ /cloudflare-one/email-security/settings/domains-and-directories/directories/manage-integrated-directories/manage-users-directory/ 301 /cloudflare-one/email-security/settings/domain-management/domain/ /cloudflare-one/email-security/settings/domains-and-directories/domains/ 301 /cloudflare-one/email-security/settings/phish-submissions/ /cloudflare-one/email-security/settings/submission-settings/ 301 /cloudflare-one/email-security/settings/phish-submissions/phishnet-365/ /cloudflare-one/email-security/settings/submission-settings/phishnet-365/ 301 +/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace/ /cloudflare-one/email-security/settings/submission-settings/phishnet-google-workspace/ 301 /cloudflare-one/email-security/settings/phish-submissions/submission-addresses/ /cloudflare-one/email-security/settings/submission-settings/submission-addresses/ 301 /cloudflare-one/email-security/monitoring/search-email/ /cloudflare-one/email-security/investigation/search-email/ 301 diff --git a/src/content/changelog/ai-gateway/2026-10-05-provider-credential-errors.mdx b/src/content/changelog/ai-gateway/2026-10-05-provider-credential-errors.mdx index 231aaeb3d35..d797ab13334 100644 --- a/src/content/changelog/ai-gateway/2026-10-05-provider-credential-errors.mdx +++ b/src/content/changelog/ai-gateway/2026-10-05-provider-credential-errors.mdx @@ -15,4 +15,4 @@ AI Gateway's REST API now returns consistent responses when an AI provider rejec Update applications that handle AI Gateway REST API errors to treat HTTP `401` as an invalid or rejected provider credential. -For details about providing provider credentials, refer to [Bring your own provider keys](/ai-gateway/configuration/bring-your-own-key/). +For details about providing provider credentials, refer to [Bring your own provider keys](/ai-gateway/configuration/bring-your-own-keys/). diff --git a/src/content/changelog/basin/2026-10-01-basin-ga.mdx b/src/content/changelog/basin/2026-10-01-basin-ga.mdx index 8d47cff3390..be391c98eee 100644 --- a/src/content/changelog/basin/2026-10-01-basin-ga.mdx +++ b/src/content/changelog/basin/2026-10-01-basin-ga.mdx @@ -15,7 +15,7 @@ import { PackageManagers } from "~/components"; ## Basin Pipelines -[Basin Pipelines](/basin-pipelines/), formerly Cloudflare Pipelines, ingests events from Workers, HTTP endpoints, and Cloudflare [Logpush](/logpush/). It transforms events with SQL and ingests them into Iceberg tables or files on R2. With Basin Pipelines you can: +[Basin Pipelines](/basin-pipelines/), formerly Cloudflare Pipelines, ingests events from Workers, HTTP endpoints, and Cloudflare [Logpush](/logs/logpush/). It transforms events with SQL and ingests them into Iceberg tables or files on R2. With Basin Pipelines you can: - Ingest application and device events through HTTP endpoints or Workers bindings. - Filter and reshape Cloudflare logs before storing them as Iceberg tables, Parquet, or JSON. diff --git a/src/content/changelog/cloudflare-one-client/2024-06-16-cloudflare-one.mdx b/src/content/changelog/cloudflare-one-client/2024-06-16-cloudflare-one.mdx index 8c87ce949a9..03608aea99d 100644 --- a/src/content/changelog/cloudflare-one-client/2024-06-16-cloudflare-one.mdx +++ b/src/content/changelog/cloudflare-one-client/2024-06-16-cloudflare-one.mdx @@ -45,6 +45,6 @@ If you are looking for older product updates, refer to the following locations. - [Magic WAN](/cloudflare-wan/changelog/) - [Network Interconnect](/network-interconnect/changelog/) - [Risk score](/cloudflare-one/changelog/risk-score/) -- [Cloudflare One Client](/changelog/cloudflare-one-client/) +- [Cloudflare One Client](/changelog/product/cloudflare-one-client/) diff --git a/src/content/changelog/cloudflare-one/2026-07-28-gateway-maximum-dns-ttl.mdx b/src/content/changelog/cloudflare-one/2026-07-28-gateway-maximum-dns-ttl.mdx index e24e88beb47..6a625c80963 100644 --- a/src/content/changelog/cloudflare-one/2026-07-28-gateway-maximum-dns-ttl.mdx +++ b/src/content/changelog/cloudflare-one/2026-07-28-gateway-maximum-dns-ttl.mdx @@ -14,7 +14,7 @@ You can now set a maximum time-to-live (TTL) for DNS responses returned by Gatew The setting is available at two levels: - **Account level** - In **Traffic Policies** > **Traffic Settings**, under **Proxy and inspection**. This sets the default cap for all DNS locations. -- **Per-location** - Each [DNS location](/cloudflare-one/networks/resolvers-proxies/) can inherit the account setting, disable the cap, or override it with a custom value. +- **Per-location** - Each [DNS location](/cloudflare-one/networks/resolvers-and-proxies/) can inherit the account setting, disable the cap, or override it with a custom value. Two new fields are also available in DNS logs: `upstream_record_ttls` (the original TTL from the upstream response) and `applied_max_ttl` (the cap Gateway applied). These appear in the DNS logs column picker and in Logpush datasets. diff --git a/src/content/changelog/d1/2026-09-01-d1-free-tier-limit-enforcement.mdx b/src/content/changelog/d1/2026-09-01-d1-free-tier-limit-enforcement.mdx index 40ec50adde3..4395bba6758 100644 --- a/src/content/changelog/d1/2026-09-01-d1-free-tier-limit-enforcement.mdx +++ b/src/content/changelog/d1/2026-09-01-d1-free-tier-limit-enforcement.mdx @@ -6,7 +6,7 @@ products: date: 2026-09-01 --- -Beginning September 1, 2026, D1 queries on the [Workers Free plan](/workers/platform/pricing/#workers) will fail when an account exceeds the daily [row read or row write limits](/d1/platform/pricing/). Queries via the [Workers Binding API](/d1/worker-api/) and the [REST API](/d1/rest-api/) will return errors until the limit resets at midnight UTC. Stored data is not affected. +Beginning September 1, 2026, D1 queries on the [Workers Free plan](/workers/platform/pricing/#workers) will fail when an account exceeds the daily [row read or row write limits](/d1/platform/pricing/). Queries via the [Workers Binding API](/d1/worker-api/) and the [REST API](/api/resources/d1/subresources/database/methods/create/) will return errors until the limit resets at midnight UTC. Stored data is not affected. You will receive email alerts when the daily limit is reached. The following errors indicate that a limit has been exceeded: diff --git a/src/content/docs/cloudflare-one/email-security/settings/domains-and-directories/directories/manage-integrated-directories/index.mdx b/src/content/docs/cloudflare-one/email-security/settings/domains-and-directories/directories/manage-integrated-directories/index.mdx index 7e744fd378b..0d97010f3ef 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/domains-and-directories/directories/manage-integrated-directories/index.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/domains-and-directories/directories/manage-integrated-directories/index.mdx @@ -16,4 +16,4 @@ To manage an integrated directory: 2. Select **Email security**. 3. Select **Directories**. 4. Under **Directory name**, select your directory. -5. You will be redirected to a page where you can manage [Groups](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory/) or [Users](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory/) directories. +5. You will be redirected to a page where you can manage [Groups](/cloudflare-one/email-security/settings/domains-and-directories/directories/manage-integrated-directories/manage-groups-directory/) or [Users](/cloudflare-one/email-security/settings/domains-and-directories/directories/manage-integrated-directories/manage-users-directory/) directories. diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/windows-no-auth-no-internet.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/windows-no-auth-no-internet.mdx index f4371df94e1..df1f3d255b0 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/windows-no-auth-no-internet.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/windows-no-auth-no-internet.mdx @@ -91,6 +91,6 @@ To block RFC 1918 traffic during lockdown, set `no_auth_no_internet_block_rfc_19 ## Limitations - The lockdown is enforced only when there is an active interactive user session (for example, a user is logged in and the device is not locked). -- A [pre-login](cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/windows-prelogin/) registration is also considered a valid registration, and the lockdown will not be enforced when a pre-login registration is in use. +- A [pre-login](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/windows-prelogin/) registration is also considered a valid registration, and the lockdown will not be enforced when a pre-login registration is in use. - Since authentication now occurs in an embedded WebView2 window, IdP flows that depend on the user's default browser (for example, browser-specific extensions or password managers) may not work. - Some Windows applications, including Copilot and Teams (personal), may retain internet access while the Cloudflare One Client authentication window is open. diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/support-lifecycle.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/support-lifecycle.mdx index c1132bf54b5..e167133f364 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/support-lifecycle.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/support-lifecycle.mdx @@ -39,7 +39,7 @@ Cloudflare will provide a minimum 90-day notice prior to removing major features ### Release schedule -Cloudflare does not operate on a fixed release schedule; all releases for the Cloudflare One Client are incremental. When a new Cloudflare One Client version is released, Cloudflare will publish release notes on the [Downloads page](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/) and in the [changelog](/changelog/cloudflare-one-client/). +Cloudflare does not operate on a fixed release schedule; all releases for the Cloudflare One Client are incremental. When a new Cloudflare One Client version is released, Cloudflare will publish release notes on the [Downloads page](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/) and in the [changelog](/changelog/product/cloudflare-one-client/). ## Supported operating systems diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/update.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/update.mdx index 0a9ad81c6be..6932e53fdfc 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/update.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/download/update.mdx @@ -25,7 +25,7 @@ If you run into issues that require troubleshooting or support tickets, one of t :::tip -To get notified of new releases, subscribe to the [Cloudflare One Client changelog](/changelog/cloudflare-one-client/). +To get notified of new releases, subscribe to the [Cloudflare One Client changelog](/changelog/product/cloudflare-one-client/). ::: ## How to update the Cloudflare One Client diff --git a/src/content/docs/cloudflare-one/traffic-policies/dns-policies/maximum-dns-ttl.mdx b/src/content/docs/cloudflare-one/traffic-policies/dns-policies/maximum-dns-ttl.mdx index 84baf484a7e..9a1816325c4 100644 --- a/src/content/docs/cloudflare-one/traffic-policies/dns-policies/maximum-dns-ttl.mdx +++ b/src/content/docs/cloudflare-one/traffic-policies/dns-policies/maximum-dns-ttl.mdx @@ -55,7 +55,7 @@ To remove the account-level cap (allow upstream TTLs to pass through), omit the ## Configure a per-location maximum TTL -Each [DNS location](/cloudflare-one/networks/resolvers-proxies/) can override the account-level setting. The per-location setting supports three modes: +Each [DNS location](/cloudflare-one/networks/resolvers-and-proxies/) can override the account-level setting. The per-location setting supports three modes: | Mode | Behavior | | --- | --- | diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx index a017783809f..0c945fbd88f 100644 --- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx +++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/active-directory-sync.mdx @@ -47,6 +47,6 @@ To add multiple groups to the registry at once: In addition, Email security allows you to: -- [Remove groups from the registry](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory/#remove-groups-from-registry). -- [Filter the impersonation registry](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-groups-directory/#filter-impersonation-registry). -- [Manage users in your directory](/cloudflare-one/email-security/directories/manage-integrated-directories/manage-users-directory/). \ No newline at end of file +- [Remove groups from the registry](/cloudflare-one/email-security/settings/domains-and-directories/directories/manage-integrated-directories/manage-groups-directory/#remove-groups-from-registry). +- [Filter the impersonation registry](/cloudflare-one/email-security/settings/domains-and-directories/directories/manage-integrated-directories/manage-groups-directory/#filter-impersonation-registry). +- [Manage users in your directory](/cloudflare-one/email-security/settings/domains-and-directories/directories/manage-integrated-directories/manage-users-directory/). \ No newline at end of file diff --git a/src/content/docs/learning-paths/secure-your-email/configure-email-security/report-phish.mdx b/src/content/docs/learning-paths/secure-your-email/configure-email-security/report-phish.mdx index 3cc5f8cd3fe..3a2259c9fbd 100644 --- a/src/content/docs/learning-paths/secure-your-email/configure-email-security/report-phish.mdx +++ b/src/content/docs/learning-paths/secure-your-email/configure-email-security/report-phish.mdx @@ -33,4 +33,4 @@ To set up PhishNet for Google Workspace: 1. Log in to the Google Workspace Marketplace using an administrator account. 2. Select **Admin install** to install Cloudflare PhishNet. -Refer to [Set up PhishNet for Google Workspace](/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace/#set-up-phishnet-for-google-workspace) for more information. \ No newline at end of file +Refer to [Set up PhishNet for Google Workspace](/cloudflare-one/email-security/settings/submission-settings/phishnet-google-workspace/#set-up-phishnet-for-google-workspace) for more information. \ No newline at end of file diff --git a/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx b/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx index e5a57972d2a..c004be94781 100644 --- a/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx +++ b/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx @@ -13,7 +13,7 @@ While Email security offers industry leading detection efficacy due to Cloudflar There are two different ways to [submit a phish](/cloudflare-one/email-security/settings/phish-submissions/) sample: - User submission: - - Submitted directly by the end user, and used with phish submission buttons. To learn more about user-submitted phish, refer to [PhishNet for Microsoft 365](/cloudflare-one/email-security/settings/phish-submissions/#phishnet-o365) or [PhishNet for Google Workspace](/cloudflare-one/email-security/settings/phish-submissions/phishnet-google-workspace/). + - Submitted directly by the end user, and used with phish submission buttons. To learn more about user-submitted phish, refer to [PhishNet for Microsoft 365](/cloudflare-one/email-security/settings/phish-submissions/#phishnet-o365) or [PhishNet for Google Workspace](/cloudflare-one/email-security/settings/submission-settings/phishnet-google-workspace/). - User submissions can create another challenge for your organization. While it is important for end users to be vigilant and report what they believe may be a phishing email, they are often wrong. About 90% of the time, when an end user reports a missed phishing email, they are mistaken. This puts an extra burden on busy security teams as they sift through end user reports. The PhishGuard team at Cloudflare can solve this problem for your organization by reviewing end user submissions for you. - Admin submission: - To be used when IT administrators or security teams submit to Email security. Submit original phish samples as an attachment in EML format to the appropriate team submission address. diff --git a/src/content/docs/realtime/realtimekit/ui-kit/chat-panel.mdx b/src/content/docs/realtime/realtimekit/ui-kit/chat-panel.mdx index 683933a4d22..bc4aa9b0a93 100644 --- a/src/content/docs/realtime/realtimekit/ui-kit/chat-panel.mdx +++ b/src/content/docs/realtime/realtimekit/ui-kit/chat-panel.mdx @@ -215,6 +215,6 @@ function CustomChat({ meeting }) { } ``` -Refer to the [`RtkChat`](/realtime/realtimekit/ui-kit/api-reference/react/RtkChat/), [`RtkChatSelector`](/realtime/realtimekit/ui-kit/api-reference/react/RtkChatSelector/), [`RtkPinnedMessageSelector`](/realtime/realtimekit/ui-kit/api-reference/react/RtkPinnedMessageSelector/), [`RtkChatMessagesUiPaginated`](/realtime/realtimekit/ui-kit/api-reference/react/RtkChatMessagesUiPaginated/), and [`RtkChatComposerView`](/realtime/realtimekit/ui-kit/api-reference/react/RtkChatComposerView/) API references for component props. +Refer to the [`RtkChat`](/realtime/realtimekit/ui-kit/api-reference/react/rtkchat/), [`RtkChatSelector`](/realtime/realtimekit/ui-kit/api-reference/react/rtkchatselector/), [`RtkPinnedMessageSelector`](/realtime/realtimekit/ui-kit/api-reference/react/rtkpinnedmessageselector/), [`RtkChatMessagesUiPaginated`](/realtime/realtimekit/ui-kit/api-reference/react/rtkchatmessagesuipaginated/), and [`RtkChatComposerView`](/realtime/realtimekit/ui-kit/api-reference/react/rtkchatcomposerview/) API references for component props. diff --git a/src/content/docs/style-guide/documentation-content-strategy/content-types/tutorial.mdx b/src/content/docs/style-guide/documentation-content-strategy/content-types/tutorial.mdx index cb703fe530e..dc941a9df60 100644 --- a/src/content/docs/style-guide/documentation-content-strategy/content-types/tutorial.mdx +++ b/src/content/docs/style-guide/documentation-content-strategy/content-types/tutorial.mdx @@ -41,7 +41,7 @@ For the full comparison, refer to [Content types](/style-guide/documentation-con - [**Steps**](/style-guide/build-the-page/components/steps/) or numbered `##` parts are the spine, and every part ends with the verbatim "You should see" output that proves it worked. Never skip one. - **Error-recovery prose** at the points readers actually stumble is happy-path content, not an exception callout, because in a tutorial an anticipated error is not an exception. -- [**GitHubCode**](/style-guide/build-the-page/components/github-code/) and [**PackageManagers**](/style-guide/build-the-page/components/package-managers/) keep sample code and install commands pinned and in sync, and [**ListTutorials**](/style-guide/build-the-page/components/list-tutorials/) surfaces the tutorial in listings. +- [**GitHubCode**](/style-guide/build-the-page/components/) and [**PackageManagers**](/style-guide/build-the-page/components/package-managers/) keep sample code and install commands pinned and in sync, and [**ListTutorials**](/style-guide/build-the-page/components/list-tutorials/) surfaces the tutorial in listings. - **What does not fit:** Tabs and options of any kind (the author already chose the one path, and per-stack means per-page), long conceptual asides (link out instead), and anything that hides steps. ## Frontmatter diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1034.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1034.mdx index ce0aedd863c..550a0fe22eb 100644 --- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1034.mdx +++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1034.mdx @@ -33,7 +33,7 @@ If you are using a SaaS provider that uses [Cloudflare for SaaS](/cloudflare-for #### Zone routing through a BYOIP address map from a different account -If your zone is a member of a Cloudflare [Address Map](/byoip/how-to/address-maps/) that contains IP addresses from a BYOIP prefix, and your Cloudflare account does not have access to that prefix, EIV will block all traffic to the zone with a `1034` error. +If your zone is a member of a Cloudflare [Address Map](/byoip/address-maps/) that contains IP addresses from a BYOIP prefix, and your Cloudflare account does not have access to that prefix, EIV will block all traffic to the zone with a `1034` error. This typically happens when: diff --git a/src/content/partials/style-guide/link-in-props.mdx b/src/content/partials/style-guide/link-in-props.mdx index e8c97e981cd..cbe2517baf7 100644 --- a/src/content/partials/style-guide/link-in-props.mdx +++ b/src/content/partials/style-guide/link-in-props.mdx @@ -1,6 +1,8 @@ --- params: - link +nimbusDisableRules: + - nimbus/internal-link --- **Don't do this!** From 4248dead0c2e4162c903e3d6511d01f9825116b3 Mon Sep 17 00:00:00 2001 From: mvm Date: Mon, 12 Oct 2026 13:56:51 -0500 Subject: [PATCH 2/5] docs: link directly to redirect destinations --- .../2026-03-26-mcp-portal-code-mode.mdx | 2 +- ...-03-26-mcp-portal-context-optimization.mdx | 2 +- .../agents/2025-03-18-npm-i-agents.mdx | 2 +- .../2026-02-20-codemode-sdk-rewrite.mdx | 4 ++-- .../2026-02-23-sandbox-backup-restore-api.mdx | 4 ++-- .../2026-03-03-sandbox-watch-file-events.mdx | 2 +- .../2026-05-29-sandbox-named-tunnels.mdx | 2 +- .../2025-08-22-audit-logs-v2-logpush.mdx | 2 +- .../2026-02-17-docker-in-docker.mdx | 2 +- .../2026-03-26-outbound-workers.mdx | 2 +- ...4-13-sandbox-outbound-workers-tls-auth.mdx | 2 +- ...-agents-api-with-cloudflare-containers.mdx | 2 +- .../2024-12-19-reclassification-tab.mdx | 2 +- .../2025-02-25-dlp-assist-for-m365.mdx | 2 +- .../2025-09-01-updated-new-roles.mdx | 4 ++-- .../2025-09-23-invalid-submissions.mdx | 2 +- .../2026-08-12-blocked-content-rules.mdx | 2 +- ...06-09-deprecating-sandbox-sdk-features.mdx | 22 +++++++++---------- .../2025-05-06-terraform-v5.4.0-provider.mdx | 2 +- .../2025-05-19-terraform-v5.5.0-provider.mdx | 2 +- .../2025-06-17-terraform-v5.6.0-provider.mdx | 2 +- .../2025-07-11-terraform-v5.7.0-provider.mdx | 2 +- .../2025-08-01-terraform-v5.8.2-provider.mdx | 2 +- .../2025-08-15-terraform-v5.8.4-provider.mdx | 2 +- .../2025-08-29-terrform-v5.9-provider.mdx | 2 +- ...2026-01-15-warp-connector-ping-support.mdx | 2 +- ...nel-routes-and-connections-api-changes.mdx | 2 +- .../changelog/waf/2025-12-05-rcs-vuln.mdx | 2 +- ...2025-12-05-waf-max-payload-size-change.mdx | 2 +- ...2025-04-08-deploy-to-cloudflare-button.mdx | 2 +- ...port-long-branch-names-preview-aliases.mdx | 2 +- .../2025-09-07-builds-increased-cpu-paid.mdx | 2 +- .../workers/2025-09-16-remote-bindings-ga.mdx | 2 +- .../2025-09-17-update-preview-url-setting.mdx | 4 ++-- ...025-10-03-one-click-access-for-workers.mdx | 2 +- ...025-10-23-preview-url-default-behavior.mdx | 10 ++++----- .../workers/2025-10-30-builds-preview.mdx | 2 +- .../2026-02-25-wrangler-autoconfig-ga.mdx | 4 ++-- .../workers/2026-05-14-domains-tab.mdx | 2 +- .../workflows/2025-04-07-workflows-ga.mdx | 4 ++-- .../servers-for-cloudflare/index.mdx | 2 +- .../agents/tools/codemode/how-it-works.mdx | 2 +- .../data-source/website/content-selectors.mdx | 2 +- .../analytics-integrations/sentinel/index.mdx | 2 +- .../guides/build-and-deploy-on-push.mdx | 2 +- .../docs/bots/get-started/bot-management.mdx | 2 +- src/content/docs/cache/get-started.mdx | 2 +- src/content/docs/cf/projects/index.mdx | 2 +- .../concepts/how-challenges-work.mdx | 2 +- .../configuration/observability.mdx | 2 +- .../ai-controls/mcp-portals.mdx | 6 ++--- .../dlp-profiles/index.mdx | 4 ++-- .../data-loss-prevention/index.mdx | 4 ++-- .../cloudflare-one/email-security/index.mdx | 2 +- .../investigation/search-email.mdx | 2 +- .../email-security/monitoring/index.mdx | 12 +++++----- .../email-security/phishguard.mdx | 8 +++---- .../policies/outbound/outbound-dlp.mdx | 4 ++-- .../reference/dispositions-and-attributes.mdx | 2 +- .../additional-detections.mdx | 2 +- .../detection-settings/best-practices.mdx | 6 ++--- .../email-security/setup/index.mdx | 8 +++---- .../post-delivery-deployment/api/index.mdx | 2 +- .../post-delivery-deployment/api/m365-api.mdx | 2 +- .../gmail-bcc-setup/connect-domains.mdx | 4 ++-- .../gmail-bcc-setup/gmail-bcc-setup.mdx | 2 +- .../journaling-setup/m365-journaling.mdx | 2 +- .../journaling-setup/manual-add.mdx | 4 ++-- .../submissions/user-submissions.mdx | 2 +- .../tunnel-with-firewall.mdx | 2 +- .../application-based-policies/index.mdx | 4 ++-- .../configuration/third-party/fortinet.mdx | 2 +- .../networks/virtual-networks.mdx | 2 +- .../docs/cloudflare-one/roles-permissions.mdx | 2 +- .../configuration/third-party/fortinet.mdx | 2 +- .../reference/virtual-networks.mdx | 2 +- .../configuration/outbound-traffic.mdx | 2 +- .../examples/dynamic-workers-starter.mdx | 2 +- .../usage/dynamic-workflows.mdx | 2 +- .../migrate-to-email-security.mdx | 12 +++++----- .../api/reference/permissions.mdx | 8 +++---- .../fundamentals/manage-members/roles.mdx | 2 +- .../reference/cdn-cgi-endpoint.mdx | 2 +- .../scim-virtual-groups-migration.mdx | 4 ++-- .../cloudflare-cookies.mdx | 2 +- .../email-security-next-steps.mdx | 8 +++---- .../monitor-your-inbox/index.mdx | 4 ++-- .../monitor-your-inbox/monitor-detections.mdx | 2 +- .../monitor-your-inbox/phish-submissions.mdx | 4 ++-- src/content/docs/logs/logpush/pricing.mdx | 2 +- .../docs/logs/logpush/transformers.mdx | 2 +- src/content/docs/magic-transit/about.mdx | 2 +- .../email-security-deployments.mdx | 8 +++---- .../design-guides/zero-trust-for-saas.mdx | 2 +- ...stributed-web-performance-architecture.mdx | 4 ++-- .../docs/sandbox/sdk/migrate/tunnels.mdx | 2 +- .../docs/security/security-insights/index.mdx | 2 +- src/content/docs/security/settings.mdx | 2 +- .../client-certificates/troubleshooting.mdx | 2 +- .../build-the-page/components/index.mdx | 4 ++-- .../docs/use-cases/e-commerce/performance.mdx | 2 +- .../media-streaming/image-optimization.mdx | 2 +- .../performance/image-optimization.mdx | 2 +- .../docs/use-cases/solutions/index.mdx | 2 +- .../workers/ci-cd/builds/automatic-prs.mdx | 2 +- .../configuration/cloudflare-access.mdx | 2 +- .../docs/workers/runtime-apis/context.mdx | 2 +- ...ube-thumbnails-with-workers-and-images.mdx | 2 +- src/content/partials/bots/bots-jsd.mdx | 2 +- src/content/partials/bots/enable-sbfm.mdx | 2 +- .../cf-clearance-cookie.mdx | 2 +- .../troubleshooting/email-security.mdx | 4 ++-- .../do-sqlite-storage-no-bill-note.mdx | 2 +- .../speed/brotli-compression-warning.mdx | 2 +- .../partials/workers/cloudflare-config.mdx | 2 +- 115 files changed, 176 insertions(+), 176 deletions(-) diff --git a/src/content/changelog/access/2026-03-26-mcp-portal-code-mode.mdx b/src/content/changelog/access/2026-03-26-mcp-portal-code-mode.mdx index 1875cceeee2..75cfa228a0f 100644 --- a/src/content/changelog/access/2026-03-26-mcp-portal-code-mode.mdx +++ b/src/content/changelog/access/2026-03-26-mcp-portal-code-mode.mdx @@ -10,7 +10,7 @@ products: To turn it off, edit the portal in **Access controls** > **AI controls** and turn off **Code Mode** under **Basic information**. -When Code Mode is active, the portal exposes a single `code` tool instead of listing every tool from every upstream MCP server. The connected AI agent writes JavaScript that calls typed `codemode.*` methods for each upstream tool. The generated code runs in an isolated [Dynamic Worker](/workers/runtime-apis/bindings/worker-loader/) environment, keeping authentication credentials and environment variables out of the model context. +When Code Mode is active, the portal exposes a single `code` tool instead of listing every tool from every upstream MCP server. The connected AI agent writes JavaScript that calls typed `codemode.*` methods for each upstream tool. The generated code runs in an isolated [Dynamic Worker](/dynamic-workers/) environment, keeping authentication credentials and environment variables out of the model context. To use Code Mode, append `?codemode=search_and_execute` to your portal URL when connecting from an MCP client: diff --git a/src/content/changelog/access/2026-03-26-mcp-portal-context-optimization.mdx b/src/content/changelog/access/2026-03-26-mcp-portal-context-optimization.mdx index 926faedf2bd..d66ca29eaea 100644 --- a/src/content/changelog/access/2026-03-26-mcp-portal-context-optimization.mdx +++ b/src/content/changelog/access/2026-03-26-mcp-portal-context-optimization.mdx @@ -18,7 +18,7 @@ https://./mcp?optimize_context=minimize_tools ### `search_and_execute` -Hides all upstream tools and exposes only two tools: `query` and `execute`. The `query` tool searches and retrieves tool definitions. The `execute` tool runs the upstream tools in an isolated [Dynamic Worker](/workers/runtime-apis/bindings/worker-loader/) environment. This reduces the initial token cost to a small constant, regardless of how many tools are available through the portal. +Hides all upstream tools and exposes only two tools: `query` and `execute`. The `query` tool searches and retrieves tool definitions. The `execute` tool runs the upstream tools in an isolated [Dynamic Worker](/dynamic-workers/) environment. This reduces the initial token cost to a small constant, regardless of how many tools are available through the portal. ```txt https://./mcp?optimize_context=search_and_execute diff --git a/src/content/changelog/agents/2025-03-18-npm-i-agents.mdx b/src/content/changelog/agents/2025-03-18-npm-i-agents.mdx index 2cc221a18e2..eaead553cf1 100644 --- a/src/content/changelog/agents/2025-03-18-npm-i-agents.mdx +++ b/src/content/changelog/agents/2025-03-18-npm-i-agents.mdx @@ -109,7 +109,7 @@ const fetchUserHistory = async () => { #### agents-starter -We've fixed a number of small bugs in the [`agents-starter`](https://github.com/cloudflare/agents-starter) project — a real-time, chat-based example application with tool-calling & human-in-the-loop built using the Agents SDK. The starter has also been upgraded to use the latest [wrangler v4](/changelog/2025-03-13-wrangler-v4/) release. +We've fixed a number of small bugs in the [`agents-starter`](https://github.com/cloudflare/agents-starter) project — a real-time, chat-based example application with tool-calling & human-in-the-loop built using the Agents SDK. The starter has also been upgraded to use the latest [wrangler v4](/changelog/post/2025-03-13-wrangler-v4/) release. If you're new to Agents, you can install and run the `agents-starter` project in two commands: diff --git a/src/content/changelog/agents/2026-02-20-codemode-sdk-rewrite.mdx b/src/content/changelog/agents/2026-02-20-codemode-sdk-rewrite.mdx index c699f2d74f2..29dbd196a85 100644 --- a/src/content/changelog/agents/2026-02-20-codemode-sdk-rewrite.mdx +++ b/src/content/changelog/agents/2026-02-20-codemode-sdk-rewrite.mdx @@ -13,7 +13,7 @@ The [`@cloudflare/codemode`](https://www.npmjs.com/package/@cloudflare/codemode) [Code Mode](https://blog.cloudflare.com/code-mode/) enables LLMs to write and execute code that orchestrates your tools, instead of calling them one at a time. This can (and does) yield significant token savings, reduces context window pressure and improves overall model performance on a task. -The new `Executor` interface is runtime agnostic and comes with a prebuilt `DynamicWorkerExecutor` to run generated code in a [Dynamic Worker Loader](/workers/runtime-apis/bindings/worker-loader/). +The new `Executor` interface is runtime agnostic and comes with a prebuilt `DynamicWorkerExecutor` to run generated code in a [Dynamic Worker Loader](/dynamic-workers/). ## Breaking changes @@ -27,7 +27,7 @@ The new `Executor` interface is runtime agnostic and comes with a prebuilt `Dyna ### `DynamicWorkerExecutor` -Runs code in a [Dynamic Worker](/workers/runtime-apis/bindings/worker-loader/). It comes with the following features: +Runs code in a [Dynamic Worker](/dynamic-workers/). It comes with the following features: - **Network isolation** — `fetch()` and `connect()` blocked by default (`globalOutbound: null`) when using `DynamicWorkerExecutor` - **Console capture** — `console.log/warn/error` captured and returned in `ExecuteResult.logs` diff --git a/src/content/changelog/agents/2026-02-23-sandbox-backup-restore-api.mdx b/src/content/changelog/agents/2026-02-23-sandbox-backup-restore-api.mdx index 63205b4413f..a998259a84e 100644 --- a/src/content/changelog/agents/2026-02-23-sandbox-backup-restore-api.mdx +++ b/src/content/changelog/agents/2026-02-23-sandbox-backup-restore-api.mdx @@ -35,7 +35,7 @@ await env.KV.put(`backup:${userId}`, JSON.stringify(backup)); await sandbox.restoreBackup(backup); ``` -Backups are stored in [R2](/r2) and can take advantage of [R2 object lifecycle rules](/sandbox/guides/backup-restore/#configure-r2-lifecycle-rules-for-automatic-cleanup) to ensure they do not persist forever. +Backups are stored in [R2](/r2) and can take advantage of [R2 object lifecycle rules](/sandbox/sdk/guides/backup-restore/#set-a-name-and-ttl) to ensure they do not persist forever. Key capabilities: @@ -48,4 +48,4 @@ Key capabilities: Backup and restore currently uses a FUSE overlay. Soon, native snapshotting at a lower level will be added to Containers and Sandboxes, improving speed and ergonomics. The current backup functionality provides a significant speed improvement over manually recreating a file system, but it will be further optimized in the future. The new snapshotting system will use a similar API, so changing to this system will be simple once it is available. ::: -To get started, refer to the [backup and restore guide](/sandbox/guides/backup-restore/) for setup instructions and usage patterns, or the [Backups API reference](/sandbox/api/backups/) for full method documentation. +To get started, refer to the [backup and restore guide](/sandbox/sdk/guides/backup-restore/) for setup instructions and usage patterns, or the [Backups API reference](/sandbox/sdk/api/backups/) for full method documentation. diff --git a/src/content/changelog/agents/2026-03-03-sandbox-watch-file-events.mdx b/src/content/changelog/agents/2026-03-03-sandbox-watch-file-events.mdx index 714b7859da0..66469c081a4 100644 --- a/src/content/changelog/agents/2026-03-03-sandbox-watch-file-events.mdx +++ b/src/content/changelog/agents/2026-03-03-sandbox-watch-file-events.mdx @@ -66,4 +66,4 @@ To update to the latest version: npm i @cloudflare/sandbox@latest ``` -For full API details, refer to the [Sandbox file watching reference](/sandbox/api/file-watching/). +For full API details, refer to the [Sandbox file watching reference](/sandbox/sdk/api/file-watching/). diff --git a/src/content/changelog/agents/2026-05-29-sandbox-named-tunnels.mdx b/src/content/changelog/agents/2026-05-29-sandbox-named-tunnels.mdx index 0277616073a..75c6ca91169 100644 --- a/src/content/changelog/agents/2026-05-29-sandbox-named-tunnels.mdx +++ b/src/content/changelog/agents/2026-05-29-sandbox-named-tunnels.mdx @@ -49,4 +49,4 @@ To update to the latest version: -For full API details, refer to the [Sandbox tunnels reference](/sandbox/api/tunnels/). +For full API details, refer to the [Sandbox tunnels reference](/sandbox/sdk/api/tunnels/). diff --git a/src/content/changelog/audit-logs/2025-08-22-audit-logs-v2-logpush.mdx b/src/content/changelog/audit-logs/2025-08-22-audit-logs-v2-logpush.mdx index c191095c8f8..998e2d98ed6 100644 --- a/src/content/changelog/audit-logs/2025-08-22-audit-logs-v2-logpush.mdx +++ b/src/content/changelog/audit-logs/2025-08-22-audit-logs-v2-logpush.mdx @@ -6,7 +6,7 @@ date: 2025-08-22 [Audit Logs v2 dataset](/logs/logpush/logpush-job/datasets/account/audit_logs_v2/) is now available via Logpush. -This expands on earlier releases of Audit Logs v2 in the [API](/changelog/2025-03-27-automatic-audit-logs-beta-release/) and [Dashboard UI](/changelog/2025-07-29-audit-logs-v2-ui-beta/). +This expands on earlier releases of Audit Logs v2 in the [API](/changelog/post/2025-03-27-automatic-audit-logs-beta-release/) and [Dashboard UI](/changelog/post/2025-07-29-audit-logs-v2-ui-beta/). We recommend creating a new Logpush job for the Audit Logs v2 dataset. diff --git a/src/content/changelog/containers/2026-02-17-docker-in-docker.mdx b/src/content/changelog/containers/2026-02-17-docker-in-docker.mdx index 83ade6aaf55..1d8e551a43f 100644 --- a/src/content/changelog/containers/2026-02-17-docker-in-docker.mdx +++ b/src/content/changelog/containers/2026-02-17-docker-in-docker.mdx @@ -15,4 +15,4 @@ This allows you to: - Build container images as part of CI/CD workflows - Deploy arbitrary images supplied at runtime within a container -For [Sandbox SDK](/sandbox/) users, see the [Docker-in-Docker guide](/sandbox/guides/docker-in-docker/) for instructions on combining Docker with the SandboxSDK. For general Containers usage, see the [Containers FAQ](/containers/faq/#can-i-run-docker-inside-a-container-docker-in-docker). +For [Sandbox SDK](/sandbox/) users, see the [Docker-in-Docker guide](/sandbox/sdk/guides/docker-in-docker/) for instructions on combining Docker with the SandboxSDK. For general Containers usage, see the [Containers FAQ](/containers/faq/#can-i-run-docker-inside-a-container-docker-in-docker). diff --git a/src/content/changelog/containers/2026-03-26-outbound-workers.mdx b/src/content/changelog/containers/2026-03-26-outbound-workers.mdx index 4d09b7a470f..b0f816024fb 100644 --- a/src/content/changelog/containers/2026-03-26-outbound-workers.mdx +++ b/src/content/changelog/containers/2026-03-26-outbound-workers.mdx @@ -78,4 +78,4 @@ This provides an easy way to associate state with any container instance, and in Upgrade to `@cloudflare/containers` version 0.2.0 or later, or `@cloudflare/sandbox` version 0.8.0 or later to use outbound Workers. -Refer to [Containers outbound traffic](/containers/configuration/outbound-traffic/) and [Sandboxes outbound traffic](/sandbox/guides/outbound-traffic/) for more details and examples. +Refer to [Containers outbound traffic](/containers/configuration/outbound-traffic/) and [Sandboxes outbound traffic](/sandbox/sdk/guides/outbound-traffic/) for more details and examples. diff --git a/src/content/changelog/containers/2026-04-13-sandbox-outbound-workers-tls-auth.mdx b/src/content/changelog/containers/2026-04-13-sandbox-outbound-workers-tls-auth.mdx index 7b563931f02..20c3e8ee4a3 100644 --- a/src/content/changelog/containers/2026-04-13-sandbox-outbound-workers-tls-auth.mdx +++ b/src/content/changelog/containers/2026-04-13-sandbox-outbound-workers-tls-auth.mdx @@ -109,4 +109,4 @@ Handlers accept `params`, so you can customize behavior per instance without def Upgrade to `@cloudflare/containers@0.3.0` or `@cloudflare/sandbox@0.8.9` to use these features. -For more details, refer to [Sandbox outbound traffic](/sandbox/guides/outbound-traffic/) and [Container outbound traffic](/containers/configuration/outbound-traffic/). +For more details, refer to [Sandbox outbound traffic](/sandbox/sdk/guides/outbound-traffic/) and [Container outbound traffic](/containers/configuration/outbound-traffic/). diff --git a/src/content/changelog/containers/2026-09-10-using-openai-agents-api-with-cloudflare-containers.mdx b/src/content/changelog/containers/2026-09-10-using-openai-agents-api-with-cloudflare-containers.mdx index 2e7f86ba10f..595d50ec717 100644 --- a/src/content/changelog/containers/2026-09-10-using-openai-agents-api-with-cloudflare-containers.mdx +++ b/src/content/changelog/containers/2026-09-10-using-openai-agents-api-with-cloudflare-containers.mdx @@ -14,4 +14,4 @@ Cloudflare Containers can now provide self-hosted execution environments for the You can configure the reference implementation to meet your needs by extending the Container to provide controlled access to data and the network or by integrating it with other Cloudflare products. -To get started, refer to [Run Codex on Cloudflare using the OpenAI Agents API](/sandbox/tutorials/openai-agents-api/). +To get started, refer to [Run Codex on Cloudflare using the OpenAI Agents API](/sandbox/coding-agents/openai-agents-api/). diff --git a/src/content/changelog/email-security-cf1/2024-12-19-reclassification-tab.mdx b/src/content/changelog/email-security-cf1/2024-12-19-reclassification-tab.mdx index 15029deeb67..f8c595297ea 100644 --- a/src/content/changelog/email-security-cf1/2024-12-19-reclassification-tab.mdx +++ b/src/content/changelog/email-security-cf1/2024-12-19-reclassification-tab.mdx @@ -8,7 +8,7 @@ import { Render } from "~/components"; You now have more transparency about team and user submissions for phishing emails through a **Reclassification** tab in the Zero Trust dashboard. -Reclassifications happen when users or admins [submit a phish](/cloudflare-one/email-security/settings/phish-submissions/) to Email security. Cloudflare reviews and - in some cases - reclassifies these emails based on improvements to our machine learning models. +Reclassifications happen when users or admins [submit a phish](/cloudflare-one/email-security/settings/submission-settings/) to Email security. Cloudflare reviews and - in some cases - reclassifies these emails based on improvements to our machine learning models. This new tab increases your visibility into this process, allowing you to view what submissions you have made and what the outcomes of those submissions are. diff --git a/src/content/changelog/email-security-cf1/2025-02-25-dlp-assist-for-m365.mdx b/src/content/changelog/email-security-cf1/2025-02-25-dlp-assist-for-m365.mdx index 109b144b623..8b05bdc5790 100644 --- a/src/content/changelog/email-security-cf1/2025-02-25-dlp-assist-for-m365.mdx +++ b/src/content/changelog/email-security-cf1/2025-02-25-dlp-assist-for-m365.mdx @@ -8,7 +8,7 @@ Cloudflare Email security customers who have Microsoft 365 environments can quic Simply deploy our add-in, create a DLP policy in Cloudflare, and configure Outlook to trigger behaviors like displaying a banner, alerting end users before sending, or preventing delivery entirely. -Refer to [Outbound Data Loss Prevention](/cloudflare-one/email-security/outbound-dlp/) to learn more about this feature. +Refer to [Outbound Data Loss Prevention](/cloudflare-one/email-security/policies/outbound/outbound-dlp/) to learn more about this feature. In GUI alert: diff --git a/src/content/changelog/email-security-cf1/2025-09-01-updated-new-roles.mdx b/src/content/changelog/email-security-cf1/2025-09-01-updated-new-roles.mdx index 4bb1aac2ac5..52f4e1c1c61 100644 --- a/src/content/changelog/email-security-cf1/2025-09-01-updated-new-roles.mdx +++ b/src/content/changelog/email-security-cf1/2025-09-01-updated-new-roles.mdx @@ -15,9 +15,9 @@ All Email security roles no longer have read or write access to any of the other - **Email security Policy Admin** - **Email security Reporting** -To configure [Data Loss Prevention (DLP)](/cloudflare-one/email-security/outbound-dlp/) or [Remote Browser Isolation (RBI)](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/#set-up-clientless-web-isolation), you now need to be an admin for the Zero Trust dashboard with the **Cloudflare Zero Trust** role. +To configure [Data Loss Prevention (DLP)](/cloudflare-one/email-security/policies/outbound/outbound-dlp/) or [Remote Browser Isolation (RBI)](/cloudflare-one/remote-browser-isolation/setup/clientless-browser-isolation/#set-up-clientless-web-isolation), you now need to be an admin for the Zero Trust dashboard with the **Cloudflare Zero Trust** role. -Also through customer feedback, we have created a new additive role to allow **Email security Analyst** to create, edit, and delete Email security policies, without needing to provide access via the **Email Configuration Admin** role. This role is called **Email security Policy Admin**, which can read all settings, but has write access to [allow policies](/cloudflare-one/email-security/settings/detection-settings/allow-policies/), [trusted domains](/cloudflare-one/email-security/settings/detection-settings/trusted-domains/), and [blocked senders](/cloudflare-one/email-security/settings/detection-settings/blocked-senders/). +Also through customer feedback, we have created a new additive role to allow **Email security Analyst** to create, edit, and delete Email security policies, without needing to provide access via the **Email Configuration Admin** role. This role is called **Email security Policy Admin**, which can read all settings, but has write access to [allow policies](/cloudflare-one/email-security/policies/inbound/allow-policies/), [trusted domains](/cloudflare-one/email-security/policies/inbound/trusted-domains/), and [blocked senders](/cloudflare-one/email-security/policies/inbound/blocked-senders/). This feature is available across these Email security packages: diff --git a/src/content/changelog/email-security-cf1/2025-09-23-invalid-submissions.mdx b/src/content/changelog/email-security-cf1/2025-09-23-invalid-submissions.mdx index ecd78ebb27e..ef46766a6ab 100644 --- a/src/content/changelog/email-security-cf1/2025-09-23-invalid-submissions.mdx +++ b/src/content/changelog/email-security-cf1/2025-09-23-invalid-submissions.mdx @@ -6,7 +6,7 @@ date: 2025-09-23T23:11:49Z Email security relies on your submissions to continuously improve our detection models. However, we often receive submissions in formats that cannot be ingested, such as incomplete EMLs, screenshots, or text files. -To ensure all customer feedback is actionable, we have launched two new features to manage invalid submissions sent to our team and user [submission aliases](/cloudflare-one/email-security/settings/phish-submissions/submission-addresses/): +To ensure all customer feedback is actionable, we have launched two new features to manage invalid submissions sent to our team and user [submission aliases](/cloudflare-one/email-security/settings/submission-settings/submission-addresses/): - **Email Notifications:** We now automatically notify users by email when they provide an invalid submission, educating them on the correct format. To disable notifications, go to **[Settings](https://one.dash.cloudflare.com/?to=/:account/email-security/settings)** > **Invalid submission emails** and turn the feature off. diff --git a/src/content/changelog/email-security-cf1/2026-08-12-blocked-content-rules.mdx b/src/content/changelog/email-security-cf1/2026-08-12-blocked-content-rules.mdx index ad66beffb8a..776f9ccf032 100644 --- a/src/content/changelog/email-security-cf1/2026-08-12-blocked-content-rules.mdx +++ b/src/content/changelog/email-security-cf1/2026-08-12-blocked-content-rules.mdx @@ -18,4 +18,4 @@ This feature is available for the following Email security packages: - **Enterprise** - **Enterprise + PhishGuard** -To get started, refer to [Blocked content](/cloudflare-one/email-security/settings/detection-settings/blocked-content/). +To get started, refer to [Blocked content](/cloudflare-one/email-security/policies/inbound/blocked-content/). diff --git a/src/content/changelog/sandbox/2026-06-09-deprecating-sandbox-sdk-features.mdx b/src/content/changelog/sandbox/2026-06-09-deprecating-sandbox-sdk-features.mdx index e8f0900ec97..90d1c6c6bd8 100644 --- a/src/content/changelog/sandbox/2026-06-09-deprecating-sandbox-sdk-features.mdx +++ b/src/content/changelog/sandbox/2026-06-09-deprecating-sandbox-sdk-features.mdx @@ -7,43 +7,43 @@ date: 2026-06-09 --- :::note[Sandbox SDK 1.0 preview] -A preview of **Sandbox SDK 1.0** is available on `@cloudflare/sandbox@next`. For new projects, or to move past these deprecations in one migration, refer to the [Sandbox SDK 1.0 preview](/sandbox/1-0-preview/) and [Migrate](/sandbox/1-0-preview/migrate/). +A preview of **Sandbox SDK 1.0** is available on `@cloudflare/sandbox@next`. For new projects, or to move past these deprecations in one migration, refer to the [Sandbox SDK 1.0 preview](/sandbox/) and [Migrate](/sandbox/sdk/migrate/). ::: Today we are announcing the deprecation of several features from the Sandbox SDK. The SDK has grown and matured substantially since it first launched. As agent workflows have developed, we have shipped many new features and experiments so developers can easily integrate secure, isolated code execution into their workflows. -We want the SDK to continue providing a stable foundation for agentic workflows while we iterate quickly on the codebase. These deprecated features have either been superseded by newer capabilities or seen low adoption. Do not build new work on them. Migrate using the [2026 deprecation migration guide](/sandbox/guides/2026-deprecation/), or move to the [Sandbox SDK 1.0 preview](/sandbox/1-0-preview/) when you can. +We want the SDK to continue providing a stable foundation for agentic workflows while we iterate quickly on the codebase. These deprecated features have either been superseded by newer capabilities or seen low adoption. Do not build new work on them. Migrate using the [2026 deprecation migration guide](/sandbox/sdk/migrate/), or move to the [Sandbox SDK 1.0 preview](/sandbox/) when you can. ## HTTP and WebSocket transports In April 2026, we released the new RPC transport and deprecated the WebSocket transport. This setting governs how the sandbox container talks to the Workers ecosystem. The RPC transport removes the limitations of both the HTTP and WebSocket transports. As of this announcement, RPC is the recommended default. HTTP and WebSocket transports are deprecated and will not ship in future Sandbox SDK majors. -To migrate, update the `SANDBOX_TRANSPORT` variable to `rpc` or set the `transport` option when calling `getSandbox()`. For more information, refer to the [transport configuration documentation](/sandbox/configuration/transport/). +To migrate, update the `SANDBOX_TRANSPORT` variable to `rpc` or set the `transport` option when calling `getSandbox()`. For more information, refer to the [transport configuration documentation](/sandbox/sdk/configuration/transport/). ## Desktop -The desktop feature ran a full Linux desktop inside the sandbox (display server, desktop environment, and VNC/noVNC) so agents and apps could drive a GUI with screenshots, mouse, and keyboard — the same *computer-use* shape other sandbox products expose for UI automation. Adoption stayed low, and we removed it in `0.10.2`. If you need that capability again, you can build it on top of the sandbox with [extensions](/sandbox/1-0-preview/extensions/) rather than a built-in `sandbox.desktop` API. +The desktop feature ran a full Linux desktop inside the sandbox (display server, desktop environment, and VNC/noVNC) so agents and apps could drive a GUI with screenshots, mouse, and keyboard — the same *computer-use* shape other sandbox products expose for UI automation. Adoption stayed low, and we removed it in `0.10.2`. If you need that capability again, you can build it on top of the sandbox with [extensions](/sandbox/) rather than a built-in `sandbox.desktop` API. ## Expose ports -We recently released support for Cloudflare Tunnel in the Sandbox SDK. This provides a robust API for exposing services running in your sandbox to the public internet. It fixes issues many were facing with local development and deployment to `workers.dev` domains. To migrate from `exposePort()` to tunnels, refer to the [tunnels API documentation](/sandbox/api/tunnels/) and the [expose services guide](/sandbox/guides/expose-services/). +We recently released support for Cloudflare Tunnel in the Sandbox SDK. This provides a robust API for exposing services running in your sandbox to the public internet. It fixes issues many were facing with local development and deployment to `workers.dev` domains. To migrate from `exposePort()` to tunnels, refer to the [tunnels API documentation](/sandbox/sdk/api/tunnels/) and the [expose services guide](/sandbox/sdk/guides/expose-services/). ## Default sessions -By default, the `exec()` method in the Sandbox SDK maintains a default session across all calls, so a `cd` in one call is honored in the next. This convenience helped developers writing `exec` statements by hand, but confused agents and caused hard-to-trace bugs. As of `0.10.3`, we have introduced the [`enableDefaultSession`](/sandbox/configuration/sandbox-options/) flag on the `getSandbox()` interface to turn this off. Default sessions as a concept — and the flag — will be removed in an upcoming release. +By default, the `exec()` method in the Sandbox SDK maintains a default session across all calls, so a `cd` in one call is honored in the next. This convenience helped developers writing `exec` statements by hand, but confused agents and caused hard-to-trace bugs. As of `0.10.3`, we have introduced the [`enableDefaultSession`](/sandbox/sdk/configuration/sandbox-options/) flag on the `getSandbox()` interface to turn this off. Default sessions as a concept — and the flag — will be removed in an upcoming release. -We recommend setting `enableDefaultSession: false` today and using the [`sandbox.createSession()` API](/sandbox/api/sessions/) when you need the previous behavior. +We recommend setting `enableDefaultSession: false` today and using the [`sandbox.createSession()` API](/sandbox/sdk/api/sessions/) when you need the previous behavior. ## Other changes -We are also consolidating all APIs that buffer data to support streaming by default. This includes [`readFile`, `writeFile`](/sandbox/api/files/), and [`exec`](/sandbox/api/commands/). The stream equivalents will be removed. +We are also consolidating all APIs that buffer data to support streaming by default. This includes [`readFile`, `writeFile`](/sandbox/sdk/api/files/), and [`exec`](/sandbox/sdk/api/commands/). The stream equivalents will be removed. -We are exploring moving non-core features like the [code interpreter](/sandbox/guides/code-execution/), [terminal](/sandbox/api/terminal/), and [git APIs](/sandbox/guides/git-workflows/) into helpers. These features will retain their existing APIs, so migration should be simple. +We are exploring moving non-core features like the [code interpreter](/sandbox/sdk/guides/code-execution/), [terminal](/sandbox/sdk/api/terminal/), and [git APIs](/sandbox/sdk/guides/git-workflows/) into helpers. These features will retain their existing APIs, so migration should be simple. ## Next steps -If you use any of these features on the **current stable** package, refer to the [2026 deprecation migration guide](/sandbox/guides/2026-deprecation/). Coding agents can use the **`sandbox-stable`** skill for stable-package work and that guide for cleanup ([Agent setup](/agent-setup/) · [Cloudflare Skills](https://github.com/cloudflare/skills)). +If you use any of these features on the **current stable** package, refer to the [2026 deprecation migration guide](/sandbox/sdk/migrate/). Coding agents can use the **`sandbox-stable`** skill for stable-package work and that guide for cleanup ([Agent setup](/agent-setup/) · [Cloudflare Skills](https://github.com/cloudflare/skills)). -If you are moving to **Sandbox SDK 1.0** (`@next`), use the [1.0 preview](/sandbox/1-0-preview/) and [Migrate](/sandbox/1-0-preview/migrate/) guides instead — or the **`sandbox-migrate-to-next`** skill after installing Cloudflare Skills. New projects should prefer **`sandbox-next`** on `@next`. +If you are moving to **Sandbox SDK 1.0** (`@next`), use the [1.0 preview](/sandbox/) and [Migrate](/sandbox/sdk/migrate/) guides instead — or the **`sandbox-migrate-to-next`** skill after installing Cloudflare Skills. New projects should prefer **`sandbox-next`** on `@next`. For any questions, ask in the [Cloudflare Developers Discord](https://discord.gg/cloudflaredev). diff --git a/src/content/changelog/terraform/2025-05-06-terraform-v5.4.0-provider.mdx b/src/content/changelog/terraform/2025-05-06-terraform-v5.4.0-provider.mdx index 7196b870f9b..af0c7246ec7 100644 --- a/src/content/changelog/terraform/2025-05-06-terraform-v5.4.0-provider.mdx +++ b/src/content/changelog/terraform/2025-05-06-terraform-v5.4.0-provider.mdx @@ -6,7 +6,7 @@ products: date: 2025-05-06 --- -Earlier this year, we announced the launch of the new [Terraform v5 Provider](/changelog/2025-02-03-terraform-v5-provider/). Unlike the earlier Terraform providers, v5 is automatically generated based on the OpenAPI Schemas for our REST APIs. Since launch, we have seen an unexpectedly high number of [issues](https://github.com/cloudflare/terraform-provider-cloudflare) reported by customers. These issues currently impact about 15% of resources. We have been working diligently to address these issues across the company, and have released the v5.4.0 release which includes a number of bug fixes. Please keep an eye on this changelog for more information about upcoming releases. +Earlier this year, we announced the launch of the new [Terraform v5 Provider](/changelog/post/2025-02-03-terraform-v5-provider/). Unlike the earlier Terraform providers, v5 is automatically generated based on the OpenAPI Schemas for our REST APIs. Since launch, we have seen an unexpectedly high number of [issues](https://github.com/cloudflare/terraform-provider-cloudflare) reported by customers. These issues currently impact about 15% of resources. We have been working diligently to address these issues across the company, and have released the v5.4.0 release which includes a number of bug fixes. Please keep an eye on this changelog for more information about upcoming releases. ### Changes diff --git a/src/content/changelog/terraform/2025-05-19-terraform-v5.5.0-provider.mdx b/src/content/changelog/terraform/2025-05-19-terraform-v5.5.0-provider.mdx index d8df9287679..47b4a235010 100644 --- a/src/content/changelog/terraform/2025-05-19-terraform-v5.5.0-provider.mdx +++ b/src/content/changelog/terraform/2025-05-19-terraform-v5.5.0-provider.mdx @@ -6,7 +6,7 @@ products: date: 2025-05-19 --- -Earlier this year, we announced the launch of the new [Terraform v5 Provider](/changelog/2025-02-03-terraform-v5-provider/). Unlike the earlier Terraform providers, v5 is automatically generated based on the OpenAPI Schemas for our REST APIs. Since launch, we have seen an unexpectedly high number of [issues](https://github.com/cloudflare/terraform-provider-cloudflare) reported by customers. These issues currently impact about 15% of resources. We have been working diligently to address these issues across the company, and have released the v5.5.0 release which includes a number of bug fixes. Please keep an eye on this changelog for more information about upcoming releases. +Earlier this year, we announced the launch of the new [Terraform v5 Provider](/changelog/post/2025-02-03-terraform-v5-provider/). Unlike the earlier Terraform providers, v5 is automatically generated based on the OpenAPI Schemas for our REST APIs. Since launch, we have seen an unexpectedly high number of [issues](https://github.com/cloudflare/terraform-provider-cloudflare) reported by customers. These issues currently impact about 15% of resources. We have been working diligently to address these issues across the company, and have released the v5.5.0 release which includes a number of bug fixes. Please keep an eye on this changelog for more information about upcoming releases. ### Changes diff --git a/src/content/changelog/terraform/2025-06-17-terraform-v5.6.0-provider.mdx b/src/content/changelog/terraform/2025-06-17-terraform-v5.6.0-provider.mdx index 88d70bea959..75affa39fe9 100644 --- a/src/content/changelog/terraform/2025-06-17-terraform-v5.6.0-provider.mdx +++ b/src/content/changelog/terraform/2025-06-17-terraform-v5.6.0-provider.mdx @@ -6,7 +6,7 @@ products: date: 2025-06-17 --- -Earlier this year, we announced the launch of the new [Terraform v5 Provider](/changelog/2025-02-03-terraform-v5-provider/). +Earlier this year, we announced the launch of the new [Terraform v5 Provider](/changelog/post/2025-02-03-terraform-v5-provider/). Unlike the earlier Terraform providers, v5 is automatically generated based on the OpenAPI Schemas for our REST APIs. Since launch, we have seen an unexpectedly high number of [issues](https://github.com/cloudflare/terraform-provider-cloudflare) reported by customers. These issues currently impact about 15% of resources. We have been working diligently to address diff --git a/src/content/changelog/terraform/2025-07-11-terraform-v5.7.0-provider.mdx b/src/content/changelog/terraform/2025-07-11-terraform-v5.7.0-provider.mdx index aaabc9c5399..e5d21f1e9d5 100644 --- a/src/content/changelog/terraform/2025-07-11-terraform-v5.7.0-provider.mdx +++ b/src/content/changelog/terraform/2025-07-11-terraform-v5.7.0-provider.mdx @@ -6,7 +6,7 @@ products: date: 2025-07-14 --- -Earlier this year, we announced the launch of the new [Terraform v5 Provider](/changelog/2025-02-03-terraform-v5-provider/). We are aware of the high number of [issues](https://github.com/cloudflare/terraform-provider-cloudflare) reported by the Cloudflare community related to the v5 release, with 13.5% of resources impacted. We have committed to releasing improvements on a 2 week cadeance to ensure it's stability and relability, including the v5.7 release. +Earlier this year, we announced the launch of the new [Terraform v5 Provider](/changelog/post/2025-02-03-terraform-v5-provider/). We are aware of the high number of [issues](https://github.com/cloudflare/terraform-provider-cloudflare) reported by the Cloudflare community related to the v5 release, with 13.5% of resources impacted. We have committed to releasing improvements on a 2 week cadeance to ensure it's stability and relability, including the v5.7 release. Thank you for continuing to raise issues and please keep an eye on this changelog for more information about upcoming releases. diff --git a/src/content/changelog/terraform/2025-08-01-terraform-v5.8.2-provider.mdx b/src/content/changelog/terraform/2025-08-01-terraform-v5.8.2-provider.mdx index 280ce29c2ae..2f22abf7523 100644 --- a/src/content/changelog/terraform/2025-08-01-terraform-v5.8.2-provider.mdx +++ b/src/content/changelog/terraform/2025-08-01-terraform-v5.8.2-provider.mdx @@ -6,7 +6,7 @@ products: date: 2025-08-01 --- -Earlier this year, we announced the launch of the new [Terraform v5 Provider](/changelog/2025-02-03-terraform-v5-provider/). We are aware of the high number of [issues](https://github.com/cloudflare/terraform-provider-cloudflare) reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a 2 week cadeance to ensure it's stability and reliability. We have also pivoted from an issue-to-issue approach to a resource-per-resource approach - we will be focusing on specific resources for every release, stabilizing the release and closing all associated bugs with that resource before moving onto resolving migration issues. +Earlier this year, we announced the launch of the new [Terraform v5 Provider](/changelog/post/2025-02-03-terraform-v5-provider/). We are aware of the high number of [issues](https://github.com/cloudflare/terraform-provider-cloudflare) reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a 2 week cadeance to ensure it's stability and reliability. We have also pivoted from an issue-to-issue approach to a resource-per-resource approach - we will be focusing on specific resources for every release, stabilizing the release and closing all associated bugs with that resource before moving onto resolving migration issues. Thank you for continuing to raise issues. We triage them weekly and they help make our products stronger. diff --git a/src/content/changelog/terraform/2025-08-15-terraform-v5.8.4-provider.mdx b/src/content/changelog/terraform/2025-08-15-terraform-v5.8.4-provider.mdx index 32201f4ca38..d6d848b5c34 100644 --- a/src/content/changelog/terraform/2025-08-15-terraform-v5.8.4-provider.mdx +++ b/src/content/changelog/terraform/2025-08-15-terraform-v5.8.4-provider.mdx @@ -6,7 +6,7 @@ products: date: 2025-08-15 --- -Earlier this year, we announced the launch of the new [Terraform v5 Provider](/changelog/2025-02-03-terraform-v5-provider/). We are aware of the high number of [issues](https://github.com/cloudflare/terraform-provider-cloudflare) reported by the Cloudflare Community related to the v5 release. We have committed to releasing improvements on a two week cadence to ensure stability and reliability. +Earlier this year, we announced the launch of the new [Terraform v5 Provider](/changelog/post/2025-02-03-terraform-v5-provider/). We are aware of the high number of [issues](https://github.com/cloudflare/terraform-provider-cloudflare) reported by the Cloudflare Community related to the v5 release. We have committed to releasing improvements on a two week cadence to ensure stability and reliability. One key change we adopted in recent weeks is a pivot to more comprehensive, test-driven development. We are still evaluating individual issues, but are also investing in much deeper testing to drive our stabilization efforts. We will subsequently be investing in comprehensive migration scripts. As a result, you will see several of the highest traffic APIs have been stabilized in the most recent release, and are supported by comprehensive acceptance tests. diff --git a/src/content/changelog/terraform/2025-08-29-terrform-v5.9-provider.mdx b/src/content/changelog/terraform/2025-08-29-terrform-v5.9-provider.mdx index f25c1bc414c..8fffffba7ad 100644 --- a/src/content/changelog/terraform/2025-08-29-terrform-v5.9-provider.mdx +++ b/src/content/changelog/terraform/2025-08-29-terrform-v5.9-provider.mdx @@ -6,7 +6,7 @@ products: date: 2025-08-29 --- -Earlier this year, we announced the launch of the new [Terraform v5 Provider](/changelog/2025-02-03-terraform-v5-provider/). We are aware of the high number of [issues](https://github.com/cloudflare/terraform-provider-cloudflare) reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a 2 week cadence to ensure its stability and reliability, including the v5.9 release. We have also pivoted from an issue-to-issue approach to a resource-per-resource approach - we will be focusing on specific resources for every release, stabilizing the release, and closing all associated bugs with that resource before moving onto resolving migration issues. +Earlier this year, we announced the launch of the new [Terraform v5 Provider](/changelog/post/2025-02-03-terraform-v5-provider/). We are aware of the high number of [issues](https://github.com/cloudflare/terraform-provider-cloudflare) reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a 2 week cadence to ensure its stability and reliability, including the v5.9 release. We have also pivoted from an issue-to-issue approach to a resource-per-resource approach - we will be focusing on specific resources for every release, stabilizing the release, and closing all associated bugs with that resource before moving onto resolving migration issues. Thank you for continuing to raise issues. We triage them weekly and they help make our products stronger. diff --git a/src/content/changelog/tunnel/2026-01-15-warp-connector-ping-support.mdx b/src/content/changelog/tunnel/2026-01-15-warp-connector-ping-support.mdx index 71d772f279b..69dbdabed58 100644 --- a/src/content/changelog/tunnel/2026-01-15-warp-connector-ping-support.mdx +++ b/src/content/changelog/tunnel/2026-01-15-warp-connector-ping-support.mdx @@ -11,6 +11,6 @@ We have made it easier to validate connectivity when deploying [WARP Connector]( You can now `ping` the WARP Connector host directly on its LAN IP address immediately after installation. This provides a fast, familiar way to confirm that the Connector is online and reachable within your network before testing access to downstream services. -Starting with [version 2025.10.186.0](/changelog/2026-01-13-warp-linux-ga/), WARP Connector responds to traffic addressed to its own LAN IP, giving you immediate visibility into Connector reachability. +Starting with [version 2025.10.186.0](/changelog/post/2026-01-13-warp-linux-ga/), WARP Connector responds to traffic addressed to its own LAN IP, giving you immediate visibility into Connector reachability. Learn more about deploying [WARP Connector](/mesh/) and building private network connectivity with [Cloudflare One](/cloudflare-one/). \ No newline at end of file diff --git a/src/content/changelog/tunnel/2026-07-09-tunnel-routes-and-connections-api-changes.mdx b/src/content/changelog/tunnel/2026-07-09-tunnel-routes-and-connections-api-changes.mdx index dbb3e3b5d79..220106efd2e 100644 --- a/src/content/changelog/tunnel/2026-07-09-tunnel-routes-and-connections-api-changes.mdx +++ b/src/content/changelog/tunnel/2026-07-09-tunnel-routes-and-connections-api-changes.mdx @@ -98,4 +98,4 @@ Update any dashboards, monitoring scripts, or automation that parses `connection - **A single way to identify a route.** Consolidating on `route_id` removes the need to URL-encode CIDR ranges into the path and matches how every other resource in the Zero Trust Networks API is addressed. - **Consistency across the API.** Both changes align these endpoints with Cloudflare's standard REST conventions for resource identifiers and nested detail endpoints. -To learn more, refer to the [Zero Trust Networks API](/api/resources/zero_trust/subresources/networks/), the [Cloudflare Tunnel API](/api/resources/zero_trust/subresources/tunnels/), and [Routes](/cloudflare-one/networks/routes/) documentation. +To learn more, refer to the [Zero Trust Networks API](/api/resources/zero_trust/subresources/networks/), the [Cloudflare Tunnel API](/api/resources/zero_trust/subresources/tunnels/), and [Routes](/cloudflare-one/networks/routes/add-routes/) documentation. diff --git a/src/content/changelog/waf/2025-12-05-rcs-vuln.mdx b/src/content/changelog/waf/2025-12-05-rcs-vuln.mdx index 264163b08db..38f37e16f70 100644 --- a/src/content/changelog/waf/2025-12-05-rcs-vuln.mdx +++ b/src/content/changelog/waf/2025-12-05-rcs-vuln.mdx @@ -10,4 +10,4 @@ Cloudflare WAF now inspects request-payload size of up to 1 MB across all plans React payloads commonly have a default maximum size of 1 MB. Cloudflare WAF previously inspected up to 128 KB on Enterprise plans, with even lower limits on other plans. -**Update:** We later reinstated the maximum request-payload size the Cloudflare WAF inspects. Refer to [Updating the WAF maximum payload values](/changelog/2025-12-05-waf-max-payload-size-change/) for details. +**Update:** We later reinstated the maximum request-payload size the Cloudflare WAF inspects. Refer to [Updating the WAF maximum payload values](/changelog/post/2025-12-05-waf-max-payload-size-change/) for details. diff --git a/src/content/changelog/waf/2025-12-05-waf-max-payload-size-change.mdx b/src/content/changelog/waf/2025-12-05-waf-max-payload-size-change.mdx index aaefa573c26..93deb457c52 100644 --- a/src/content/changelog/waf/2025-12-05-waf-max-payload-size-change.mdx +++ b/src/content/changelog/waf/2025-12-05-waf-max-payload-size-change.mdx @@ -8,7 +8,7 @@ We are reinstating the maximum request-payload size the Cloudflare WAF inspects, **Key Findings** -On [December 5, 2025](/changelog/2025-12-05-rcs-vuln/), we initially attempted to increase the maximum WAF payload limit to 1 MB across all plans. However, an automatic rollout for all customers proved impractical because the increase led to a surge in false positives for existing managed rules. +On [December 5, 2025](/changelog/post/2025-12-05-rcs-vuln/), we initially attempted to increase the maximum WAF payload limit to 1 MB across all plans. However, an automatic rollout for all customers proved impractical because the increase led to a surge in false positives for existing managed rules. This issue was particularly notable within the Cloudflare Managed Ruleset and the Cloudflare OWASP Core Ruleset, impacting customer traffic. diff --git a/src/content/changelog/workers/2025-04-08-deploy-to-cloudflare-button.mdx b/src/content/changelog/workers/2025-04-08-deploy-to-cloudflare-button.mdx index b181a32cdbb..fd90e270846 100644 --- a/src/content/changelog/workers/2025-04-08-deploy-to-cloudflare-button.mdx +++ b/src/content/changelog/workers/2025-04-08-deploy-to-cloudflare-button.mdx @@ -14,7 +14,7 @@ The Deploy to Cloudflare button: 1. **Creates a new Git repository on your GitHub/ GitLab account**: Cloudflare will automatically clone and create a new repository on your account, so you can continue developing. 2. **Automatically provisions resources the app needs**: If your repository requires Cloudflare primitives like a [Workers KV namespace](/kv/), a [D1 database](/d1/), or an [R2 bucket](/r2/), Cloudflare will automatically provision them on your account and bind them to your Worker upon deployment. 3. **Configures Workers Builds (CI/CD)**: Every new push to your production branch on your newly created repository will automatically build and deploy courtesy of [Workers Builds](/workers/ci-cd/builds/). -4. **Adds preview URLs to each pull request**: If you'd like to test your changes before deploying, you can push changes to a [non-production branch](/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds) and [preview URLs](/workers/versions-and-deployments/preview-urls/) will be generated and [posted back to GitHub as a comment](/workers/ci-cd/builds/git-integration/github-integration/#pull-request-comment). +4. **Adds preview URLs to each pull request**: If you'd like to test your changes before deploying, you can push changes to a [non-production branch](/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds) and [preview URLs](/workers/versions-and-deployments/version-urls/) will be generated and [posted back to GitHub as a comment](/workers/ci-cd/builds/git-integration/github-integration/#pull-request-comment). ![Import repo or choose template](~/assets/images/workers/dtw-user-flow.png) diff --git a/src/content/changelog/workers/2025-08-08-support-long-branch-names-preview-aliases.mdx b/src/content/changelog/workers/2025-08-08-support-long-branch-names-preview-aliases.mdx index 5a2300e5af0..c8247261624 100644 --- a/src/content/changelog/workers/2025-08-08-support-long-branch-names-preview-aliases.mdx +++ b/src/content/changelog/workers/2025-08-08-support-long-branch-names-preview-aliases.mdx @@ -6,7 +6,7 @@ tags: date: 2025-08-14T01:00:00Z --- -We've updated [preview URLs](/workers/versions-and-deployments/preview-urls/) for Cloudflare Workers to support long branch names. +We've updated [preview URLs](/workers/versions-and-deployments/version-urls/) for Cloudflare Workers to support long branch names. Previously, branch and Worker names exceeding the 63-character DNS limit would cause alias generation to fail, leaving pull requests without aliased preview URLs. This particularly impacted teams relying on descriptive branch naming. diff --git a/src/content/changelog/workers/2025-09-07-builds-increased-cpu-paid.mdx b/src/content/changelog/workers/2025-09-07-builds-increased-cpu-paid.mdx index 8226df15cb8..74568bb2c3e 100644 --- a/src/content/changelog/workers/2025-09-07-builds-increased-cpu-paid.mdx +++ b/src/content/changelog/workers/2025-09-07-builds-increased-cpu-paid.mdx @@ -4,7 +4,7 @@ description: Increased the available vCPU for Workers Builds from 2 to 4 vCPUs f - workers date: 2025-09-18 --- -We recently [increased the available disk space](/changelog/2025-08-04-builds-increased-disk-size/) from 8 GB to 20 GB for **all** plans. Building on that improvement, we’re now doubling the CPU power available for paid plans — from 2 vCPU to **4 vCPU**. +We recently [increased the available disk space](/changelog/post/2025-08-04-builds-increased-disk-size/) from 8 GB to 20 GB for **all** plans. Building on that improvement, we’re now doubling the CPU power available for paid plans — from 2 vCPU to **4 vCPU**. These changes continue our focus on making [Workers Builds](/workers/ci-cd/builds/) faster and more reliable. diff --git a/src/content/changelog/workers/2025-09-16-remote-bindings-ga.mdx b/src/content/changelog/workers/2025-09-16-remote-bindings-ga.mdx index 037d11809f9..594d0e27c71 100644 --- a/src/content/changelog/workers/2025-09-16-remote-bindings-ga.mdx +++ b/src/content/changelog/workers/2025-09-16-remote-bindings-ga.mdx @@ -8,7 +8,7 @@ date: 2025-09-16 import { WranglerConfig, Aside } from "~/components"; -Three months ago [we announced the public beta](/changelog/2025-06-18-remote-bindings-beta/) of [remote bindings](/workers/local-development/#remote-bindings) for local development. Now, we're excited to say that it's available for everyone in Wrangler, Vite, and Vitest without using an experimental flag! +Three months ago [we announced the public beta](/changelog/post/2025-06-18-remote-bindings-beta/) of [remote bindings](/workers/local-development/#remote-bindings) for local development. Now, we're excited to say that it's available for everyone in Wrangler, Vite, and Vitest without using an experimental flag! With remote bindings, you can now connect to deployed resources like [R2 buckets](/r2/) and [D1 databases](/d1/) while running Worker code on your local machine. This means you can test your local code changes against real data and services, without the overhead of deploying for each iteration. diff --git a/src/content/changelog/workers/2025-09-17-update-preview-url-setting.mdx b/src/content/changelog/workers/2025-09-17-update-preview-url-setting.mdx index 9fe282634c4..4a01e2e246c 100644 --- a/src/content/changelog/workers/2025-09-17-update-preview-url-setting.mdx +++ b/src/content/changelog/workers/2025-09-17-update-preview-url-setting.mdx @@ -5,7 +5,7 @@ date: 2025-09-17 --- import { WranglerConfig, Aside } from "~/components"; -To prevent the accidental exposure of applications, we've updated how [Worker preview URLs](/workers/versions-and-deployments/preview-urls/) (`-..workers.dev`) are handled. We made this change to ensure preview URLs are only active when intentionally configured, improving the default security posture of your Workers. +To prevent the accidental exposure of applications, we've updated how [Worker preview URLs](/workers/versions-and-deployments/version-urls/) (`-..workers.dev`) are handled. We made this change to ensure preview URLs are only active when intentionally configured, improving the default security posture of your Workers. ## One-Time Update for Workers with workers.dev Disabled We performed a one-time update to disable preview URLs for existing Workers where the [workers.dev subdomain](/workers/configuration/routing/workers-dev/) was also disabled. @@ -16,7 +16,7 @@ If your Worker was affected, its preview URL (`-. diff --git a/src/content/docs/bots/get-started/bot-management.mdx b/src/content/docs/bots/get-started/bot-management.mdx index 19e908989ec..361922e5874 100644 --- a/src/content/docs/bots/get-started/bot-management.mdx +++ b/src/content/docs/bots/get-started/bot-management.mdx @@ -37,7 +37,7 @@ Bot Management is automatically enabled for Enterprise zones entitled with the a 5. Choose how your domain should respond to various types of traffic by selecting the associated edit icon. - For more details on verified bots, refer to [Verified Bots](/bots/concepts/bot/verified-bots/). - For more details on supported file types, refer to [Static resource protection](/bots/additional-configurations/static-resources/). - - For more details on invisible code injection, refer to [JavaScript detections](/bots/additional-configurations/javascript-detections/). + - For more details on invisible code injection, refer to [JavaScript detections](/cloudflare-challenges/challenge-types/javascript-detections/). - For more details on WordPress optimization, refer to [Super Bot Fight Mode for WordPress](/bots/troubleshooting/wordpress-loopback-issue/). diff --git a/src/content/docs/cache/get-started.mdx b/src/content/docs/cache/get-started.mdx index ab1be925723..9bbcc7376cb 100644 --- a/src/content/docs/cache/get-started.mdx +++ b/src/content/docs/cache/get-started.mdx @@ -74,7 +74,7 @@ These alterations only affect cached copies at Cloudflare's edge and do not chan * [Polish](/images/polish/) * [Hotlink Protection](/waf/tools/scrape-shield/hotlink-protection/) * [Email address obfuscation](/waf/tools/scrape-shield/email-address-obfuscation/) -* [Bot Management JavaScript Detections](/bots/additional-configurations/javascript-detections/) +* [Bot Management JavaScript Detections](/cloudflare-challenges/challenge-types/javascript-detections/) ## Troubleshoot diff --git a/src/content/docs/cf/projects/index.mdx b/src/content/docs/cf/projects/index.mdx index 3bc35f646c9..db76f01c3d0 100644 --- a/src/content/docs/cf/projects/index.mdx +++ b/src/content/docs/cf/projects/index.mdx @@ -264,7 +264,7 @@ cf workers versions create This command builds and validates the project the same way as `cf deploy`. It accepts `--prebuilt`, `--mode`, `--message`, `--tag`, `--secrets-file`, `--dry-run`, and `--worker`. Use `--preview-alias ` to give the version -a [preview URL](/workers/versions-and-deployments/preview-urls/) alias. +a [preview URL](/workers/versions-and-deployments/version-urls/) alias. To send traffic to an uploaded version, create a deployment: diff --git a/src/content/docs/cloudflare-challenges/concepts/how-challenges-work.mdx b/src/content/docs/cloudflare-challenges/concepts/how-challenges-work.mdx index 44a9b4ad7e8..28b90b5ff2a 100644 --- a/src/content/docs/cloudflare-challenges/concepts/how-challenges-work.mdx +++ b/src/content/docs/cloudflare-challenges/concepts/how-challenges-work.mdx @@ -14,7 +14,7 @@ Challenges can be issued in three primary ways depending on which Cloudflare pro | Product | Challenge type(s) | | --------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | | [WAF](/waf/) ([custom rules](/waf/custom-rules/), [rate limiting rules](/waf/rate-limiting-rules/), [IP access rules](/waf/tools/ip-access-rules/)) | [Interstitial Challenge Page](/cloudflare-challenges/challenge-types/challenge-pages/) | -| [Bot Management](/bots/get-started/bot-management/) | [JavaScript Detections](/bots/additional-configurations/javascript-detections/) | +| [Bot Management](/bots/get-started/bot-management/) | [JavaScript Detections](/cloudflare-challenges/challenge-types/javascript-detections/) | | [Bot Fight Mode](/bots/get-started/bot-fight-mode/), [Super Bot Fight Mode](/bots/get-started/super-bot-fight-mode/) | [Interstitial Challenge Page](/cloudflare-challenges/challenge-types/challenge-pages/) | | [Turnstile](/turnstile/) | Embedded widget | | [HTTP DDoS attack protection](/ddos-protection/managed-rulesets/http/) | Any Challenge | diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/observability.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/observability.mdx index 5af9ebfa3cc..da93da2a365 100644 --- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/observability.mdx +++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/observability.mdx @@ -20,7 +20,7 @@ There are a few ways to access logs with Workers for Platforms. They differ in h [Workers Logs](/workers/observability/logs/workers-logs/) automatically stores logs from your user Workers in your Cloudflare account, where you can query them with the [Query Builder](/workers/observability/query-builder/) or the [Workers Observability API](/api/resources/workers/subresources/observability/). Because it is fully managed, you can surface a per-user view of logs in your own dashboard without standing up a database, setting up Logpush, or deploying a Tail Worker. -Enable Workers Logs on a user Worker by including the `observability` setting in the [metadata](/cloudflare-for-platforms/workers-for-platforms/reference/metadata/) when you [upload the script](/api/resources/workers_for_platforms/subresources/dispatch/subresources/namespaces/subresources/scripts/methods/update/) to your dispatch namespace: +Enable Workers Logs on a user Worker by including the `observability` setting in the [metadata](/workers/configuration/multipart-upload-metadata/) when you [upload the script](/api/resources/workers_for_platforms/subresources/dispatch/subresources/namespaces/subresources/scripts/methods/update/) to your dispatch namespace: ```json { diff --git a/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx b/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx index 121295ecd7a..861ac27635b 100644 --- a/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx +++ b/src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx @@ -29,7 +29,7 @@ MCP server portals provide the following capabilities: - **Tool and prompt aliases**: Admins can [rename tools and prompts](#rename-tools-and-prompts-with-aliases) and edit their descriptions at the portal or server level without modifying the upstream MCP server. Aliases help end users find the right tool and help AI agents select the correct one. - **Context optimization**: Portals support query parameter options that reduce context window usage by minimizing or hiding tool definitions. Refer to [Optimize context](#optimize-context) for details. - **Non-browser client support**: MCP clients authenticate to the portal using a standard OAuth 2.0 authorization code flow via [managed OAuth](/cloudflare-one/access-controls/applications/http-apps/managed-oauth/). This managed OAuth configuration applies to the portal's Access application. It is separate from upstream OAuth used by individual MCP servers in the portal. Non-browser clients receive a `401` response with a `WWW-Authenticate` header pointing to Access's OAuth discovery endpoints, rather than a browser redirect. You can also connect using [Access service tokens](#connect-with-a-service-token) for machine-to-machine access. -- **Code Mode**: Code Mode collapses all upstream tools into two tools for search and code execution. The AI agent writes JavaScript that calls typed methods for each tool. The code runs in an isolated [Dynamic Worker](/workers/runtime-apis/bindings/worker-loader/) environment. Admins can control whether Code Mode is unavailable, optional, on by default, or required. Refer to [Code Mode](#code-mode) for configuration and connection instructions. +- **Code Mode**: Code Mode collapses all upstream tools into two tools for search and code execution. The AI agent writes JavaScript that calls typed methods for each tool. The code runs in an isolated [Dynamic Worker](/dynamic-workers/) environment. Admins can control whether Code Mode is unavailable, optional, on by default, or required. Refer to [Code Mode](#code-mode) for configuration and connection instructions. - **Observability**: Once the user's AI agent is connected to the portal, Cloudflare Access logs the individual requests made using the tools in the portal. You can optionally route portal traffic through [Cloudflare Gateway](#route-portal-traffic-through-gateway) for richer HTTP logging and data loss prevention (DLP) scanning. ## How it works @@ -772,7 +772,7 @@ For the full list of supported resource arguments, refer to the [Terraform provi ## Code Mode -[Code Mode](/agents/tools/codemode/) reduces context window usage by replacing upstream tool definitions with two tools for search and code execution. The connected AI agent writes JavaScript that calls typed `codemode.*` methods. The generated code runs in an isolated [Dynamic Worker](/workers/runtime-apis/bindings/worker-loader/) environment. Authentication credentials and environment variables remain outside the model context. +[Code Mode](/agents/tools/codemode/) reduces context window usage by replacing upstream tool definitions with two tools for search and code execution. The connected AI agent writes JavaScript that calls typed `codemode.*` methods. The generated code runs in an isolated [Dynamic Worker](/dynamic-workers/) environment. Authentication credentials and environment variables remain outside the model context. Code Mode is useful for portals with many MCP servers or tools. Context window usage stays fixed as the portal adds tools. @@ -1087,7 +1087,7 @@ For MCP clients with server configuration files: ### Search and execute -The `search_and_execute` option hides all upstream tools and exposes only two tools to the agent: `query` and `execute`. The `query` tool searches and retrieves tool definitions. The `execute` tool runs the upstream tools. The generated code runs in an isolated [Dynamic Worker](/workers/runtime-apis/bindings/worker-loader/) environment, which keeps authentication credentials and environment variables out of the model context. +The `search_and_execute` option hides all upstream tools and exposes only two tools to the agent: `query` and `execute`. The `query` tool searches and retrieves tool definitions. The `execute` tool runs the upstream tools. The generated code runs in an isolated [Dynamic Worker](/dynamic-workers/) environment, which keeps authentication credentials and environment variables out of the model context. This option reduces the initial token cost of portal tools to a small constant, regardless of how many tools are available. However, the agent becomes fully reliant on `query` to discover tools before it can call them. diff --git a/src/content/docs/cloudflare-one/data-loss-prevention/dlp-profiles/index.mdx b/src/content/docs/cloudflare-one/data-loss-prevention/dlp-profiles/index.mdx index 71d32f72a43..18af1a34bdf 100644 --- a/src/content/docs/cloudflare-one/data-loss-prevention/dlp-profiles/index.mdx +++ b/src/content/docs/cloudflare-one/data-loss-prevention/dlp-profiles/index.mdx @@ -34,7 +34,7 @@ To decide which data types to focus on, use [Passive Detection](/cloudflare-one/ product="cloudflare-one" /> -You can now use this profile in a [DLP policy](/cloudflare-one/data-loss-prevention/dlp-policies/#2-create-a-dlp-policy), [CASB integration](/cloudflare-one/cloud-and-saas-findings/casb-dlp/), [AI Gateway DLP policy](/ai-gateway/features/dlp/set-up-dlp/), or [Email Security outbound DLP policy](/cloudflare-one/email-security/outbound-dlp/). +You can now use this profile in a [DLP policy](/cloudflare-one/data-loss-prevention/dlp-policies/#2-create-a-dlp-policy), [CASB integration](/cloudflare-one/cloud-and-saas-findings/casb-dlp/), [AI Gateway DLP policy](/ai-gateway/features/dlp/set-up-dlp/), or [Email Security outbound DLP policy](/cloudflare-one/email-security/policies/outbound/outbound-dlp/). ## Build a custom profile @@ -42,4 +42,4 @@ You can now use this profile in a [DLP policy](/cloudflare-one/data-loss-prevent Before you apply a custom profile to production traffic, use [Test scan](/cloudflare-one/data-loss-prevention/test-scan/) to confirm that it detects the content you expect. -You can now use this profile in a [DLP policy](/cloudflare-one/data-loss-prevention/dlp-policies/#2-create-a-dlp-policy), [CASB integration](/cloudflare-one/cloud-and-saas-findings/casb-dlp/), [AI Gateway DLP policy](/ai-gateway/features/dlp/set-up-dlp/), or [Email Security outbound DLP policy](/cloudflare-one/email-security/outbound-dlp/). +You can now use this profile in a [DLP policy](/cloudflare-one/data-loss-prevention/dlp-policies/#2-create-a-dlp-policy), [CASB integration](/cloudflare-one/cloud-and-saas-findings/casb-dlp/), [AI Gateway DLP policy](/ai-gateway/features/dlp/set-up-dlp/), or [Email Security outbound DLP policy](/cloudflare-one/email-security/policies/outbound/outbound-dlp/). diff --git a/src/content/docs/cloudflare-one/data-loss-prevention/index.mdx b/src/content/docs/cloudflare-one/data-loss-prevention/index.mdx index cb1e066e34e..894003319ae 100644 --- a/src/content/docs/cloudflare-one/data-loss-prevention/index.mdx +++ b/src/content/docs/cloudflare-one/data-loss-prevention/index.mdx @@ -51,9 +51,9 @@ To get started, refer to [Scan SaaS applications with DLP](/cloudflare-one/cloud ## Email security -Data Loss Prevention integrates with [Cloudflare Email Security](/cloudflare-one/email-security/) to scan [outbound emails](/cloudflare-one/email-security/outbound-dlp/) for sensitive data. Outbound DLP requires [Microsoft 365](https://www.cloudflare.com/learning/cloud/what-is-microsoft-365/) and uses a client-side Outlook add-in to inspect emails before they are sent. +Data Loss Prevention integrates with [Cloudflare Email Security](/cloudflare-one/email-security/) to scan [outbound emails](/cloudflare-one/email-security/policies/outbound/outbound-dlp/) for sensitive data. Outbound DLP requires [Microsoft 365](https://www.cloudflare.com/learning/cloud/what-is-microsoft-365/) and uses a client-side Outlook add-in to inspect emails before they are sent. -To get started, refer to [Outbound Data Loss Prevention (DLP)](/cloudflare-one/email-security/outbound-dlp/). +To get started, refer to [Outbound Data Loss Prevention (DLP)](/cloudflare-one/email-security/policies/outbound/outbound-dlp/). ## Troubleshooting diff --git a/src/content/docs/cloudflare-one/email-security/index.mdx b/src/content/docs/cloudflare-one/email-security/index.mdx index ba5fbeb75d6..74ee042dee9 100644 --- a/src/content/docs/cloudflare-one/email-security/index.mdx +++ b/src/content/docs/cloudflare-one/email-security/index.mdx @@ -30,7 +30,7 @@ The Email security overview provides you with: - **Quick actions**, where you can: - View [submissions](/cloudflare-one/email-security/submissions/) - - Manage detection settings: manage [allow policies](/cloudflare-one/email-security/settings/detection-settings/allow-policies/), [blocked senders](/cloudflare-one/email-security/settings/detection-settings/blocked-senders/), [trusted domains](/cloudflare-one/email-security/settings/detection-settings/trusted-domains/), [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/) and [additional detections](/cloudflare-one/email-security/settings/detection-settings/additional-detections/). + - Manage detection settings: manage [allow policies](/cloudflare-one/email-security/policies/inbound/allow-policies/), [blocked senders](/cloudflare-one/email-security/policies/inbound/blocked-senders/), [trusted domains](/cloudflare-one/email-security/policies/inbound/trusted-domains/), [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/) and [additional detections](/cloudflare-one/email-security/settings/detection-settings/additional-detections/). - [Run screens](/cloudflare-one/email-security/investigation/search-email/#screen-criteria): Search, filter, reclassify, and bulk-move emails - **Recommendations**: Suggested next steps to improve your configuration. For example, submitting misclassified emails for reclassification, creating policies, or protecting users at risk of [impersonation](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/). - **Email security metrics**: Activity from the last seven days. diff --git a/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx b/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx index 014c621a7fc..36c8c9dcbba 100644 --- a/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx +++ b/src/content/docs/cloudflare-one/email-security/investigation/search-email.mdx @@ -136,7 +136,7 @@ To view status and actions for each email: - **View details**. - **View similar emails**. - **View submission detail**. - - **[Move](/cloudflare-one/email-security/settings/auto-moves/)** (only available if you authorized moves). + - **[Move](/cloudflare-one/email-security/settings/detection-settings/auto-moves/)** (only available if you authorized moves). - **[Submit for review](#reclassify-messages)**. ## Email details diff --git a/src/content/docs/cloudflare-one/email-security/monitoring/index.mdx b/src/content/docs/cloudflare-one/email-security/monitoring/index.mdx index ea58b10a9fd..1022ec722fa 100644 --- a/src/content/docs/cloudflare-one/email-security/monitoring/index.mdx +++ b/src/content/docs/cloudflare-one/email-security/monitoring/index.mdx @@ -28,8 +28,8 @@ The dashboard will display the following metrics: - [Disposition evaluation](/cloudflare-one/email-security/reference/dispositions-and-attributes/) - Detection details - [Impersonations](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/) -- [Phish submissions](/cloudflare-one/email-security/settings/phish-submissions/) -- [Auto-move events](/cloudflare-one/email-security/settings/auto-moves/) +- [Phish submissions](/cloudflare-one/email-security/settings/submission-settings/) +- [Auto-move events](/cloudflare-one/email-security/settings/detection-settings/auto-moves/) - [Detection settings metrics](/cloudflare-one/email-security/settings/detection-settings/) ## Email activity @@ -77,13 +77,13 @@ Impersonations are a form of phishing attack where the actor pretends to be some - To view all impersonation emails, select **View all impersonation emails**. - To view impersonated users, select **View impersonated users**. -Refer to [Trusted domains](/cloudflare-one/email-security/settings/detection-settings/trusted-domains/) to add a trusted domain, and [Impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/) to add a user to the impersonation registry. +Refer to [Trusted domains](/cloudflare-one/email-security/policies/inbound/trusted-domains/) to add a trusted domain, and [Impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/) to add a user to the impersonation registry. ## Phish submissions Phishing is a type of attack that involves stealing sensitive information with the aim of using and selling the information. -A phish submission happens when a user or an administrator reports a phishing attack. Refer to [Phish submissions](/cloudflare-one/email-security/settings/phish-submissions/) to learn how to submit a phish. +A phish submission happens when a user or an administrator reports a phishing attack. Refer to [Phish submissions](/cloudflare-one/email-security/settings/submission-settings/) to learn how to submit a phish. Phish submissions displays the following information: @@ -99,7 +99,7 @@ Auto-move events are emails moved to different inboxes based on the disposition This panel shows you the total number of auto-moves and the source folder from which these retractions are originating from. -Refer to [Auto-moves](/cloudflare-one/email-security/settings/auto-moves/) to configure auto-move events. +Refer to [Auto-moves](/cloudflare-one/email-security/settings/detection-settings/auto-moves/) to configure auto-move events. ## Detection settings metrics @@ -109,4 +109,4 @@ Detection settings metric displays information about: - **Blocked traffic**: Traffic that Email security automatically blocks from senders. Blocked traffic shows metrics on emails that were blocked from user inboxes. - **Domain age**: The number of days since domain registration. -Select **Configure** to configure policy and rules for [allowed traffic](/cloudflare-one/email-security/settings/detection-settings/allow-policies/), [blocked traffic](/cloudflare-one/email-security/settings/detection-settings/blocked-senders/) and [domain age](/cloudflare-one/email-security/settings/detection-settings/additional-detections/). +Select **Configure** to configure policy and rules for [allowed traffic](/cloudflare-one/email-security/policies/inbound/allow-policies/), [blocked traffic](/cloudflare-one/email-security/policies/inbound/blocked-senders/) and [domain age](/cloudflare-one/email-security/settings/detection-settings/additional-detections/). diff --git a/src/content/docs/cloudflare-one/email-security/phishguard.mdx b/src/content/docs/cloudflare-one/email-security/phishguard.mdx index 7509b89fc68..94dcb2e76d3 100644 --- a/src/content/docs/cloudflare-one/email-security/phishguard.mdx +++ b/src/content/docs/cloudflare-one/email-security/phishguard.mdx @@ -12,7 +12,7 @@ PhishGuard is a team of analysts that routinely inspects your email environment While Email security uses advanced technologies to protect your email inbox, PhishGuard offers an additional human component to protect your email environment against impersonation events, suspicious items, false negatives/false positives, and any new event that automated intelligent systems may miss due to a lack of context (for example, a compromised account activity). -PhishGuard only works on a post-delivery environment (only emails that have already landed in your email inbox are reviewed). As a result, PhishGuard analysts may [submit a message for review](/cloudflare-one/email-security/submissions/#submit-messages-for-review) or [auto-move](/cloudflare-one/email-security/settings/auto-moves/) based on their findings. +PhishGuard only works on a post-delivery environment (only emails that have already landed in your email inbox are reviewed). As a result, PhishGuard analysts may [submit a message for review](/cloudflare-one/email-security/submissions/#submit-messages-for-review) or [auto-move](/cloudflare-one/email-security/settings/detection-settings/auto-moves/) based on their findings. :::caution Auto-moves are mandatory for PhishGuard customers. @@ -74,7 +74,7 @@ Email threat hunting also gives you information on **Threat leads generated** an API Status allows you to monitor and configure the current status of API message auto-moves and directory integrations. -Select **Message moves** to [configure auto-moves](/cloudflare-one/email-security/settings/auto-moves/). Select **Directory integration** to [configure directories](/cloudflare-one/email-security/directories/). +Select **Message moves** to [configure auto-moves](/cloudflare-one/email-security/settings/detection-settings/auto-moves/). Select **Directory integration** to [configure directories](/cloudflare-one/email-security/settings/domains-and-directories/directories/). ## Managed email security operations @@ -82,7 +82,7 @@ Managed email security operations allows you to review the results of phish subm It displays the following: -- Total [phish submissions](/cloudflare-one/email-security/settings/phish-submissions/) +- Total [phish submissions](/cloudflare-one/email-security/settings/submission-settings/) - Tracked incidents - Median time to resolve - Resolved track incidents @@ -99,4 +99,4 @@ If you select the three dots, you can: - **Details**: Displays information such as delivery disposition, current disposition, ES Alert ID, Message-ID, Timestamp, Subject, and Attempted Fraudulent Amount. - **Indicators of compromise (IOC)**: [Indicators of compromise (IOC)](https://www.cloudflare.com/en-gb/learning/security/what-are-indicators-of-compromise/) are information about a specific security breach that can help security teams determine if an attack has taken place. - Preview email. -- [Move email](/cloudflare-one/email-security/settings/auto-moves/). +- [Move email](/cloudflare-one/email-security/settings/detection-settings/auto-moves/). diff --git a/src/content/docs/cloudflare-one/email-security/policies/outbound/outbound-dlp.mdx b/src/content/docs/cloudflare-one/email-security/policies/outbound/outbound-dlp.mdx index 7c1f8ed0cec..aee9d0a6b22 100644 --- a/src/content/docs/cloudflare-one/email-security/policies/outbound/outbound-dlp.mdx +++ b/src/content/docs/cloudflare-one/email-security/policies/outbound/outbound-dlp.mdx @@ -18,8 +18,8 @@ Outbound Data Loss Prevention ensures the protection of sensitive information in To enable Outbound DLP: -1. [Create an outbound policy](/cloudflare-one/email-security/outbound-dlp/#1-create-an-outbound-policy). -2. [Set up DLP Assist add-in](/cloudflare-one/email-security/outbound-dlp/#2-dlp-assist-add-in). +1. [Create an outbound policy](/cloudflare-one/email-security/policies/outbound/outbound-dlp/#1-create-an-outbound-policy). +2. [Set up DLP Assist add-in](/cloudflare-one/email-security/policies/outbound/outbound-dlp/#2-dlp-assist-add-in). ## 1. Create an outbound policy diff --git a/src/content/docs/cloudflare-one/email-security/reference/dispositions-and-attributes.mdx b/src/content/docs/cloudflare-one/email-security/reference/dispositions-and-attributes.mdx index b376e682daf..e11610aa97f 100644 --- a/src/content/docs/cloudflare-one/email-security/reference/dispositions-and-attributes.mdx +++ b/src/content/docs/cloudflare-one/email-security/reference/dispositions-and-attributes.mdx @@ -20,7 +20,7 @@ Detection is the process Email security does to identify what threat an email ma Any traffic that flows through Email security is given a final disposition, which represents our evaluation of that specific message. Each message will receive only one disposition header, so your organization can take clear and specific actions on different message types. -You can use disposition values when [setting up auto-moves](/cloudflare-one/email-security/settings/auto-moves/). +You can use disposition values when [setting up auto-moves](/cloudflare-one/email-security/settings/detection-settings/auto-moves/). ### Available values diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/additional-detections.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/additional-detections.mdx index e63fb6d1b04..0a68b0cdc65 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/additional-detections.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/additional-detections.mdx @@ -26,7 +26,7 @@ To configure additional detections: The domain age is the time since the domain has been registered. -Because of the domain age detection, [trusted domains](/cloudflare-one/email-security/settings/detection-settings/trusted-domains/) can be used to create an exception to the age detection. +Because of the domain age detection, [trusted domains](/cloudflare-one/email-security/policies/inbound/trusted-domains/) can be used to create an exception to the age detection. To configure a domain age: diff --git a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/best-practices.mdx b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/best-practices.mdx index c929a6a728d..323f7197866 100644 --- a/src/content/docs/cloudflare-one/email-security/settings/detection-settings/best-practices.mdx +++ b/src/content/docs/cloudflare-one/email-security/settings/detection-settings/best-practices.mdx @@ -12,13 +12,13 @@ This guide describes how to configure detection settings to mitigate impersonati Once you configure the [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/) to mitigate spoof detections, you can add emails in the impersonation registry as secondary email. Refer to [Edit users](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/#edit-users) to learn how to add a secondary email address. -For impersonation events that are caused by systems, Cloudflare recommends that you configure an [allow policy](/cloudflare-one/email-security/settings/detection-settings/allow-policies/) to mitigate delivery disruptions. +For impersonation events that are caused by systems, Cloudflare recommends that you configure an [allow policy](/cloudflare-one/email-security/policies/inbound/allow-policies/) to mitigate delivery disruptions. To maintain a higher security posture, allow policies should be defined with the narrowest possible scope. Start with specific expressions or email addresses that will target the actual sender or system. If the system is sending from a variety of addresses, you can create an expression that is wider while keeping the expression specific. In some situations, it is better to have multiple specific entries than a more generic policy that allows a whole domain. ## Policy selection criteria -When you configure an [allow policy](/cloudflare-one/email-security/settings/detection-settings/allow-policies/), you can choose how Email security handles messages that match your criteria. +When you configure an [allow policy](/cloudflare-one/email-security/policies/inbound/allow-policies/), you can choose how Email security handles messages that match your criteria. Allow policies are suitable for services that may spoof people's names. @@ -36,4 +36,4 @@ Example use cases: - Prioritize static IPs: Use known and owned, static IP addresses for relay servers. Avoid [ephemeral IP addresses](https://docs.cloud.google.com/vpc/docs/ip-addresses#ephemeral_and_static_ip_addresses) as their transient nature can lead to policy degradation. - Enforce Sender Verification: Always have **Sender Verification (Recommended)** enabled in the Cloudflare dashboard. It validates the originating system's email authentication records (namely [SPF](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-spf-record/), [DKIM](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dkim-record/), and [DMARC](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-dmarc-record/)) against the domain to ensure authenticity. -- Handle unsanctioned traffic: Unsanctioned traffic is traffic which has not been approved within an organization. This is also known as [Shadow IT](https://www.cloudflare.com/en-gb/learning/access-management/what-is-shadow-it/). If an unsanctioned system generates spam or spoofed content, [configure a text add-on](/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons/) to append a tag to the subject line and automatically [move](/cloudflare-one/email-security/settings/auto-moves/) the message to the junk folder. +- Handle unsanctioned traffic: Unsanctioned traffic is traffic which has not been approved within an organization. This is also known as [Shadow IT](https://www.cloudflare.com/en-gb/learning/access-management/what-is-shadow-it/). If an unsanctioned system generates spam or spoofed content, [configure a text add-on](/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons/) to append a tag to the subject line and automatically [move](/cloudflare-one/email-security/settings/detection-settings/auto-moves/) the message to the junk folder. diff --git a/src/content/docs/cloudflare-one/email-security/setup/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/index.mdx index c65b4336fa5..009e8d3e128 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/index.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/index.mdx @@ -32,8 +32,8 @@ The following table compares features available across API, BCC/Journaling and M Note that: - All email providers support MX/Inline deployment. -- Microsoft 365 or Google Workspace users who integrate Email security via API, BCC/Journaling can modify emails primarily through deletion or post-delivery [move](/cloudflare-one/email-security/settings/auto-moves/). -- Microsoft 365 or Google Workspace users who integrate Email security via MX/Inline can modify emails via post-delivery [move](/cloudflare-one/email-security/settings/auto-moves/), [link actions](/cloudflare-one/email-security/settings/detection-settings/configure-link-actions/) and [text add-ons](/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons/). +- Microsoft 365 or Google Workspace users who integrate Email security via API, BCC/Journaling can modify emails primarily through deletion or post-delivery [move](/cloudflare-one/email-security/settings/detection-settings/auto-moves/). +- Microsoft 365 or Google Workspace users who integrate Email security via MX/Inline can modify emails via post-delivery [move](/cloudflare-one/email-security/settings/detection-settings/auto-moves/), [link actions](/cloudflare-one/email-security/settings/detection-settings/configure-link-actions/) and [text add-ons](/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons/). ## 1. Choose a deployment @@ -47,7 +47,7 @@ If you are a [Google Workspace](/cloudflare-one/email-security/setup/post-delive #### Why you should consider post-delivery deployment -Post-delivery deployment is time-efficient, because it does not involve MX changes. Post-delivery deployment does not disrupt mail flow. Post-delivery deployment allows you to enable [auto-move events](/cloudflare-one/email-security/settings/auto-moves/) to hard or soft delete messages, and synchronize your [directory](/cloudflare-one/email-security/directories/) when you use Microsoft Graph API or Google Workspace. +Post-delivery deployment is time-efficient, because it does not involve MX changes. Post-delivery deployment does not disrupt mail flow. Post-delivery deployment allows you to enable [auto-move events](/cloudflare-one/email-security/settings/detection-settings/auto-moves/) to hard or soft delete messages, and synchronize your [directory](/cloudflare-one/email-security/settings/domains-and-directories/directories/) when you use Microsoft Graph API or Google Workspace. :::note When you choose post-delivery deployment: @@ -130,7 +130,7 @@ Follow the below checklist to ensure your email environment is set up correctly: | Associate an integration with an MX/Inline domain | | Required | | Add/verify domains | Required | Required | | [Update MX records/connector](/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup/), then allow Cloudflare [egress IPs](/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips/) on downstream mail server | | Required | -| Populate [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/) and [allow](/cloudflare-one/email-security/settings/detection-settings/allow-policies/)/[block](/cloudflare-one/email-security/settings/detection-settings/blocked-senders/) lists | Required | Required | +| Populate [impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/) and [allow](/cloudflare-one/email-security/policies/inbound/allow-policies/)/[block](/cloudflare-one/email-security/policies/inbound/blocked-senders/) lists | Required | Required | | Configure [partner domain TLS](/cloudflare-one/email-security/setup/pre-delivery-deployment/partner-domain-tls/) and admin quarantine | | Required | | Configure [text add-ons](/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons/) and [link actions](/cloudflare-one/email-security/settings/detection-settings/configure-link-actions/) | | Required | | Send a test email and verify it appears in **Monitoring** > [**Email activity**](/cloudflare-one/email-security/monitoring/#email-activity) with expected disposition | Required | Required | diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/api/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/api/index.mdx index 0cb8028b0cc..90903557a16 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/api/index.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/api/index.mdx @@ -10,7 +10,7 @@ sidebar: When you choose an API deployment, email messages only reach Email security after they have already reached a user's inbox. -Then, through an integration with your email provider, Email security can [auto-move messages](/cloudflare-one/email-security/settings/auto-moves/) based on your organization's policies. +Then, through an integration with your email provider, Email security can [auto-move messages](/cloudflare-one/email-security/settings/detection-settings/auto-moves/) based on your organization's policies. ![With API deployment, messages travel through Email security's email filter after reaching your users.](~/assets/email-security/M365_API_Deployment_Graph.png) diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/api/m365-api.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/api/m365-api.mdx index fdd6e5cc02d..8277025900e 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/api/m365-api.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/api/m365-api.mdx @@ -59,7 +59,7 @@ On the **Set up Email security** page, you will be able to connect your Microsof 1. **Connect domains**: Select at least one domain. Then, select **Continue**. 2. (Optional) **Modify default scanning**: You can configure which folder Email security can scan. -3. (Optional - select **Skip for now** to skip this step) **Redirect messages**: Refer to [Auto-moves](/cloudflare-one/email-security/settings/auto-moves/) to learn what auto-moves are, and how to configure auto-moves. +3. (Optional - select **Skip for now** to skip this step) **Redirect messages**: Refer to [Auto-moves](/cloudflare-one/email-security/settings/detection-settings/auto-moves/) to learn what auto-moves are, and how to configure auto-moves. 4. **Review details**: Review your connected domains, then select **Go to Domains**. Your domains are now connected successfully. diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/connect-domains.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/connect-domains.mdx index 0d6916e81d6..94df6bab637 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/connect-domains.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/connect-domains.mdx @@ -17,13 +17,13 @@ On the **Set up Email security** page: 1. **Connect domains**: Select at least one domain. Then, select **Continue**. 2. (**Optional**) **Add manual domains**: Select **Add domain name** to manually enter additional domains. Then, select **Continue**. 3. (**Optional**) **Adjust hop count**: Enter the number of hops. Then, select **Continue**. Configuring the hop count will determine where you want Cloudflare to sit in the email processing chain. -4. (**Optional**, select **Skip for now** to skip this step) **Move messages**: Refer to [Auto-moves](/cloudflare-one/email-security/settings/auto-moves/) to configure auto-moves. Then, select **Continue**. +4. (**Optional**, select **Skip for now** to skip this step) **Move messages**: Refer to [Auto-moves](/cloudflare-one/email-security/settings/detection-settings/auto-moves/) to configure auto-moves. Then, select **Continue**. 5. **Select your processing location**: Configure where you want Cloudflare to process your email. **Global** will be the default option. If you choose **Global**, `@CF-emailsecurity.com` will be your regional service address. Once you have chosen your processing location, select **Continue**. Refer to [Regional processing](/cloudflare-one/email-security/reference/regional-processing/) to learn more. 6. **Review details**: Review your connected domains and service addresses. Then, select **Go to domains.** Your domains are now added successfully. -On the **Domains** page, select the three dots > **View integration**. The dashboard will display your [domain information](/cloudflare-one/email-security/settings/domain-management/domain/). +On the **Domains** page, select the three dots > **View integration**. The dashboard will display your [domain information](/cloudflare-one/email-security/settings/domains-and-directories/domains/). Under **Source**, the dashboard will display **Google integration**, along with the **Integration name**. diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/gmail-bcc-setup.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/gmail-bcc-setup.mdx index c34bda7121a..d3b27a93a98 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/gmail-bcc-setup.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/gmail-bcc-setup.mdx @@ -12,7 +12,7 @@ For customers using Gmail as their email provider, setting up Email security is You will need to [create an integration](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration/), [add BCC rules](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/add-bcc-rules/), and [connect your domain(s)](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/connect-domains/). You can choose to [add additional domains](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/connect-domains/#add-additional-domains) at a later stage. -Once you set up Google integration, Email security will receive a copy of your email messages. You will need a Google integration to enable [auto-moves](/cloudflare-one/email-security/settings/auto-moves/). +Once you set up Google integration, Email security will receive a copy of your email messages. You will need a Google integration to enable [auto-moves](/cloudflare-one/email-security/settings/detection-settings/auto-moves/). The following email flow shows how this works: diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx index 8ff736556bd..f95d89d3cd8 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/m365-journaling.mdx @@ -47,7 +47,7 @@ On the **Set up Email security** page: 1. **Connect domains**: Select at least one domain. Then, select **Continue**. 2. (**Optional**) **Add manual domains**: Select **Add domain name** to manually enter additional domains. Then, select **Continue**. 3. (**Optional**) **Adjust hop count**: Enter the number of hops. Then, select **Continue**. -4. (**Optional**, select **Skip for now** to skip this step) **Move messages**: Refer to [Auto-moves](/cloudflare-one/email-security/settings/auto-moves/) to configure auto-moves. Then, select **Continue**. +4. (**Optional**, select **Skip for now** to skip this step) **Move messages**: Refer to [Auto-moves](/cloudflare-one/email-security/settings/detection-settings/auto-moves/) to configure auto-moves. Then, select **Continue**. 5. **Select your processing location**: Configure where you want Cloudflare to [process your email](/cloudflare-one/email-security/reference/regional-processing/). **Global** will be the default option. If you choose **Global**, `@CF-emailsecurity.com` will be your regional service address. Once you have chosen your processing location, select **Continue**. 6. **Review details**: Review your connected domains and service addresses. Then, select **Go to domains.** diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx index 4c636aa1972..c464d2abd30 100644 --- a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx +++ b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/manual-add.mdx @@ -11,7 +11,7 @@ import { GlossaryTooltip, Render } from "~/components"; This page will teach you how to manually add domains via BCC/Journaling on the Cloudflare dashboard. -This setup is ideal if your email provider is not Microsoft 365 or Google Workspace, or you do not want to directly integrate your account. Beware that manually add does not support [auto-move](/cloudflare-one/email-security/settings/auto-moves/) or [directory synchronization](/cloudflare-one/email-security/directories/). +This setup is ideal if your email provider is not Microsoft 365 or Google Workspace, or you do not want to directly integrate your account. Beware that manually add does not support [auto-move](/cloudflare-one/email-security/settings/detection-settings/auto-moves/) or [directory synchronization](/cloudflare-one/email-security/settings/domains-and-directories/directories/). ## Prerequisites @@ -72,4 +72,4 @@ To associate an integration: 4. Select **Connect an integration**. Follow the steps to [enable the Microsoft 365 integration](/cloudflare-one/email-security/setup/post-delivery-deployment/api/m365-api/#enable-microsoft-integration). 5. Select the three dots, then select **Associate an integration**. Select the integration, then select **Associate**. -Now that your domain has an associated integration, enable [auto-move events](/cloudflare-one/email-security/settings/auto-moves/) on your domain. +Now that your domain has an associated integration, enable [auto-move events](/cloudflare-one/email-security/settings/detection-settings/auto-moves/) on your domain. diff --git a/src/content/docs/cloudflare-one/email-security/submissions/user-submissions.mdx b/src/content/docs/cloudflare-one/email-security/submissions/user-submissions.mdx index 157f7404a08..f15d47d44db 100644 --- a/src/content/docs/cloudflare-one/email-security/submissions/user-submissions.mdx +++ b/src/content/docs/cloudflare-one/email-security/submissions/user-submissions.mdx @@ -10,7 +10,7 @@ sidebar: User submissions are the emails your users submitted for submission. User submissions help enhance our detection model, but can be escalated for human review. -Any email that is reported as [phish](/cloudflare-one/email-security/settings/phish-submissions/#reclassify-an-email) will be displayed under **User submissions**. +Any email that is reported as [phish](/cloudflare-one/email-security/settings/submission-settings/#reclassify-an-email) will be displayed under **User submissions**. :::note [PhishGuard](/cloudflare-one/email-security/phishguard/) customers can have submissions analyzed when submitting at either user or team level. Any non-PhishGuard customer can still have submissions analyzed by submitting at team level. diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall.mdx index 5954dd3c2bb..5c5a7da1ead 100644 --- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall.mdx +++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-with-firewall.mdx @@ -103,7 +103,7 @@ Allows `cloudflared` to report [post-quantum key exchange](https://blog.cloudfla | -------------- | -------------- | -------------- | -------------- | | Not applicable | Not applicable | Not applicable | Not applicable | -Performing a DNS query for a `TXT` record to this hostname allows `cloudflared` to determine which version of [UDP datagram](/changelog/2025-07-15-udp-improvements/) to use when connecting via the `quic` protocol. If your firewall filters egress DNS queries by FQDN, you may need to allow queries for this domain to ensure optimal `quic` performance. +Performing a DNS query for a `TXT` record to this hostname allows `cloudflared` to determine which version of [UDP datagram](/changelog/post/2025-07-15-udp-improvements/) to use when connecting via the `quic` protocol. If your firewall filters egress DNS queries by FQDN, you may need to allow queries for this domain to ensure optimal `quic` performance. ## Firewall configuration diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/index.mdx index b7b422cd309..38d539f2595 100644 --- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/index.mdx +++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/appliance/network-options/application-based-policies/index.mdx @@ -11,9 +11,9 @@ import { DirectoryListing } from "~/components"; Standard traffic policies match on network-layer attributes like IP addresses and port ranges. Application-aware policies go further — they identify traffic by the application generating it, so you can make routing and security decisions based on what the traffic is, not just where it is going. -Cloudflare One Appliance (formerly Magic WAN Connector) classifies traffic using the same application categories used across Cloudflare's [Secure Web Gateway](/cloudflare-one/policies/gateway/). This means routing decisions on the Appliance and security policies in Gateway use the same application definitions. +Cloudflare One Appliance (formerly Magic WAN Connector) classifies traffic using the same application categories used across Cloudflare's [Secure Web Gateway](/cloudflare-one/traffic-policies/). This means routing decisions on the Appliance and security policies in Gateway use the same application definitions. -For the full list of recognized applications and categories, refer to [Applications and app types](/cloudflare-one/policies/gateway/application-app-types/). +For the full list of recognized applications and categories, refer to [Applications and app types](/cloudflare-one/traffic-policies/application-app-types/). With application-aware policies, you can: diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet.mdx index 8b9661f952e..9e626f33b98 100644 --- a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet.mdx +++ b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-wan/configuration/third-party/fortinet.mdx @@ -69,7 +69,7 @@ end ### Configure NAT-T (optional) :::note -This configuration is no longer required. Cloudflare now supports NAT-T starting on UDP port `500`, so devices can negotiate the standard NAT-T flow without forcing port `4500`. Refer to the [changelog entry](/changelog/2026-05-11-nat-t-port-500/) for details. This guide has not been re-tested since the change. +This configuration is no longer required. Cloudflare now supports NAT-T starting on UDP port `500`, so devices can negotiate the standard NAT-T flow without forcing port `4500`. Refer to the [changelog entry](/changelog/post/2026-05-11-nat-t-port-500/) for details. This guide has not been re-tested since the change. ::: If you have Network Address Translation Traversal (NAT-T) on your network, you can enable this feature and initiate Internet Key Exchange (IKE) communications on port `4500`. diff --git a/src/content/docs/cloudflare-one/networks/virtual-networks.mdx b/src/content/docs/cloudflare-one/networks/virtual-networks.mdx index be3b5f47dd7..8da69d70c0e 100644 --- a/src/content/docs/cloudflare-one/networks/virtual-networks.mdx +++ b/src/content/docs/cloudflare-one/networks/virtual-networks.mdx @@ -129,5 +129,5 @@ To add static routes or configure BGP peering within the Cloudflare Virtual Netw ## Related resources - [Private networks](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/) — Connect your infrastructure to Cloudflare -- [Routes](/cloudflare-one/networks/routes/) — Define IP and hostname routes through your connectors +- [Routes](/cloudflare-one/networks/routes/add-routes/) — Define IP and hostname routes through your connectors - [Traffic steering](/cloudflare-one/networks/connectors/cloudflare-wan/reference/traffic-steering/) — Route prioritization, ECMP, and BGP within the Cloudflare Virtual Network diff --git a/src/content/docs/cloudflare-one/roles-permissions.mdx b/src/content/docs/cloudflare-one/roles-permissions.mdx index f602ee0decc..e45aabb15a5 100644 --- a/src/content/docs/cloudflare-one/roles-permissions.mdx +++ b/src/content/docs/cloudflare-one/roles-permissions.mdx @@ -57,4 +57,4 @@ For more information on Email security roles, refer to [Account-scoped roles](/f - **Email security Analyst**: Has analyst access. Can take action on emails and read emails. - **Email security Reporting**: Can read metrics. - **Email security Read Only**: Can read all information, but cannot take action on anything. -- **Email security Policy Admin**: Can read all settings, but only write [allow policies](/cloudflare-one/email-security/settings/detection-settings/allow-policies/), [trusted domains](/cloudflare-one/email-security/settings/detection-settings/trusted-domains/), and [blocked senders](/cloudflare-one/email-security/settings/detection-settings/blocked-senders/). +- **Email security Policy Admin**: Can read all settings, but only write [allow policies](/cloudflare-one/email-security/policies/inbound/allow-policies/), [trusted domains](/cloudflare-one/email-security/policies/inbound/trusted-domains/), and [blocked senders](/cloudflare-one/email-security/policies/inbound/blocked-senders/). diff --git a/src/content/docs/cloudflare-wan/configuration/third-party/fortinet.mdx b/src/content/docs/cloudflare-wan/configuration/third-party/fortinet.mdx index 058b2a81bd0..58926ccc405 100644 --- a/src/content/docs/cloudflare-wan/configuration/third-party/fortinet.mdx +++ b/src/content/docs/cloudflare-wan/configuration/third-party/fortinet.mdx @@ -67,7 +67,7 @@ end ### Configure NAT-T (optional) :::note -This configuration is no longer required. Cloudflare now supports NAT-T starting on UDP port `500`, so devices can negotiate the standard NAT-T flow without forcing port `4500`. Refer to the [changelog entry](/changelog/2026-05-11-nat-t-port-500/) for details. This guide has not been re-tested since the change. +This configuration is no longer required. Cloudflare now supports NAT-T starting on UDP port `500`, so devices can negotiate the standard NAT-T flow without forcing port `4500`. Refer to the [changelog entry](/changelog/post/2026-05-11-nat-t-port-500/) for details. This guide has not been re-tested since the change. ::: If you have Network Address Translation Traversal (NAT-T) on your network, you can enable this feature and initiate Internet Key Exchange (IKE) communications on port `4500`. diff --git a/src/content/docs/cloudflare-wan/reference/virtual-networks.mdx b/src/content/docs/cloudflare-wan/reference/virtual-networks.mdx index be2aff99352..cfd48821821 100644 --- a/src/content/docs/cloudflare-wan/reference/virtual-networks.mdx +++ b/src/content/docs/cloudflare-wan/reference/virtual-networks.mdx @@ -127,5 +127,5 @@ To add static routes or configure BGP peering within the Cloudflare Virtual Netw ## Related resources - [Private networks](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/) — Connect your infrastructure to Cloudflare -- [Routes](/cloudflare-one/networks/routes/) — Define IP and hostname routes through your connectors +- [Routes](/cloudflare-one/networks/routes/add-routes/) — Define IP and hostname routes through your connectors - [Traffic steering](/cloudflare-wan/reference/traffic-steering/) — Route prioritization, ECMP, and BGP within the Cloudflare Virtual Network diff --git a/src/content/docs/containers/configuration/outbound-traffic.mdx b/src/content/docs/containers/configuration/outbound-traffic.mdx index 3445218c084..a019ae90c39 100644 --- a/src/content/docs/containers/configuration/outbound-traffic.mdx +++ b/src/content/docs/containers/configuration/outbound-traffic.mdx @@ -421,6 +421,6 @@ The `Container` class calls these methods automatically when you use the functio ## Related resources - [Connect to Workers bindings](/containers/configuration/workers-connections/) — Access KV, R2, Durable Objects, and other bindings from a container -- [Control outbound traffic (Sandboxes)](/sandbox/guides/outbound-traffic/) — Sandbox SDK API for outbound handlers +- [Control outbound traffic (Sandboxes)](/sandbox/sdk/guides/outbound-traffic/) — Sandbox SDK API for outbound handlers - [Environment variables and secrets](/containers/configuration/environment-variables/) — Configure secrets and environment variables - [Durable Object Container API](/containers/api/durable-object-container/) — Full `ctx.container` API reference diff --git a/src/content/docs/dynamic-workers/examples/dynamic-workers-starter.mdx b/src/content/docs/dynamic-workers/examples/dynamic-workers-starter.mdx index 0baf6221af4..18636433ce3 100644 --- a/src/content/docs/dynamic-workers/examples/dynamic-workers-starter.mdx +++ b/src/content/docs/dynamic-workers/examples/dynamic-workers-starter.mdx @@ -19,7 +19,7 @@ A [starter template](https://github.com/cloudflare/agents/tree/main/examples/dyn ## What it does -This template demonstrates how to use the [Worker Loader API](/workers/runtime-apis/bindings/worker-loader/) to execute code at runtime. The host Worker exposes an `/api/run` endpoint that accepts code from the frontend, loads it into a sandboxed Dynamic Worker, and returns the result. +This template demonstrates how to use the [Worker Loader API](/dynamic-workers/) to execute code at runtime. The host Worker exposes an `/api/run` endpoint that accepts code from the frontend, loads it into a sandboxed Dynamic Worker, and returns the result. Use this pattern for AI agents that need to execute a snippet of code to complete an action. diff --git a/src/content/docs/dynamic-workers/usage/dynamic-workflows.mdx b/src/content/docs/dynamic-workers/usage/dynamic-workflows.mdx index e6002b5cdee..574f7cf80fb 100644 --- a/src/content/docs/dynamic-workers/usage/dynamic-workflows.mdx +++ b/src/content/docs/dynamic-workers/usage/dynamic-workflows.mdx @@ -213,5 +213,5 @@ curl "http://localhost:8787/api/status?instanceId=YOUR_INSTANCE_ID" - [Trigger Workflows](/workflows/build/trigger-workflows/) - [Events and parameters](/workflows/build/events-and-parameters/) - [Dynamic Workers getting started](/dynamic-workers/getting-started/) -- [Dynamic Worker Loaders](/workers/runtime-apis/bindings/worker-loader/) +- [Dynamic Worker Loaders](/dynamic-workers/) - [Bindings with Dynamic Workers](/dynamic-workers/usage/bindings/) diff --git a/src/content/docs/email-security/migrate-to-email-security.mdx b/src/content/docs/email-security/migrate-to-email-security.mdx index 0c0c234d566..220ec843b32 100644 --- a/src/content/docs/email-security/migrate-to-email-security.mdx +++ b/src/content/docs/email-security/migrate-to-email-security.mdx @@ -63,7 +63,7 @@ Starting from October 1, 2025, Area 1 webhooks will be visible in Zero Trust Ema In Area 1, you can [create alert webhooks](/email-security/email-configuration/domains-and-routing/alert-webhooks/#create-an-alert-webhook). -In Zero Trust Email security, webhooks are instead referred to as logs. You can enable [detection logs](/cloudflare-one/insights/logs/logpush/email-security-logs/#enable-detection-logs) and/or [user action logs](/cloudflare-one/insights/logs/logpush/email-security-logs/#enable-user-action-logs). Additionally, you can enable [Outbound Data Loss Prevention](/cloudflare-one/email-security/outbound-dlp/) to protect sensitive information in outbound emails. +In Zero Trust Email security, webhooks are instead referred to as logs. You can enable [detection logs](/cloudflare-one/insights/logs/logpush/email-security-logs/#enable-detection-logs) and/or [user action logs](/cloudflare-one/insights/logs/logpush/email-security-logs/#enable-user-action-logs). Additionally, you can enable [Outbound Data Loss Prevention](/cloudflare-one/email-security/policies/outbound/outbound-dlp/) to protect sensitive information in outbound emails. ## Set up system alerts @@ -123,7 +123,7 @@ In Email security, you can check your metrics in the [Monitoring](/cloudflare-on Area 1 allows you to set up [message retraction](/email-security/email-configuration/retract-settings/) to move messages to specific folders. This is known as **retraction**. -Moving messages to a specific folder is known as [auto-moves](/cloudflare-one/email-security/settings/auto-moves/) in Zero Trust Email security. +Moving messages to a specific folder is known as [auto-moves](/cloudflare-one/email-security/settings/detection-settings/auto-moves/) in Zero Trust Email security. ## Create policies @@ -131,9 +131,9 @@ This table displays the difference in terminology used when creating policies: | Area 1 | Email security | | --------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | -| [Allowed patterns](/email-security/email-configuration/lists/allowed-patterns/) | [Allow policies](/cloudflare-one/email-security/settings/detection-settings/allow-policies/) | -| [Block lists](/email-security/email-configuration/lists/block-list/) | [Blocked senders](/cloudflare-one/email-security/settings/detection-settings/blocked-senders/) | -| [Trusted domains](/email-security/email-configuration/lists/trusted-domains/) | [Trusted domains](/cloudflare-one/email-security/settings/detection-settings/trusted-domains/) | +| [Allowed patterns](/email-security/email-configuration/lists/allowed-patterns/) | [Allow policies](/cloudflare-one/email-security/policies/inbound/allow-policies/) | +| [Block lists](/email-security/email-configuration/lists/block-list/) | [Blocked senders](/cloudflare-one/email-security/policies/inbound/blocked-senders/) | +| [Trusted domains](/email-security/email-configuration/lists/trusted-domains/) | [Trusted domains](/cloudflare-one/email-security/policies/inbound/trusted-domains/) | | [Text add-ons](/email-security/email-configuration/email-policies/text-addons/) | [Text add-ons](/cloudflare-one/email-security/settings/detection-settings/configure-text-add-ons/) | | [Link actions](/email-security/email-configuration/email-policies/link-actions/) | [Link actions](/cloudflare-one/email-security/settings/detection-settings/configure-link-actions/) | | [Added detections](/email-security/email-configuration/enhanced-detections/added-detections/) | [Additional detections](/cloudflare-one/email-security/settings/detection-settings/additional-detections/) | @@ -159,7 +159,7 @@ In Email security, this feature is known as [impersonation registry](/cloudflare In Area 1, you can [integrate directories](/email-security/email-configuration/enhanced-detections/business-email-compromise/#integrating-a-directory) in your email provider. -In Email security, you can add and sync [directories](/cloudflare-one/email-security/directories/). +In Email security, you can add and sync [directories](/cloudflare-one/email-security/settings/domains-and-directories/directories/). ## API diff --git a/src/content/docs/fundamentals/api/reference/permissions.mdx b/src/content/docs/fundamentals/api/reference/permissions.mdx index 251b07d66ce..aea8b5895fa 100644 --- a/src/content/docs/fundamentals/api/reference/permissions.mdx +++ b/src/content/docs/fundamentals/api/reference/permissions.mdx @@ -153,8 +153,8 @@ The `AI Gateway Read`, `Run`, and `Edit` permissions are account-scoped only — | Cloudforce One Edit | Grants write access to Cloudforce One. | | Email Security Read | Grants read access to [Cloud Email Security](/email-security/). | | Email Security Edit | Grants write access to [Email Security](/email-security/). | -| Constellation Read | Grants read access to [Constellation](/constellation/). | -| Constellation Edit | Grants write access to [Constellation](/constellation/). | +| Constellation Read | Grants read access to [Constellation](/workers-ai/). | +| Constellation Edit | Grants write access to [Constellation](/workers-ai/). | | Containers Read | Grants read access to [Containers](/containers/). | | Containers Edit | Grants write access to [Containers](/containers/). | | D1 Read | Grants read access to [D1](/d1/). | @@ -331,8 +331,8 @@ The `AI Gateway Read`, `Run`, and `Edit` permissions are account-scoped only — | Cloudforce One Write | Grants write access to Cloudforce One. | | Cloud Email Security: Read | Grants read access to [Cloud Email Security](/email-security/). | | Cloud Email Security: Write | Grants write access to [Email Security](/email-security/). | -| Constellation Read | Grants read access to [Constellation](/constellation/). | -| Constellation Write | Grants write access to [Constellation](/constellation/). | +| Constellation Read | Grants read access to [Constellation](/workers-ai/). | +| Constellation Write | Grants write access to [Constellation](/workers-ai/). | | Containers Read | Grants read access to [Containers](/containers/). | | Containers Write | Grants write access to [Containers](/containers/). | | D1 Read | Grants read access to [D1](/d1/). | diff --git a/src/content/docs/fundamentals/manage-members/roles.mdx b/src/content/docs/fundamentals/manage-members/roles.mdx index 477ca330138..9f268a79e33 100644 --- a/src/content/docs/fundamentals/manage-members/roles.mdx +++ b/src/content/docs/fundamentals/manage-members/roles.mdx @@ -69,7 +69,7 @@ Account-scoped roles apply across an entire Cloudflare account, and through all | Email Security Analyst | Grants analyst access. Can take action on emails and read emails. | | Email Security Read only | Grants read only access to all of Email security. | | Email Security Reporting | Grants read access to Email security metrics. | -| Email Security Policy Admin | Grants read access to all settings, and write access to [allow policies](/cloudflare-one/email-security/settings/detection-settings/allow-policies/), [trusted domains](/cloudflare-one/email-security/settings/detection-settings/trusted-domains/), and [blocked senders](/cloudflare-one/email-security/settings/detection-settings/blocked-senders/) | +| Email Security Policy Admin | Grants read access to all settings, and write access to [allow policies](/cloudflare-one/email-security/policies/inbound/allow-policies/), [trusted domains](/cloudflare-one/email-security/policies/inbound/trusted-domains/), and [blocked senders](/cloudflare-one/email-security/policies/inbound/blocked-senders/) | | Firewall | Can edit [WAF](/waf/), [IP Access rules](/waf/tools/ip-access-rules/), [Zone Lockdown](/waf/tools/zone-lockdown/) settings, [Cache Rules](/cache/how-to/cache-rules/), and [Cache Response Rules](/cache/how-to/cache-response-rules/). | | HTTP Applications | Grants full access to HTTP Applications. | | HTTP Applications Read | Grants read-only access to HTTP Applications. | diff --git a/src/content/docs/fundamentals/reference/cdn-cgi-endpoint.mdx b/src/content/docs/fundamentals/reference/cdn-cgi-endpoint.mdx index f040e11a625..6fdc1449fad 100644 --- a/src/content/docs/fundamentals/reference/cdn-cgi-endpoint.mdx +++ b/src/content/docs/fundamentals/reference/cdn-cgi-endpoint.mdx @@ -13,7 +13,7 @@ This endpoint is managed and served by Cloudflare. It cannot be modified or cust A few examples include (but are not limited to): * [Identify the Cloudflare data center serving your request](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#identify-the-cloudflare-data-center-serving-your-request), which is helpful for troubleshooting (`https:///cdn-cgi/trace`). -* [JavaScript detection](/bots/additional-configurations/javascript-detections/) used by Cloudflare bot products (`example.com/cdn-cgi/challenge-platform/`) +* [JavaScript detection](/cloudflare-challenges/challenge-types/javascript-detections/) used by Cloudflare bot products (`example.com/cdn-cgi/challenge-platform/`) * [Image transformations](/images/optimization/transformations/overview/) in the new URLs you would use for images (`example.com/cdn-cgi/image/`) * [Email address obfuscation](/waf/tools/scrape-shield/email-address-obfuscation/) used to hide email addresses from malicious bots (`example.com/cdn-cgi/l/email-protection`) * [Web analytics](/web-analytics/get-started/#sites-proxied-through-cloudflare) for a website proxied through Cloudflare (`example.com/cdn-cgi/rum`). This endpoint returns a `204` HTTP status code. diff --git a/src/content/docs/fundamentals/reference/migration-guides/scim-virtual-groups-migration.mdx b/src/content/docs/fundamentals/reference/migration-guides/scim-virtual-groups-migration.mdx index 15fcb26bc96..60a07062b89 100644 --- a/src/content/docs/fundamentals/reference/migration-guides/scim-virtual-groups-migration.mdx +++ b/src/content/docs/fundamentals/reference/migration-guides/scim-virtual-groups-migration.mdx @@ -17,7 +17,7 @@ While customers could add or remove members from these groups within their IdP, - They could not be managed within Cloudflare. - Functionally, managing a Virtual Group was equivalent to syncing users and editing each member’s policies individually. -With the GA of [User Groups](/changelog/2025-06-23-user-groups-ga/), Virtual Groups are now deprecated. Customers should migrate to [User Groups](/fundamentals/manage-members/user-groups/), which provide a more flexible and scalable way to assign and manage policies. To maintain SCIM synchronization with the Cloudflare Dashboard, we strongly recommend migrating to **SCIM User Groups**. +With the GA of [User Groups](/changelog/post/2025-06-23-user-groups-ga/), Virtual Groups are now deprecated. Customers should migrate to [User Groups](/fundamentals/manage-members/user-groups/), which provide a more flexible and scalable way to assign and manage policies. To maintain SCIM synchronization with the Cloudflare Dashboard, we strongly recommend migrating to **SCIM User Groups**. If you have never synced a group linked to a `CF--` Virtual Group from your IdP to Cloudflare, no action is needed. @@ -32,7 +32,7 @@ If you have never synced a group linked to a `CF--` Virtua ## More resources -* [User Groups changelog](/changelog/2025-06-02-user-groups-beta/) +* [User Groups changelog](/changelog/post/2025-06-02-user-groups-beta/) * [User Groups documentation](/fundamentals/manage-members/user-groups/) * [Create an Account Owned Token](/fundamentals/api/get-started/account-owned-tokens/#create-an-account-owned-token) * [SCIM provisioning setup guide](/fundamentals/account/account-security/scim-setup/) diff --git a/src/content/docs/fundamentals/reference/policies-compliances/cloudflare-cookies.mdx b/src/content/docs/fundamentals/reference/policies-compliances/cloudflare-cookies.mdx index d34d51355ad..e87e63221cd 100644 --- a/src/content/docs/fundamentals/reference/policies-compliances/cloudflare-cookies.mdx +++ b/src/content/docs/fundamentals/reference/policies-compliances/cloudflare-cookies.mdx @@ -59,7 +59,7 @@ Bot Management is available to Enterprise customers as an add-on service. Contac ### cf_clearance cookie for Cloudflare bot products -The `cf_clearance` cookie is required for [JavaScript detections](/bots/additional-configurations/javascript-detections/). JavaScript detections are stored in the `cf_clearance` cookie. +The `cf_clearance` cookie is required for [JavaScript detections](/cloudflare-challenges/challenge-types/javascript-detections/). JavaScript detections are stored in the `cf_clearance` cookie. The `cf_clearance` cookie is set with `SameSite=None; Secure; Partitioned` so that challenge state is preserved across cross-site requests while complying with [CHIPS ↗](https://developers.google.com/privacy-sandbox/cookies/chips). When the cookie is issued inside a third-party context, it is stored in a partition keyed to the top-level site and is not shared across embedding sites. For details, refer to [Partitioned cookies (CHIPS) and `cf_clearance`](/waf/troubleshooting/samesite-cookie-interaction/#partitioned-cookies-chips-and-cf_clearance). diff --git a/src/content/docs/learning-paths/cybersafe/email-security-onboarding/email-security-next-steps.mdx b/src/content/docs/learning-paths/cybersafe/email-security-onboarding/email-security-next-steps.mdx index 48450f88d81..ee5007340f8 100644 --- a/src/content/docs/learning-paths/cybersafe/email-security-onboarding/email-security-next-steps.mdx +++ b/src/content/docs/learning-paths/cybersafe/email-security-onboarding/email-security-next-steps.mdx @@ -14,10 +14,10 @@ Now that you have learned how Email security can protect your inbox from phishin | Resource | Description | | ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [Phish submissions](/cloudflare-one/email-security/settings/phish-submissions/) | As part of your continuous email security posture, administrators and security analysts need to submit missed phish samples so Cloudflare can process them and take necessary action. | +| [Phish submissions](/cloudflare-one/email-security/settings/submission-settings/) | As part of your continuous email security posture, administrators and security analysts need to submit missed phish samples so Cloudflare can process them and take necessary action. | | [API integration](/cloudflare-one/email-security/setup/post-delivery-deployment/api/) | Onboard your domain via API deployment. | | [Impersonation registry](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/) | The impersonation registry contains combinations of emails of users who are likely to be impersonated. | -| [Trusted domains](/cloudflare-one/email-security/settings/detection-settings/trusted-domains/) | Trusted domains allows you to identify domains that should be exempted from Email security detections. | -| [Allow policies](/cloudflare-one/email-security/settings/detection-settings/allow-policies/) | Allow policies exempt messages that match certain patterns from normal detection scanning. | -| [Blocked senders](/cloudflare-one/email-security/settings/detection-settings/blocked-senders/) | Blocked senders can mark all messages from specific senders with a `MALICIOUS` disposition. | +| [Trusted domains](/cloudflare-one/email-security/policies/inbound/trusted-domains/) | Trusted domains allows you to identify domains that should be exempted from Email security detections. | +| [Allow policies](/cloudflare-one/email-security/policies/inbound/allow-policies/) | Allow policies exempt messages that match certain patterns from normal detection scanning. | +| [Blocked senders](/cloudflare-one/email-security/policies/inbound/blocked-senders/) | Blocked senders can mark all messages from specific senders with a `MALICIOUS` disposition. | | [PhishGuard](/cloudflare-one/email-security/phishguard/) | PhishGuard is a managed email security service that provides resources for end-to-end phish and targeted attack management and response. | diff --git a/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/index.mdx b/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/index.mdx index 99194b1606d..48216040b37 100644 --- a/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/index.mdx +++ b/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/index.mdx @@ -21,8 +21,8 @@ The dashboard will display the following metrics: - [Disposition evaluation](/cloudflare-one/email-security/reference/dispositions-and-attributes/) - Detection details - [Impersonations](/cloudflare-one/email-security/settings/detection-settings/impersonation-registry/) -- [Phish submissions](/cloudflare-one/email-security/settings/phish-submissions/) -- [Auto-move events](/cloudflare-one/email-security/settings/auto-moves/) +- [Phish submissions](/cloudflare-one/email-security/settings/submission-settings/) +- [Auto-move events](/cloudflare-one/email-security/settings/detection-settings/auto-moves/) - [Detection settings metrics](/cloudflare-one/email-security/settings/detection-settings/) Email activity aggregates statistics about emails scanned and dispositions assigned (the number of email flagged due to a detection) within a given timeframe. diff --git a/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/monitor-detections.mdx b/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/monitor-detections.mdx index 2f5d85db0ca..2563c3a0ccf 100644 --- a/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/monitor-detections.mdx +++ b/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/monitor-detections.mdx @@ -17,7 +17,7 @@ Messages that receive a Spoof disposition should be investigated because it sign In most cases, a Spoof disposition is triggered by a legitimate third-party mail service. If you determine that the Spoofed email is a legitimate business use case, you can either: - Update your email authentication records. -- Add an acceptable sender [allow policy](/cloudflare-one/email-security/settings/detection-settings/allow-policies/) to exempt messages from the Spam, Spoof, or Bulk disposition, but not Malicious or Suspicious, so the content of the message can still be monitored. +- Add an acceptable sender [allow policy](/cloudflare-one/email-security/policies/inbound/allow-policies/) to exempt messages from the Spam, Spoof, or Bulk disposition, but not Malicious or Suspicious, so the content of the message can still be monitored. ## Search email messages diff --git a/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx b/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx index c004be94781..c959dc1b2d9 100644 --- a/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx +++ b/src/content/docs/learning-paths/secure-your-email/monitor-your-inbox/phish-submissions.mdx @@ -10,10 +10,10 @@ products: While Email security offers industry leading detection efficacy due to Cloudflare's Threat Intelligence, Preemptive Threat Hunting (actor and campaign infrastructure hunting with 8B, plus campaign threat signals assessed every day) and ML-Based Detection Models (Trust Graphs Computer Vision, Sentiment/Thread/Structural Analysis, Industry/Natural Language Understanding Modeling) false negatives and false positive can occur. -There are two different ways to [submit a phish](/cloudflare-one/email-security/settings/phish-submissions/) sample: +There are two different ways to [submit a phish](/cloudflare-one/email-security/settings/submission-settings/) sample: - User submission: - - Submitted directly by the end user, and used with phish submission buttons. To learn more about user-submitted phish, refer to [PhishNet for Microsoft 365](/cloudflare-one/email-security/settings/phish-submissions/#phishnet-o365) or [PhishNet for Google Workspace](/cloudflare-one/email-security/settings/submission-settings/phishnet-google-workspace/). + - Submitted directly by the end user, and used with phish submission buttons. To learn more about user-submitted phish, refer to [PhishNet for Microsoft 365](/cloudflare-one/email-security/settings/submission-settings/phishnet-365/) or [PhishNet for Google Workspace](/cloudflare-one/email-security/settings/submission-settings/phishnet-google-workspace/). - User submissions can create another challenge for your organization. While it is important for end users to be vigilant and report what they believe may be a phishing email, they are often wrong. About 90% of the time, when an end user reports a missed phishing email, they are mistaken. This puts an extra burden on busy security teams as they sift through end user reports. The PhishGuard team at Cloudflare can solve this problem for your organization by reviewing end user submissions for you. - Admin submission: - To be used when IT administrators or security teams submit to Email security. Submit original phish samples as an attachment in EML format to the appropriate team submission address. diff --git a/src/content/docs/logs/logpush/pricing.mdx b/src/content/docs/logs/logpush/pricing.mdx index b0f95d822d7..745a8bce6fe 100644 --- a/src/content/docs/logs/logpush/pricing.mdx +++ b/src/content/docs/logs/logpush/pricing.mdx @@ -26,7 +26,7 @@ R2 and Pipelines are internal destinations. All other destinations are external. Existing Enterprise contracts retain their current Logpush pricing through renewal. Contact your account team for contract-specific pricing. ::: -Logpush rates do not include charges from destination services. For internal destinations, refer to [R2 pricing](/r2/pricing/) and [Pipelines pricing](/pipelines/platform/pricing/). +Logpush rates do not include charges from destination services. For internal destinations, refer to [R2 pricing](/r2/pricing/) and [Pipelines pricing](/basin-pipelines/platform/pricing/). ## Measure usage diff --git a/src/content/docs/logs/logpush/transformers.mdx b/src/content/docs/logs/logpush/transformers.mdx index 0c2fb25468b..b8d2d771307 100644 --- a/src/content/docs/logs/logpush/transformers.mdx +++ b/src/content/docs/logs/logpush/transformers.mdx @@ -320,5 +320,5 @@ To debug, open the transformer in [Transformer Studio](#transformer-studio-ui) a - [Logpush datasets](/logs/logpush/logpush-job/datasets/) - the fields your SQL queries reference - [Logpush job setup](/logs/logpush/logpush-job/) - creating and managing Logpush jobs -- [Log fields reference](/logs/reference/log-fields/) - full field descriptions across datasets +- [Log fields reference](/logs/logpush/logpush-job/datasets/) - full field descriptions across datasets - [Filters](/logs/logpush/logpush-job/filters/) - simpler filtering without SQL diff --git a/src/content/docs/magic-transit/about.mdx b/src/content/docs/magic-transit/about.mdx index d24ff959ee9..1b251f605f4 100644 --- a/src/content/docs/magic-transit/about.mdx +++ b/src/content/docs/magic-transit/about.mdx @@ -57,4 +57,4 @@ linkStyle 4 stroke-width:3px,stroke:green Cloudflare's China Network does not yet support Magic Transit. ::: -For detailed information on Magic Transit architecture, refer to the [Reference section](/magic-transit/reference/). +For detailed information on Magic Transit architecture, refer to the [Reference section](/magic-transit/reference/anti-replay-protection/). diff --git a/src/content/docs/reference-architecture/architectures/email-security-deployments.mdx b/src/content/docs/reference-architecture/architectures/email-security-deployments.mdx index 8991f05c3d5..7b0b672a26f 100644 --- a/src/content/docs/reference-architecture/architectures/email-security-deployments.mdx +++ b/src/content/docs/reference-architecture/architectures/email-security-deployments.mdx @@ -124,7 +124,7 @@ Cisco offers a unique capability to integrate with Cloudflare using a connector An alternative approach is to integrate via the Graph [API](/cloudflare-one/email-security/setup/post-delivery-deployment/api/m365-api/) in Microsoft 365. In this model, emails are delivered directly to the user inbox, where Cloudflare then receives copies of messages, scans them, and moves them as configured by [disposition](/cloudflare-one/email-security/reference/dispositions-and-attributes/#dispositions). -This is performed by subscribing to all user mailboxes on the authorized domains. You have the ability to choose if the scope should be restricted to the Inbox only, or All Folders during the authorization process. Upon delivery to the mailbox, the subscription triggers an action within Microsoft 365 that sends Cloudflare a copy of the email to be scanned and assigned a disposition. Once the disposition has been assigned, our solution will look at the [auto-move](/cloudflare-one/email-security/settings/auto-moves/) policy and perform the desired action. +This is performed by subscribing to all user mailboxes on the authorized domains. You have the ability to choose if the scope should be restricted to the Inbox only, or All Folders during the authorization process. Upon delivery to the mailbox, the subscription triggers an action within Microsoft 365 that sends Cloudflare a copy of the email to be scanned and assigned a disposition. Once the disposition has been assigned, our solution will look at the [auto-move](/cloudflare-one/email-security/settings/detection-settings/auto-moves/) policy and perform the desired action. ![API deployment](~/assets/images/reference-architecture/understanding-email-security-deployments/API.svg) @@ -177,7 +177,7 @@ Before deploying Email security via [API deployment](/cloudflare-one/email-secur BCC/Journaling is very similar to API deployments with the exception of how emails are delivered to Cloudflare. As with API the email is delivered to the mailbox first, but at the same time an account specific email address is added to the email so a copy is transmitted via SMTP to Cloudflare for evaluation. -Once Cloudflare receives the email, it will scan and determine the [disposition](/cloudflare-one/email-security/reference/dispositions-and-attributes/#dispositions) of the email. Once an email has a disposition our solution will look at the API authorizations and [auto-move](/cloudflare-one/email-security/settings/auto-moves/) policy and perform the desired action. This method is less at risk to API Throttling as the APIs for Microsoft 365 and Google are only used to remediate emails. +Once Cloudflare receives the email, it will scan and determine the [disposition](/cloudflare-one/email-security/reference/dispositions-and-attributes/#dispositions) of the email. Once an email has a disposition our solution will look at the API authorizations and [auto-move](/cloudflare-one/email-security/settings/detection-settings/auto-moves/) policy and perform the desired action. This method is less at risk to API Throttling as the APIs for Microsoft 365 and Google are only used to remediate emails. ![BCC/Journaling deployment](~/assets/images/reference-architecture/understanding-email-security-deployments/Journaling_Diagram.svg) @@ -224,7 +224,7 @@ When you choose mixed deployment, you need to consider that: ## Automated Post Delivery -Cloudflare offers automated workflows based on continuous analysis and submissions. These features enable Cloudflare to move messages using the API [auto-move](/cloudflare-one/email-security/settings/auto-moves/) policy after delivery. This is best paired with the phish submissions or third-party user submissions. +Cloudflare offers automated workflows based on continuous analysis and submissions. These features enable Cloudflare to move messages using the API [auto-move](/cloudflare-one/email-security/settings/detection-settings/auto-moves/) policy after delivery. This is best paired with the phish submissions or third-party user submissions. ### Submission Handling @@ -234,6 +234,6 @@ Cloudflare prioritizes Administrator Submissions for false positives and negativ To summarize, Email security offers three core deployment models: API, BCC/Journaling, and Inline (or MX). Inline is the preferred deployment model as it filters and remediates malicious messages before they reach the user inbox, thereby removing dwell time risk and allowing for features like URL Rewriting and message modification. -API and BCC/Journaling models are post-delivery solutions, integrating directly with platforms like Microsoft 365 or Google Workspace to inspect and [auto-move](/cloudflare-one/email-security/settings/auto-moves/) emails after they have landed in the user mailbox. While these post-delivery methods are easier to deploy and require no mail flow changes, they face limitations such as API throttling risks and the inability to modify message content (like subjects or body text). +API and BCC/Journaling models are post-delivery solutions, integrating directly with platforms like Microsoft 365 or Google Workspace to inspect and [auto-move](/cloudflare-one/email-security/settings/detection-settings/auto-moves/) emails after they have landed in the user mailbox. While these post-delivery methods are easier to deploy and require no mail flow changes, they face limitations such as API throttling risks and the inability to modify message content (like subjects or body text). Finally, the mixed deployment combines the benefits of Inline for external email protection (critical for systems like CRM or ticketing that ingest email) with BCC/Journaling for internal email evaluation. diff --git a/src/content/docs/reference-architecture/design-guides/zero-trust-for-saas.mdx b/src/content/docs/reference-architecture/design-guides/zero-trust-for-saas.mdx index 70f74881e55..ddd1c929086 100644 --- a/src/content/docs/reference-architecture/design-guides/zero-trust-for-saas.mdx +++ b/src/content/docs/reference-architecture/design-guides/zero-trust-for-saas.mdx @@ -195,7 +195,7 @@ Cloudflare also helps ensure the availability of cloud email services. It auto-s #### Filtering outbound emails with outbound data loss prevention -Organizations using Microsoft 365 can enhance protection against sensitive information leaks through email by integrating a Cloudflare add-in into their environment. This integration enables IT administrators to establish [outbound Data Loss Prevention (DLP) policies](/cloudflare-one/email-security/outbound-dlp/) that leverage the same DLP profiles used with the Secure Web Gateway (SWG) and API Cloud Access Security Broker (CASB). +Organizations using Microsoft 365 can enhance protection against sensitive information leaks through email by integrating a Cloudflare add-in into their environment. This integration enables IT administrators to establish [outbound Data Loss Prevention (DLP) policies](/cloudflare-one/email-security/policies/outbound/outbound-dlp/) that leverage the same DLP profiles used with the Secure Web Gateway (SWG) and API Cloud Access Security Broker (CASB). Moreover, organizations that utilize [Microsoft Purview Sensitivity Labels](/cloudflare-one/data-loss-prevention/dlp-profiles/integration-profiles/) for classifying and safeguarding sensitive documents can incorporate these labels into Cloudflare's DLP profiles. This capability allows the creation of targeted policies, such as blocking emails containing Microsoft Office documents marked as 'Highly Confidential' in Microsoft Outlook from being sent to external recipients. These DLP profiles can also be applied across SWG and API CASB. diff --git a/src/content/docs/reference-architecture/diagrams/content-delivery/distributed-web-performance-architecture.mdx b/src/content/docs/reference-architecture/diagrams/content-delivery/distributed-web-performance-architecture.mdx index dba07003b95..a21f28c0394 100644 --- a/src/content/docs/reference-architecture/diagrams/content-delivery/distributed-web-performance-architecture.mdx +++ b/src/content/docs/reference-architecture/diagrams/content-delivery/distributed-web-performance-architecture.mdx @@ -83,7 +83,7 @@ For demonstration purposes, the architecture is organized into four logical laye The performance journey begins at the client's device. Device hardware, [browser](https://caniuse.com/), network quality and topology determine initial responsiveness. The goal here is to establish the fastest possible connection to the Cloudflare network. - **DNS Resolution:** The client device queries the domain, going through both a public DNS resolver and, ultimately, to an authoritative DNS server. Cloudflare's [global anycast network](https://www.cloudflare.com/network/) routes requests to the nearest Point of Presence (PoP), with [global DNS](https://www.dnsperf.com/) resolution ensuring minimal lookup latency, including the possibility to expand to [mainland China](/china-network/). -- **Connection Establishment:** The client establishes a connection via IPv4/[IPv6](/network/ipv6-compatibility/) using [HTTP/3 (QUIC)](/speed/optimization/protocol/http3/) and [TLS 1.3](/ssl/edge-certificates/additional-options/tls-13/) - this also allows for [Post-Quantum Cryptography (PQC)](/ssl/post-quantum-cryptography/). If the client has visited before, [0-RTT Connection Resumption](/speed/optimization/protocol/0-rtt-connection-resumption/) eliminates round-trips during the handshake. Additionally, [HTTP Strict Transport Security (HSTS)](/ssl/edge-certificates/additional-options/http-strict-transport-security/) enforces browser-side redirects to HTTPS, removing unnecessary server round-trips. It is generally recommended to [enforce HTTPS connections](/ssl/edge-certificates/encrypt-visitor-traffic/). Furthermore, by leveraging relevant [TCP fields](/changelog/2025-10-30-tcp-rtt-and-tcp-fields/), you can implement adaptive performance strategies. +- **Connection Establishment:** The client establishes a connection via IPv4/[IPv6](/network/ipv6-compatibility/) using [HTTP/3 (QUIC)](/speed/optimization/protocol/http3/) and [TLS 1.3](/ssl/edge-certificates/additional-options/tls-13/) - this also allows for [Post-Quantum Cryptography (PQC)](/ssl/post-quantum-cryptography/). If the client has visited before, [0-RTT Connection Resumption](/speed/optimization/protocol/0-rtt-connection-resumption/) eliminates round-trips during the handshake. Additionally, [HTTP Strict Transport Security (HSTS)](/ssl/edge-certificates/additional-options/http-strict-transport-security/) enforces browser-side redirects to HTTPS, removing unnecessary server round-trips. It is generally recommended to [enforce HTTPS connections](/ssl/edge-certificates/encrypt-visitor-traffic/). Furthermore, by leveraging relevant [TCP fields](/changelog/post/2025-10-30-tcp-rtt-and-tcp-fields/), you can implement adaptive performance strategies. - **Browser Optimization:** Features like [Speed Brain](/speed/optimization/content/speed-brain/) (Speculation Rules API) proactively prefetch resources, while [Early Hints](/cache/advanced-configuration/early-hints/) send link headers to the browser during "server think time", speeding up page rendering. - **Third-Party Offloading:** [Zaraz](/zaraz/) offloads third-party tools (like Google Analytics 4 or Mixpanel) to the cloud. This reduces main thread blocking on the device, significantly improving INP. - **Web Analytics (RUM):** Leverage Cloudflare [Web Analytics](/web-analytics/) to collect privacy-first, cookie-less performance data directly from the user's browser. This lightweight JavaScript beacon provides real-world insights into Core Web Vitals (LCP, INP, CLS) without tracking users or storing client-side state. @@ -141,7 +141,7 @@ When analyzing this data, it is important to take into account [connection limit - [GraphQL Analytics API](/analytics/graphql-api/): Use this for Trends and [Timing Insights](https://blog.cloudflare.com/introducing-timing-insights/). Query specific metrics like `edgeDnsResponseTimeMs` versus `originResponseDurationMs` to pinpoint exactly where latency is introduced. - [Web Analytics](/web-analytics/): Specific for privacy-first, edge-based RUM analytics. - [Cache Analytics](/cache/performance-review/cache-analytics/): Critical for analyzing Cache Hit Ratio (CHR) and "Requests by Cache Status" to find uncached content that causes origin load. -- [Ruleset Engine](/ruleset-engine/): Review and leverage the extensive library of [fields](/ruleset-engine/rules-language/fields/reference/), including network metrics like [TCP RTT and TCP fields](/changelog/2025-10-30-tcp-rtt-and-tcp-fields/), to implement precise custom logic for routing, caching, and security based on real-time connection properties. +- [Ruleset Engine](/ruleset-engine/): Review and leverage the extensive library of [fields](/ruleset-engine/rules-language/fields/reference/), including network metrics like [TCP RTT and TCP fields](/changelog/post/2025-10-30-tcp-rtt-and-tcp-fields/), to implement precise custom logic for routing, caching, and security based on real-time connection properties. - Logging & Forensics: - [Log Explorer](/log-explorer/): For ad-hoc querying of request logs directly in the dashboard. Use [Custom Log Fields](/logs/logpush/logpush-job/custom-fields/) to log additional request headers, response headers and cookies. - [Logpush](/logs/logpush/): For exporting logs to third-party SIEMs with optional [Log Output Options](/logs/logpush/logpush-job/log-output-options/), supporting formats such as CSV or JSON. Essential for analyzing custom fields and long-term trends, as well as calculating the Download Success Rate and analyzing Download Throughput for large files. diff --git a/src/content/docs/sandbox/sdk/migrate/tunnels.mdx b/src/content/docs/sandbox/sdk/migrate/tunnels.mdx index ddb311cf558..8f5c3d82c52 100644 --- a/src/content/docs/sandbox/sdk/migrate/tunnels.mdx +++ b/src/content/docs/sandbox/sdk/migrate/tunnels.mdx @@ -353,6 +353,6 @@ Call `resumeTunnel(8080)`, and send the request again. The response comes from y ## Related resources - [Move preview URLs](/sandbox/sdk/migrate/preview-urls/) -- [Quick tunnels](/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/trycloudflare/) +- [Quick tunnels](/tunnel/get-started/quick-tunnels/) - [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/) - [Run a server in the background](/sandbox/commands/run-a-server-in-the-background/) diff --git a/src/content/docs/security/security-insights/index.mdx b/src/content/docs/security/security-insights/index.mdx index 2b858852d70..9472004dac8 100644 --- a/src/content/docs/security/security-insights/index.mdx +++ b/src/content/docs/security/security-insights/index.mdx @@ -43,7 +43,7 @@ Listed below are the specific insights currently available: | [Client-side security not enabled](/client-side-security/get-started/) | Client-side security (formerly known as Page Shield) helps meet PCI DSS v4.0 compliance regarding requirement 6.4.3. | | [SPF Record Errors](/dns/manage-dns-records/reference/dns-record-types/#spf) | We detect an incorrect or missing `SPF` record. | | [Sensitive data in API response](/api-shield/management-and-monitoring/#sensitive-data-detection) | Sensitive data in API responses detected. | -| [Turn on JavaScript Detection](/bots/additional-configurations/javascript-detections/) | One or more of your Bot Management enabled zones does not have JavaScript Detection enabled, which is a critical part of our bot detection suite. | +| [Turn on JavaScript Detection](/cloudflare-challenges/challenge-types/javascript-detections/) | One or more of your Bot Management enabled zones does not have JavaScript Detection enabled, which is a critical part of our bot detection suite. | | [Unassigned Access seats](/cloudflare-one/) | We detect a Zero Trust subscription that is not configured yet. | | [Unauthenticated API endpoints detected](/api-shield/management-and-monitoring/endpoint-labels/#managed-labels) | None of the successful requests against API endpoints carried session identifiers. | | [Unprotected Cloudflare Tunnels](/cloudflare-one/access-controls/applications/http-apps/self-hosted-public-app/#4-connect-your-origin-to-cloudflare) | We detect an application that is served by a Cloudflare Tunnel but not protected by a corresponding Access policy. | diff --git a/src/content/docs/security/settings.mdx b/src/content/docs/security/settings.mdx index c467fa8aae0..0f6790c46f3 100644 --- a/src/content/docs/security/settings.mdx +++ b/src/content/docs/security/settings.mdx @@ -122,7 +122,7 @@ The following table links to additional information about each available setting | [AI Security for Apps](/waf/detections/ai-security-for-apps/) | _N/A_ | | [Block AI Bots](/bots/concepts/bot/#ai-bots) | **Security** > **Bots** > **Configure Bot Fight Mode
Security** > **Bots** > **Configure Super Bot Fight Mode
Security** > **Bots** > **Configure Bot Management** | | [Bot Management](/bots/get-started/bot-management/): | **Security** > **Bots** | -| — [JS detections](/bots/additional-configurations/javascript-detections/) | **Security** > **Bots** > **Configure Super Bot Fight Mode
Security** > **Bots** > **Configure Bot Management** | +| — [JS detections](/cloudflare-challenges/challenge-types/javascript-detections/) | **Security** > **Bots** > **Configure Super Bot Fight Mode
Security** > **Bots** > **Configure Bot Management** | | — [Auto-update machine learning](/bots/reference/machine-learning-models/) | **Security** > **Bots** > **Configure Bot Management** | | [Browser integrity check](/waf/tools/browser-integrity-check/) | **Security** > **Settings** | | Challenge Passage: [Timeout](/cloudflare-challenges/challenge-types/challenge-pages/challenge-passage/) | **Security** > **Settings** | diff --git a/src/content/docs/ssl/client-certificates/troubleshooting.mdx b/src/content/docs/ssl/client-certificates/troubleshooting.mdx index 3daacb783a9..7411dd57c04 100644 --- a/src/content/docs/ssl/client-certificates/troubleshooting.mdx +++ b/src/content/docs/ssl/client-certificates/troubleshooting.mdx @@ -141,7 +141,7 @@ If you exceed this limit, the API returns: To free a slot, you must first remove all hostname associations from the CA before deleting it. To increase your quota, contact your account team. :::note -CAs uploaded through [Cloudflare Access](/cloudflare-one/identity/devices/warp-client-checks/client-certificate/) use a separate quota. Error `12130` ("maximum number of certificates has been reached") in Access refers to the Access-specific certificate limit, not the BYOCA quota described in [Bring your own CA (BYOCA)](#bring-your-own-ca-byoca). +CAs uploaded through [Cloudflare Access](/cloudflare-one/reusable-components/posture-checks/client-checks/client-certificate/) use a separate quota. Error `12130` ("maximum number of certificates has been reached") in Access refers to the Access-specific certificate limit, not the BYOCA quota described in [Bring your own CA (BYOCA)](#bring-your-own-ca-byoca). ::: --- diff --git a/src/content/docs/style-guide/build-the-page/components/index.mdx b/src/content/docs/style-guide/build-the-page/components/index.mdx index 5b6351148a1..99069e214a3 100644 --- a/src/content/docs/style-guide/build-the-page/components/index.mdx +++ b/src/content/docs/style-guide/build-the-page/components/index.mdx @@ -27,7 +27,7 @@ To add a component to a page: ; ``` - For example, if you were to add [the `DashButton` component](/style-guide/build-the-page/components/dash-button/) to the [Images getting started page](/images/get-started/), the top of the MDX file corresponding to that page would look like the following: + For example, if you were to add [the `DashButton` component](/style-guide/build-the-page/components/dash-button/) to the [Images getting started page](/images/get-started/introduction/), the top of the MDX file corresponding to that page would look like the following: ```mdx --- @@ -56,7 +56,7 @@ To add a component to a page: ``` - For example, if you were to add the `DashButton` component to some steps in the [Images getting started page](/images/get-started/), here is how the MDX file would look: + For example, if you were to add the `DashButton` component to some steps in the [Images getting started page](/images/get-started/introduction/), here is how the MDX file would look: ```mdx 1. In the Cloudflare dashboard, go to the **Transformations** page. diff --git a/src/content/docs/use-cases/e-commerce/performance.mdx b/src/content/docs/use-cases/e-commerce/performance.mdx index 7c7d4fc51d1..503325ebdc1 100644 --- a/src/content/docs/use-cases/e-commerce/performance.mdx +++ b/src/content/docs/use-cases/e-commerce/performance.mdx @@ -48,7 +48,7 @@ Build and deploy serverless applications on Cloudflare's global network. [Learn ## Get started 1. [Configure Cache Rules](/cache/how-to/cache-rules/) -2. [Set up Cloudflare Images](/images/get-started/) +2. [Set up Cloudflare Images](/images/get-started/introduction/) 3. [Enable Speed optimizations](/speed/optimization/) 4. [Configure Zaraz](/zaraz/get-started/) 5. [Rewrite HTML at the edge with HTMLRewriter](/workers/runtime-apis/html-rewriter/) \ No newline at end of file diff --git a/src/content/docs/use-cases/media-streaming/image-optimization.mdx b/src/content/docs/use-cases/media-streaming/image-optimization.mdx index cf857e9a44f..4b131aa0484 100644 --- a/src/content/docs/use-cases/media-streaming/image-optimization.mdx +++ b/src/content/docs/use-cases/media-streaming/image-optimization.mdx @@ -29,6 +29,6 @@ Automatic image compression without quality loss. [Learn more about Polish](/ima ## Get started -1. [Images get started](/images/get-started/) +1. [Images get started](/images/get-started/introduction/) 2. [Enable Polish](/images/polish/) 3. [Transform images via URL](/images/optimization/transformations/overview/) diff --git a/src/content/docs/use-cases/performance/image-optimization.mdx b/src/content/docs/use-cases/performance/image-optimization.mdx index 425474d2146..829fe757eaf 100644 --- a/src/content/docs/use-cases/performance/image-optimization.mdx +++ b/src/content/docs/use-cases/performance/image-optimization.mdx @@ -34,5 +34,5 @@ Improve page load performance with built-in optimizations. [Learn more about Spe ## Get started -1. [Images get started](/images/get-started/) +1. [Images get started](/images/get-started/introduction/) 2. [Enable Polish](/images/polish/) diff --git a/src/content/docs/use-cases/solutions/index.mdx b/src/content/docs/use-cases/solutions/index.mdx index 35f44ab5a9b..1042a1f5dae 100644 --- a/src/content/docs/use-cases/solutions/index.mdx +++ b/src/content/docs/use-cases/solutions/index.mdx @@ -10,6 +10,6 @@ products: import { DirectoryListing } from "~/components"; -Each guide starts from your goal, identifies which Cloudflare products you need, and walks through setting them up. For more information about solution guides, refer to [Solution guide](/style-guide/documentation-content-strategy/content-types/solution-guide/). +Each guide starts from your goal, identifies which Cloudflare products you need, and walks through setting them up. For more information about solution guides, refer to [Solution guide](/style-guide/documentation-content-strategy/content-types/how-to/). diff --git a/src/content/docs/workers/ci-cd/builds/automatic-prs.mdx b/src/content/docs/workers/ci-cd/builds/automatic-prs.mdx index 262ee076da4..884ad81a58e 100644 --- a/src/content/docs/workers/ci-cd/builds/automatic-prs.mdx +++ b/src/content/docs/workers/ci-cd/builds/automatic-prs.mdx @@ -60,7 +60,7 @@ This can happen when: The PR will update the `name` field in your Wrangler configuration to match the Worker name in the dashboard. -For more details, refer to the [name conflict changelog](/changelog/2025-02-20-builds-name-conflict/). +For more details, refer to the [name conflict changelog](/changelog/post/2025-02-20-builds-name-conflict/). ## Reviewing PRs diff --git a/src/content/docs/workers/configuration/cloudflare-access.mdx b/src/content/docs/workers/configuration/cloudflare-access.mdx index 9ef64930498..cf6d012f8b7 100644 --- a/src/content/docs/workers/configuration/cloudflare-access.mdx +++ b/src/content/docs/workers/configuration/cloudflare-access.mdx @@ -376,4 +376,4 @@ If you remove a more specific rule, a broader rule may still protect the Worker. - [Access policies](/cloudflare-one/access-controls/policies/) - [Self-hosted Access applications](/cloudflare-one/access-controls/applications/http-apps/self-hosted-public-app/) - [Routes and domains](/workers/configuration/routing/) -- [Preview URLs](/workers/configuration/previews/) +- [Preview URLs](/workers/versions-and-deployments/version-urls/) diff --git a/src/content/docs/workers/runtime-apis/context.mdx b/src/content/docs/workers/runtime-apis/context.mdx index edb90c0c156..e4a171b111c 100644 --- a/src/content/docs/workers/runtime-apis/context.mdx +++ b/src/content/docs/workers/runtime-apis/context.mdx @@ -175,7 +175,7 @@ export default { -Specifying props dynamically is permitted in this case because the caller is the same Worker, and thus can be presumed to be trusted to specify any props. The ability to customize props is particularly useful when the resulting binding is to be passed to another Worker over RPC or used in the `env` of a [dynamically-loaded worker](/workers/runtime-apis/bindings/worker-loader/). +Specifying props dynamically is permitted in this case because the caller is the same Worker, and thus can be presumed to be trusted to specify any props. The ability to customize props is particularly useful when the resulting binding is to be passed to another Worker over RPC or used in the `env` of a [dynamically-loaded worker](/dynamic-workers/). Note that `props` values specified in this way are allowed to contain any "persistently" serializable type. This includes all basic [structured cloneable data types](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm). It also includes Service Bindings themselves: you can place a Service Binding into the `props` of another Service Binding. diff --git a/src/content/docs/workers/tutorials/generate-youtube-thumbnails-with-workers-and-images.mdx b/src/content/docs/workers/tutorials/generate-youtube-thumbnails-with-workers-and-images.mdx index e76b2ffcbd3..68ae5d856f7 100644 --- a/src/content/docs/workers/tutorials/generate-youtube-thumbnails-with-workers-and-images.mdx +++ b/src/content/docs/workers/tutorials/generate-youtube-thumbnails-with-workers-and-images.mdx @@ -405,7 +405,7 @@ export default { }; ``` -Update `env.CLOUDFLARE_ACCOUNT_HASH` with your [Cloudflare account ID](/fundamentals/account/find-account-and-zone-ids/). Update `env.IMAGE_ID` with your [image ID](/images/get-started/). +Update `env.CLOUDFLARE_ACCOUNT_HASH` with your [Cloudflare account ID](/fundamentals/account/find-account-and-zone-ids/). Update `env.IMAGE_ID` with your [image ID](/images/get-started/introduction/). Run your Worker and go to the `/original-image` route to review your image. diff --git a/src/content/partials/bots/bots-jsd.mdx b/src/content/partials/bots/bots-jsd.mdx index 0db49de66e6..85d85ae3bf7 100644 --- a/src/content/partials/bots/bots-jsd.mdx +++ b/src/content/partials/bots/bots-jsd.mdx @@ -3,4 +3,4 @@ --- -The [**JavaScript Detections (JSD)**](/bots/additional-configurations/javascript-detections/) engine identifies headless browsers and other malicious fingerprints. This engine performs a lightweight, invisible JavaScript injection on the client side of any request while honoring our [strict privacy standards](https://www.cloudflare.com/privacypolicy/). We do not collect any personally identifiable information during the process. The JSD engine either blocks, challenges, or passes requests to other engines. +The [**JavaScript Detections (JSD)**](/cloudflare-challenges/challenge-types/javascript-detections/) engine identifies headless browsers and other malicious fingerprints. This engine performs a lightweight, invisible JavaScript injection on the client side of any request while honoring our [strict privacy standards](https://www.cloudflare.com/privacypolicy/). We do not collect any personally identifiable information during the process. The JSD engine either blocks, challenges, or passes requests to other engines. diff --git a/src/content/partials/bots/enable-sbfm.mdx b/src/content/partials/bots/enable-sbfm.mdx index e8d3a639929..9fc6fdde89d 100644 --- a/src/content/partials/bots/enable-sbfm.mdx +++ b/src/content/partials/bots/enable-sbfm.mdx @@ -15,7 +15,7 @@ import { Steps, DashButton } from "~/components"; - For more details on verified bots, refer to [Verified Bots](/bots/concepts/bot/verified-bots/). - For more details on supported file types, refer to [Static resource protection](/bots/additional-configurations/static-resources/). - - For more details on invisible code injection, refer to [JavaScript detections](/bots/additional-configurations/javascript-detections/). + - For more details on invisible code injection, refer to [JavaScript detections](/cloudflare-challenges/challenge-types/javascript-detections/). - For more details on WordPress optimization, refer to [Super Bot Fight Mode for WordPress](/bots/troubleshooting/wordpress-loopback-issue/). diff --git a/src/content/partials/cloudflare-challenges/cf-clearance-cookie.mdx b/src/content/partials/cloudflare-challenges/cf-clearance-cookie.mdx index d3952905643..215cf537cc8 100644 --- a/src/content/partials/cloudflare-challenges/cf-clearance-cookie.mdx +++ b/src/content/partials/cloudflare-challenges/cf-clearance-cookie.mdx @@ -5,7 +5,7 @@ :::note -[JavaScript detections](/bots/additional-configurations/javascript-detections/) are stored in the `cf_clearance` cookie. +[JavaScript detections](/cloudflare-challenges/challenge-types/javascript-detections/) are stored in the `cf_clearance` cookie. The `cf_clearance` cookie cannot exceed the maximum size of 4096 bytes. ::: \ No newline at end of file diff --git a/src/content/partials/cloudflare-one/troubleshooting/email-security.mdx b/src/content/partials/cloudflare-one/troubleshooting/email-security.mdx index 77aac5be079..ed125816dfa 100644 --- a/src/content/partials/cloudflare-one/troubleshooting/email-security.mdx +++ b/src/content/partials/cloudflare-one/troubleshooting/email-security.mdx @@ -21,7 +21,7 @@ A false positive occurs when a legitimate email is incorrectly flagged as malici 1. In the Email Security dashboard, go to **Investigation**. 2. Find the email and select **Submit for reclassification**. 3. Choose the correct disposition (for example, `Clean`). -4. To prevent future blocks, add the sender to your [Acceptable Senders](/cloudflare-one/email-security/settings/detection-settings/allow-policies/) list. +4. To prevent future blocks, add the sender to your [Acceptable Senders](/cloudflare-one/email-security/policies/inbound/allow-policies/) list. ### Handle a false negative A false negative occurs when a malicious email is not detected by Email Security. @@ -37,7 +37,7 @@ Email Security may mark an email as **SPAM** if it fails DMARC authentication an **Solution**: - Ask the sender to fix their DMARC/SPF/DKIM records. -- Configure an [Acceptable Sender](/cloudflare-one/email-security/settings/detection-settings/allow-policies/) entry to suppress the failure for that specific sender. +- Configure an [Acceptable Sender](/cloudflare-one/email-security/policies/inbound/allow-policies/) entry to suppress the failure for that specific sender. ## Delivery issues diff --git a/src/content/partials/durable-objects/do-sqlite-storage-no-bill-note.mdx b/src/content/partials/durable-objects/do-sqlite-storage-no-bill-note.mdx index 6c20a79b786..e980f235ad2 100644 --- a/src/content/partials/durable-objects/do-sqlite-storage-no-bill-note.mdx +++ b/src/content/partials/durable-objects/do-sqlite-storage-no-bill-note.mdx @@ -3,5 +3,5 @@ --- :::note[Storage billing on SQLite-backed Durable Objects] -Storage billing for SQLite-backed Durable Objects will be enabled in January 2026, with a target date of January 7, 2026 (no earlier). Only SQLite storage usage on and after the billing target date will incur charges. For more information, refer to [Billing for SQLite Storage](/changelog/2025-12-12-durable-objects-sqlite-storage-billing/). +Storage billing for SQLite-backed Durable Objects will be enabled in January 2026, with a target date of January 7, 2026 (no earlier). Only SQLite storage usage on and after the billing target date will incur charges. For more information, refer to [Billing for SQLite Storage](/changelog/post/2025-12-12-durable-objects-sqlite-storage-billing/). ::: diff --git a/src/content/partials/speed/brotli-compression-warning.mdx b/src/content/partials/speed/brotli-compression-warning.mdx index 0e8cb285114..7cf98926f5b 100644 --- a/src/content/partials/speed/brotli-compression-warning.mdx +++ b/src/content/partials/speed/brotli-compression-warning.mdx @@ -13,7 +13,7 @@ Even when using the same compression algorithm end to end (between your origin s - [Email Address Obfuscation](/waf/tools/scrape-shield/email-address-obfuscation/) - [Polish](/images/polish/) - [Rocket Loader](/speed/optimization/content/rocket-loader/) -- [JavaScript detections](/bots/additional-configurations/javascript-detections/) +- [JavaScript detections](/cloudflare-challenges/challenge-types/javascript-detections/) - [RUM](/speed/observatory/run-speed-test/#enable-real-user-monitoring-rum) To disable these settings for specific URI paths, create a [configuration rule](/rules/configuration-rules/). diff --git a/src/content/partials/workers/cloudflare-config.mdx b/src/content/partials/workers/cloudflare-config.mdx index d8d709decac..ce4f4809392 100644 --- a/src/content/partials/workers/cloudflare-config.mdx +++ b/src/content/partials/workers/cloudflare-config.mdx @@ -151,7 +151,7 @@ The `worker` object supports these fields: | `logpush` | No | Sends trace events to Workers Logpush | | `observability` | No | Configures logs, traces, and sampling | | `placement` | No | Configures smart or targeted placement | -| `previewUrls` | No | Controls [version preview URLs](/workers/versions-and-deployments/preview-urls/) | +| `previewUrls` | No | Controls [version preview URLs](/workers/versions-and-deployments/version-urls/) | | `tailConsumers` | No | Sends events to Tail Workers | | `triggers` | No | Declares routes, queues, schedules, and sockets | | `unsafe` | No | Passes unsupported metadata through to deployment | From eb6b211fa476d8da198aa0a7b7f6b75e81a409be Mon Sep 17 00:00:00 2001 From: mvm Date: Mon, 12 Oct 2026 13:57:58 -0500 Subject: [PATCH 3/5] docs: remove reference to GitHubCode component --- .../documentation-content-strategy/content-types/tutorial.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/style-guide/documentation-content-strategy/content-types/tutorial.mdx b/src/content/docs/style-guide/documentation-content-strategy/content-types/tutorial.mdx index dc941a9df60..1740f6b3ec4 100644 --- a/src/content/docs/style-guide/documentation-content-strategy/content-types/tutorial.mdx +++ b/src/content/docs/style-guide/documentation-content-strategy/content-types/tutorial.mdx @@ -41,7 +41,7 @@ For the full comparison, refer to [Content types](/style-guide/documentation-con - [**Steps**](/style-guide/build-the-page/components/steps/) or numbered `##` parts are the spine, and every part ends with the verbatim "You should see" output that proves it worked. Never skip one. - **Error-recovery prose** at the points readers actually stumble is happy-path content, not an exception callout, because in a tutorial an anticipated error is not an exception. -- [**GitHubCode**](/style-guide/build-the-page/components/) and [**PackageManagers**](/style-guide/build-the-page/components/package-managers/) keep sample code and install commands pinned and in sync, and [**ListTutorials**](/style-guide/build-the-page/components/list-tutorials/) surfaces the tutorial in listings. +- [**PackageManagers**](/style-guide/build-the-page/components/package-managers/) keeps install commands in sync, and [**ListTutorials**](/style-guide/build-the-page/components/list-tutorials/) surfaces the tutorial in listings. - **What does not fit:** Tabs and options of any kind (the author already chose the one path, and per-stack means per-page), long conceptual asides (link out instead), and anything that hides steps. ## Frontmatter From 08b74b32873d428375ce1e793193dde1abdd04f5 Mon Sep 17 00:00:00 2001 From: mvm Date: Mon, 12 Oct 2026 14:10:54 -0500 Subject: [PATCH 4/5] docs: unlink KV Instant page and fix Access beta changelog link --- .../changelog/access/2025-09-22-browser-based-rdp-ga.mdx | 2 +- src/content/docs/kv/get-started.mdx | 4 ++-- src/content/partials/workers/wrangler-commands/kv.mdx | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/content/changelog/access/2025-09-22-browser-based-rdp-ga.mdx b/src/content/changelog/access/2025-09-22-browser-based-rdp-ga.mdx index 380a92d1417..2aaae4b35e3 100644 --- a/src/content/changelog/access/2025-09-22-browser-based-rdp-ga.mdx +++ b/src/content/changelog/access/2025-09-22-browser-based-rdp-ga.mdx @@ -8,7 +8,7 @@ products: [Browser-based RDP](/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/rdp/rdp-browser/) with [Cloudflare Access](/cloudflare-one/access-controls/policies/) is now generally available for all Cloudflare customers. It enables secure, remote Windows server access without VPNs or RDP clients. -Since we announced our [open beta](/changelog/access/#2025-06-30), we've made a few improvements: +Since we announced our [open beta](/changelog/post/2025-07-01-browser-based-rdp-open-beta/), we've made a few improvements: - Support for targets with IPv6. - Support for [Magic WAN](/cloudflare-wan/) and [WARP Connector](/mesh/) as on-ramps. diff --git a/src/content/docs/kv/get-started.mdx b/src/content/docs/kv/get-started.mdx index ea13c38b0d7..b4f723cea0c 100644 --- a/src/content/docs/kv/get-started.mdx +++ b/src/content/docs/kv/get-started.mdx @@ -188,7 +188,7 @@ To create a KV namespace via Wrangler: -Use [Workers KV Instant](/kv/reference/kv-instant/) for small, read-heavy application configurations values that update infrequently and are proactively propagated across Cloudflare's network. +Use Workers KV Instant for small, read-heavy application configurations values that update infrequently and are proactively propagated across Cloudflare's network. To optionally create a KV Instant namespace named `APP_CONFIG` with [Wrangler](/workers/wrangler/), pass `--experimental-mode instant`: @@ -212,7 +212,7 @@ Alternatively, create it through the API with `mode: "instant"`: json={{ title: "APP_CONFIG", mode: "instant" }} /> -KV Instance namespaces have additional limitations compared to classic namespaces. Refer to [KV Instant limits](/kv/platform/limits/#kv-instant) and [API differences](/kv/reference/kv-instant/#compare-api-behavior) before choosing this mode. +KV Instance namespaces have additional limitations compared to classic namespaces. Refer to [KV Instant limits](/kv/platform/limits/#kv-instant) before choosing this mode. ## 3. Bind your Worker to your KV namespace diff --git a/src/content/partials/workers/wrangler-commands/kv.mdx b/src/content/partials/workers/wrangler-commands/kv.mdx index 8fca96027e9..c9dc107955f 100644 --- a/src/content/partials/workers/wrangler-commands/kv.mdx +++ b/src/content/partials/workers/wrangler-commands/kv.mdx @@ -24,7 +24,7 @@ To restrict where a namespace durably stores data, specify `--jurisdiction` when -To create a [Workers KV Instant](/kv/reference/kv-instant/) namespace, pass `--experimental-mode instant`. This example creates a namespace named `APP_CONFIG` for small, infrequently updated configuration: +To create a Workers KV Instant namespace, pass `--experimental-mode instant`. This example creates a namespace named `APP_CONFIG` for small, infrequently updated configuration: Date: Mon, 12 Oct 2026 14:14:14 -0500 Subject: [PATCH 5/5] docs: unlink CASB Zoom page until it exists --- .../changelog/casb/2026-09-09-casb-zoom-integration.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/changelog/casb/2026-09-09-casb-zoom-integration.mdx b/src/content/changelog/casb/2026-09-09-casb-zoom-integration.mdx index 211f92b73e5..d127b96fcfa 100644 --- a/src/content/changelog/casb/2026-09-09-casb-zoom-integration.mdx +++ b/src/content/changelog/casb/2026-09-09-casb-zoom-integration.mdx @@ -6,7 +6,7 @@ products: date: 2026-09-09 --- -[Cloudflare CASB](/cloudflare-one/integrations/cloud-and-saas/) now integrates with [Zoom](/cloudflare-one/integrations/cloud-and-saas/zoom/). The integration connects through Cloudflare's pre-built OAuth application — no manual app setup in Zoom is required. After an initial scan, CASB continuously scans your Zoom account to surface new findings as your environment changes. +[Cloudflare CASB](/cloudflare-one/integrations/cloud-and-saas/) now integrates with Zoom. The integration connects through Cloudflare's pre-built OAuth application — no manual app setup in Zoom is required. After an initial scan, CASB continuously scans your Zoom account to surface new findings as your environment changes. Zoom is widely used for meetings, webinars, and collaboration. Misconfigurations in account settings, meeting security controls, and recording access can expose organizations to data leakage, unauthorized access, and compliance risk. Cloudflare CASB ingests Zoom account data via API to surface security findings across these areas. @@ -22,4 +22,4 @@ Starting today, security teams can scan for security findings across the followi ### Learn more -This [integration](/cloudflare-one/integrations/cloud-and-saas/zoom/) is available to all Cloudflare Zero Trust customers today. New customers can sign up and start with their first two integrations for free. Existing customers can enable the integration directly in the Cloudflare One dashboard under **Cloud & SaaS findings** > **Integrations**. The integration begins scanning immediately and surfaces findings in the dashboard within minutes. +This integration is available to all Cloudflare Zero Trust customers today. New customers can sign up and start with their first two integrations for free. Existing customers can enable the integration directly in the Cloudflare One dashboard under **Cloud & SaaS findings** > **Integrations**. The integration begins scanning immediately and surfaces findings in the dashboard within minutes.