Powershell attribute to distinguish where a group was provisioned?

%3CLINGO-SUB%20id%3D%22lingo-sub-53351%22%20slang%3D%22en-US%22%3EPowershell%20attribute%20to%20distinguish%20where%20a%20group%20was%20provisioned%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-53351%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20would%20like%20to%20determine%20where%20a%20group%20was%20provisioned%2C%20whether%20it%20was%20Planner%2C%20Teams%2C%20etc.%20%26nbsp%3BIs%20there%20a%20PS%20attribute%20that%20can%20help%20with%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-53351%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%20Groups%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-301895%22%20slang%3D%22en-US%22%3ERe%3A%20Powershell%20attribute%20to%20distinguish%20where%20a%20group%20was%20provisioned%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-301895%22%20slang%3D%22en-US%22%3E%3CP%3ESo%2C%20i'm%20not%20seeing%20the%20attribute%20anymore%2C%20was%20it%20removed%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-282920%22%20slang%3D%22en-US%22%3ERe%3A%20Powershell%20attribute%20to%20distinguish%20where%20a%20group%20was%20provisioned%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-282920%22%20slang%3D%22en-US%22%3EFrank%20as%20mentioned%20before%20we%20do%20not%20have%20a%20timeline%20to%20share%20at%20this%20stage.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-282826%22%20slang%3D%22en-US%22%3ERe%3A%20Powershell%20attribute%20to%20distinguish%20where%20a%20group%20was%20provisioned%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-282826%22%20slang%3D%22en-US%22%3EHi%20Christophe%2C%20can%20you%20please%20be%20a%20little%20more%20specific%20on%20the%20timeline.%20This%20has%20become%20critical%20for%20us%20as%20it%20is%20affecting%20our%20overall%20governance%20practices%20and%20delaying%20further%20deployments%20across%20other%20Office%20365%20apps%2Fservices%20as%20a%20result.%20If%20we%20cannot%20determine%20how%20these%20groups%20are%20provisioned%20(ie.%20from%20which%20app%2Fservice)%2C%20we%20will%20be%20required%20to%20lock%20these%20down%2C%20which%20will%20severely%20impact%20adoption.%20Please%20advise%20ASAP.%20Thank%20you.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-242181%22%20slang%3D%22en-US%22%3ERe%3A%20Powershell%20attribute%20to%20distinguish%20where%20a%20group%20was%20provisioned%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-242181%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%2F67%22%20target%3D%22_blank%22%3E%40Christophe%20Fiessinger%3C%2FA%3E%20may%20I%20ask%20for%20updates%20in%20this%20topic%3F%20Thank%20you!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-173239%22%20slang%3D%22en-US%22%3ERe%3A%20Powershell%20attribute%20to%20distinguish%20where%20a%20group%20was%20provisioned%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-173239%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20updates%20on%20this%3F%26nbsp%3B%20I%20don't%20see%20%22YammerProvisioning%22%20anymore%20but%20now%20see%20%22YammerEmailAddress%22.%26nbsp%3B%20We%20still%20need%20a%20way%20to%20determine%20where%20groups%20are%20created%20for%20admin%20purposes.%26nbsp%3B%20For%20example%20if%20I'm%20trying%20to%20link%20a%20group%20to%20Yammer%20or%20Teams%20I%20need%20to%20find%20a%20way%20to%20determine%20quickly%20where%20it%20was%20provisioned.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-156996%22%20slang%3D%22en-US%22%3ERe%3A%20Powershell%20attribute%20to%20distinguish%20where%20a%20group%20was%20provisioned%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-156996%22%20slang%3D%22en-US%22%3EMukesh%20this%20item%20is%20still%20on%20our%20backlog%20and%20I%20don't%20have%20a%20timeline%20to%20share%20at%20this%20stage.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-156382%22%20slang%3D%22en-US%22%3ERe%3A%20Powershell%20attribute%20to%20distinguish%20where%20a%20group%20was%20provisioned%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-156382%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Christophe%20-%20Do%20you%20have%20any%20further%20update%20on%20this%20item%20%3F%20Is%20ProvisioningOption%20a%20reliable%20value%20to%20do%20this%20check%20%3F%20Actually%20we%20are%20trying%20to%20identify%20and%20differentiate%20the%20O365%20groups%20based%20on%20their%20origin%20so%20this%20would%20be%20helpful.%20Cheers%2C%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBR%2C%3C%2FP%3E%0A%3CP%3EMukesh%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-129874%22%20slang%3D%22en-US%22%3ERe%3A%20Powershell%20attribute%20to%20distinguish%20where%20a%20group%20was%20provisioned%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-129874%22%20slang%3D%22en-US%22%3E%3CP%3Ei%20found%20that%20from%20one%20drive%20they%20have%20option%20to%20create%20group%20even%20they%20don't%20have%20access%20to%20team%20or%20yammer.%20how%20we%20can%20find%20the%20exchange%20provisioning%20for%20this%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-116545%22%20slang%3D%22en-US%22%3ERe%3A%20Powershell%20attribute%20to%20distinguish%20where%20a%20group%20was%20provisioned%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-116545%22%20slang%3D%22en-US%22%3Ethis%20item%20is%20still%20on%20our%20backlog.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-116149%22%20slang%3D%22en-US%22%3ERe%3A%20Powershell%20attribute%20to%20distinguish%20where%20a%20group%20was%20provisioned%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-116149%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20this%20situation%20still%20the%20same.%20Can%20we%20use%20%3CSPAN%3EProvisioningoption%20as%20a%20reliable%20source%20to%20know%20where%20the%20groups%20has%20come%20from%20%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EWe%20have%20different%20values%20as%20below%2C%20i%20heard%20that%20the%20values%20%22ExchangeProvisiongFlags%3A****%22%20will%20be%20changed%20with%20proper%20text%20like%20Teams%2C%20Planner.....%20Is%20the%20value%20%22YammerProvisioning%22%20will%20remain%20as%20it%20is%20%3F%3C%2FSPAN%3E%3C%2FP%3E%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3EExchangeProvisioningFlags%3A2028%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3EYammerProvisioning%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3EExchangeProvisioningFlags%3A227%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3EExchangeProvisioningFlags%3A481%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3EExchangeProvisioningFlags%3A2020%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54160%22%20slang%3D%22en-US%22%3ERe%3A%20Powershell%20attribute%20to%20distinguish%20where%20a%20group%20was%20provisioned%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54160%22%20slang%3D%22en-US%22%3E%3CP%3EToday%20there%20is%20not%20determistic%20way%20of%20knowing%20where%20the%20group%20is%20created%20from%20via%20PowerShell.%20This%20is%20something%20we%20have%20on%20our%20backlog%20and%20don't%20have%20a%20date%20we%20can%20share.%3C%2FP%3E%0A%3CP%3EUsing%20ExchangeProvisioningOption%20is%20NOT%20recommended%20since%20not%20all%20apps%20leverage%20it%20plus%20you%20can%20create%20a%20Teams%20against%20an%20existing%20Group%20for%20instance%20and%20this%20is%20not%20reflected%20in%20the%20script%20below.%3C%2FP%3E%0A%3CP%3EBest%20you%20can%20do%20today%20is%20leverage%20the%20audit%20logs%20instead.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-53825%22%20slang%3D%22en-US%22%3ERe%3A%20Powershell%20attribute%20to%20distinguish%20where%20a%20group%20was%20provisioned%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-53825%22%20slang%3D%22en-US%22%3EThank%20you!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-53702%22%20slang%3D%22en-US%22%3ERe%3A%20Powershell%20attribute%20to%20distinguish%20where%20a%20group%20was%20provisioned%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-53702%22%20slang%3D%22en-US%22%3EAwesome%20Santosh!!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-53697%22%20slang%3D%22en-US%22%3ERe%3A%20Powershell%20attribute%20to%20distinguish%20where%20a%20group%20was%20provisioned%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-53697%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20can%20use%20the%20below%20scripts%20to%20find%20the%20Groups%20that%20were%20provisioned%20by%20Yammer%20and%20Teams.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYammer%20integrated%20Office%20365%26nbsp%3B%20Group%20List%3C%2FP%3E%3CPRE%3EGet-UnifiedGroup%20%7CWhere-Object%20%7B%24_.ProvisioningOption%20-eq%20'YammerProvisioning'%7D%20%7Cselect%20DisplayName%2CAlias%2CProvisioningOption%2CGroupSKU%2CSharePointSiteUrl%2CSharePointDocumentsUrl%2CAccessType%3C%2FPRE%3E%3CP%3ETeams%20group%20List%3C%2FP%3E%3CPRE%3EGet-UnifiedGroup%20%7CWhere-Object%20%7B%24_.ProvisioningOption%20-eq%20'ExchangeProvisioningFlags%3A481'%7D%7Cselect%20DisplayName%2CAlias%2CProvisioningOption%2CGroupSKU%2CSharePointSiteUrl%2CSharePointDocumentsUrl%2CAccessType%3C%2FPRE%3E%3CP%3ESimilarly%20we%20expect%20MSFT%20to%20work%20on%20for%20Planner.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-53586%22%20slang%3D%22en-US%22%3ERe%3A%20Powershell%20attribute%20to%20distinguish%20where%20a%20group%20was%20provisioned%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-53586%22%20slang%3D%22en-US%22%3E%3CP%3EShouldn't%20the%20auditing%20controls%20we%20have%20across%20the%20service%20cover%20that%3F%20Granted%2C%20they%20only%20hold%20data%20for%2090%20days...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-53445%22%20slang%3D%22en-US%22%3ERe%3A%20Powershell%20attribute%20to%20distinguish%20where%20a%20group%20was%20provisioned%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-53445%22%20slang%3D%22en-US%22%3EInteresting%20requirement...curious%20to%20know%20if%20this%20kind%20of%20information%20is%20being%20registered%20Today%20behind%20the%20scenes%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-53359%22%20slang%3D%22en-US%22%3ERe%3A%20Powershell%20attribute%20to%20distinguish%20where%20a%20group%20was%20provisioned%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-53359%22%20slang%3D%22en-US%22%3E%3CP%3EMainly%20for%20reporting%20and%20auditing%20and%20honestly%20just%20curiosity.%20%26nbsp%3BWe%20enabled%20Planner%20soon%20after%20our%20migration%20to%20O365%20so%20I'm%20sure%20the%20majority%20of%20our%20Groups%20were%20created%20there.%20%26nbsp%3BGroup%20creation%20through%20Outlook%2FOWA%20is%20limited%20by%20policy%20(soon%20to%20be%20enabled%20for%20everyone)%20and%20now%20Teams%20is%20enabled%20for%20everyone.%20%26nbsp%3BWe%20want%20to%20get%20a%20handle%20on%20what%20services%20everyone%20is%20using.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGroup%20expiry%20will%20definitely%20help%20so%20we%20are%20looking%20forward%20to%20that!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-53356%22%20slang%3D%22en-US%22%3ERe%3A%20Powershell%20attribute%20to%20distinguish%20where%20a%20group%20was%20provisioned%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-53356%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20is%20no%20such%20attribute%20today.%20Stepping%20back%20what%20are%20you%20trying%20to%20achieve%20with%20this%20information%2C%20what's%20the%20use%20case%20please%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1099058%22%20slang%3D%22en-US%22%3ERe%3A%20Powershell%20attribute%20to%20distinguish%20where%20a%20group%20was%20provisioned%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1099058%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F58%22%20target%3D%22_blank%22%3E%40Vasil%20Michev%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3Echeck%20this%20article%20which%20might%20help%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.nubo.eu%2FReturn-The-Connected-Services-Of-Office365-Groups%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.nubo.eu%2FReturn-The-Connected-Services-Of-Office365-Groups%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

