<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
0D54z00007FeKCeCANOkta Classic EngineDirectoriesAnswered2022-03-09T20:39:40.000Z2021-10-22T01:47:41.000Z2021-10-24T11:50:41.000Z

TaiB.46430 (Customer) asked a question.

Make Azure Active Directory an identity provider

Hi,

At my current company, we have a on-prem AD connect to both Okta and Azure AD, however the on-prem AD server is not correct domain name (Thanks to contractors). Our Azure AD is correct domain name but it is syncing with on-prem AD for now. I plan to move everything to the cloud, but I have few question. If I follow this instruction https://help.okta.com/en/prod/Content/Topics/Provisioning/azure/azure-identify-identity-provider.htm. Does it mean I will have two AD agents on different domain? What I want to do is, get rid of on-prem domain server (again, wrong domain name) then move to Azure AD. Okta will use Azure AD to sync.

 

Also, we use Okta radius and it installed on the on-prem server. If I move to Azure AD, can I still use my current radius to authenticate?

 

Thanks


  • SathishK.23283 (Customer)

    I believe you can use the current RADIUS Setup. do we have anyone worked on this ?

This question is closed.
Loading
Make Azure Active Directory an identity provider