Legacy smtp auth vs app registrations
Mainly from the context of service / printer / scanner emails..
Could someone please help me understand why using an app registration that has to generally be granted mail access for all users and then restricted in exchange admin to just a single account is somehow better than using a username and password for a single account?
Smtp auth: username + password, doesn't support MFA / Conditional access
App registration: app id + secret, doesn't support MFA / Conditional access on the app id/secret (but obviously does if used for user sso)
It's just a username and password but named differently?
I'm really struggling to see the benefits of disabling legacy auth tenant wide for anything other than users mailboxes?
Posted Jul 13, 2022, 10:28 PM UTC
02
So, at its lowest, probably not much different at all on the security side if you were using per consumer accounts sensibly. A lot of folks get lazy and share those, so they blur the lines between "printer" and "30 printers" and "this app over here needs auth too, so let me just use that one rather than making sure I get another created without spurious licenses or permissions..."
In the long run, clear segregation of accounts for services to auth against other services, registered, clearly identified with purpose, using terrifyingly complex passwords/secrets/keys that you copy/paste once... clearly marks "this isn't a person, don't consider it in my licensing", preps for huge red flags if it shows up trying to reach outside "smtp only." or similar scope, etc.
Edit: Also, later tag on "set this for all my users" changes won't trample "except these that aren't real people" as easily.
This makes a little more sense now, thanks.