Issue No. 17 | February 2026 

In this edition of the Platform Newsletter, we’re highlighting the production readiness of our Agentic AI Platform and the new Trimble Engine Development Framework for .NET. We also have critical security updates regarding Trimble Identity and mandatory MFA requirements you’ll want to track. Read on for the latest releases, upcoming DR drills, and regional compliance notices.

Agentic AI Platform: Trimble Agent Studio Launching to Private Labs

Trimble Agent Studio (the Agentic AI Platform’s application experience for creating agents) is now production-ready and available to all Trimble employees in staging and production environments.

Our strategy is to enable Trimble, customers, and third-party partners to develop, deploy, and monitor agents and multi-agent systems. To this end, we are inviting an initial group of select, strategic accounts to access Trimble Agent Studio via an upcoming Private Labs release.

If you know of a key account that would like to participate, you can nominate an account using this form.

Check out the full announcement:

Build Smarter, Not Harder

We’re excited to unveil the Trimble Engine Development Framework, a specialized .NET ecosystem designed to get your engines running in the Processing Framework faster than ever before.

It’s a cohesive ecosystem for building standard Processing Framework engines, consisting of high-level SDKs, automated tools, and .NET conventions. Whether you're targeting .NET Standard 2.0 or .NET Core 9, this framework moves you away from manual Python scripts and into a strongly typed, C#-first environment.

Read the announcement and watch the videos:

🚀 File Service - Data Experience Object Type

We are excited to announce that the new File Service - Data Experience Object type and its associated capabilities are now live in the Stage environment.

As we continue to evolve our Data experience management capabilities within File Service, we are releasing this feature as a Preview. This is an invitation for the integrators to get an early look at the functionality, integrate it into your test workflows, and help shape the final version with your feedback.

Read all the details:

Trimble Platform on Charlie

Subscribe to our Charlie channel for the latest Platform news.


🎗️ REMINDERS

Trimble ID: Primary Email Verification Requirement

All native users – with or without multi-factor authentication (MFA) enabled – will be prompted to either verify or update their primary email address during their next log in.

This nudge serves as an account security health check, ensuring users can access their listed email for future security prompts and notifications. Users will be able to skip this prompt, ensuring they don’t experience account lockout.

Staging - February 12, 2026

Production - February 17, 2026

Trimble ID:  Mandatory OTP Verification for Non-MFA Users

Trimble ID (TID) will enable two-step verification (2SV) for all unfederated users, in response to Cyber’s 2025 Security mandate. TID will enable one-time passcode (OTP) sign-in verification for all integrated applications in Production on March 31, 2026. This security enhancement will apply to all unfederated Trimble Identity users that sign in with email and have not yet enabled an MFA method

Production - March 31, 5:30 AM UTC


📅 UPCOMING EVENTS

Trimble ID: [MFA] Progressive Security Enrollment

Trimble ID (TID) is introducing a system of "smart nudges" aimed at encouraging all native TID users to adopt stronger multi-factor authentication (MFA) methods (e.g., passkeys, an authenticator app, and secondary email) during sign-in. This initiative is part of a broader enhancement to the Trimble ID security framework.

Staging - February 12, 5:30 AM UTC

Production - February 17, 5:30 AM UTC

Trimble ID: Security Update to Email Verification Claims

To enhance security and address vulnerabilities related to identity spoofing, Trimble Identity (TID) is updating its email verification logic. Previously, TID defaulted the email_verified claim to true for all social federation (Microsoft Azure, Google, Apple) logins, based on implicit trust in the provider's email claim. With this update, Trimble Identity will implement a more robust mechanism to accurately determine the email_verified claim's value.

Staging - February 13, 5:30 AM UTC

Production - March 13, 5:30 AM UTC

Trimble ID: Enhanced Security for SAML Authentication Paths

We have enhanced security for all authentication paths starting with /saml/. This upgrade effectively detects and manages unusual traffic patterns instantly, ensuring our service remains available. By handling unexpected traffic surges behind the scenes, we strengthen protection against automated disruptions while maintaining a smooth experience for all users. These improvements work automatically, so no changes are needed in your current workflow.

Staging - February 12, 5:30 AM UTC

