This is an Early AccessEarly Access (EA) features are opt-in features that you can try out in your org by asking Okta Support to enable them. Additionally, the Features page in the Okta Admin Console (Settings > Features) allows Super Admins to enable and disable some EA features themselves. feature. To enable it, please contact Okta Support.
Settings > Email & SMS
You can configure a custom email domainA domain is an attribute of an Okta organization. Okta uses a fully-qualified domain name, meaning it always includes the top-level domain (.com, .eu, etc.), but does not include the protocol (https). so that email Okta sends to your end usersIn Okta literature, we generally refer to "end users" as the people who have their own Okta home page (My Applications), using chiclets to authenticate into all of their apps. End users do not have any administrative control. When we refer to "users" we are generally referring to the individual(s) who have administrative control. appears to come from an address that you specify instead of the default Okta sender email@example.com. This allows you to present a more branded experience to your end usersIn Okta literature, we generally refer to "users" as the people who serve as Okta administrators. When we refer to "end users" we are generally referring to the people who the administrators serve. That is, those who use Okta chiclets to access their apps, but have no administrative control.. You can switch to a different custom domain or easily revert to the default Okta email domain. However, only one email domain can be in use at a time.
Okta sends your super admins a confirmation email once your custom domain is configured and operating correctly. To help ensure continuous operation, Okta polls your custom email domain once every 24 hours. If a problem occurs, Okta alerts super admins via email, and Okta-generated emails are sent from the default domain firstname.lastname@example.org until the problem is resolved.
- Only qualified administrators with access to the DNS records of your public custom domain should attempt these procedures.
- Okta strongly recommends that your organization implement the Sender Policy Framework (SPF) to prevent sender address forgery. If you already implement SPF in your custom domain, be aware that you must update the SPF record as described in this procedure.
- Go to Settings > Email & SMS.
- Click the Sender link. Screenshot
- Select a sender in the Configure Email Sender dialog box.
If you select Custom email domain, enter or edit information in the following fields:
- Email address to send from
- Name of sender
- Mail domain to send from.
Important: You must enter a unique subdomain that your organization has dedicated for Okta to send mail from. Later in this procedure, you will add this subdomain to your SPF record as an include-statement to show that you allow Okta to send mail from this subdomain.
- Save your changes.
- The Save button appears if you chose email@example.com, or if you chose a custom email domain and your orgThe Okta container that represents a real-world organization.'s DNS records do not need to be updated. You are finished after you click Save.
- The Save & View Required DNS Records button appears if you chose a custom email domain and your org's DNS records need to be updated before your settings can take effect. After you click the button, the DNS records that you need to update are shown.
- Update your DNS records using the provided values. Screenshot
- Click a DNS update option:
- I've updated the DNS records — Okta begins polling your DNS records until it detects your updates (up to 24 hours). Your configuration is pending until the DNS updates are detected.
- I will update the DNS records later — Your records are not polled and your configuration is incomplete until you update the relevant DNS records and click I've updated the DNS records. You can view the list of records that require an update at any time.
Add the SPF record to your DNS zone (root domain).
If your root domain already has an SPF record, Okta strongly recommends that you update it as described below to help prevent spoofers from sending mail that appears to have been sent from your domain.
An SPF record specifies the mail servers that your organization has authorized to send mail from your domain.
For example, if you only send mail from Microsoft Office 365, your SPF record will have an include-statement like this:
example.com TXT v=spf1 include:spf.protection.outlook.com -all
To complete this procedure, you must add another include-statement that specifies the host shown in the first CNAME row in the Configure Email Sender dialog box. (This is also the domain that you specified in the Mail domain to send from field.)
Add the host to the existing record to configure a combined SPF record like this:
example.com TXTv=spf1 include:oktamail.example.com include:spf.protection.outlook.com -all
- If you already send emails through SendGrid, you cannot configure Okta to send emails through that same domain.
- You cannot have more than 10 DNS lookups in your SPF record.