SOLVED
Home

Org-wide members

%3CLINGO-SUB%20id%3D%22lingo-sub-458444%22%20slang%3D%22en-US%22%3ERe%3A%20Org-wide%20members%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-458444%22%20slang%3D%22en-US%22%3EThey%20check%20for%20every%20user%20with%20a%20license%20which%20could%20also%20invluxe%20accounts%20not%20really%20belonging%20in%20a%20team!%3CBR%20%2F%3E%3CBR%20%2F%3ERead%20more%20here%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Foffice365itpros.com%2F2018%2F10%2F10%2Forg-wide-teams-now-available%2Famp%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Foffice365itpros.com%2F2018%2F10%2F10%2Forg-wide-teams-now-available%2Famp%2F%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20is%20from%20official%20doc%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fcreate-an-org-wide-team%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fcreate-an-org-wide-team%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%E2%80%9CWhen%20an%20org-wide%20team%20is%20created%2C%20all%20global%20admins%20are%20added%20as%20team%20owners%20and%20all%20active%20users%20are%20added%20as%20team%20members.%20Users%20who%20are%20disabled%20for%20Teams%2C%20guest%20users%2C%20and%20most%20rooms%20aren't%20added%20to%20the%20team.%20As%20your%20organization's%20directory%20is%20updated%20to%20include%20new%20active%20users%20or%20if%20users%20no%20longer%20work%20at%20your%20company%20and%20their%20Teams%20license%20is%20disabled%2C%20changes%20are%20automatically%20synced%20and%20the%20users%20are%20added%20or%20removed%20from%20the%20team.%E2%80%9D%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-748406%22%20slang%3D%22en-US%22%3ERe%3A%20Org-wide%20members%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-748406%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F72542%22%20target%3D%22_blank%22%3E%40adam%20deltinger%3C%2FA%3E%26nbsp%3B%20%26nbsp%3BWould%20you%20happen%20to%20know%20when%20they%20(documentation)%20says%20Organization%20is%20that%20to%20be%20interpreted%20or%20equal%20to%20tenant%3F%26nbsp%3B%20The%20reason%20I%20ask%20is%20because%20we%20have%20a%20multi-domain%20tenant%20and%20we%20have%20unlicensed%20users%20in%20those%20domains%20that%20we%20do%20not%20want%20to%20have%20in%20the%20org-wide%20Team.%26nbsp%3B%20We%20use%20that%20domain%20specifically%20to%20collaborate%20in%20SharePoint%20with%20pseudo-Guests%20and%20it%20would%20not%20be%20appropriate%20for%20them%20to%20see%20everything%20that%20the%20primary%20domain%20(onmicrosoft.com)%20or%20main%20tenant%20sees.%20I%20would%20post%20this%20to%20the%20docs.microsoft.com%20site%20but%20that%20requires%20GitHub%20account%20now.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-748617%22%20slang%3D%22en-US%22%3ERe%3A%20Org-wide%20members%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-748617%22%20slang%3D%22en-US%22%3EI%20don%E2%80%99t%20really%20get%20what%20your%20question%20was%3F%3CBR%20%2F%3EThey%20shouldn%E2%80%99t%20get%20added%20if%20they%20aren%E2%80%99t%20licensed%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-748643%22%20slang%3D%22en-US%22%3ERe%3A%20Org-wide%20members%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-748643%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F72542%22%20target%3D%22_blank%22%3E%40adam%20deltinger%3C%2FA%3E%26nbsp%3B%20Sorry%2C%26nbsp%3B%20When%20I%20read%20the%20%3CA%20title%3D%22MS%20Official%20documentation%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fcreate-an-org-wide-team%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Edocs%3C%2FA%3E%2C%20in%20the%20second%20paragraph%20it%20specifically%20states%3C%2FP%3E%3CP%3E%22%3CSPAN%3EWhen%20an%20org-wide%20team%20is%20created%2C%20all%20global%20admins%20are%20added%20as%20team%20owners%20and%20all%20active%20users%20are%20added%20as%20team%20members.%20Unlicensed%20users%20are%20also%20added%20to%20the%20team.%20The%20first%20time%20an%20unlicensed%20user%20signs%20in%20to%20Teams%2C%20the%20user%20is%20assigned%20a%20Microsoft%20Teams%20Commercial%20Cloud%20Trial%20license.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20do%20not%20even%20want%20that%20to%20happen%20if%20we%20assign%20new%20unlicensed%20users%20to%20the%20other%20domain.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20could%20probably%20remove%20the%20ability%20for%20them%20to%20set%20up%20Trial%20but%20it%20sounds%20like%20a%20lot%20of%20manual%20work.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-748664%22%20slang%3D%22en-US%22%3ERe%3A%20Org-wide%20members%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-748664%22%20slang%3D%22en-US%22%3EHmm!%20True!%20Can%E2%80%99t%20rememver%20seeing%20this%20last%20time%20I%20checked!!%3CBR%20%2F%3E%3CBR%20%2F%3EBut%20you%20can%20disable%20users%20to%20access%20that%20trial%20as%20well%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fiw-trial-teams%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fiw-trial-teams%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EAdam%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-458407%22%20slang%3D%22en-US%22%3EOrg-wide%20members%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-458407%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20creating%20an%20Org-wide%20Team%20it%20pulls%20in%20every%20user%20in%20the%20organization%20and%20keeps%20the%20membership%20up%20to%20date%20with%20Active%20Directory%20as%20users%20join%20and%20leave%20the%20organization.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThen%20John%20starts%20Monday%20in%20the%20marketing%20department%20-%20he%20is%20then%20added%20automatically%20-%20but%20'how'%20-%20what's%20the%20'trigger'%20for%20adding%20john%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-458407%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EIT%20Pro%20Training%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-748831%22%20slang%3D%22en-US%22%3ERe%3A%20Org-wide%20members%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-748831%22%20slang%3D%22en-US%22%3ETrue%2C%20but%20this%20will%20impact%20All%20users%20in%20the%20tenant%2C%20not%20just%20the%20Unlicensed%20ones.%20I%20just%20checked%20and%20my%20settings%20for%20the%20Store%20and%20Trials%20is%20already%20off.%20If%20we%20ever%20decide%20we%20can%20trust%20our%20licensed%20users%20I%20will%20have%20to%20re-visit%20how%20to%20handle%20the%20Unlicensed.%3CBR%20%2F%3E%3CBR%20%2F%3ESo%20now%20the%20discussion%20is%20an%20academic%20one.%20What%20does%20the%20organization%20mean%3F%20Is%20it%20all%20of%20the%20domains%20in%20a%20tenant%20or%20just%20the%20primary%20originally%20set%20with%20the%20onmicrosoft%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-748860%22%20slang%3D%22en-US%22%3ERe%3A%20Org-wide%20members%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-748860%22%20slang%3D%22en-US%22%3EIt%E2%80%99s%20all%20the%20users%20in%20the%20directory%20except%20the%20accounts%20mentioned%20in%20the%20docs..%3C%2FLINGO-BODY%3E
Taen keren
Regular Contributor

