Issue No. 16 | January 2026 

Welcome to the January 2026 edition of the Core Platform Newsletter. As we kick off the new year, we are focusing on future strategy with the release of our 2026 Platform Engineering OKRs and a video update on the Agentic AI Platform. This month also brings critical announcements, including a Service End of Life notice for the Customer Data Hub and an urgent request for your input on our Platform-Wide API Standards Evaluation.

Action Required: Platform-Wide API Standards Evaluation

To accelerate our support for developers and next-gen AI agentic workflows, we are launching a platform-wide evaluation of Trimble HTTP API Standard adoption. We are calling on all API providers—whether your HTTP API is currently in development or production—to help us build a complete picture by filling out the brief form below. Your participation is a vital step in expanding our platform’s integration capabilities.

Link to survey

Access the survey and more information on Charlie:

📐 2026 Platform Eng OKRs

As we kick off the new year, we are taking a moment to review our 2025 Platform Engineering OKRs and share our vision for 2026. Despite our organization nearly doubling in size following the Cloud Core and AECO merger, our "Aspirational OKR" model—which targets 70% completion to encourage bold, cross-functional innovation—remained highly effective. Looking ahead, we will continue our strong alignment with Trimble’s "Connect and Scale" strategy by retaining our primary objectives for the third year in a row, while introducing a new fourth objective specifically dedicated to the growth and maturation of our organization.

See the post on Charlie for the complete details:

Service End of Life - Customer Data Hub

We are officially retiring the capability to read Account information from the Customer Data Hub (CDH) in H2 2026. This strategic decision addresses critical architectural and security limitations while paving the way for a new Enterprise MDM platform. Product teams must transition to IAM for all authentication and user membership needs, ensuring a more secure, standardized foundation for Trimble’s future Customer & Account 360 solution.

See the announcement on Charlie for more details:

✨ Agentic AI Platform - End of year update

Watch a short end of year status update video on the Agentic AI Platform and the first agents that are going live in Trimble Labs soon.

Access the video of Charlie:

📅 REMINDERS

Trimble Identity: HTTP Strict Transport Security (HSTS)

This is a reminder about the upcoming security enhancement for the Trimble Identity (TID) Staging environment. As previously communicated, TID will implement HTTP Strict Transport Security (HSTS) headers for all HTTPS responses to further strengthen security.

January 22, 2026

Trimble Identity: Mandatory OTP Verification for Non-MFA Users

This is a reminder that the upcoming enhancement to Trimble Identity (TID), which mandates One-Time Passcode (OTP) verification for all integrated applications, will be enabled in Staging on January 19th. This security enhancement will apply to all unfederated TID users that sign in with email and have not yet enabled an alternative MFA method.

Staging - January 19, 5:30 AM UTC

Trimble Identity: User Account ID in SAML Assertions

This is a reminder regarding the upcoming enhancement to Trimble Identity (TID)'s SAML support, which will introduce the user's account_id as a standard attribute within all SAML assertions.

Staging - January 8, 5:30 AM UTC

Production - January 13, 5:30 AM UTC

📅 UPCOMING EVENTS

Trimble Identity: 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

🚀 RELEASE NOTES

Trimble Identity

• Added support for Mutual TLS (mTLS) within the Application Client Credential flow.
• SAML Security Enhancements.
• Enhanced 3rd-Party Identity Support.
• Introduced Refresh Token support for the Token Exchange grant type.
• Updated the user interface and email templates to direct support inquiries to Contact Form instead of email.
• Updated the "f2c" grant type to the standard JWT grant type.
• Enhanced security and session management.
• Compliance Updates.

Identity and Access Management (IAM)

🚀 Release Highlights:

• Expanded Security & Permissions: We’ve doubled the maximum permissions per role (from 50 to 100) and enhanced security checks across Dealer endpoints and Device-related actions.
• Upgraded Invitation Management: You can now configure invitations with a longer Time-To-Live (up to 60 days). We’ve also improved lifecycle tracking, ensuring cancelled invitations immediately remove orphaned identities and expiry dates sync correctly across systems.
• Streamlined Group Logic: Managing complex organizations is easier with new "Cascade Delete" functionality (removing subgroups automatically) and smarter handling of nested groups when removing applications or devices.
• Developer Experience: We’ve improved error reporting for Webhooks and regional data access (404s now include region details). Additionally, RSQL user searches now support case-insensitive wildcard matching.
• Data Integrity & Sync: Significant backend improvements to ensure user data, device profiles, and account statuses sync accurately between IAM, TID, OpenSearch, and the Enterprise Data Warehouse (EDW).

IoT

🛠️ Stability & Quality Improvements:

• System Resilience: We’ve resolved stability issues affecting Event Listener containers and fixed replication time-outs in the Disaster Recovery (DR) manager to ensure clean, reliable data deletion.
  
• Device Operations: Device management is smoother with fixes for legacy device activation (eliminating 500 errors) and improved synchronization for certificate rotation metadata during batch processing.
• API Precision: We have tightened validation logic for License Notifications and Bootstrap Configs. APIs now return accurate error codes for invalid IDs and configurations, eliminating misleading success messages or generic "not found" errors.
• Error Handling: Enhanced the IoT Logs handler to gracefully manage missing trace IDs, ensuring better log consistency without errors

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