SOLVED

Generic (but not shared) email

%3CLINGO-SUB%20id%3D%22lingo-sub-1625217%22%20slang%3D%22en-US%22%3EGeneric%20(but%20not%20shared)%20email%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1625217%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20a%20computer%20that%20requires%20email%20(and%20the%20Office%20365%20apps)%20in%20our%20shipping%20department%2C%20but%20we%20sometimes%20have%20different%20people%20working%20in%20that%20department%20and%20sometimes%20temporary%20people.%20So%20we%20don't%20really%20want%20to%20set%20up%20an%20Office%20365%20account%20for%20%22Joe%20Smith%22%2C%20it%20would%20make%20more%20sense%20for%20the%20account%20to%20be%20%22Shipping%20Department%22.%20Any%20issues%20with%20that%20that%20I%20can't%20think%20of%3F%20If%20I%20made%20a%20shared%20mailbox%2C%20I%20would%20still%20need%20to%20buy%20a%20license%20in%20someone's%20name%20for%20the%20apps%20on%20that%20computer...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1625217%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1625751%22%20slang%3D%22en-US%22%3ERe%3A%20Generic%20(but%20not%20shared)%20email%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1625751%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F446800%22%20target%3D%22_blank%22%3E%40Microfiche%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20can%20do%20it%20this%20way%2C%20and%20some%20of%20my%20clients%20insist%20on%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20always%20preferred%20to%20use%20their%20own%20accounts%20and%20receive%20email%20in%20a%20shared%20mailbox%20rather%20than%20set%20up%20generic%20users%20-%20in%20terms%20of%20keeping%20track%20of%20exactly%20who%20has%20done%20what%20or%20when%2C%20it%20makes%20it%20easier%20from%20a%20auditing%20point%20of%20view%20when%20we've%20been%20tasks%20with%20figuring%20out%20who%20sent%20what%20out%20or%20if%20something%20is%20deleted%2Famended%20etc.%20We%20tend%20to%20also%20have%20security%20concerns%20with%20corporate%20data%20potentially%20being%20open%20to%20users%2Fguests%2Funauthorised%20users%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20believe%20most%20M365%20subscriptions%20allow%20users%20to%20activate%20on%20multiple%20machines%2C%20so%20in%20your%20position%20would%20encourage%20users%20to%20log%20in%20with%20their%20own%20account%20and%20access%20emails%20through%20mailbox%20sharing.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EProvided%20the%20organisation%20understands%20and%20accepts%20security%20and%20compliance%20issues%2C%20then%20you%20can%20crack%20on%2C%20but%20I%20personally%20avoid%20it%20if%20possible.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1625821%22%20slang%3D%22en-US%22%3ERe%3A%20Generic%20(but%20not%20shared)%20email%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1625821%22%20slang%3D%22en-US%22%3EGreat%20-%20thanks%20for%20the%20insights!%3C%2FLINGO-BODY%3E
Occasional Contributor

We have a computer that requires email (and the Office 365 apps) in our shipping department, but we sometimes have different people working in that department and sometimes temporary people. So we don't really want to set up an Office 365 account for "Joe Smith", it would make more sense for the account to be "Shipping Department". Any issues with that that I can't think of? If I made a shared mailbox, I would still need to buy a license in someone's name for the apps on that computer...

2 Replies
best response confirmed by Microfiche (Occasional Contributor)
Solution

Hi @Microfiche 

 

You can do it this way, and some of my clients insist on it.

 

I've always preferred to use their own accounts and receive email in a shared mailbox rather than set up generic users - in terms of keeping track of exactly who has done what or when, it makes it easier from a auditing point of view when we've been tasks with figuring out who sent what out or if something is deleted/amended etc. We tend to also have security concerns with corporate data potentially being open to users/guests/unauthorised users 

 

I believe most M365 subscriptions allow users to activate on multiple machines, so in your position would encourage users to log in with their own account and access emails through mailbox sharing. 

 

Provided the organisation understands and accepts security and compliance issues, then you can crack on, but I personally avoid it if possible.

Great - thanks for the insights!