Stitchflow
Glint logo

Glint SCIM guide

Connector Only

How to automate Glint user provisioning, and what it actually costs

Summary and recommendation

Microsoft Viva Glint (formerly Glint) does not support SCIM provisioning at all. Instead, it relies exclusively on Microsoft Entra ID native integration, which only works if your organization uses Microsoft 365 and Entra ID as your primary identity provider. This creates a significant constraint: users must be manually created in both Entra ID and Viva Glint with matching email addresses, and a Microsoft 365 Global Admin must register Viva Glint in your Entra tenant. Organizations using other identity providers like Okta, Google Workspace, or OneLogin are completely locked out of automated provisioning.

The Entra ID dependency creates real operational friction even for Microsoft-centric organizations. While SSO authentication works through Entra, the user lifecycle management still requires manual coordination between your identity team and HR administrators. Survey population management and manager hierarchy synchronization—critical for employee engagement platforms—become manual processes that don't scale with organizational changes. For companies using multi-IdP environments or non-Microsoft identity solutions, Viva Glint essentially forces a choice between automated provisioning and your preferred identity architecture.

The strategic alternative

Glint 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 protocolAzure AD/Entra SSO
DocumentationNot available

Supported identity providers

IdPSSOSCIMNotes
OktaVia third-partyMicrosoft Viva Glint is a Microsoft product - not in Okta OIN. Requires Microsoft Entra ID for identity management.
Microsoft Entra IDVia third-partyUsers must exist in both Entra ID and Viva Glint with matching email addresses. Microsoft 365 Global Admin must register Viva Glint in Entra tenant. Supports external partner access via Entra B2B guest accounts (Dec 2025+).
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 Glint 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 Glint pricing problem

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

Tier comparison

PlanPriceSSOSCIM
Employee Communications$2/user/month
Workplace Analytics + Feedback$6/user/month
Viva Suite$12/user/month

Pricing structure

PlanPricingSCIMSSO
Employee Communications$2/user/month❌ Not available❌ Not available
Workplace Analytics + Feedback$6/user/month❌ Not available❌ Not available
Viva Suite$12/user/month❌ Not available✓ Entra ID only

What this means in practice

Microsoft ecosystem lock-in: Glint only works with Microsoft Entra ID (Azure AD). If you use Okta, Google Workspace, or OneLogin as your primary IdP, you'll need to maintain a hybrid identity setup or switch entirely to Microsoft's ecosystem.

Manual user management: Without SCIM, user provisioning requires manual coordination between your HR systems, Entra ID, and Viva Glint. Users must exist in both Entra ID and Viva Glint with matching email addresses.

Survey population sync challenges: Employee engagement surveys require accurate, up-to-date user lists and manager hierarchies. Manual provisioning makes it difficult to ensure survey participants reflect your actual organizational structure.

Additional constraints

Entra ID dependency
Requires Microsoft 365 Global Admin to register Viva Glint in your Entra tenant
No third-party IdP support
Cannot integrate directly with non-Microsoft identity providers
Bundle requirement
Glint functionality requires Viva Workplace Analytics + Feedback ($6/user/month) or full Viva Suite ($12/user/month)
Guest access complexity
External partner access requires Entra B2B guest accounts (available Dec 2025+)

Summary of challenges

  • Glint 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 Glint actually offers for identity

Microsoft Entra ID Integration (Viva Suite required)

Microsoft Viva Glint (formerly Glint) doesn't support traditional SCIM—it's a Microsoft product that relies entirely on Microsoft's identity ecosystem:

SettingDetails
ProtocolEntra ID native provisioning (not SCIM)
Supported IdPsMicrosoft Entra ID only
ConfigurationMicrosoft 365 Global Admin registers Viva Glint in tenant
User requirementUsers must exist in both Entra ID and Viva Glint with matching emails
External usersEntra B2B guest accounts supported (Dec 2025+)

The Microsoft lock-in: Since Microsoft acquired Glint, it's been integrated into the Viva ecosystem. There's no SCIM support because Microsoft expects you to use their identity infrastructure.

What you get with Viva Suite ($12/user/month)

Viva Suite includes:

Viva Glint employee engagement platform
Automatic user provisioning via Entra ID
Connections, Engage, Amplify, Insights, Pulse, Goals, Learning
Integration with Microsoft 365 ecosystem

