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 required | N/A |
| SSO required first? | Yes |
| SSO available? | Yes |
| SSO protocol | Azure AD/Entra SSO |
| Documentation | Not available |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | Via third-party | ❌ | Microsoft Viva Glint is a Microsoft product - not in Okta OIN. Requires Microsoft Entra ID for identity management. |
| Microsoft Entra ID | Via third-party | ❌ | 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+). |
| 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 Glint accounts manually. Here's what that costs:
The Glint pricing problem
Glint gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Employee Communications | $2/user/month | ||
| Workplace Analytics + Feedback | $6/user/month | ||
| Viva Suite | $12/user/month |
Pricing structure
| Plan | Pricing | SCIM | SSO |
|---|---|---|---|
| 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
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:
| Setting | Details |
|---|---|
| Protocol | Entra ID native provisioning (not SCIM) |
| Supported IdPs | Microsoft Entra ID only |
| Configuration | Microsoft 365 Global Admin registers Viva Glint in tenant |
| User requirement | Users must exist in both Entra ID and Viva Glint with matching emails |
| External users | Entra 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:
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
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 365 Global Admin must register Viva Glint in Entra tenant.
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 Situation | Recommendation |
|---|---|
| Small HR team (<25 users) with Microsoft 365 | Use Entra ID native provisioning |
| Mid-size organization (25-200 users) | Use Stitchflow: eliminates Microsoft licensing complexity |
| Enterprise without Microsoft Viva Suite | Use 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 compliance | Use 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.
Technical specifications
SCIM Version
Not specifiedSupported Operations
Not specifiedSupported Attributes
Plan requirement
Not specifiedPrerequisites
Not specifiedKey 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
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


