MAS 9.2 Is Here: What Actually Changed and What Maximo Teams Need to Do About It

IBM shipped Maximo Application Suite 9.2 on June 25, 2026. If you have been tracking the monthly Feature Channel drops since the April 2026 preview, you already know this was not a surprise. But the scope of what landed is worth a careful look. MAS 9.2 is not a minor increment. It touches MAS Core, Manage, Monitor, Health, Predict, Optimizer, Mobile, Visual Inspection, AI Service, Assist, Collaborate, and Real Estate and Facilities, all in a single coordinated release window.

For teams running MAS 9.0 or 9.1, the question is not whether to upgrade. It is when, how, and what breaks along the way. This article walks through what actually shipped, what changed under the hood, and what you need to plan for before you touch your production environment.

The release cadence IBM has settled into is worth understanding first. MAS now ships a new major version roughly every June: 9.0 in June 2024, 9.1 in June 2025, and 9.2 in June 2026. Between major releases, monthly Feature Channel drops deliver incremental capabilities that eventually roll into the next major version. This means the June 2026 Feature Channel and MAS 9.2.0 are effectively the same thing for most components. If you have been applying Feature Channel updates monthly, you have already seen much of what 9.2 contains. If you have been holding at a fixed release, the delta is larger.

What Shipped: The Full Component Matrix