The pricing reality: You're paying $12/user/month for the entire Viva Suite just to get automated provisioning for Glint. Most organizations only want the employee engagement surveys—not Microsoft's full workplace analytics stack.

What's missing for non-Microsoft shops

No integration with Okta, Google Workspace, or OneLogin
No standard SCIM protocol support
No flexibility to use Glint without Microsoft 365 licensing
Forces migration to Microsoft identity stack for a single HR tool

Translation: If you're not already committed to Microsoft's ecosystem, Viva Glint's identity requirements may force expensive infrastructure changes that go far beyond employee engagement surveys.

What IT admins are saying

Microsoft Viva Glint's Microsoft-only ecosystem creates integration challenges for IT teams managing mixed environments:

  • Forced Microsoft dependency: Requires Microsoft 365 licensing and Entra ID even if your primary IdP is Okta or Google Workspace
  • No SCIM standard: Uses proprietary Entra ID provisioning instead of industry-standard SCIM protocols
  • Limited IdP flexibility: Can't leverage existing Okta or Google Workspace provisioning workflows
  • Complex licensing maze: Understanding which Viva plan includes Glint functionality requires navigating Microsoft's complex SKU structure

Users must exist in both Entra ID and Viva Glint with matching email addresses.

Microsoft Learn documentation

Microsoft 365 Global Admin must register Viva Glint in Entra tenant.

Microsoft Viva Glint setup guide

The recurring theme

IT teams using non-Microsoft identity providers face a costly choice - either maintain parallel Microsoft infrastructure just for Glint, or find alternative employee engagement platforms that work with their existing tech stack.

The decision

Your SituationRecommendation
Small HR team (<25 users) with Microsoft 365Use Entra ID native provisioning
Mid-size organization (25-200 users)Use Stitchflow: eliminates Microsoft licensing complexity
Enterprise without Microsoft Viva SuiteUse Stitchflow: avoids $12/user/month enterprise requirement
Multi-IdP environment (Okta, Google Workspace, etc.)Use Stitchflow: Microsoft-only integration won't work
Organizations requiring audit trails and complianceUse Stitchflow: managed automation with SOC 2 compliance

The bottom line

Microsoft Viva Glint forces you into their ecosystem—requiring Viva Suite licensing at $12/user/month and limiting you to Entra ID only. For organizations that want employee engagement analytics without Microsoft's expensive bundle or vendor lock-in, Stitchflow provides automated provisioning that works with any IdP at predictable flat-rate pricing.

Make Glint workflows AI-native

Glint 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

Now part of Microsoft VivaAzure AD/Entra ID integrationMicrosoft 365 licensing required

Plan requirement

Not specified

Prerequisites

Not specified

Key limitations

  • Now part of Microsoft Viva
  • Azure AD/Entra ID integration
  • Microsoft 365 licensing required

Documentation not available.

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 → Glint → Single sign-on

Users must exist in both Entra ID and Viva Glint with matching email addresses. Microsoft 365 Global Admin must register Viva Glint in Entra tenant. Supports external partner access via Entra B2B guest accounts (Dec 2025+).

Use Stitchflow for automated provisioning.

Unlock SCIM for
Glint

Glint 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
Glint logo
Glint
via Stitchflow

Last updated: 2026-01-11

* Pricing and features sourced from public documentation.

Keep exploring

Related apps

TinyPulse logo

TinyPulse

No SCIM

Employee Engagement / HR

ProvisioningNot Supported
Manual Cost$11,754/yr

TinyPulse (now part of WebMD Health Services) does not offer native SCIM provisioning. While the platform supports SAML SSO with major identity providers including Okta, OneLogin, PingFederate, and ADFS, automated user provisioning is only available through OneLogin's connector—leaving Okta, Entra, and Google Workspace admins without provisioning options. This creates a significant gap for IT teams using other identity providers, as they must manually manage user lifecycle events like onboarding new employees or deprovisioning departing staff. The absence of universal SCIM support means IT teams face ongoing manual overhead and compliance risks. When employees leave the organization, their TinyPulse access must be manually revoked, creating potential security gaps. For growing organizations conducting regular employee engagement surveys, this manual user management becomes increasingly time-consuming and error-prone, especially given TinyPulse's inflexible annual licensing model that makes it difficult to adjust user counts mid-contract.

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