MAS 9.2 Is Here: What Maximo Teams Need to Know Before Upgrading

IBM dropped MAS 9.2 on June 25, 2026, and it is not just another feature release. It arrives at a moment when every organization still running Maximo Asset Management 7.6.1.x is staring down a hard deadline: April 30, 2027. After that date, dual support ends. EAM 7.6.1.x usage rights expire, and continued use puts you out of compliance. No more fixes. No more security patches. The clock is ticking.

MAS 9.2 is the release that IBM wants you to land on. It consolidates years of incremental improvements from the 9.0 and 9.1 lines, introduces a new Feature Channel delivery model, and makes architectural changes that affect how administrators manage users, email, reports, and the platform itself. This article breaks down what is new, what is changing under the hood, and how to plan your migration whether you are coming from 7.6, 8.x, or an earlier MAS version.

The Feature Channel: Continuous Delivery Comes to MAS

The biggest operational change in MAS 9.2 is not a feature. It is the delivery model. IBM has introduced the Feature Channel, a monthly capability drop that delivers new functionality ahead of the next major release. The first Feature Channel drop shipped alongside MAS 9.2 on June 25, 2026, with prior monthly drops having been available since February 2026 for early adopters.

This is a significant departure from the traditional MAS release cadence. Historically, MAS followed a roughly annual major release cycle (9.0, 9.1, 9.2) with periodic fix packs in between. The Feature Channel changes the equation: organizations can now evaluate and adopt new capabilities incrementally rather than waiting for a major version boundary.

Here is how the Feature Channel release history looks so far:

The practical implication is that the old model of "wait for the next major version, then plan a big-bang upgrade" is being replaced by a continuous evaluation cycle. Teams that subscribe to the Feature Channel can test new capabilities in non-production environments, build internal readiness, and adopt features incrementally. This reduces the risk and disruption associated with traditional major-version upgrades.

However, the Feature Channel is not a replacement for production fix packs. IBM continues to ship cumulative patches for the 9.0 and 9.1 lines. As of June 25, 2026, MAS Core 9.0 is at patch level 9.0.27, MAS Core 9.1 is at 9.1.19, and MAS Core 8.10 is at 8.10.37. Organizations on stable production environments should continue applying fix packs on their current version track while using the Feature Channel in sandbox or development environments to prepare for 9.2 adoption.

User Management Moves Entirely Into Manage

One of the most impactful architectural changes in MAS 9.2 is the consolidation of user management into Maximo Manage. In previous MAS versions, user records existed in two places: the MAS Core identity layer and within Manage itself. This dual-registration model created synchronization headaches. A user might exist in MAS Core but lack a corresponding Manage record, or vice versa. Administrators had to maintain two separate user directories, and discrepancies between them were a common source of support tickets.

In MAS 9.2, the MAS Core version of the user record goes away entirely. Manage becomes the single source of truth for all user identity, role assignments, and permissions. This has several downstream effects:

Identity providers are now managed within Manage. In previous versions, MAS Core handled SAML/OIDC provider configuration. In 9.2, Manage knows about all your identity providers directly. This simplifies the authentication flow and eliminates the need to synchronize provider configuration between layers.

Communication templates drive all email notifications. Previously, MAS Core had its own notification framework for system-level events (password resets, account provisioning). In 9.2, everything flows through Manage's communication template engine. This means you get the full power of substitution variables, conditional logic, and automation script triggers for every email the system sends, not just work-order notifications.

Automation scripts can chain through the entire suite. Because user context and communication templates are unified under Manage, an automation script triggered by a work order can now fire a communication template that references user attributes from the identity provider, triggers an API call to an external system, and logs the result back to the work order. The integration surface is cleaner and more powerful.

For teams migrating from 7.6, this is actually a simplification. In 7.6, user management was entirely within the Maximo database. The MAS 8.x/9.0 model of dual user records was an intermediate step that added complexity. MAS 9.2 brings it back to a single-source model, but with the added benefit of modern identity provider integration.

