Organization: has a few Teams-licenses; non-licensed user guest access problematic?

%3CLINGO-SUB%20id%3D%22lingo-sub-891481%22%20slang%3D%22en-US%22%3EOrganization%3A%20has%20a%20few%20Teams-licenses%3B%20non-licensed%20user%20guest%20access%20problematic%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-891481%22%20slang%3D%22en-US%22%3E%3CP%3EWe've%20noticed%20today%20an%20issue%20with%20an%20invitation%20from%20an%20external%20company%20for%20guest%20access%20to%20their%20Teams%20site.%20Within%20our%20organization%2C%20only%20a%20subset%20of%20the%20users%20are%20now%20using%20O365%3B%20while%20everyone%20has%20Exchange%20Online%20mailboxes.%20Now%20one%20of%20the%20people%20who%20doesn't%20have%20an%20O365-license%20(and%20so%20no%20Teams%20license%20within%20our%20organization)%20has%20received%20an%20invitation%20to%20join%20an%20external%20Teams%20as%20guest.%20But%20we%20keep%20getting%20in%20a%20loop%20where%20our%20company%20admin%20(yours%20truly)%20needs%20to%20enable%20Teams%20for%20this%20user%3F%20How%2C%20without%20license%3F%20After%20all%2C%20he's%20only%20a%20guest%20now%20in%20another%20Teams%20environment%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-891481%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-891514%22%20slang%3D%22en-US%22%3ERe%3A%20Organization%3A%20has%20a%20few%20Teams-licenses%3B%20non-licensed%20user%20guest%20access%20problematic%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-891514%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F245955%22%20target%3D%22_blank%22%3E%40jbostoen%3C%2FA%3EDue%20to%20your%20organisation%20having%20Office%20365%20you%20need%20to%20license%20the%20user%20for%20Teams%20for%20them%20to%20be%20able%20to%20accept%20an%20invitation%20sent%20to%20their%20work%20email%20address.%20I%20haven't%20found%20a%20way%20around%20this%20previously.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-891530%22%20slang%3D%22en-US%22%3ERe%3A%20Organization%3A%20has%20a%20few%20Teams-licenses%3B%20non-licensed%20user%20guest%20access%20problematic%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-891530%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F214649%22%20target%3D%22_blank%22%3E%40Andrew%20Hodges%3C%2FA%3E%26nbsp%3B%20I'm%20afraid%20so.%20We're%20planning%20to%20roll%20out%20O365%20in%20about%20a%20year%20to%20the%20entire%20organization%2C%20but%20not%20now.%3CBR%20%2F%3E%3CBR%20%2F%3EReally%20doesn't%20seem%20to%20make%20sense%20you%20can%20allow%20access%20to%20people%20with%20no%20O365%20at%20all%3B%20but%20they%20can't%20belong%20to%20an%20organization%20which%20partially%20has%20O365%20licenses...%3CBR%20%2F%3E%3CBR%20%2F%3EAnother%20(ridiculous)%20work%20around%20I've%20heard%20is%20to%20use%20private%20accounts%20which%20really%20is%20questionable%20in%20all%20other%20ways.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-891601%22%20slang%3D%22en-US%22%3ERe%3A%20Organization%3A%20has%20a%20few%20Teams-licenses%3B%20non-licensed%20user%20guest%20access%20problematic%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-891601%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F245955%22%20target%3D%22_blank%22%3E%40jbostoen%3C%2FA%3E%26nbsp%3B%20The%20only%20other%20possible%20suggestion%20would%20be%20to%20give%20them%20a%20temp%2C%20%22in%20cloud%20account%22%20so%20email%20would%20be%20jbostoen%40domain.onmicrosoft.com.%20That%20is%20a%20bit%20of%20a%20phaff%20but%20as%20they%20are%20an%20external%20user%20in%20the%20other%20tenant%20the%20account%20could%20just%20be%20deleted%20nearer%20the%20time%20of%20rollout.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20other%20workaround%20you%20mention%20is%20a%20possibility%20but%20not%20exactly%20an%20%22Enterprise%22%20solution.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-892286%22%20slang%3D%22en-US%22%3ERe%3A%20Organization%3A%20has%20a%20few%20Teams-licenses%3B%20non-licensed%20user%20guest%20access%20problematic%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-892286%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F245955%22%20target%3D%22_blank%22%3E%40jbostoen%3C%2FA%3EThinking%20about%20this%20a%20bit%20more.%20I%20think%20you%20dont%20need%20to%20license%20them%20for%20Teams%2C%20they%20just%20need%20to%20exist%20as%20a%20user%20in%20your%20Tenant%2C%20you%20may%20not%20need%20to%20license%20them%20at%20all%2C%20but%20not%20something%20I%20have%20ever%20tried.%20They%20would%20have%20to%20login%20to%20the%20web%20version%20of%20teams%20in%20the%20other%20company%20in%20this%20scenario.%20To%20access%20an%20external%20network%20that%20you%20are%20a%20guest%20of%20in%20the%20desktop%20client%20you%20have%20to%20be%20licensed%20in%20your%20tenant%20to%20login.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

We've noticed today an issue with an invitation from an external company for guest access to their Teams site. Within our organization, only a subset of the users are now using O365; while everyone has Exchange Online mailboxes. Now one of the people who doesn't have an O365-license (and so no Teams license within our organization) has received an invitation to join an external Teams as guest. But we keep getting in a loop where our company admin (yours truly) needs to enable Teams for this user? How, without license? After all, he's only a guest now in another Teams environment?

4 Replies
Highlighted

@jbostoenDue to your organisation having Office 365 you need to license the user for Teams for them to be able to accept an invitation sent to their work email address. I haven't found a way around this previously. 

Highlighted

@Andrew Hodges  I'm afraid so. We're planning to roll out O365 in about a year to the entire organization, but not now.

Really doesn't seem to make sense you can allow access to people with no O365 at all; but they can't belong to an organization which partially has O365 licenses...

Another (ridiculous) work around I've heard is to use private accounts which really is questionable in all other ways.

Highlighted

@jbostoen  The only other possible suggestion would be to give them a temp, "in cloud account" so email would be jbostoen@domain.onmicrosoft.com. That is a bit of a phaff but as they are an external user in the other tenant the account could just be deleted nearer the time of rollout. 

 

The other workaround you mention is a possibility but not exactly an "Enterprise" solution.

Highlighted

@jbostoenThinking about this a bit more. I think you dont need to license them for Teams, they just need to exist as a user in your Tenant, you may not need to license them at all, but not something I have ever tried. They would have to login to the web version of teams in the other company in this scenario. To access an external network that you are a guest of in the desktop client you have to be licensed in your tenant to login.