Other · Okta coverage
ArcGIS Online and Okta: SSO and SCIM
Cloud GIS for mapping parcels, zoning, infrastructure and land records. No SCIM provisioning found.
SCIM pricing for every app →What Okta covers for ArcGIS Online, and what StitchOps adds.
Okta signs users in and manages accounts where the app supports it in the Okta Integration Network. StitchOps covers the rest of the ArcGIS Online account lifecycle.
In the OIN with SWA password fill only. No SAML, OIDC or provisioning.
StitchOps covers 8 of 8 capabilities for ArcGIS Online.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | Password fill only (SWA). No SAML or OIDC. | Enterprise password management signs users in to ArcGIS Online with vaulted credentials. Users never need the password. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares ArcGIS Online logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | No account creation in the OIN. | Creates the ArcGIS Online account with the right role on day one, anywhere a person can log in and act. |
| Movers | No account updates in the OIN. | Changes ArcGIS Online roles and access when someone changes jobs, anywhere a person can log in and act. |
| Leavers | No deprovisioning in the OIN. | Removes ArcGIS Online access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal. |
| Password rotation | No password rotation in ArcGIS Online. | Changes the ArcGIS Online password on a schedule and the day someone leaves, and updates your vault in the same run. |
| Access reviews | No connector to read or remove ArcGIS Online accounts. | Pulls the ArcGIS Online user list on a schedule, compares it to your directory, and removes what you approve. |
| Audit evidence | Nothing logged inside ArcGIS Online. | Step level evidence for every action StitchOps takes in ArcGIS Online. |
Single sign on
Okta, from the OIN
Password fill only (SWA). No SAML or OIDC.
StitchOps
Enterprise password management signs users in to ArcGIS Online with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares ArcGIS Online logins and their MFA across a team, with credentials kept in your vault.
Joiners
Okta, from the OIN
No account creation in the OIN.
StitchOps
Creates the ArcGIS Online account with the right role on day one, anywhere a person can log in and act.
Movers
Okta, from the OIN
No account updates in the OIN.
StitchOps
Changes ArcGIS Online roles and access when someone changes jobs, anywhere a person can log in and act.
Leavers
Okta, from the OIN
No deprovisioning in the OIN.
StitchOps
Removes ArcGIS Online access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal.
Password rotation
Okta, from the OIN
No password rotation in ArcGIS Online.
StitchOps
Changes the ArcGIS Online password on a schedule and the day someone leaves, and updates your vault in the same run.
Access reviews
Okta, from the OIN
No connector to read or remove ArcGIS Online accounts.
StitchOps
Pulls the ArcGIS Online user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside ArcGIS Online.
StitchOps
Step level evidence for every action StitchOps takes in ArcGIS Online.
Okta coverage from the Okta Integration Network, read October 10, 2026. ArcGIS on okta.com StitchOps for Okta →
SCIM and API tax
What ArcGIS Online charges to automate accounts.
We found no SCIM provisioning for ArcGIS Online: the Okta Integration Network lists no provisioning for it, and ArcGIS Online does not publish SCIM support. Ask the vendor before you count on it.
Pricing notes
Added for the government app catalog from vendor research (high confidence, vendor Esri). No SCIM found: no provisioning in the Okta Integration Network as of 2026 to 10 to 10 and no published SCIM support (rule set by Kyle 2026 to 10 to 10).
Last verified 2026-10-10 (estimate). SCIM pricing for every app · Method
Estimate ArcGIS Online and your other apps
Loading prices.
Expected scenario, list prices, SSO required, default department shares.
Automate ArcGIS Online accounts on the plan you have.
StitchOps carries what your identity provider decides into the app, through an API when one exists, and anywhere a person can log in and act when one does not.
Joiners
Create the ArcGIS Online account with the right role when your HR system or identity provider says someone starts.
Movers
Change ArcGIS Online roles, teams and access when someone changes department or manager.
Leavers
Remove ArcGIS Online access the same day someone leaves, and free the seat.
Access checks
List who can log in to ArcGIS Online on a schedule, with evidence for the audit.
Common questions.
Does ArcGIS Online support SCIM?
Not that we found. The Okta Integration Network lists no provisioning for ArcGIS Online, and ArcGIS Online does not publish SCIM support, so accounts are created and removed by hand or by a tool that works in ArcGIS Online the way an admin would.
Can ArcGIS Online accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes ArcGIS Online accounts on the plan you already have, triggered by the events your identity provider already sends. It uses an API when one exists and works anywhere a person can log in and act when one does not.
Is ArcGIS Online in the Okta Integration Network?
Yes. As of October 10, 2026, the OIN lists ArcGIS with SWA sign in and no provisioning.
Can Okta deprovision ArcGIS Online users?
Not through an OIN connector. StitchOps removes ArcGIS Online accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.
How do you rotate ArcGIS Online passwords when someone leaves?
StitchOps logs in to ArcGIS Online, sets a new password, confirms it took effect, and updates 1Password, Keeper or the StitchOps vault in the same run.
Last updated . Product names are trademarks of their respective owners. StitchOps is not affiliated with or endorsed by them.
Start with one workflow that never had an API.
Fifteen minutes on your top three manual processes. We tell you which one to run first.