We would like to determine where a group was provisioned, whether it was Planner, Teams, etc.  Is there a PS attribute that can help with this?

19 Replies
Highlighted

There is no such attribute today. Stepping back what are you trying to achieve with this information, what's the use case please?

Highlighted

Mainly for reporting and auditing and honestly just curiosity.  We enabled Planner soon after our migration to O365 so I'm sure the majority of our Groups were created there.  Group creation through Outlook/OWA is limited by policy (soon to be enabled for everyone) and now Teams is enabled for everyone.  We want to get a handle on what services everyone is using.

 

Group expiry will definitely help so we are looking forward to that!

Highlighted
Interesting requirement...curious to know if this kind of information is being registered Today behind the scenes
Highlighted

Shouldn't the auditing controls we have across the service cover that? Granted, they only hold data for 90 days...

Highlighted

You can use the below scripts to find the Groups that were provisioned by Yammer and Teams.

 

Yammer integrated Office 365  Group List

Get-UnifiedGroup |Where-Object {$_.ProvisioningOption -eq 'YammerProvisioning'} |select DisplayName,Alias,ProvisioningOption,GroupSKU,SharePointSiteUrl,SharePointDocumentsUrl,AccessType

Teams group List

Get-UnifiedGroup |Where-Object {$_.ProvisioningOption -eq 'ExchangeProvisioningFlags:481'}|select DisplayName,Alias,ProvisioningOption,GroupSKU,SharePointSiteUrl,SharePointDocumentsUrl,AccessType

