Summary and recommendation
GoTo Meeting does not support SCIM provisioning on any plan. While the platform offers SAML 2.0 SSO integration with major identity providers including Okta, Entra ID, and others, this only handles authentication—not user lifecycle management. GoTo Meeting previously supported Azure AD automatic provisioning, but this feature has been deprecated, leaving IT teams with only manual provisioning or GoTo's AD Connector v2 for limited automation. For organizations seeking true SCIM provisioning, GoTo recommends upgrading to GoToConnect (their unified communications platform that includes GoToMeeting functionality), but this forces teams into a completely different product suite.
This creates a significant gap for organizations that need GoTo Meeting specifically for video conferencing but require automated user provisioning. IT teams must either manually manage user accounts—creating compliance risks and operational overhead—or invest in GoToConnect's broader platform just to access SCIM capabilities. The deprecated Azure provisioning particularly impacts Microsoft-centric organizations that were relying on this integration for user lifecycle management.
The strategic alternative
GoTo Meeting 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? | Yes |
| SSO available? | Yes |
| SSO protocol | SAML 2.0 |
| Documentation | Not available |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | Via third-party | ❌ | GoToMeeting SSO via SAML only. For SCIM provisioning, use GoToConnect integration which includes GoToMeeting. |
| Microsoft Entra ID | Via third-party | ❌ | Azure AD automatic provisioning for GoToMeeting deprecated. Use AD Connector v2 or GoToConnect for provisioning. |
| 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 GoTo Meeting accounts manually. Here's what that costs:
The GoTo Meeting pricing problem
GoTo Meeting gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Professional | $12/organizer/mo (annual) | ||
| Business | $16/organizer/mo (annual) | ||
| Enterprise | Custom pricing |
Pricing structure
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Professional | $12/organizer/mo (annual) | ||
| Business | $16/organizer/mo (annual) | ||
| Enterprise | Custom pricing |
Key limitation: GoTo Meeting previously supported Azure AD automatic provisioning, but this feature was deprecated in 2024. No replacement SCIM solution exists within GoTo Meeting itself.
What this means in practice
Without SCIM, IT teams face significant operational overhead:
Workaround costs
Additional constraints
Summary of challenges
- GoTo Meeting 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 GoTo Meeting actually offers for identity
SAML SSO (Business and Enterprise plans)
GoTo Meeting supports SAML 2.0 integration through their Organization Center:
| Setting | Details |
|---|---|
| Protocol | SAML 2.0 |
| Supported IdPs | Okta, Entra ID, CyberArk, Duo, generic SAML |
| Configuration | Via GoTo Organization Center with domain verification |
| Initiation methods | SP-initiated and IdP-initiated (varies by provider) |
| User requirement | Accounts must be provisioned separately |
Major limitation: SAML SSO only handles authentication. All user provisioning must be handled manually or through alternative methods.
Provisioning Options (All Deprecated or Workarounds)
| Method | Status | Details |
|---|---|---|
| Native SCIM | ❌ Not supported | GoTo Meeting has no SCIM 2.0 implementation |
| Azure AD provisioning | ❌ Deprecated | Microsoft's automatic provisioning tutorial marked as deprecated |
| AD Connector v2 | ⚠️ Alternative only | On-premises connector for directory sync |
| GoToConnect SCIM | ⚠️ Different product | Requires upgrading to GoToConnect (includes GoTo Meeting) |
The reality: GoTo Meeting treats user provisioning as an afterthought. Their recommended solution is either manual management or purchasing their unified communications platform (GoToConnect) to get SCIM support.
Okta Integration (Password vaulting only)
The official Okta Integration Network listing shows extremely limited functionality:
| Feature | Supported? |
|---|---|
| SAML SSO | ✓ Yes (via SAML app) |
| Create users | ❌ No |
| Update users | ❌ No |
| Deactivate users | ❌ No |
| Group management | ❌ No |
| Password sync | ✓ Yes (SWA only) |
The Okta integration primarily offers secure web authentication (password vaulting), not true federated identity management.
What IT admins are saying
Community sentiment on GoTo Meeting's provisioning reveals widespread frustration with manual user management:
- No SCIM support forces manual provisioning for every user
- Azure AD automatic provisioning was deprecated, leaving teams without automation
- AD Connector v2 is the only alternative but requires additional setup complexity
- SSO works but doesn't solve the core problem of lifecycle management
Azure AD automatic provisioning for GoToMeeting deprecated. Use AD Connector v2 or GoToConnect for provisioning.
GoToMeeting SSO via SAML only. For SCIM provisioning, use GoToConnect integration which includes GoToMeeting.
The recurring theme
GoTo Meeting stripped away their automated provisioning without providing a seamless replacement. IT teams are left choosing between manual user management or migrating to GoToConnect just to get basic automation features back.
The decision
| Your Situation | Recommendation |
|---|---|
| Small team (<20 meeting organizers) | Manual provisioning is manageable given lack of alternatives |
| Growing organization with regular turnover | Use Stitchflow: manual processes don't scale |
| Enterprise with compliance requirements | Use Stitchflow: audit trails and automated lifecycle essential |
| Multi-department video conferencing needs | Use Stitchflow: centralized automation prevents access creep |
| Already using GoToConnect platform | Consider GoToConnect's native SCIM via Okta instead |
The bottom line
GoTo Meeting offers solid video conferencing but zero provisioning automation—no SCIM support and deprecated Azure AD integration leave you with manual user management only. For organizations that need automated user lifecycle management without the overhead of manual provisioning, Stitchflow delivers the automation GoTo Meeting simply doesn't provide.
Make GoTo Meeting workflows AI-native
GoTo Meeting 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 SCIM 2.0 support
- Azure AD automatic provisioning deprecated
- AD Connector v2 available as alternative
- SP-initiated SSO only with some IdPs
Documentation not available.
Configuration for Okta
Integration type
Okta Integration Network (OIN) app
Prerequisite
SSO must be configured before enabling SCIM.
Where to enable
Docs
GoToMeeting SSO via SAML only. For SCIM provisioning, use GoToConnect integration which includes GoToMeeting.
Use Stitchflow for automated provisioning.
Configuration for Entra ID
Integration type
Microsoft Entra Gallery app
Prerequisite
SSO must be configured before enabling SCIM.
Where to enable
Azure AD automatic provisioning for GoToMeeting deprecated. Use AD Connector v2 or GoToConnect for provisioning.
Use Stitchflow for automated provisioning.
Unlock SCIM for
GoTo Meeting
GoTo Meeting has no native SCIM. We still automate end-to-end workflows across every app, including the ones without APIs.
See how it works


