Best Way to Deploy Teams in Confidential Environment

[CSI_Guy]

Hello there, our company is exploring the use of Teams to help push out department/company announcements immediately rather than waiting on memos or meetings to do the same thing.

We are relatively strict on our policies, most of our employees have access to email out but do not receive emails, using shared MS Exchange accounts. So we have between 30-40 people, and we have the ability to set up 8 seats of Teams (paid version) between our existing Microsoft accounts. 

For the remaining employees, we do not want to require them to setup a new account to use Teams, nor do we want them to have to use their personal email account (primarily for security reasons). 

Is there a way to let them login using "aliases" made from one of our shared email accounts? Or what would be another good option to keep the accounts used controlled by the company?

Please help me out with the best way to do this, between seasonal workers and temp workers, we have high turnaround for about half of the office - so the ability to reuse accounts would be handy if possible. I am just setting up Teams to test between my PC, laptop and phone, so I am not too familiar with it yet. None of the guides or videos really explore my topic here.

[#2]

@CSI_Guy  this is great U guys are using Teams or moving towards Microsoft Teams;

secondly yes you have the ability to add Shared Mailboxes as the member in Teams but the issue is those Shared Mailboxes may have more than one user and if those users do not have emails how we can add them to shared Mailboxes, besides if someone does not have a regular email account s/he can't login/use shared Mailbox.

The best practice is to give Teams license to everyone who got regular email account & mailbox which they could use full features of Teams Chat, Conversation, Audio & Vido calls, and post in channels.

Teams in Teams will be created as private groups one for all company and then based on each group you could even have a private channel or standard channels base on the requirement.

If you guys are only sending email between your own self the best way is using Teams either posting or making announcement in general channel if that is for everyone or post in private channel if that is only for specific group of people.

[#3]

@PDostiyar 

We currently have a shared email (general) and aliases setup for each workstation. So everyone is using General, but individually they see their aliases as CSI 01, CSI 02, CSI 03, etc. matching the workstation they they are assigned to. 

My only issue, is I don't want them to have the ability to sign in from outside the company (easiest way to do that is just control the account used to sign in). So I don't want them to be able to "sign in" to either the Teams or the email - as it stands, everything is setup and managed by our IT (myself). 

We are not so much worried about what content they have access to, but just to ensure that they cannot log in outside of work due to confidentiality. 

[#4 · Accepted solution]

Okay, so I think I figured it out! (Holy crap batman!)

So, I revisited using the email aliases from the shared email account. Turns out that it will work with some (A LOT) of massaging.  First of all, our company has NEVER had to use to access Azure Active Directory, so the fact that I had to for this is immediately frustrating. Anyhow, once logged into the AAD, navigate to your users. There you will see the alias accounts. Since the issue was with the password, select an alias user and choose to Reset Password. There was technically no password associated with the alias account, even though it was created from an account with a password. Make sure to document your temporary password.

Go back to Teams now, login with your alias' email, using your temporary password. Once you login, it will prompt you to change your password (I just set it to the same as the Master Account). And voilà!