Production - February 17, 5:30 AM UTC

IAM Provenance Data Update - CDH Identifier as Source System

IAM is implementing  a  foundational change to how it manages account provenance data. IAM will refer to the CDH original system reference as the Source System, updating the provenance data based on the source of truth claimed by Digital Transformation (DX). There is no planned change to how data is discovered via API at this time, this update is a change in how we will internally identify the source system.

Production - March

IAM: Geoisolation 

As part of our commitment to enhancing data security and compliance, we are implementing geoisolation within our Identity and Access Management (IAM) product. This change is scheduled to take effect in the next quarter, and we want to ensure you are well-prepared for this transition.

All integrations must be updated to use the correct regional endpoints by August 29th, 2026.

Production - April 1

IoT: Nginx Patching

The NetOps team will be patching the Nginx instances in stage and production. TCP/UDP comms devices are likely to expect five minutes of downtime. No message loss is expected as queued messages from devices  would be processed once the service is operational.

Staging - February 12, 5:30 AM - 7:30 AM UTC

Production (Europe) - February 12, 1:30 AM - 3:30 AM UTC

Production (North America) - February 12, 5:30 AM - 7:30 AM UTC

IoT: Ag Access to DID

Beginning April 1, 2026 AG devices will no longer be able to make calls to DID.

Customer Data Hub (CDH) - End of Life

Reading account information from Customer Data Hub (CDH) will be officially retired in H2 2026. Teams will need to migrate from CDH to IAM for fetching any account-related information.

Processing Framework - Maintenance Window Release

On Mar 14, 2026, a Maintenance Window will be scheduled in order to perform upgrades to the Trimble Platform Processing Framework service infrastructure. The outage period should be minimal, at less than 5 minutes. Clients may experience degraded performance for up to 30 minutes, with slower response times.

Production - March 14, 4:00 PM - 4:30 PM UTC


🧪 DISASTER RECOVERY

TAM: Disaster Recovery Drill in Staging - Partial Downtime

The TAM DR Drill for transitioning from Primary to Secondary in the Staging environment is scheduled for March 04, 2026 - 05:30 UTC to 10:30 UTC, with a failover to secondary at 05:30 UTC  and failback to primary at 09:30 UTC. This activity may cause partial downtime for integrators during failover and failback.

Staging - March 4, 5:30 AM - 10:30 AM UTC

Iot: Disaster Recovery Drill in Staging

IoT DR Drill for transitioning from Primary to Secondary in the Staging environment is scheduled for February 26, 2026 - 04:30 UTC to 8:30 UTC, with a rollback to Primary. This activity may cause partial downtime for integrators.

Staging - February 26, 5:00 AM - 8:30 AM UTC


🚀 RELEASE NOTES

Trimble Identity

This month, our team focused heavily on strengthening security infrastructure, streamlining administrative workflows, and improving user accessibility across our global environments. Key highlights for January include:

  • Security & Compliance: We have expanded mTLS support for Token Exchange grant types and implemented HSTS headers in our staging environment to enforce encrypted browser connections. Additionally, legal consent copy and regional mTLS domain names have been updated to ensure global compliance.
  • User Experience & Accessibility: To reduce friction, we re-introduced the "Skip Once" option for Email OTP and optimized mobile input fields to meet WCAG accessibility standards.
  • Admin & Infrastructure: A new bulk user creation tool now supports large-scale migrations via CSV. We also rolled out significant backend improvements, including enhanced SAML support, improved logging for email changes, and synchronization groundwork between TID and IAM modules.

IoT

Profiles Fallback for Device Authorization and Lookup: The IoT service now enhances reliability by automatically falling back to using Profiles during device authorization and lookup when IAM live sync experiences delays or failures, ensuring continuous functionality and seamless operation.

Platform Support

Service Requests

Integrators with questions regarding their Platform adoption or retention (e.g., related to compliance, configuration, data, training, or reporting) should submit a generic request.

Incident Reporting

Integrators should report incidents when they observe a degradation or major outage of a Platform Service that affects their business operations. If the Impacted service is not listed, then please contact the Impacted Services point of contact(s) directly.



Need to join the mailing list for this newsletter or know someone who does? Let us know by filling out this very short form: