Questo browser non è più supportato.
Esegui l'aggiornamento a Microsoft Edge per sfruttare i vantaggi di funzionalità più recenti, aggiornamenti della sicurezza e supporto tecnico.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(236.8, 71%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGI%3C/text%3E%3C/svg%3E)
Hello, I’m having issues enabling OAuth2 SMTP authentication on two Ricoh devices (SP 330SFN and M 320SE), both updated to the latest firmware that supports Exchange Online OAuth.
When I start the OAuth registration,
the printer generates a device code, and the Microsoft 365 sign‑in flow works normally: I enter the code, log in, approve the “Email App” access, and Microsoft confirms the sign‑in is completed.
However, the printer never finalizes the registration. It remains stuck in an infinite loading loop on the “Sign in…” page. Occasionally, the final OAuth screen appears for a second, but the registration is not saved.
I have tested:
The result is always the same.
Any guidance or indications would be very helpful. Thank you.
Una solida piattaforma di posta elettronica, calendario e collaborazione sviluppata da Microsoft, progettata per la gestione dei dati e delle comunicazioni a livello aziendale.Argomenti vari che non rientrano in categorie specifiche.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(220.8, 92%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
Hello Gabriele Icardi,
Since the sign-in and consent complete successfully on the Microsoft side, the issue is most likely happening when the printer tries to finalize the OAuth registration.
Given that you’ve already tested across different accounts, tenants, and roles, this doesn’t look user- or tenant-related.
A few things you can check:
login.microsoftonline.com. Firewalls or proxies can block the final token exchange.If all of the above looks fine, this is likely related to how the device handles the final step of the OAuth flow. We’ve seen cases where the device code flow completes, but the device fails to retrieve or store the token.
At that point, reviewing device logs (if available) or checking with Ricoh support would help confirm if this is a firmware limitation or known issue with these models.
Hello Gabriele Icardi,
Any update on this? Could you please confirm if you have further queries on this?
Hello,
First of all, apologies for the delayed response. I’ve just noticed this ticket now, it was previously blocked and I had been restricted due to guideline issues, so I didn't receive any notification when it was eventually published.
Device date, time, and timezone are correctly configured and aligned
TLS 1.2/1.3 are enabled (older versions disabled)
Outbound connectivity is working correctly.
Tested across multiple users, tenants (including a clean tenant without Conditional Access or Security Defaults)
App consent is correctly granted and not restricted by tenant settings
Repeated the OAuth registration multiple times and also tested from different client devices
Based on this, and considering that the Microsoft sign-in and consent phase always completes successfully, it does seem to confirm that the issue occurs on the device during the final OAuth step (token retrieval or storage).