Before you start
- Use a dedicated employee email domain you control and can verify with a DNS TXT record. Cloudflare applies this setting to the whole email domain.
- You need a Cloudflare super administrator, API access, a Zero Trust organization, and an Okta administrator. Keep an API token with Cloudflare’s SSO Connector Edit permission available for rollback.
- Check Cloudflare availability
Data and access
Who does what
Confirm the test domain
Check that the email domain belongs only to the test organization and that you can reach the Cloudflare API independently. Domain enforcement affects every user with that email domain.
Check. The recorded pilot email domain is the one you control, and the independent API access can read its test configuration.
Set up and test the connector
Follow Cloudflare’s Okta setup instructions. Verify the test domain and retain the backup administrative access described by Cloudflare before enabling the connector.
Check. The dashboard lists the test domain as verified. Check the intended connector and the backup access before enforcement.
Verify access and rollback
Start at the Cloudflare dashboard and authenticate through Okta as a pilot user. Rehearse disabling the connector through the API with the backup access you prepared, then verify the pilot user can regain access.
Check. A fresh pilot session opens the expected Cloudflare account. After rollback, verify both connector state and recovered access.
Check your result
Cloudflare applies the requirement to users with the verified email domain. Confirm which users are in scope and rehearse the emergency path before switching a shared domain.
If you get stuck
The test user cannot enter the dashboard
Check that the email domain is verified in Cloudflare and the test user is assigned to the app in Okta. Use the separate emergency administrator to pause the rollout if those checks fail.