Stitchflow
GoTo Meeting logo

GoTo Meeting SCIM guide

Connector Only

How to automate GoTo Meeting user provisioning, and what it actually costs

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 requiredN/A
SSO required first?Yes
SSO available?Yes
SSO protocolSAML 2.0
DocumentationNot available

Supported identity providers

IdPSSOSCIMNotes
OktaVia third-partyGoToMeeting SSO via SAML only. For SCIM provisioning, use GoToConnect integration which includes GoToMeeting.
Microsoft Entra IDVia third-partyAzure AD automatic provisioning for GoToMeeting deprecated. Use AD Connector v2 or GoToConnect for provisioning.
Google WorkspaceVia third-partyNo native support
OneLoginVia third-partyNo 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:

Source: Stitchflow aggregate data across apps with 2+ instances, normalized to 500 employees
Orphaned accounts (ex-employees with access)7
Unused licenses12
IT hours spent on manual management/year101 hours
Unused license cost/year$3,925
IT labor cost/year$6,088
Cost of compliance misses/year$1,741
Total annual financial impact$11,754

The GoTo Meeting pricing problem

GoTo Meeting gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.

Tier comparison

PlanPriceSSOSCIM
Professional$12/organizer/mo (annual)
Business$16/organizer/mo (annual)
EnterpriseCustom pricing

Pricing structure

PlanPriceSSOSCIM
Professional$12/organizer/mo (annual)
Business$16/organizer/mo (annual)
EnterpriseCustom 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:

Manual onboarding
Every new employee requires manual account creation in GoTo Meeting
No automated deprovisioning
Terminated employees retain access until manually removed
License waste
No automatic seat reclamation when users leave
Compliance gaps
Cannot enforce consistent provisioning policies across the organization

Workaround costs

AD Connector v2 requires additional infrastructure and Active Directory integration
GoToConnect (which includes GoTo Meeting) offers SCIM but requires migrating to their unified communications platform
API-based automation requires custom development and maintenance

Additional constraints

Platform migration required
True SCIM provisioning only available by upgrading to GoToConnect
AD dependency
AD Connector v2 only works with organizations using Active Directory
SSO prerequisite
SAML SSO requires Business plan minimum ($16/organizer/mo vs $12/organizer/mo Professional)
Domain verification
SSO setup requires DNS configuration and domain ownership verification

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:

SettingDetails
ProtocolSAML 2.0
Supported IdPsOkta, Entra ID, CyberArk, Duo, generic SAML
ConfigurationVia GoTo Organization Center with domain verification
Initiation methodsSP-initiated and IdP-initiated (varies by provider)
User requirementAccounts 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)

MethodStatusDetails
Native SCIM❌ Not supportedGoTo Meeting has no SCIM 2.0 implementation
Azure AD provisioning❌ DeprecatedMicrosoft's automatic provisioning tutorial marked as deprecated
AD Connector v2⚠️ Alternative onlyOn-premises connector for directory sync
GoToConnect SCIM⚠️ Different productRequires 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:

FeatureSupported?
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.

Microsoft Entra documentation

GoToMeeting SSO via SAML only. For SCIM provisioning, use GoToConnect integration which includes GoToMeeting.

Okta Integration Network

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 SituationRecommendation
Small team (<20 meeting organizers)Manual provisioning is manageable given lack of alternatives
Growing organization with regular turnoverUse Stitchflow: manual processes don't scale
Enterprise with compliance requirementsUse Stitchflow: audit trails and automated lifecycle essential
Multi-department video conferencing needsUse Stitchflow: centralized automation prevents access creep
Already using GoToConnect platformConsider 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.

Covers apps without native SCIM, including the ones without APIs
Less than a week, start to finish (~2 hours of your time)
Built with your team; extend to anything else in the company
Book a Demo

Technical specifications

SCIM Version

Not specified

Supported Operations

Not specified

Supported Attributes

No SCIM 2.0 supportAzure AD automatic provisioning deprecatedAD Connector v2 available as alternativeSP-initiated SSO only with some IdPs

Plan requirement

Not specified

Prerequisites

Not specified

Key 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

Okta Admin Console → Applications → GoTo Meeting → Sign On

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

Entra admin center → Enterprise applications → GoTo Meeting → Single sign-on

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
Admin Console
Directory
Applications
GoTo Meeting logo
GoTo Meeting
via Stitchflow

Last updated: 2026-01-11

* Pricing and features sourced from public documentation.

Keep exploring

Related apps

Lifesize logo

Lifesize

No SCIM

Video Conferencing

ProvisioningNot Supported
Manual Cost$11,754/yr

Lifesize, the video conferencing platform now owned by Enghouse, does not offer SCIM provisioning on any plan. While Lifesize supports SAML 2.0 SSO integration with identity providers like Okta, Azure AD, and generic SAML providers, this only handles authentication—not user lifecycle management. IT teams must manually create, update, and deactivate user accounts in the Lifesize admin console, even though SSO can authenticate users once they exist in the system. This creates a significant operational gap for organizations using Lifesize for company-wide video conferencing. Without automated provisioning, IT teams face the ongoing burden of manually managing user accounts as employees join, change roles, or leave the organization. For video conferencing platforms where user access needs to scale with organizational changes, this manual overhead becomes particularly problematic during onboarding/offboarding cycles and can create security risks when former employees retain access to meeting capabilities.

View full guide
6sense logo

6sense

No SCIM

B2B Revenue Intelligence / ABM

ProvisioningNot Supported
Manual Cost$11,754/yr

6sense, the B2B revenue intelligence platform, has paused SCIM provisioning for new customers until Q4 2026. While existing customers with SCIM enabled can continue using it, new implementations are limited to JIT (Just-In-Time) provisioning through SAML SSO. This creates a significant gap for IT teams managing revenue intelligence access, as JIT only creates users on first login and provides minimal attribute mapping (email, first name, last name only). For an enterprise platform with typical pricing of $55,000-$130,000 annually, the absence of automated user lifecycle management is a substantial limitation. The lack of SCIM until Q4 2026 forces IT teams into manual provisioning workflows for a platform handling sensitive revenue data. While SAML SSO handles authentication, it doesn't address user lifecycle events like role changes, department transfers, or offboarding. This creates compliance risks in revenue teams where access to prospect data and sales intelligence must be tightly controlled. The nearly two-year wait for SCIM restoration means organizations implementing 6sense today face manual user management for the foreseeable future.

View full guide
ActiveCampaign logo

ActiveCampaign

No SCIM

Marketing Automation / Email

ProvisioningNot Supported
Manual Cost$11,754/yr

ActiveCampaign, the marketing automation platform, does not offer native SCIM provisioning on any plan. While the Enterprise plan ($145+/month) includes SAML 2.0 SSO with just-in-time (JIT) provisioning, this only creates user accounts on first login—there's no automated deprovisioning when employees leave or change roles. New SSO users are automatically added to a generic "SSO Users" group with configurable permissions, but IT teams have no way to programmatically manage user lifecycles or enforce granular access controls based on department or role changes. This creates a significant gap for marketing teams that need to manage access to customer data and campaign tools. When employees leave the company or change departments, their ActiveCampaign access must be manually revoked, creating compliance risks and potential data exposure. The lack of automated deprovisioning means former employees could theoretically retain access to sensitive marketing data and customer information until someone manually removes them from the platform.

View full guide