Marketo Measure needs a Salesforce access check before the JWT deadline

Adobe's 7 November notice says Marketo Measure customers should complete Salesforce connected-app settings by 12 November 2026 for a move to JWT-based authentication. The app still appears as Bizible in Salesforce. A working sync today does not establish that the integration user will be allowed to obtain a new token after the change.

Find the integration user and app

Ask the Salesforce admin to identify the Measure sync user, the Bizible connected app, its installation state, and its current access policy. Salesforce's connected-app guidance explains how an installed app can be governed through permitted users and permission sets. Do not create a replacement app merely because Bizible is not immediately visible; Adobe's notice directs administrators to Support when the expected entry or action is missing.

Stage the access change as one controlled operation

Adobe's notice calls for the app to be installed where needed, an admin-approved-user policy, and a permission set assigned to the Measure sync user. These are security settings. Record existing access, identify other legitimate users of the app, then have the Salesforce owner perform the documented steps. A policy changed before assignment may cut off access. Treat screenshots as examples because Salesforce menus and org configuration vary.

Prove the connection after the change

Check the Measure connection state and a recent sync, then preserve the time and error details if authentication fails. Adobe's connection guide provides the product context; it does not replace the newer deadline notice. Escalate missing Bizible access or an unexpected login path to Adobe and Salesforce administrators before the announced date.

Adovo’s view

Authentication migrations fail at the handoff between product owner and identity owner. Make one named person accountable for the sync user, policy and proof of connection. A deadline is only useful when it ends with a tested token path.