When creating an Org-wide Team it pulls in every user in the organization and keeps the membership up to date with Active Directory as users join and leave the organization.

 

Then John starts Monday in the marketing department - he is then added automatically - but 'how' - what's the 'trigger' for adding john?

7 Replies
Solution
They check for every user with a license which could also invluxe accounts not really belonging in a team!

Read more here:

https://office365itpros.com/2018/10/10/org-wide-teams-now-available/amp/

This is from official doc:

https://docs.microsoft.com/en-us/microsoftteams/create-an-org-wide-team

“When an org-wide team is created, all global admins are added as team owners and all active users are added as team members. Users who are disabled for Teams, guest users, and most rooms aren't added to the team. As your organization's directory is updated to include new active users or if users no longer work at your company and their Teams license is disabled, changes are automatically synced and the users are added or removed from the team.”

@adam deltinger   Would you happen to know when they (documentation) says Organization is that to be interpreted or equal to tenant?  The reason I ask is because we have a multi-domain tenant and we have unlicensed users in those domains that we do not want to have in the org-wide Team.  We use that domain specifically to collaborate in SharePoint with pseudo-Guests and it would not be appropriate for them to see everything that the primary domain (onmicrosoft.com) or main tenant sees. I would post this to the docs.microsoft.com site but that requires GitHub account now.

I don’t really get what your question was?
They shouldn’t get added if they aren’t licensed

@adam deltinger  Sorry,  When I read the docs, in the second paragraph it specifically states

"When an org-wide team is created, all global admins are added as team owners and all active users are added as team members. Unlicensed users are also added to the team. The first time an unlicensed user signs in to Teams, the user is assigned a Microsoft Teams Commercial Cloud Trial license."

 

I do not even want that to happen if we assign new unlicensed users to the other domain.

I could probably remove the ability for them to set up Trial but it sounds like a lot of manual work.

Hmm! True! Can’t rememver seeing this last time I checked!!

But you can disable users to access that trial as well:

https://docs.microsoft.com/en-us/microsoftteams/iw-trial-teams

Adam
True, but this will impact All users in the tenant, not just the Unlicensed ones. I just checked and my settings for the Store and Trials is already off. If we ever decide we can trust our licensed users I will have to re-visit how to handle the Unlicensed.

So now the discussion is an academic one. What does the organization mean? Is it all of the domains in a tenant or just the primary originally set with the onmicrosoft?
It’s all the users in the directory except the accounts mentioned in the docs..