Teams rollout - replacing Slack

%3CLINGO-SUB%20id%3D%22lingo-sub-389823%22%20slang%3D%22en-US%22%3ETeams%20rollout%20-%20replacing%20Slack%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-389823%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20all%2C%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EI%20am%20in%20the%20middle%20of%20rolling%20out%20Microsoft%20365%20(with%20Azure%20AD)%20to%20all%20PC's%20in%20the%20business.%20Something%20i'm%20a%20bit%20stuck%20on%20how%20to%20proceed%2C%20is%20Teams.%20This%20will%20be%20replacing%20Slack%2C%20which%20we%20currently%20use%20-%20and%20as%20its%20free%2C%20every%20staff%20member%20(including%20casuals%20that%20may%20only%20work%20once%20a%20week)%20has%20an%20account%2Flogin.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20many%20machines%20that%20are%20'Hotdesks'%20-%20with%20people%20moving%20around%20(eg.%20Casual%20staff%20etc.).%20To%20connect%20these%20machines%20to%20our%20AD%2C%20I%20have%20added%20each%20machine%20as%20'Hotdesk1%2C%20Hotdesk2'%20etc.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20-%20for%20Full%20time%20staff%20it's%20no%20problem%2C%20as%20most%20have%20their%20own%20PC.%20For%20the%20casuals%20that%20will%20be%20sharing%20PCs%2C%20I%20need%20them%20to%20each%20have%20their%20own%20login%20for%20Teams%20-%20so%20messages%20come%20from%20that%20person%2C%20not%20'Hotdesk1'%20for%20example.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhats%20the%20best%20way%20to%20go%20about%20this%2Fwhat%20do%20people%20usually%20do%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ECorey%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-389823%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHow-to%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESlack%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EUsers%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-389849%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20rollout%20-%20replacing%20Slack%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-389849%22%20slang%3D%22en-US%22%3ESaw%20my%20Swedish%20keyboard%20messed%20up%20my%20text%20there%20%3A)%3C%2Fimg%3E%3CBR%20%2F%3E%3CBR%20%2F%3EAs%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F27835%22%20target%3D%22_blank%22%3E%40Karuana%20Gatimu%3C%2FA%3E%20also%20said%20the%20user%20adoption%20is%20way%20beyond%20the%20tech%2C%20so%20make%20sure%20this%20is%20not%20forgotten%20in%20order%20for%20a%20successful%20rollout!!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-389834%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20rollout%20-%20replacing%20Slack%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-389834%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F309415%22%20target%3D%22_blank%22%3E%40pooch3%3C%2FA%3E%26nbsp%3B%20I%20agree%20with%20Adam.%26nbsp%3B%20Each%20user%20should%20have%20an%20identity%20in%20M365%2FAAD%26nbsp%3B%20That%20will%20unblock%20them%20from%20using%20the%20web%20or%20mobile%20clients%20if%20you%20support%20the%20latter.%26nbsp%3B%20For%20more%20info%20on%20how%20to%20roll%20out%20Teams%20visit%20our%20practical%20guidance%20at%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FSuccessWithTeams%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2FSuccessWithTeams%3C%2FA%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETo%20be%20successful%20I'd%20highly%20recommend%20you%20engage%20with%20those%20former%20Slack%20user%20and%20truly%20understand%20their%20use%20cases%20so%20you%20can%20asisst%20them%20with%20their%20transition.%26nbsp%3B%20%26nbsp%3BWe%20talk%20about%20this%20and%20much%20more%20on%20adoption%20over%20the%20the%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FDriveAdoption%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3EDriving%20Adoption%3C%2FA%3E%20forum.%26nbsp%3B%20Feel%20free%20to%20ask%20here%2C%20or%20join%20us%20there%20to%20meet%20other%20people%20doing%20what%20you're%20doing.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-389830%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20rollout%20-%20replacing%20Slack%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-389830%22%20slang%3D%22en-US%22%3EWith%20tou%20create%20individual%20aad%20accounts%20for%20these%20users%20and%20use%20them%20to%20login%20the%20machines%20and%20then%20have%20Thats%20raml%C3%B6sa%20experience%20with%20teams%3CBR%20%2F%3E%3CBR%20%2F%3EOtherwise%20They%20can%20use%20the%20web%20client%20to%20login%20with%20their%20AAD%20account%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hey all,


I am in the middle of rolling out Microsoft 365 (with Azure AD) to all PC's in the business. Something i'm a bit stuck on how to proceed, is Teams. This will be replacing Slack, which we currently use - and as its free, every staff member (including casuals that may only work once a week) has an account/login.

 

We have many machines that are 'Hotdesks' - with people moving around (eg. Casual staff etc.). To connect these machines to our AD, I have added each machine as 'Hotdesk1, Hotdesk2' etc.

 

Now - for Full time staff it's no problem, as most have their own PC. For the casuals that will be sharing PCs, I need them to each have their own login for Teams - so messages come from that person, not 'Hotdesk1' for example.

 

Whats the best way to go about this/what do people usually do?

 

Thanks in advance :)


Corey

3 Replies
With tou create individual aad accounts for these users and use them to login the machines and then have Thats ramlösa experience with teams

Otherwise They can use the web client to login with their AAD account
Highlighted

@pooch3  I agree with Adam.  Each user should have an identity in M365/AAD  That will unblock them from using the web or mobile clients if you support the latter.  For more info on how to roll out Teams visit our practical guidance at https://aka.ms/SuccessWithTeams  

 

To be successful I'd highly recommend you engage with those former Slack user and truly understand their use cases so you can asisst them with their transition.   We talk about this and much more on adoption over the the Driving Adoption forum.  Feel free to ask here, or join us there to meet other people doing what you're doing.  

Highlighted
Saw my Swedish keyboard messed up my text there :)

As @Karuana Gatimu also said the user adoption is way beyond the tech, so make sure this is not forgotten in order for a successful rollout!!