Okta Secure Partner Access

Name: Okta Secure Partner Access
Brand: Okta

Leader

Okta secures AI

Est 2009|Valuation $37B|Raised $417.7M

LinkedIn 679K|Website|Web traffic 153.9M|FTEs 6,366|HQ San Francisco, CA

MarketsIdentity Provider (IdP) & SSO Identity Provider (IdP) & Single Sign-On (SSO)

01Competitive Landscape

Narrative analysis

**Where SPA appears to differentiate** - SPA’s packaging around delegated partner administration and realm-based segmentation is intended to provide a structured alternative to managing external users within a regular workforce tenant. **Where competitors may be stronger** - Microsoft Entra External ID provides published usage-based pricing and has native integration advantages for Microsoft-first organizations; this can simplify cost forecasting for large, sporadic partner populations. **Customer sentiment comparing Okta vs Microsoft (indicative, not SPA-specific)** - Practitioner sentiment varies: some report longer troubleshooting cycles with Microsoft support and prefer Okta for certain operational models; others migrate toward Microsoft to consolidate licensing and platform footprint. **Market adoption signals (limited in this run)** - Okta reports a large customer base overall, but public information does not quantify the subset of customers using SPA specifically.

	Okta Secure Partner Access	Microsoft Entra External ID	Ping Identity (PingOne for Workforce)
Starting Price	Not publicly listed; typically quote-based; SPA is a Workforce SKU	Published usage-based pricing model with tiers	Typically quote/contract-based; public pricing is variable
Suitable scenarios	Enterprises needing partner user segmentation and delegated partner administration within a workforce identity context	External identities at scale; CIAM-like scenarios and federation with external identity providers	Enterprises standardizing on Ping’s workforce IAM capabilities
Key Strength	Realms and a partner administration portal intended to separate partner management from the central Admin Console	Transparent usage economics and integration with Microsoft ecosystem services	Broad enterprise IAM feature set (SSO, MFA, directory services)
Key Weakness	Pricing opacity; governance complexity; reported friction around trust-center access	Licensing and governance add-ons can introduce complexity for some deployments	Pricing and contract terms can be a procurement consideration for some buyers

01Competitive Landscape

Narrative analysis

Where SPA appears to differentiate

SPA’s packaging around delegated partner administration and realm-based segmentation is intended to provide a structured alternative to managing external users within a regular workforce tenant.

Where competitors may be stronger

Microsoft Entra External ID provides published usage-based pricing and has native integration advantages for Microsoft-first organizations; this can simplify cost forecasting for large, sporadic partner populations.

Customer sentiment comparing Okta vs Microsoft (indicative, not SPA-specific)

Practitioner sentiment varies: some report longer troubleshooting cycles with Microsoft support and prefer Okta for certain operational models; others migrate toward Microsoft to consolidate licensing and platform footprint.

Market adoption signals (limited in this run)

Okta reports a large customer base overall, but public information does not quantify the subset of customers using SPA specifically.

	Okta Secure Partner Access	Microsoft Entra External ID	Ping Identity (PingOne for Workforce)
Starting Price	Not publicly listed; typically quote-based; SPA is a Workforce SKU	Published usage-based pricing model with tiers	Typically quote/contract-based; public pricing is variable
Suitable scenarios	Enterprises needing partner user segmentation and delegated partner administration within a workforce identity context	External identities at scale; CIAM-like scenarios and federation with external identity providers	Enterprises standardizing on Ping’s workforce IAM capabilities
Key Strength	Realms and a partner administration portal intended to separate partner management from the central Admin Console	Transparent usage economics and integration with Microsoft ecosystem services	Broad enterprise IAM feature set (SSO, MFA, directory services)
Key Weakness	Pricing opacity; governance complexity; reported friction around trust-center access	Licensing and governance add-ons can introduce complexity for some deployments	Pricing and contract terms can be a procurement consideration for some buyers