<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D54z00009NKDaNCAXOkta Classic EngineIntegrationsAnswered2026-06-04T20:28:37.000Z2023-06-26T19:49:38.000Z2026-06-04T20:28:37.000Z

FredR.54024 (Customer) asked a question.

June 26, 2023 at 7:49 PM
Setting up a Custom Domain - Branding

Hello,

 

I am new to OKTA and looking to deploy OKTA with Office365 integration. Currently we have a hybrid environment with O365 and Azure. I have added the Office 365 application and want to use WS Federation to authenticate as OKTA is integrated with our Active Directory.

 

I am trying to set up a custom Domain under Brands so that users will be redirected to our companies Domain. I have added TXT and CNAMES records to GoDaddy ( our host provider) but the Domain will still not verify in OKTA or O365.

 

Thanks in advance for any assistance that can be offered.

 

Cheers,

 

Fred

  • 3 answers
  • 1.16K views
FredR.54024 likes this.

  • NiallM.34104 (Atlas Identity)

    Hi Fred. That's a task I've performed quite a few times, and it's usually a straight shot. I would ask you to check your DNS records a second time. The only time I've seen that fail is when the DNS records do not exist, or do not reflect the value that Okta has provided. DNS provides vary in how they want those values presented, so also check with your Go Daddy documentation for TXT and CNAME values.

     

    Then also check Google's DIG tool to see how Okta is seeing your DNS records.

    Expand Post
    Selected as Best

  • NiallM.34104 (Atlas Identity)

    Hi Fred. That's a task I've performed quite a few times, and it's usually a straight shot. I would ask you to check your DNS records a second time. The only time I've seen that fail is when the DNS records do not exist, or do not reflect the value that Okta has provided. DNS provides vary in how they want those values presented, so also check with your Go Daddy documentation for TXT and CNAME values.

     

    Then also check Google's DIG tool to see how Okta is seeing your DNS records.

    Expand Post
    Selected as Best

  • FredR.54024 (Customer)

    Hi Niall,

     

    Thanks for the response. Im not sure what the issue might be but it is my first time setting it up. We use GoDaddy for our DNS records. We have .com domain but also a .io and im not sure if that is causing conflict for the configuration. I tried the TXT and CNAME OKTA provides when setting up the domain under brands in OKTA on both our .com and .io but still will not verify.

     

    When i try to add Domain in O365 it gives .io for TXT name however the .com is our main Domain.

     

    Cheers,

     

    Fred

    Expand Post

  • NiallM.34104 (Atlas Identity)

    Hi Fred. Easiest way to check. Go here: https://toolbox.googleapps.com/apps/dig/

     

    Put in your custom domain. Check what TXT and CNAME records Google Dig can see. If you can't see them, or they are not exactly what Okta told you to put in, then that's the cause.

     

    Expand Post
This question is closed.
Loading
Setting up a Custom Domain - Branding