Introduction

activate can integrate with okta to provide single sign on (sso) and custom authentication capabilities this connection allows users to authenticate to activate using their okta credentials, enabling centralized identity management and consistent access control across your environment okta is not used by activate for directory synchronization or provisioning — it is solely used as an authentication provider once configured, activate will redirect users to okta for sign in, and okta will handle user verification and token issuance before returning authenticated users to activate when to use okta use an okta connection when your organization manages identities and authentication in okta rather than microsoft entra id (azure ad) this approach is suitable when okta is your primary identity provider and you want users to sign in with their existing okta accounts you require sso or mfa policies already managed within okta you want to maintain a separation between identity management and microsoft 365 integration if your environment uses microsoft entra id , it is generally recommended to configure sso through entra id instead, as this provides deeper integration with microsoft services such as exchange online and graph api