[Cloudflare for SaaS] Clarify O2O works with full and partial DNS setups - #32579
Open
damiete wants to merge 2 commits into
Open
[Cloudflare for SaaS] Clarify O2O works with full and partial DNS setups#32579damiete wants to merge 2 commits into
damiete wants to merge 2 commits into
Conversation
O2O is enabled by a proxied CNAME to the SaaS provider in the customer zone. Authoritative DNS does not need to be Cloudflare (partial/CNAME setup is supported). Document full vs partial paths, CNAME target requirements, and distinguish hostname priority from O2O.
damiete
requested review from
a team,
SebastiaanYN,
Woutifier,
baubuchon-cf,
chreo,
dinasaur404,
dklbreitling,
elithrar,
esomoza-cf,
hannes-cf,
irvinebroque,
lgarofalo,
matildeopbravo,
svenr-cf,
vendemiat and
xofyarg
as code owners
August 6, 2026 16:12
Contributor
Review✅ No issues found in commit Code ReviewThis code review is in beta and may not always be helpful — use your judgment. No code review issues found. ConventionsNo convention issues found. Style Guide ReviewNo style-guide issues found. CommandsOnly codeowners can run commands. Post a comment with the command to trigger it.
|
github-actions
Bot
added
product:ssl
Address cloudflare-docs-bot style-guide findings on PR cloudflare#32579: monospace CNAME/A/AAAA, convert two-item bullet list to prose.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Clarify that orange-to-orange (O2O) applies when a customer zone has a proxied CNAME to a SaaS provider on Cloudflare, including partial (CNAME) DNS setups where Cloudflare is not the authoritative DNS provider.
Why
The O2O how-it-works page currently reads as if Cloudflare must be authoritative DNS ("If your authoritative DNS is Cloudflare, you have the option to proxy…"). Customers on partial setup with SaaS providers already use O2O; the docs should match that behavior and call out that the proxied CNAME in the customer zone is what enables O2O.
Changes
Provider-specific steps remain in the existing provider guides.
Pages
/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works//ssl/reference/certificate-and-hostname-priority//dns/zone-setups/partial-setup/setup//cloudflare-for-platforms/cloudflare-for-saas/saas-customers/product-compatibility/