For teams already on MAS 9.0 or 9.1, the migration to 9.2 requires careful planning around user record consolidation. You will need to audit your existing MAS Core users against Manage users, resolve any discrepancies, and ensure that role assignments and security groups are correctly mapped before the MAS Core user record is decommissioned.

SMTP, OAuth, and Scheduled Reports: The Communication Stack Gets Real

Email in MAS has historically been a pain point. SMTP relay configuration was brittle. OAuth 2.0 support for modern email services (Microsoft 365, Google Workspace) was absent or required workarounds. Scheduled reports always sent from the user who created the schedule, which meant that when that user left the organization, reports broke. Administrators built elaborate automation scripts to work around these limitations.

MAS 9.2 addresses all three issues.

SMTP email queuing and OAuth support. MAS 9.2 introduces native OAuth 2.0 authentication for SMTP. If your organization uses Microsoft 365 or Google Workspace, you can now configure MAS to authenticate directly with the email provider using OAuth tokens instead of basic authentication. This is critical because both Microsoft and Google have been deprecating basic authentication across their platforms. The new SMTP implementation also includes email queuing, which improves reliability by buffering outbound messages and retrying on failure rather than dropping them silently.

Scheduled report send-from configuration. In MAS 9.2, administrators can configure the "send from" address on scheduled reports at an organizational level. Reports no longer need to be sent as the user who created the schedule. This means you can configure reports to send from a generic address like maximo-reports@yourcompany.com, and they will continue working regardless of personnel changes. For organizations that built complex automation to proxy report execution through a service account (as many did), this feature eliminates a significant maintenance burden.

Preventive maintenance date control. While not strictly a communication feature, MAS 9.2 adds the ability to control PM generation dates at both the organizational level and the individual PM level. You can now configure a PM to generate on the last day of the month, and the system will calculate the correct date regardless of month length. This was a long-requested feature that previously required custom cron task logic or automation scripts.

Here is a practical example of the new OAuth SMTP configuration pattern:

# MAS 9.2 SMTP OAuth configuration (conceptual)
smtp:
  host: smtp.office365.com
  port: 587
  starttls: true
  auth:
    mechanism: oauth2
    tenant_id: "your-tenant-id"
    client_id: "your-client-id"
    scope: "https://outlook.office365.com/.default"
  queue:
    enabled: true
    max_retries: 3
    retry_interval_seconds: 300

Operational Dashboards, Role-Based Applications, and the Mobile Story

MAS 9.2 continues to invest in Operational Dashboards as the successor to Start Centers. While Start Centers are not being removed, the writing is on the wall: Operational Dashboards are the strategic direction for user-facing landing pages and KPI displays.

Key improvements in 9.2 include:

Custom actions that call automation scripts. Operational Dashboards can now include custom action buttons that trigger automation scripts. For example, a dashboard showing high-priority work orders could include a "Take Ownership" button that assigns the selected work orders to the current user via an automation script. This bridges the gap between passive dashboards and active work management.

Single work queue replacing result sets. The single work queue widget can now replace a result set portlet, giving users a more interactive way to view and act on records directly from the dashboard. This is particularly useful for supervisor dashboards where users need to triage work without navigating into individual applications.

Role-based application improvements. Role-based applications (RBAs) continue to mature. In 9.2, RBAs gain attachment support, which was a notable gap in earlier versions. Field technicians using a role-based application can now attach photos, documents, and other files directly to work orders and inspections without switching to the full Manage application.

Maximo Mobile QR-code setup. Mobile device provisioning gets a quality-of-life improvement with QR-code based setup. Instead of manually entering server URLs and credentials on each device, administrators can generate a QR code that technicians scan to configure their mobile app. This reduces deployment friction for large field teams.

Mobile dashboards and Visual Inspection. Maximo Mobile in 9.2 includes dashboard capabilities and integration with Maximo Visual Inspection for on-device AI inference. A technician can point their phone camera at a piece of equipment and get an instant AI-based assessment of its condition, with results fed directly into the work order.

The EAM 7.6.1.x Migration Imperative

Let us talk about the elephant in the room. IBM has set April 30, 2027, as the end of dual support for EAM 7.6.1.x. After that date:

