Skip to content
Okta vs Entra

Reviewed 10 November 2026

Agent pricing as published for Agent 365 and Okta Agent SSO

Reviewed 2026-11-10 · Editorial assessment by the editors

By the editors. Published 2026-11-10. 5 min read. Tags: AI agents, Pricing, Buying.

Microsoft Agent 365 lists a per-user price, not a per-agent price. Okta includes Agent SSO in core SSO for agents supporting Cross App Access, while its wider agent offering is separate. NewCore publishes no list price. Compare entitlement boundaries and prerequisites before treating these as equivalent purchasing options.

Start with the billing unit

Agent procurement needs a scope comparison before a price comparison. A workforce subscription, a supported agent connection and a governance layer describe different purchases. Putting their labels in adjacent spreadsheet rows does not make their coverage equal. Record the billing unit beside the capability, then mark every prerequisite that the published material leaves to a contract discussion. The aim is to distinguish a confirmed price from an estimate, not to produce a single number from incomplete inputs.

The cited vendor pricing pages are the price baseline here. They were read on 3 November 2026. Their entries are published listings, not negotiated quotes or promises about a particular deployment. Use the Entra pricing page and Okta pricing page for the workforce context. An agent evaluation should then add a separate entitlement record rather than silently assigning every agent control to the underlying employee license.

Agent 365 is priced per user

The published Microsoft Agent 365 entry is $15 per user per month, paid yearly with an annual commitment. It is explicitly per user, not per agent. The pricing record says to check prerequisite subscriptions. Do not multiply this listing by the discovered agent count and present the result as a Microsoft quote. Equally, do not assume that a user license removes every other subscription requirement for every agent capability.

The same records list Entra ID P1 at $7 per user per month and P2 at $10, paid yearly. Entra Suite is $12 per user per month, paid yearly, and requires P1 or a plan including P1. Entra ID Governance is listed at $7 with prerequisite licenses and coverage to be confirmed. These workforce entries provide context, not a formula for adding all products together. Ask which subscriptions are already held and which proposed controls require something additional.

  • Record the population licensed for Agent 365 without substituting the agent inventory for that population.
  • Ask for the prerequisite subscription and the capability it enables in writing.
  • Keep an included entitlement separate from an incremental purchase in the cost worksheet.

Okta Agent SSO inclusion has a boundary

Okta states that Agent SSO is included in core Okta SSO at no additional cost for agents supporting Cross App Access. That is a useful purchasing distinction: a supported connection can use the included capability without turning the whole agent product into a free offering. The wider Okta for AI Agents offering is a separate subscription. The inclusion statement does not establish a published price for that broader subscription.

Read the Agent SSO and Cross App Access note before writing the requirement. It distinguishes enterprise-managed connections from approving a later operation. A purchase request for connection authorization should name the agent client and resource. A request for runtime action checks should identify that separate requirement. Otherwise a buyer can appear to have priced a control that was never part of the selected entitlement.

The workforce pricing records list Okta Starter at $6 per user per month, Core Essentials at $14 and Essentials at $17, billed annually. Those entries carry a $1,500 annual minimum. Professional and Enterprise say to inquire for pricing. None of those workforce listings should be relabeled as a published per-agent price. Confirm the selected suite, add-ons and contract scope rather than inferring agent coverage from the suite name.

Treat an unpublished price as an open question

NewCore publishes no list price. Its sourced pages describe discovery, task-scoped access and human approval as an agent governance layer alongside the identity provider a company already has. Those capabilities can be relevant to a requirement that workforce sign-in does not answer. Their relevance does not supply a public price, a billing unit or a contract minimum. Request those terms rather than borrowing a workforce price from another product.

An AWS Marketplace listing is not itself a published list price in the material reviewed here. The same discipline applies to the wider Okta agent subscription: the Agent SSO inclusion statement is not a quote for every agent capability. Leave the amount unresolved until the vendor confirms it. A blank estimate with a named follow-up is more useful than a precise-looking total based on a product with a different scope.

Use the NewCore profile to identify the capability under discussion. Ask for discovery coverage, the enforcement boundary and the human approval requirement to appear beside the commercial line item. This keeps a governance proposal comparable with the work it is intended to perform, without suggesting that it replaces the existing workforce provider or that the absence of a list price implies any particular cost.

Build a purchasing worksheet around evidence

Create one row per proposed control, not one row per vendor logo. Each row should identify the current subscription, the published incremental price if one exists, the billing unit and the unresolved prerequisite. Add the exact client and resource for connection features. For action governance, name the operation being evaluated and the evidence the pilot must produce. This is a procurement method, not a claim that any one bundle covers the whole workflow.

Keep the commercial review and technical acceptance connected. An included feature that does not support the selected connection cannot satisfy that requirement merely because its incremental price is zero. A quoted governance service still needs a demonstration of the relevant action boundary. Compare the same workflow and retain unresolved terms as explicit questions. The decision should show what is purchased, what is already included and what remains unconfirmed, without manufacturing a total from unlike units.

Frequently asked questions

Is Agent 365 priced per agent?

The published record lists Microsoft Agent 365 at $15 per user per month, paid yearly with an annual commitment. It is not a per-agent listing. Confirm prerequisite subscriptions and the licensed population before calculating a deployment budget.

Does included Agent SSO make all Okta agent controls free?

No. The inclusion applies to Agent SSO in core Okta SSO for agents supporting Cross App Access. The wider Okta for AI Agents offering is a separate subscription. Confirm the scope of that subscription rather than extending the inclusion statement.

Does NewCore publish a list price?

NewCore publishes no list price in the reviewed material. Its sourced pages describe agent governance alongside an existing identity provider. Request a quote that specifies the billing unit, covered capabilities and contract conditions instead of assuming a price from another product.