Verified domains
Prove your organization owns a domain with a DNS TXT record. Single sign-on routes and enforces only at a verified domain, one organization holds each domain, and a domain whose record disappears lapses after a 14-day warning.
A verified domain is your organization's proof that it controls the addresses its members sign in with. Single sign-on routes sign-ins, and SSO enforcement applies, only at a domain your organization has verified. You do not need an external identity provider to verify a domain.
Organization owners and admins manage domains under Settings → Platform → Identity → Domains. Nobody else can see or change them.
Verify a domain
- Select Add domain and enter the domain your members' addresses use,
such as
example.com. - The row shows a TXT record: a Name (
_scrydon-verification.example.com) and a Value (scrydon-verification=…). Publish it at your DNS provider. Other TXT records can stay at the same name. Each Scrydon environment, such as staging and production, gives its own value: publish one record for each, side by side, and each environment finds its own. - Select Verify. If the record is not visible yet, the domain stays Awaiting DNS record; DNS changes can take a while to appear, so try again later.
Once verified, every SSO provider of your organization whose domains are all verified starts routing sign-ins.
Leave the record published. Scrydon checks it again every day.
Verifying a domain also brings the accounts at it under your organization's sign-in policy, after a notice: see Managed accounts and joining.
Subdomains
Verifying example.com does not cover eu.example.com. Add each domain your
members sign in with. A subdomain of a domain your organization has already
verified is verified at once, without a record of its own, and shows
Verified through example.com. It is removed with its parent.
One organization per domain
Only one organization can hold a domain verified. Scrydon refuses:
- a domain another organization has verified, and any domain below it;
- a public suffix, such as
co.uk, that no single organization owns; - a public email provider, such as
gmail.com; - an IP address or a single word.
If your deployment's operator has allowed a public suffix your organization owns (a ministry owning a national suffix), you can claim it like any other domain.
When the record goes missing
If the daily check finds the record gone, the domain stays verified but shows a warning with the date it lapses: 14 days later. Owners and admins are notified in Scrydon and by email. Publish the record again and select Verify to clear it.
A domain that lapses stops single sign-on at that domain, and owners and admins are notified again. Prove it again with Verify. A failure to reach DNS at all never counts against the domain.
If the domain is federated to Scrydon in Microsoft Entra, a lapse here also stops your users signing in to Microsoft 365. Treat the warning as urgent.
Remove a domain
Remove asks for confirmation, then removes the domain and every subdomain verified through it. Single sign-on stops routing sign-ins at those domains.
Audit
Adding, verifying, failing, recovering, lapsing and removing a domain are each
written to the audit log as sso.organization_domain.*.