Impact of changing exchange online licenses

%3CLINGO-SUB%20id%3D%22lingo-sub-661396%22%20slang%3D%22en-US%22%3EImpact%20of%20changing%20exchange%20online%20licenses%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-661396%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EWe%20have%20a%20mailboxes%20that%20we%20use%20to%20allow%20multi-function%20copiers%20to%20scan%20to%20email.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20those%20need%20to%20have%20a%20licenses%20associated%20to%20it%3F%20It%20just%20represents%20a%20machine%20that%20people%20are%20using.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20want%20to%20make%20sure%20that%20we%20are%20doing%20the%20right%20thing%2C%20but%20also%20not%20spending%20money%20where%20we%20don't%20need%20to.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EBen%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-661396%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-661457%22%20slang%3D%22en-US%22%3ERe%3A%20Impact%20of%20changing%20exchange%20online%20licenses%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-661457%22%20slang%3D%22en-US%22%3EI'd%20setup%20a%20Shared%20mailbox%2C%20then%20you%20can%20setup%20a%20login%20to%20it%20and%20use%20it%20that%20way.%20I%20think%20it%20should%20still%20work.%20Since%20that's%20not%20technically%20a%20user%2C%20you%20should%20be%20fine%20as%20far%20as%20licensing%20is%20concerned%20if%20ever%20audited.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-663367%22%20slang%3D%22en-US%22%3ERe%3A%20Impact%20of%20changing%20exchange%20online%20licenses%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-663367%22%20slang%3D%22en-US%22%3E%3CP%3EYou're%20not%20supposed%20to%20be%20logging%20in%20directly%20with%20shared%20mailbox%20credentials%20though%2C%20Chris.%20While%20it's%20not%20that%20hard%20to%20actually%20make%20it%20work%2C%20it's%20on%20the%20shady%20side%20of%20the%20license%20agreement.%20Anyway%2C%20the%20available%20method%20to%20configure%20this%20in%20O365%2C%20with%20or%20without%20credentials%2C%20are%20listed%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fmail-flow-best-practices%2Fhow-to-set-up-a-multifunction-device-or-application-to-send-email-using-office-3%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fmail-flow-best-practices%2Fhow-to-set-up-a-multifunction-device-or-application-to-send-email-using-office-3%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Visitor

Hello,

We have a mailboxes that we use to allow multi-function copiers to scan to email.

 

Do those need to have a licenses associated to it? It just represents a machine that people are using.

 

Just want to make sure that we are doing the right thing, but also not spending money where we don't need to.

 

Thanks,

Ben

 

2 Replies
Highlighted
I'd setup a Shared mailbox, then you can setup a login to it and use it that way. I think it should still work. Since that's not technically a user, you should be fine as far as licensing is concerned if ever audited.
Highlighted

You're not supposed to be logging in directly with shared mailbox credentials though, Chris. While it's not that hard to actually make it work, it's on the shady side of the license agreement. Anyway, the available method to configure this in O365, with or without credentials, are listed here: https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-dev...