-
-
Notifications
You must be signed in to change notification settings - Fork 7
Expand file tree
/
Copy pathdevices.json
More file actions
283 lines (283 loc) · 17.9 KB
/
Copy pathdevices.json
File metadata and controls
283 lines (283 loc) · 17.9 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
{
"$comment": [
"Machine-readable OAuth 2.0 / SMTP AUTH status for systems affected by the",
"Microsoft 365 Basic auth shutdown. Source of truth for the table in",
"docs/DEVICE-COMPATIBILITY.md, which is generated from this file by",
"tools/build-device-table.py and checked in CI, so the two cannot drift.",
"",
"Every entry must carry an `evidence` URL. If nobody has published",
"anything, the entry does not belong here - a compatibility list is only",
"worth citing if each row can be checked.",
"",
"status values:",
" none-planned vendor has stated no OAuth firmware is coming",
" available OAuth support exists for the listed models or versions",
" partial some models or versions only; the list decides",
" check-advisory vendor publishes a per-model list we do not reproduce",
" unsupported the product has no OAuth capability for this purpose"
],
"updated": "2026-09-07",
"entries": [
{
"vendor": "Konica Minolta / DEVELOP",
"product": "ineo and ineo+ MFPs",
"status": "none-planned",
"models": [
"ineo 306",
"ineo 7228",
"ineo 266",
"ineo+ 266",
"ineo+ 256",
"ineo+ 226",
"ineo 4752",
"ineo 4052",
"ineo 4750",
"ineo 4050",
"ineo+ 3110",
"ineo+ 3100P",
"ineo+ 754e",
"ineo+ 654e",
"ineo 654e",
"ineo 226",
"ineo 246",
"ineo 236",
"ineo 216",
"ineo 7223",
"ineo 206",
"ineo 4700P",
"ineo 3301P",
"ineo 4000P",
"ineo 4020",
"ineo 3320",
"ineo 165",
"ineo 165e",
"ineo 185",
"ineo 185e"
],
"evidence": "https://www.develop.eu/en/support/discontinuation-of-basic-authentication-for-smtp.html",
"notes": "Marked \"N/A\" in the vendor's own OAuth column, and the advisory states that \"for devices marked as N/A under Release Schedule and devices not listed, no firmware update is planned\". It points these owners at a different mail service rather than at an update. One suffix decides: ineo 165en and ineo 185en are listed as Released (V3.00) while ineo 165/165e and 185/185e are N/A. Other ineo product groups in the same advisory do have OAuth firmware - check the exact model. A third category exists that is neither: several Product Group 10 models are listed as \"Under planning\" with no release date, so their owners have no answer yet in either direction."
},
{
"vendor": "Xerox",
"product": "ConnectKey printers and MFPs",
"status": "partial",
"models": [
"VersaLink B415",
"VersaLink C415",
"VersaLink B620",
"VersaLink C620",
"VersaLink B625",
"VersaLink C625",
"AltaLink"
],
"evidence": "https://www.xerox.com/en-us/office/insights/exchange-online-authentication",
"notes": "Device Code Flow is available now across the whole published range; Client Credentials Flow only on the ConnectKey models listed here. PrimeLink is not one of them - Xerox's table marks PrimeLink C9065/C9070, B9100/B9110/B9125/B9136 and C9265/C9275/C9281 as \"Not Available\" in the Client Credential Flow column. Devices not on Xerox's supported-firmware list are the problem cases and are not promised an update. Affects Scan to Email, Internet Fax (Send), Fax Forward to Email and Auto Email Notifications."
},
{
"vendor": "Ricoh",
"product": "multifunction printers",
"status": "check-advisory",
"models": [],
"evidence": "https://www.ricoh.com/info/2025/0526_1",
"notes": "Ricoh publishes affected products with per-product firmware status, last updated 2026-02-06, in two tables - products with released OAuth firmware, and products added as of 2026-01-30 - plus a third group the Ricoh Firmware Update Tool cannot update, where the local representative has to do it. Not reproduced here because the list is long and still moving; check the model against the advisory. Firmware is not the end of it: because \"the TLS cipher suites supported by Microsoft 365 will be updated\", Ricoh warns that \"some Ricoh products - including models that already support OAuth 2.0 authentication - will no longer be able to send or receive emails via Exchange Online\". Ricoh does not say any product is permanently excluded, but for devices still waiting its own recommendation is to stop relying on email from the device or to use a mail service other than Exchange Online."
},
{
"vendor": "Brother",
"product": "printers, MFPs and document scanners",
"status": "check-advisory",
"models": [],
"evidence": "https://support.brother.com/g/b/oscontents.aspx?c=us&lang=en&ossid=42",
"notes": "Brother publishes a per-model Product Support List and states plainly that a machine not on it does not support OAuth 2.0, with no firmware promised - the vendor's own guidance for those owners is to use a different mail service. Listed models split into two tiers: OAuth already present, or present after a firmware update that is already downloadable. Affects Scan to Email Server, Internet Fax, Email Reports and Email Notifications. Check the exact model: support is firmware-dependent as well as model-dependent."
},
{
"vendor": "Canon",
"product": "Maxify MB2755",
"status": "unsupported",
"models": [
"Maxify MB2755"
],
"evidence": "https://github.com/msgwing/ZeroSMTP/blob/main/docs/DEVICE-CASE-STUDIES.md",
"notes": "Separate failure mode from OAuth: the firmware ships a fixed root CA store predating current Let's Encrypt roots, so certificate validation fails regardless of authentication. Hardware-confirmed, unchanged after a firmware update. Verification has to be disabled on the device."
},
{
"vendor": "Kyocera",
"product": "MFPs reporting send error 1102",
"status": "check-advisory",
"models": [],
"evidence": "https://github.com/msgwing/ZeroSMTP/blob/main/docs/ERROR-MESSAGES.md",
"notes": "1102 / 0x1102 is Kyocera's device-side code for an SMTP authentication failure, not a model list. No public per-model OAuth statement located; check with the vendor for a specific model."
},
{
"vendor": "QNAP",
"product": "NAS notification settings",
"status": "unsupported",
"models": [],
"evidence": "https://gist.github.com/msgwing/39958d909e085ae9cc0e6b3584d930bf",
"notes": "The notification settings accept username and password only; there is no OAuth option for Microsoft 365 SMTP."
},
{
"vendor": "Veeam",
"product": "Backup for Microsoft 365 and related products",
"status": "partial",
"models": [],
"evidence": "https://helpcenter.veeam.com/docs/vbo365/guide/smtp_server.html",
"notes": "Corrected 2026-08-16 - the previous note claimed newer versions added OAuth for SMTP, which the linked page does not support. The v8 documentation offers \"SMTP server (basic authentication)\" and does not describe an OAuth option for SMTP notifications; modern app-only authentication appears elsewhere in the product, for Entra applications, not here. So the fix is not \"upgrade and SMTP gets OAuth\" - check whether your build offers a notification method that is not SMTP at all, and treat the SMTP path as basic-auth only."
},
{
"vendor": "Cisco",
"product": "Unity Connection",
"status": "check-advisory",
"models": [],
"evidence": "https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online",
"notes": "Named in Microsoft's own deprecation documentation. OAuth support depends on the release; check yours before assuming either way."
},
{
"vendor": "Microsoft",
"product": "Teams Rooms",
"status": "available",
"models": [],
"evidence": "https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online",
"notes": "Microsoft's own product. Enable modern auth on the resource account - no relay needed."
},
{
"vendor": "Microsoft",
"product": "Dynamics NAV / Business Central",
"status": "partial",
"models": [],
"evidence": "https://www.innovia.com/blog/microsoft-to-retire-basic-auth-smtp-for-exchange-online-what-bc-nav-users-need-to-know",
"notes": "Newer Business Central handles modern auth. Older on-prem NAV installs generally need the SMTP account repointed."
},
{
"vendor": "Laserfiche",
"product": "Workflow email",
"status": "partial",
"models": [],
"evidence": "https://answers.laserfiche.com/questions/200557/Disabling-basic-authentication-causing-Workflow-emails-to-fail",
"notes": "Laserfiche now answers this thread directly. The selected answer: \"Customers must upgrade to the Laserfiche Workflow 12 2025H1 release or later to use OAuth 2.0 for SMTP through Exchange Online. There are no current plans to backport OAuth support for Exchange Online SMTP to earlier versions of Workflow.\" The approved answer, updated April 2026, adds that \"version 12 Laserfiche products support Microsoft OAuth 2.0\", and that for v10.4, v11 and v12 installs which cannot upgrade, Laserfiche has confirmed Microsoft's own alternatives instead - High Volume Email, Azure Communication Services Email, or on-premises Exchange in a hybrid configuration."
},
{
"vendor": "ManageEngine",
"product": "OpManager",
"status": "check-advisory",
"models": [],
"evidence": "https://www.manageengine.com/network-monitoring/how-to/fix-smtpclientauth-disabled-error.html",
"notes": "OpManager supports OAuth 2.0 from build 126306, so for anyone on that build or later this is a settings change rather than a migration - the vendor's guide states it directly. The same page also documents re-enabling SMTP AUTH in the Exchange admin centre, which works until the end of December 2026 and not after; treat it as breathing room, not a fix."
},
{
"vendor": "Cerberus",
"product": "FTP Server",
"status": "partial",
"models": [],
"evidence": "https://support.cerberusftp.com/hc/en-us/articles/24103821642643-Troubleshooting-SMTP-Setup-Error-on-Office365-com-Resolving-EHLO-Message-Failure-535-5-7-139-Authentication-Unsuccessful-Basic-Authentication-Disabled",
"notes": "The vendor article on the exact 535 5.7.139 failure now answers it: \"Microsoft deprecated Basic Authentication as the default setting for O365 in October of 2023 and Cerberus now supports Microsoft OAuth2 for O365 SMTP Authentication.\" The current SMTP setup article documents an Authentication selector on the SMTP target with a Microsoft OAuth2 option taking tenant ID, application (client) ID and client secret from Entra ID, and describes Basic as the same functionality as the previous Use Authentication checkbox \"(prior to Cerberus 2025.3.0)\" - so the build decides. Older builds offer username and password only."
},
{
"vendor": "Faxination",
"product": "fax server",
"status": "partial",
"models": [],
"evidence": "https://faxination.com/microsoft-timeline-for-basic-authentication-deprecation-in-exchange-online-smtp-auth/",
"notes": "Fenestrae states that \"Faxination 2024 supports Modern Authentication (OAuth 2.0) for Microsoft 365 and Exchange Online\", so for this product the answer is a version number rather than a firmware wait; older installs still have to repoint the outbound SMTP account. Read the timeline on the same page with care - it still describes the superseded March-April 2026 schedule rather than the current one."
},
{
"vendor": "Lexmark",
"product": "printers and MFPs",
"status": "check-advisory",
"models": [],
"evidence": "https://support.lexmark.com/content/support/guides/en/kb20211110020010549/setup-installation-and-configuration-issues/how-to-set-up-oauth-2-authentication.html",
"notes": "Lexmark documents OAuth 2.0 authentication for printers starting with the FW24 firmware release, including Outlook Live and Microsoft 365. The Email Server flow is configured through the printer's Embedded Web Server and requires OAuth 2.0 registration. Verify the specific device and firmware before assuming support.",
"contributor": "Mohitingale13",
"contributor_pr": 223
},
{
"vendor": "HP",
"product": "printers and MFPs",
"status": "partial",
"models": [],
"evidence": "https://support.hp.com/nz-en/document/ish_13623350-13600809-16",
"notes": "HP documents OAuth 2.0 support for Microsoft 365 Scan to Email on HP Enterprise and HP Managed printers running FutureSmart firmware 5.7 and newer. However, HP also states that certain LaserJet Pro models, including the M478-M479 and M428-M429f, do not support OAuth 2.0. Verify the exact product family and firmware before assuming Microsoft 365 SMTP AUTH compatibility.",
"guide": "HP-PRINTER-SMTP.md",
"guide_title": "HP printer: \"SMTP server requires authentication\"",
"contributor": "Mohitingale13",
"contributor_pr": 230
},
{
"vendor": "Sharp",
"product": "printers and MFPs",
"status": "partial",
"models": [],
"evidence": "https://global.sharp/restricted/print/manuals/5/bp70m65/us/contents_09-07_018.html",
"notes": "Sharp documents OAuth 2.0 for SMTP in the machine manual rather than in a compatibility advisory: under Network Settings the SMTP \"Authentication Method\" reads \"Select OAuth 2.0 when using Microsoft365, Exchange Online, etc.\", with Provider defaulting to Microsoft and a Get Token key on the device. The same option appears on the POP3 side for Internet Fax reception. Sharp does not appear to publish a centralized compatibility list or a universal firmware floor for the full printer/MFP range, so verify the exact model's current manual before assuming OAuth 2.0 support.",
"contributor": "Mohitingale13",
"contributor_pr": 238
},
{
"vendor": "Toshiba",
"product": "printers and MFPs",
"status": "check-advisory",
"models": [],
"evidence": "https://www.toshibatec.com/information/20260113_01.html",
"notes": "Toshiba Tec publishes a model-by-model Exchange Online OAuth 2.0 compatibility table for its MFPs, including firmware release information, compatible models, pending firmware updates, and explicitly incompatible models. Verify the exact model and current firmware status against Toshiba's published advisory before assuming Microsoft 365 SMTP AUTH compatibility.",
"contributor": "Mohitingale13",
"contributor_pr": 245
},
{
"vendor": "Synology",
"product": "NAS notification email",
"status": "check-advisory",
"models": [],
"evidence": "https://kb.synology.com/en-us/DSM/help/DSM/AdminCenter/system_notification_email?version=7",
"notes": "Synology DSM 7 supports Outlook as an email notification service with an interactive Sign In flow rather than manual SMTP credentials. Synology documents OAuth-based authentication for this Outlook integration, but availability and behavior depend on the DSM version. Verify the exact DSM version and current Outlook notification configuration before assuming Microsoft 365 SMTP AUTH OAuth compatibility.",
"contributor": "Mohitingale13",
"contributor_pr": 252
},
{
"vendor": "Sophos",
"product": "Sophos Firewall (email alerts and reports)",
"status": "available",
"models": [
"Sophos Firewall 22.0",
"Sophos Firewall 20.0"
],
"evidence": "https://docs.sophos.com/nsg/sophos-firewall/22.0/Help/en-us/webhelp/onlinehelp/AdministratorHelp/Administration/HowToArticles/NotificationsConfigureMicrosoft365/",
"notes": "Sophos publishes an official guide 'Configure OAuth 2.0 on Microsoft 365' for Sophos Firewall 22.0: register the firewall as an app in Microsoft Entra, add delegated SMTP.Send + offline_access permissions, turn on Authenticated SMTP for the sending user, and configure notifications with client ID / secret / refresh token. Confirms Modern (OAuth 2.0) SMTP AUTH support; availability depends on the firewall version.",
"contributor": "TrueFurina",
"contributor_pr": 310
},
{
"vendor": "TrueNAS",
"product": "TrueNAS email alerts",
"status": "partial",
"models": [],
"evidence": "https://www.truenas.com/docs/scale/systemsettings/general/settingupsystememail/",
"notes": "TrueNAS SCALE supports OAuth for Outlook and Gmail, but standard SMTP requires basic authentication. Some forum users report issues with Microsoft 365 enforcing OAuth while configuring standard SMTP on CORE.",
"contributor": "Mohitingale13",
"contributor_pr": 368
},
{
"vendor": "Zabbix",
"product": "email notifications",
"status": "partial",
"models": [],
"evidence": "https://www.zabbix.com/documentation/7.4/en/manual/introduction/whatsnew",
"notes": "Zabbix 7.4 introduced OAuth 2.0 authentication for SMTP, including automated OAuth configuration for Office365 and Gmail. Verify the Zabbix version and Office365 SmtpClientAuthentication configuration before assuming Microsoft 365 SMTP AUTH compatibility.",
"contributor": "Mohitingale13",
"contributor_pr": 369
},
{
"vendor": "Xerox",
"product": "MFPs reporting send error 027-779",
"status": "check-advisory",
"models": [
"WorkCentre 7328",
"WorkCentre 7335",
"WorkCentre 7345",
"WorkCentre 7346"
],
"evidence": "https://www.support.xerox.com/en-us/article/KB0238716",
"notes": "027-779 is Xerox's device-side code for an SMTP authentication failure on WorkCentre 7328/7335/7345/7346 and related MFPs. No public per-model OAuth statement located; check with the vendor for a specific model.",
"contributor": "Mohitingale13",
"contributor_pr": 416
}
]
}