Similarly we expect MSFT to work on for Planner.

Highlighted
Highlighted
Highlighted

Today there is not determistic way of knowing where the group is created from via PowerShell. This is something we have on our backlog and don't have a date we can share.

Using ExchangeProvisioningOption is NOT recommended since not all apps leverage it plus you can create a Teams against an existing Group for instance and this is not reflected in the script below.

Best you can do today is leverage the audit logs instead.

Highlighted

Is this situation still the same. Can we use Provisioningoption as a reliable source to know where the groups has come from ?

We have different values as below, i heard that the values "ExchangeProvisiongFlags:****" will be changed with proper text like Teams, Planner..... Is the value "YammerProvisioning" will remain as it is ?

ExchangeProvisioningFlags:2028
YammerProvisioning
ExchangeProvisioningFlags:227
ExchangeProvisioningFlags:481
ExchangeProvisioningFlags:2020
Highlighted
this item is still on our backlog.
Highlighted

i found that from one drive they have option to create group even they don't have access to team or yammer. how we can find the exchange provisioning for this

Highlighted

Hi Christophe - Do you have any further update on this item ? Is ProvisioningOption a reliable value to do this check ? Actually we are trying to identify and differentiate the O365 groups based on their origin so this would be helpful. Cheers, 

 

BR,

Mukesh

Highlighted
Mukesh this item is still on our backlog and I don't have a timeline to share at this stage.
Highlighted

Any updates on this?  I don't see "YammerProvisioning" anymore but now see "YammerEmailAddress".  We still need a way to determine where groups are created for admin purposes.  For example if I'm trying to link a group to Yammer or Teams I need to find a way to determine quickly where it was provisioned.

Highlighted

Hi @Christophe Fiessinger may I ask for updates in this topic? Thank you!

Highlighted
Hi Christophe, can you please be a little more specific on the timeline. This has become critical for us as it is affecting our overall governance practices and delaying further deployments across other Office 365 apps/services as a result. If we cannot determine how these groups are provisioned (ie. from which app/service), we will be required to lock these down, which will severely impact adoption. Please advise ASAP. Thank you.
Highlighted
Frank as mentioned before we do not have a timeline to share at this stage.
Highlighted

So, i'm not seeing the attribute anymore, was it removed?