• EAM 7.6.1.x usage rights expire under MAS license terms
• No further fixes or security patches will be released
• Continued use of EAM 7.6.1.x will be out of compliance with subscription terms
• Extended support for EAM 7.6.1.x ended on September 30, 2026

If you are still on EAM 7.6.1.x, you have less than 10 months to complete your migration to MAS. This is not a "nice to have" timeline. It is a compliance deadline with contractual implications.

The migration path depends on your current deployment model:

On-premises WebSphere/DB2 to MAS on OpenShift. This is the most common migration pattern. It involves standing up a Red Hat OpenShift cluster, deploying MAS, migrating your database (typically to Db2 or PostgreSQL on the cluster), and re-implementing your customizations as automation scripts or configuration changes. The database migration alone can take weeks of planning and testing, especially if you have custom tables, views, or stored procedures.

On-premises to MAS SaaS. IBM now offers MAS as a fully managed SaaS offering. This eliminates the infrastructure burden but requires careful evaluation of integration points, data residency requirements, and customization compatibility. Not all customizations that work on self-managed MAS will work in the SaaS environment.

MAS 8.x to MAS 9.2. If you are already on MAS 8.x, the migration to 9.2 is more straightforward but still requires planning. MAS 8.10 is at patch level 8.10.37 as of April 2026, and IBM continues to ship fixes. However, the Feature Channel and user management changes in 9.2 mean you should treat this as a significant upgrade rather than a simple patch.

Here is a recommended migration planning timeline:

Total: 26-46 weeks. If you start in July 2026, you have roughly 40 weeks until the April 2027 deadline. That is tight but achievable if you start now.

Practical Implications

Start your migration planning this quarter. If you are on EAM 7.6.1.x and have not started, you are already behind. The organizations that will have the smoothest migrations are those that began planning in early 2026. If you are just starting now, prioritize: (1) inventory your customizations, (2) stand up a sandbox MAS environment, and (3) begin database migration testing.

Evaluate the Feature Channel in a non-production environment. Even if you are not ready to adopt MAS 9.2 in production, subscribe to the Feature Channel in your development or sandbox environment. This gives your team hands-on experience with the new capabilities and helps you build internal readiness without disrupting production operations.

Audit your user records now. The user management consolidation in 9.2 means you need a clean user directory. Start auditing your MAS Core users against your Manage users. Identify discrepancies. Clean up orphaned accounts. Document your security group assignments. The cleaner your user data is before migration, the smoother the 9.2 transition will be.

Plan your SMTP migration to OAuth. If you are using basic authentication for SMTP, start planning your migration to OAuth 2.0. Work with your email administration team to register the necessary application credentials in Microsoft Entra ID or Google Cloud Console. Test the OAuth configuration in your sandbox environment before rolling it out to production.

Do not underestimate the OpenShift learning curve. If your team has been managing WebSphere on Windows or Linux, OpenShift is a different world. Invest in training. Consider engaging an IBM business partner with OpenShift expertise. The MAS application layer is well-documented, but the underlying platform requires a different skill set.

Bottom Line

MAS 9.2 is a meaningful release that addresses long-standing pain points in user management, email configuration, and report scheduling while introducing a continuous delivery model through the Feature Channel. For organizations still on EAM 7.6.1.x, the April 30, 2027 dual-support deadline makes this release strategically important: it is the version you should target for your migration.

The Feature Channel changes how teams should think about upgrades. Instead of planning a single big-bang migration every few years, adopt a continuous evaluation model. Subscribe to the Feature Channel in non-production environments. Test new capabilities as they arrive. Build organizational readiness incrementally.

The user management consolidation is the most impactful architectural change in this release. It simplifies the identity model but requires careful planning for teams migrating from MAS 9.0 or 9.1. Audit your user records early.

The SMTP OAuth support and scheduled report improvements eliminate two of the most common sources of custom automation in MAS environments. If you have built workarounds for these, 9.2 lets you retire that technical debt.

The clock is ticking for EAM 7.6.1.x. Start your migration planning now. MAS 9.2 is the target. The path is well-documented, the partner ecosystem is experienced, and the platform is mature. The biggest risk is not the technology. It is waiting too long to start.