Ejento AI
GuidesQuickstartRecipesREST APIsRelease NotesFAQs
GuidesQuickstartRecipesREST APIsRelease NotesFAQs
Ejento AI
  1. Setup After Deployment
  • How to Setup Ejento on Azure
  • Prerequisites
  • Deployment on Azure
  • Setup After Deployment
    • Custom Domain Set Up
    • Microsoft SSO Authentication
    • Okta SSO Authentication
    • SharePoint Connection Set Up
    • Developer API Set Up
  • Overview
    • Azure Resources
  1. Setup After Deployment

Custom Domain Set Up

Important: The Ejento team will provide the exact values you must use. You will create four DNS records total:
2 × CNAME (one for the Ejento App, one for the Authentication Service) and 2 × TXT (one verification record for each).

💡 Note: The following steps are to be completed after deployment is initiated — please finish the deployment process before proceeding.

Overview#

You’ll map two subdomains to Ejento’s Azure Front Door (AFD) endpoints:
Ejento App (UI) — e.g., ejento.yourdomain.com
Authentication Service — e.g., idejento.yourdomain.com
Each subdomain needs:
CNAME → points your subdomain to the Ejento AFD endpoint
TXT → used to verify domain ownership for certificate issuance
Recommendation: Use subdomains like ejento and idejento. Avoid using the apex/root domain unless your DNS provider supports ALIAS/ANAME/flattening at apex.

The Four DNS Records (Template)#

Replace everything in angle brackets <> with values from the Ejento team.
PurposeTypeHost / NameTarget / ValueTTL
Ejento App (UI)CNAME<app-subdomain>.<yourdomain><ejento-ui-afd-endpoint>.azurefd.netAuto
Ejento App (UI) VerificationTXT_dnsauth.<app-subdomain>.<yourdomain><ui-verification-token>Auto
Authentication ServiceCNAME<auth-subdomain>.<yourdomain><ejento-auth-afd-endpoint>.azurefd.netAuto
Authentication Service VerificationTXT_dnsauth.<auth-subdomain>.<yourdomain><auth-verification-token>Auto
Notes
Host/Name may be entered as just the label at some providers (e.g., ejento or _dnsauth.ejento). The provider will append your domain automatically.
If using Cloudflare, set CNAME Proxy status = DNS only

Example (Filled-In using ejento.yourdomain.com)#

This is an example only. Do not use these values—Ejento will share your real endpoints and tokens.
PurposeTypeHost / NameTarget / ValueTTL
Ejento App (UI)CNAMEejento.yourdomain.comejento-ui-prod-12345.azurefd.netAuto
Ejento App (UI) VerificationTXT_dnsauth.ejento.yourdomain.comejento-domain-verification=UI_7f2a9bcdAuto
Authentication ServiceCNAMEauth.yourdomain.comejento-auth-prod-67890.azurefd.netAuto
Authentication Service VerificationTXT_dnsauth.auth.yourdomain.comejento-domain-verification=AUTH_e31c45daAuto

Step-by-Step#

1.
Choose subdomains for the app and auth services (e.g., ejento.yourdomain.com, idejento.yourdomain.com).
2.
Create four DNS records (two CNAME + two TXT) using the template above and the values from Ejento.
3.
Notify Ejento once records are saved; we’ll trigger verification and provision HTTPS certificates.
4.
Wait for propagation: usually 5–30 minutes, but it can take up to 24–48 hours depending on your DNS.

DNS provider guides (how to add CNAME/TXT records)#

If your DNS provider is one of the following, use their official guide(s) to add the records :
Azure DNS
AWS Route 53
Cloudflare
Namecheap
Not listed? Search your provider’s help center for “Add CNAME record” and “Add TXT record,” then follow the same four-record pattern from this guide.
Previous
Deployment on Azure
Next
Microsoft SSO Authentication