Toshiba e-STUDIO (e-BRIDGE Next) scan to email with Microsoft 365: email through Microsoft 365 after Basic auth ends

Short answer: e-BRIDGE Next Series II and III e-STUDIO models have Cloud Authentication for Email (OAuth) from firmware 2100 (Series II) or 1801 (Series III). In TopAccess, set the SMTP Client to Authentication: Application, assign Cloud Authentication for Email and sign in with the sending mailbox. Other models: relay connector.

Deadline: Microsoft 365 turns off SMTP AUTH Basic auth by default at the end of December 2026 – dates and background.

Modern authentication (OAuth) support

Toshiba calls its OAuth feature Cloud Authentication for Email. Toshiba's firmware table lists e-BRIDGE Next Series III models (e-STUDIO2020AC, 2525AC/3025AC/3525AC, 4525AC, 5525AC/6525AC, 6526AC/6527AC/7527AC, 2528A, 5528A/6528A, 7529A/9029A) from firmware 1801, and Series II models (e-STUDIO2010AC, 2515AC/3015AC/3515AC/4515AC/5015AC, 5516AC/6516AC/7516AC, 2518A, 5518A/7518A/8518A, 330AC/400AC) from firmware 2100. The SMTP Client still points at smtp.office365.com port 587, but the password field stays blank: the device signs in once through Microsoft's login page instead. That keeps it working after the Basic auth switch-off. Which Microsoft permissions Toshiba requests is not documented. Toshiba documents no OAuth option for e-BRIDGE Next Series I or older models, and Toshiba Tec's Japanese notice says models without OAuth support should move to another email service.

What you will see when it breaks

Best fix

  1. Open the SMTP Client in TopAccess: Administration → Setup → Network → SMTP Client (Toshiba's A3 guide: Administration → Setup → Email → SMTP Client). smtp.office365.com with a Login Name and password is Basic auth and fails once Microsoft turns it off by default at the end of December 2026. To find every device like this in your tenant, run the free SMTP AUTH sender script.
  2. Check the model and firmware against Toshiba's table: Series III needs firmware 1801 or later, Series II needs 2100 or later. Update older firmware first.
  3. Microsoft 365 admin center → Settings → Org Settings → Modern authentication: confirm Turn on modern authentication for Outlook 2013 for Windows and later is ticked (Toshiba says it is on by default). Keep Authenticated SMTP ticked for the sending mailbox under Users → Active users → Mail → Manage email apps: OAuth logins still use the SMTP AUTH protocol.
  4. In TopAccess (log in as admin), set the SMTP Client: Enable SMTP Client Enable, Enable SSL / TLS Accept all certificates without CA, SMTP Server Address smtp.office365.com, Authentication Application, Login Name the mailbox address, Password blank, Port Number 587.
  5. Click Assignment, select Cloud Authentication for Email, click OK, then Save and OK.
  6. Open the Cloud Authentication for Email link. Type the same address under Account Name, tick Send Email and click Account Registration. Sign in with that mailbox on Microsoft's login page. On the permissions screen, tick Consent on behalf of your organisation if it applies, then click Accept.
  7. Wait for Access was approved. Please continue on the MFP panel. Back in TopAccess, check that the account is registered to send email, then send a test scan.

If it can't do OAuth

  1. No OAuth firmware for your model (for example e-BRIDGE Next Series I)? Create a relay connector that trusts your office's static public IP.
  2. Then set the SMTP Client to Toshiba's direct send values: SMTP Server Address your MX host (for example contoso-com.mail.protection.outlook.com), SSL/TLS STARTTLS, POP Before SMTP Disable, Authentication Disable, Login Name and Password blank, Port Number 25. Click Execute and expect Successfully Connected.
  3. Without the connector this is direct send, which only reaches mailboxes inside your organization (Microsoft Learn). Toshiba also asks for an active, working mailbox address in From Address under Administration → Setup → Email → General Setting.
  4. Stopgap only: an admin can turn Basic auth for SMTP AUTH back on for now. It ends when Microsoft removes it for good; the date is due in the second half of 2027. See the SMTP AUTH change.
OAuth featureCloud Authentication for Email (TopAccess)
Minimum firmwaree-BRIDGE Next Series III: 1801. Series II: 2100. Series I and older: OAuth not documented
TopAccess pathAdministration > Setup > Network > SMTP Client (A3 guide: Administration > Setup > Email > SMTP Client)
SMTP Client for OAuthsmtp.office365.com, port 587, Enable SSL/TLS: Accept all certificates without CA, Authentication: Application, Login Name: mailbox address, Password: blank
AssignmentCloud Authentication for Email, then Account Registration with Send Email ticked
Microsoft 365 sideModern authentication on (Org Settings); Authenticated SMTP on for the sending mailbox
Microsoft permissions requestedNot documented
Relay / direct sendMX host, port 25, SSL/TLS: STARTTLS, Authentication: Disable, no login

Check your domain's SPF and DMARC

A relay sends from your office IP, so it must be in your SPF record.

Several devices to move? The Microsoft 365 SMTP Fix Kit puts every printer, scanner, app and script on one printable guide: decision table, relay connector set-up, per-device steps, a sender worksheet and a checklist.

Get the kit ($19)

Rather have it done for you? I move your devices and apps on Fiverr – relay, Direct Send or OAuth, tested, from $25.

Sources

Did this fix it?

What's still not working?

Paste the bounce message or describe what happens. We read every report and add fixes for new errors.

Other devices and apps