The IBM support page for MAS releases (Reference #7277376 for MAS Core 9.2.0) documents the full matrix. Here is what landed on June 25:

MAS Core 9.2.0 with the June Feature Channel. This is the platform layer: authentication, SSO, user and role management, AppPoints license administration, workspace management, security services, API and integration framework, and tenant management. Core also picked up OAuth support for SMTP, a change that was backported to 9.1 and 9.0 in their respective June fix packs (9.1.19 and 9.0.27).

Manage 9.2.0 with the June Feature Channel. This is the containerized evolution of Maximo Asset Management 7.6. The big story here is the continued migration away from classic applications toward role-based applications. The classic User application is effectively deprecated in 9.2: the user record version goes away entirely, and all user management moves to the newer User application. Communication templates now drive all notification workflows, replacing the older email configuration approach.

Monitor/IoT 9.2.0 with the June Feature Channel. Monitor continues to receive monthly updates, with the April 2026 Feature Channel (Reference #7271136) having already delivered significant enhancements that rolled into 9.2.

Health 9.2.0 with the June Feature Channel. Health scoring, failure risk indicators, and replacement planning all received updates. The 9.0 track also got Health 9.0.27 on the same day.

Predict 9.2.0 with the June Feature Channel. AI-powered failure forecasting with updated models and improved integration with Health and Monitor data pipelines.

Maximo Optimizer 9.2.0 with the June Feature Channel. Maintenance scheduling optimization with new what-if analysis capabilities and conversational scheduling interfaces.

Maximo Visual Inspection 9.2.0 with the June Feature Channel. Local inference on mobile devices is the headline feature here, enabling AI-based visual inspection without requiring constant connectivity.

AI Service 9.2.0 with the June Feature Channel. This is where the agentic AI capabilities land: Condition Insight, RCM Advisor (coming soon), Smart Alerts, and Work Order Automation.

Assist 9.2.0, Collaborate 9.2.0, and Real Estate and Facilities 9.2.0 all shipped with their own June Feature Channel updates.

For teams still on MAS 9.0, IBM also shipped 9.0.27 (Core), 9.0.22 (Monitor), 9.0.27 (Health), 9.0.16 (Predict), 9.0.24 (Optimizer), and 9.0.18 (Assist) on the same day. The 9.0 track is clearly still supported, but the feature gap is widening.

The Feature Channel Model: How We Got Here

The Feature Channel is worth understanding because it changes how teams should think about upgrade planning. Instead of waiting 12 months for a major release, organizations can adopt capabilities incrementally. The April 2026 Feature Channel (MAS Core Reference #7270979) delivered a substantial set of updates that became part of the 9.2 baseline. The March 2026 Feature Channel (Reference #7267467) did the same.

For teams that adopted the Feature Channel model early, the 9.2 upgrade is a smaller step. For teams that stayed on fixed releases, the jump is larger and riskier. This is not a theoretical distinction. Naviam's analysis of MAS 9.2, published on June 22, makes the case that 9.2 may be the inflection point where the value of moving to role-based applications finally outweighs the cost of staying on classic applications. If you have been deferring that migration, 9.2 is the release that makes deferral harder to justify.

The Operational Dashboard is the most visible example. In 9.2, it takes a significant step forward with Work Queue charting, maps, custom actions, and a Bulletin Board card. These are not cosmetic changes. They represent a shift in how users interact with Maximo: from navigating to applications and running queries, to landing on a personalized dashboard that surfaces what they need. Start Centers are not going away, but the investment direction is clear.

OAuth for SMTP: A Small Change with Big Implications

One of the most practically significant changes in MAS 9.2 is OAuth support for SMTP. This was backported to 9.1.19 and 9.0.27, which tells you how important IBM considers it. Microsoft 365 and Google Workspace have been tightening authentication requirements for SMTP relay. Basic authentication is deprecated or already blocked in many tenant configurations. Organizations that relied on username/password SMTP authentication were facing a hard deadline.

The new OAuth support works at two levels. At the Manage level, you configure an OAuth client in the Endpoints application, then specify which OAuth client to use via a system property. At the suite level, MAS Core can now handle OAuth for SMTP independently of Manage. This means email notifications from MAS itself (password resets, license notifications) can use modern authentication even if your Manage instance has not been reconfigured yet.

The configuration pattern looks like this:

1. Register an application in Azure AD / Google Cloud Console
2. Capture the client ID, client secret, and tenant ID
3. In Manage: Endpoints application > New OAuth Client
4. Set system property mxe.smtp.oauth.client to the client name
5. In MAS Core: Suite Administration > SMTP Settings > OAuth

The practical implication is that organizations which had been running SMTP relays or maintaining legacy Exchange configurations to work around the authentication gap can now retire those workarounds. This is a compliance and security win, not just a convenience feature.

User Management: The Classic User Application Goes Away

In MAS 9.2, the version of the user record in the classic Users application goes away entirely. This has been telegraphed for multiple releases. MAS 9.1 already pushed administrators toward the newer User application, expanding it with additional User and Security Group capabilities. MAS 9.2 completes that migration.

What this means in practice:

• All user management must happen through the role-based User application
• Any automation scripts or integrations that reference the classic user record structure need review
• Security group assignments, AppPoint calculations, and user provisioning workflows that relied on the classic application need to be migrated

The newer User application is approaching functional parity with the classic version, and it receives enhancements that are not backported. For organizations managing AppPoint calculations and user access, the classic User application should no longer be treated as the default. If you have customizations built on the classic user record, now is the time to inventory them and plan the migration.

Communication Templates Replace Email Configuration

Another architectural shift in 9.2: all notification workflows are now triggered from communication templates. The older email configuration approach, where SMTP settings and email templates were configured separately, is replaced by a unified communication template framework. This is not just a UI change. It means that every notification, every workflow email, and every scheduled report distribution goes through the same templating engine.

The practical benefit is consistency. Instead of maintaining email templates in one place, workflow notifications in another, and scheduled report distributions in a third, everything converges on communication templates. The trade-off is that teams need to migrate their existing email configurations to the new model. For organizations with hundreds of custom notifications, this is a non-trivial migration task.

Operational Dashboards vs. Start Centers: The Investment Direction

The Operational Dashboard in MAS 9.2 is not just a prettier Start Center. It is a fundamentally different approach to the user experience. Start Centers are per-user, query-driven, and relatively static. Operational Dashboards are role-based, API-driven, and dynamic. They support:

• Work Queue charting: visualize work backlog by status, priority, assignment
• Maps: geospatial view of work orders, assets, and field technicians
• Custom actions: launch workflows directly from dashboard cards
• Bulletin Board card: broadcast announcements to user groups
• Security-based access: different dashboard tabs for different security groups
• Configurable dashboard tabs: administrators define what each role sees

The key architectural difference is that Operational Dashboards are built on the same API layer that powers the role-based applications. This means they can surface data from across the suite (Manage, Health, Monitor, Mobile) in a single view. Start Centers are limited to Manage data. For organizations that have adopted multiple MAS components, the Operational Dashboard is the integration point that Start Centers never were.

AppPoints and Licensing: What Changed

MAS 9.2 does not fundamentally change the AppPoints licensing model, but it does change how AppPoints are consumed. The migration to role-based applications means that user access patterns are different. A user who previously needed access to the classic Work Order Tracking application might now access the same functionality through a role-based application that consumes AppPoints differently.

The standard AppPoints tiers remain:

What changed is that the newer applications are more granular about what constitutes "access." A user who only needs to view work orders in a dashboard may consume fewer AppPoints than a user who needs full create/update/delete access in the classic application. This makes AppPoints planning more nuanced, but also more efficient if you design your security groups carefully.

Upgrade Planning: What to Do Before You Touch Production

The upgrade from MAS 9.0 or 9.1 to 9.2 follows the same pattern as previous major version upgrades, but the scope of changes in 9.2 makes preparation more important than usual. Here is a practical checklist:

1. Inventory your customizations. Every automation script, every BIRT report, every MIF integration, every workflow modification. The classic User application deprecation alone means that any customization touching user records needs review.

2. Audit your communication templates. If you have been using the older email configuration approach, you need to migrate to communication templates before or during the upgrade. This is not optional in 9.2.

3. Review your security groups. The AppPoints consumption model changes when users move from classic to role-based applications. A security group that was correctly configured for 9.1 may consume more or fewer AppPoints in 9.2.

4. Test OAuth SMTP in non-production first. If you are moving from basic authentication to OAuth for SMTP, test the configuration in a non-production environment before touching production. The Azure AD / Google Workspace registration process has its own lead time.

5. Plan your Operational Dashboard rollout. Do not just turn on Operational Dashboards and hope users figure it out. Design the dashboards for each role, configure the cards, and run user acceptance testing before production cutover.

6. Run Integrity Checker. This is standard for any Maximo upgrade, but it bears repeating. Run Integrity Checker in report mode, fix every error, then run it again in activation mode before starting the database upgrade.

7. Clone and rehearse. The safest approach is to clone your production database, build a non-production MAS 9.2 environment, run the full upgrade, document every error, fix the root causes, and only then repeat the process for production.

Practical Implications

For teams on MAS 9.0: the feature gap between 9.0 and 9.2 is now substantial. You are missing OAuth SMTP, the Operational Dashboard enhancements, the role-based application improvements, and the AI capabilities in Condition Insight and Smart Alerts. The 9.0 track is still receiving fix packs (9.0.27 shipped alongside 9.2), but the investment is clearly in 9.2 and beyond. Start planning your upgrade now, even if execution is months away.

For teams on MAS 9.1: the jump to 9.2 is smaller, especially if you have been applying Feature Channel updates. The main migration tasks are the classic User application deprecation and the communication template migration. If you have already moved users to the newer User application and adopted communication templates, the 9.2 upgrade may be relatively straightforward.

For teams still on Maximo 7.6: MAS 9.2 is not your first step. You need to go through the 7.6 to MAS migration, which is a platform transformation, not just an application upgrade. The 7.6 to MAS 9 upgrade checklist published by Avinash Kumar on the IBM Community (May 30, 2026) is the best starting point. The key insight from that guide: start with readiness assessment, not with installation. Clone your database, validate it, build a non-production MAS environment, activate the upgrade, document every error, and only then repeat for production.

Bottom Line

MAS 9.2 is the most feature-rich release since the MAS platform launched. The headline items (OAuth SMTP, Operational Dashboards, role-based application maturity, AI capabilities) are individually significant. Taken together, they represent a platform that is increasingly difficult to justify staying on older versions of. The classic User application deprecation is the clearest signal yet that IBM is moving forward and expects customers to move with them.

The upgrade itself is not technically harder than previous major version upgrades. But the scope of changes means that preparation matters more. Teams that inventory their customizations, audit their communication templates, review their security groups, and rehearse the upgrade in non-production will have a smooth transition. Teams that skip preparation will discover the gaps in production, and that is a much more expensive way to learn.

Sources

• IBM Maximo Application Suite Releases Information: https://www.ibm.com/support/pages/maximo-application-suite-releases-information-0
• IBM MAS 9.2 Announcement (June 25, 2026): https://www.ibm.com/new/announcements/introducing-maximo-application-suite-9-2
• Naviam: "Is MAS 9.2 the Right Time to Move Beyond Classic Maximo Applications?" (June 22, 2026): https://www.naviam.io/resources/blog/is-mas-9-2-the-right-time-to-move-beyond-classic-maximo-applications
• Avinash Kumar: "IBM Maximo 7.6 to MAS 9 Upgrade Checklist" (May 30, 2026): https://community.ibm.com/community/user/blogs/avinash-kumar/2026/05/30/ibm-maximo-76-to-mas-9-upgrade-checklist
• Naviam: "Ep. 1 | IBM Maximo Application Suite 9.2: What Maximo Teams Need to Know" (June 25, 2026): https://www.youtube.com/watch?v=K99fytkRa3Y
• Chris Winston: "Maximo 7.6 to MAS 9.x Upgrade Guide" (June 21, 2026): https://www.linkedin.com/posts/arhagba_maximo-openshift-activity-7474429099139080193-icJR