Major Marketo Changes Are Here: What You Need to Know and Do Now

If you’re a Marketo Engage user, there’s a lot changing over the next few months—and it’s critical you prepare now to avoid disruption.

Adobe has announced a series of deprecations and transitions that will affect how users access Marketo, authenticate API calls, and manage integrations. At RightWave, we’ve already started helping our clients adapt to these changes so they’re not caught off guard.

Here’s a quick breakdown of what’s changing—and our take on what to do about it:

1. Marketo Engage Identity Is Going Away

• What’s happening: Starting August 2025, Adobe will begin phasing out support for the legacy Marketo Engage Identity login (login.marketo.com). By September 30, 2025, all users must transition to Adobe Identity.

• RightWave POV: This is not just a UI change—Adobe Identity introduces new admin controls, user provisioning, and access governance. We recommend starting the transition early to ensure role-based access, SSO, and admin workflows are all configured correctly.

2. IP-Based Login Restrictions Are Being Deprecated

• What’s happening: Support ends July 30, 2025, and is replaced by location-based access control via the Adobe Admin Console (targeted for August release).

• RightWave POV: If your compliance team relies on IP-based restrictions, now’s the time to evaluate the Adobe Admin Console’s location controls. Expect a learning curve and plan a phased rollout with stakeholder input from IT/security teams.

3. SSO for Marketo Identity Is Being Sunset

• What’s happening: Marketo Identity SSO support ends July 30, 2025. Users must move to Adobe Identity SSO, which requires fresh setup via the Adobe Admin Console.

• RightWave POV: We advise customers not to treat this as a “lift and shift.” Re-audit your SSO configuration, user groups, and MFA policies while you’re at it. Our MOPS and IT teams can help with seamless migration and testing.

4. access_token in REST API Calls Is Deprecated

• What’s happening: The access_token as a query parameter in REST API calls will be deprecated after October 31, 2025. Authentication must now use the Authorization header instead.

• RightWave POV: This is a small change with big consequences if missed. We’ve seen clients with dozens of legacy API scripts that need to be updated. Time to audit every integration and refactor your calls using the new method.

5. SOAP API Is Being Retired

• What’s happening: Support for the SOAP API ends October 31, 2025.

• RightWave POV: If you’re still using SOAP, you’re overdue for modernization. Migrating to REST isn’t just about compliance—it’s about performance, scalability, and unlocking newer features. We can help rewrite and test your integrations to minimize downtime.

🔧 What Should You Do Now?

RightWave recommends a 3-phase response:

1. Assess – Run an audit of current users, API integrations, and access protocols.

2. Plan – Create a migration roadmap for identity, SSO, and API transitions.

3. Act – Begin updates, testing, and training your teams—well before the cut-off dates.

💡 Need Help Navigating the Transition?

RightWave has helped dozens of enterprise clients through Marketo transitions, from identity and SSO to full API rewrites. Whether you’re migrating from SOAP or ensuring Adobe Identity is rolled out across global teams, our experts are ready to help.

Let’s connect. We can assess your current setup and build a transition plan tailored to your stack and scale.

Reference –  https://experienceleague.adobe.com/en/docs/marketo/using/release-notes/current