Help

How to: Set up Single Sign-On (SSO) for Trimble Identity via Entra (Azure AD) or Google

Modified: 29 Sep 2026 Stabicad
Not version-specific
Stabicad

Understanding the Issue

Trimble Identity is the central authentication platform used across many Trimble products. By default, users manage a separate Trimble Identity account. Through federation (Single Sign-On), organizations can link their existing corporate identity provider — such as Microsoft Entra (Azure AD) or Google Workspace — to Trimble Identity, allowing users to log in with their familiar corporate credentials.

For a full technical overview of the federation requirements and process, refer to the official Trimble documentation:
Trimble Help – Federation Overview, Requirements and Process

Key Benefits

  • Single password policy enforced by your own IT organization.
  • Multi-Factor Authentication (MFA) managed through your existing corporate infrastructure.
  • Centralized user account management — onboarding and offboarding in one place.
  • Reduced login complexity for end users.

Supported Products & Scope

All Trimble products that use Trimble Identity benefit from this federation, including:

  • Stabicad
  • Trimble Connect
  • Projectsight
  • Field View
  • SketchUp
  • Tekla
  • And more...

Prerequisites

  • The request must be submitted by your IT department, as technical knowledge of identity federation (SAML / OIDC) is required.
  • Administrative access to your organization's identity provider (Microsoft Entra / Azure AD or Google Workspace).
  • Ability to place a TXT record on your DNS zone to prove domain ownership.

Step-by-Step Guide

  1. Review the official Trimble federation documentation to understand all technical requirements before starting:
    Trimble Help – Federation Overview, Requirements and Process
  2. Submit the federation request via the official Google Form:
    Trimble Identity Federation Request Form
    Tip: This form must be completed by an IT administrator with knowledge of identity federation protocols.
  3. Prove domain ownership by placing a TXT record on your DNS zone as requested by Trimble.
  4. Exchange tokens and secrets with Trimble to establish the technical federation connection between your identity provider and Trimble Identity.
  5. Test with a selection of users to verify that Single Sign-On works correctly before a full rollout.
  6. Schedule the full domain migration — once the test is successful, agree on a date and time window with Trimble to migrate the entire domain.
    Tip: Inform all end users in advance that their login screens will look different after the migration. One-time cookie conflicts may also occur during the transition.

⚠️ Important: Impact on Existing Trimble Connect Projects

If the domain name changes as part of this federation process, this will directly affect existing Trimble Connect projects. User identities tied to the old domain may lose access to shared projects. Ensure that project administrators review and update project memberships after the domain migration is completed.

Submit