Summary and recommendation
Moz Pro, the SEO platform used by marketing teams and agencies, does not offer native SCIM provisioning. While Moz supports SSO through SAML 2.0 and OpenID Connect via OneLogin, Ping Identity, and other third-party connectors, user provisioning is only available through OneLogin's specific connector. This creates a significant limitation: if your organization uses Okta, Entra ID, or Google Workspace, you're forced into manual user management despite paying up to $599/month for Premium plans.
This OneLogin-only provisioning creates a real operational burden for IT teams. Most enterprises standardize on a single identity provider, and being locked into OneLogin just for Moz provisioning means either switching IdPs entirely (costly and disruptive) or accepting the security and compliance risks of manual user lifecycle management. When SEO teams need rapid access to campaign data and keyword tracking, manual provisioning delays can directly impact marketing operations.
The strategic alternative
Moz has no native SCIM. Automate offboarding, user access reviews, and license workflows across every app, including the ones without APIs. We maintain the integration layer underneath. You focus on judgment, not plumbing.
Quick SCIM facts
| SCIM available? | No |
| SCIM tier required | N/A |
| SSO required first? | No |
| SSO available? | Yes |
| SSO protocol | SAML 2.0, OpenID Connect |
| Documentation | Not available |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | Via third-party | ❌ | No Moz Pro app found in OIN catalog with SCIM. SSO via custom SAML setup only. |
| Microsoft Entra ID | Via third-party | ❌ | No native Entra ID integration documented. Use OneLogin for provisioning or manual user management. |
| Google Workspace | Via third-party | ❌ | No native support |
| OneLogin | Via third-party | ❌ | No native support |
The cost of not automating
Without SCIM (or an alternative like Stitchflow), your IT team manages Moz accounts manually. Here's what that costs:
The Moz pricing problem
Moz gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Starter | $49/month | ||
| Standard | $99/month | ||
| Medium | $179/month | ||
| Large | $299/month | ||
| Premium | $599/month |
Provisioning options
| Plan | Price | SCIM | Provisioning Method |
|---|---|---|---|
| Starter | $49/month | ❌ Not available | Manual only |
| Standard | $99/month | ❌ Not available | Manual only |
| Medium | $179/month | ❌ Not available | Manual only |
| Large | $299/month | ❌ Not available | Manual only |
| Premium | $599/month | ❌ Not available | OneLogin connector only |
What this means in practice
Limited IdP compatibility: If you're using Okta, Entra ID, or Google Workspace, you'll need to manage Moz users manually. Only OneLogin customers get automated provisioning through their proprietary connector.
No standardized API: Moz doesn't expose SCIM endpoints, meaning custom integrations aren't possible. You're locked into either manual user management or OneLogin's specific implementation.
SSO without provisioning: While Moz supports SAML SSO through multiple providers (OneLogin, Ping Identity, AuthDigital), this only handles authentication—not user lifecycle management.
Additional constraints
Summary of challenges
- Moz does not provide native SCIM at any price tier
- Organizations must rely on third-party tools or manual provisioning
- Our research shows teams manually provisioning this app spend significant hidden costs annually
What Moz actually offers for identity
OneLogin Connector (Third-party provisioning)
Moz provides user provisioning exclusively through OneLogin's marketplace connector:
| Feature | Details |
|---|---|
| Protocol | OneLogin's proprietary API |
| Supported operations | Create, update, delete users |
| Entitlement management | Yes (role assignments) |
| Real-time sync | Yes |
| IdP requirement | OneLogin only |
Major limitation: This provisioning option only works if your organization uses OneLogin as its primary identity provider. Teams using Okta, Entra ID, or Google Workspace are locked out entirely.
SAML SSO (Multiple providers)
Moz supports federated SSO through several identity providers:
| Setting | Details |
|---|---|
| Protocol | SAML 2.0, OpenID Connect |
| Supported IdPs | OneLogin, Ping Identity, AuthDigital |
| Configuration | Provider-specific setup required |
| JIT provisioning | ❌ No |
| User requirement | Manual account creation before SSO login |
Okta Integration Status
The Okta Integration Network shows no native Moz Pro application:
| Feature | Supported? |
|---|---|
| SAML SSO | ❌ No native app |
| OIDC SSO | ❌ No native app |
| SCIM provisioning | ❌ No |
| Custom SAML | ✓ Manual setup only |
Translation: Okta customers must configure SAML manually and handle all user provisioning through manual processes or CSV imports.
Why this approach fails at scale
The OneLogin-only provisioning creates a significant vendor lock-in problem. If your team uses any other IdP, you're stuck with manual user management across all Moz pricing tiers—from the $49/month Starter plan to the $599/month Premium plan. There's no native SCIM endpoint that works universally with modern identity providers.
What IT admins are saying
Moz's lack of native SCIM provisioning forces IT teams into vendor-specific workarounds:
- No standard SCIM endpoint means you're locked into specific IdP connectors
- OneLogin is the only documented provisioning path - limiting IdP flexibility
- Manual user management required for Okta and Entra ID environments
- SSO setup requires custom SAML configuration instead of pre-built connectors
"User provisioning (create/update/delete) and entitlement management" only works through OneLogin's connector, according to their marketplace documentation.
The recurring theme
Moz's SEO platform forces architectural decisions around your identity provider. If you're not using OneLogin, you're managing Moz users manually despite having enterprise-grade identity infrastructure.
The decision
| Your Situation | Recommendation |
|---|---|
| Small SEO team (<10 users) | Manual management is acceptable |
| Using OneLogin as your IdP | OneLogin's native provisioning connector handles automation |
| Large marketing organization (50+ users) | Use Stitchflow: automation essential across team sizes |
| Multi-IdP environment (Okta, Entra, etc.) | Use Stitchflow: OneLogin-only provisioning creates IdP lock-in |
| Enterprise with compliance requirements | Use Stitchflow: automation essential for audit trail |
The bottom line
Moz Pro is a leading SEO platform, but provisioning automation is limited to OneLogin users only. If you're on Okta, Entra ID, or Google Workspace, you're stuck with manual user management. For teams that want provisioning automation regardless of their IdP choice, Stitchflow eliminates the OneLogin dependency.
Make Moz workflows AI-native
Moz has no native SCIM. We build complete offboarding, user access reviews, and license workflows across every app, including the ones without APIs.
Technical specifications
SCIM Version
Not specifiedSupported Operations
Not specifiedSupported Attributes
Plan requirement
Not specifiedPrerequisites
Not specifiedKey limitations
- No native SCIM endpoint documented
- Provisioning via OneLogin integration
- SSO via third-party connectors
Documentation not available.
Configuration for Okta
Integration type
Okta Integration Network (OIN) app
Where to enable
Docs
No Moz Pro app found in OIN catalog with SCIM. SSO via custom SAML setup only.
Use Stitchflow for automated provisioning.
Unlock SCIM for
Moz
Moz has no native SCIM. We still automate end-to-end workflows across every app, including the ones without APIs.
See how it works


