Home

Inconsistent Date Values and Attribute Names

%3CLINGO-SUB%20id%3D%22lingo-sub-813315%22%20slang%3D%22en-US%22%3EInconsistent%20Date%20Values%20and%20Attribute%20Names%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-813315%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20I%20use%20the%20Graph%20Explorer%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fgraph.microsoft.com%2Fv1.0%2Fgroups%2F%7BID%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgraph.microsoft.com%2Fv1.0%2Fgroups%2F%7BID%3C%2FA%3E%7D%20it%20returns%26nbsp%3B%20%22createdDateTime%22%3A%20%222016-03-17T13%3A37%3A42Z%22%2C%3C%2FP%3E%3CP%3EWhen%20I%20use%26nbsp%3BGet-UnifiedGroup%20-Identity%20ID%20-IncludeAllProperties%20it%20returns%3C%2FP%3E%3CP%3EWhenCreated%20%3A%208%2F9%2F2018%2012%3A40%3A08%20PM.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20come%20what%20appears%20to%20be%20the%20same%20attribute%2C%20has%202%20different%20names%20and%202%20different%20values%20for%20the%20same%20group%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-813315%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20AD%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-813353%22%20slang%3D%22en-US%22%3ERe%3A%20Inconsistent%20Date%20Values%20and%20Attribute%20Names%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-813353%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20guessing%20it's%20because%20they%20represent%20different%20objects%20-%20the%20%22parent%22%20object%20in%20AAD%20and%20the%20workload-specific%20representation%20in%20ExO.%20In%20particular%2C%20if%20you%20have%20some%20very%20old%20ones%2C%20you%20might%20see%20that%20they%20all%20have%20a%20very%20similar%20creation%20dates%20in%20ExO%2C%20corresponding%20to%20the%20time%20around%20which%20Microsoft%20changed%20their%20recipient%20type%2C%20while%20the%20AAD%20value%20is%20a%20very%20different%20one.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-813355%22%20slang%3D%22en-US%22%3ERe%3A%20Inconsistent%20Date%20Values%20and%20Attribute%20Names%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-813355%22%20slang%3D%22en-US%22%3EIs%20there%20a%20powershell%20module%2Fcmdlet%20that%20returns%20the%20same%20data%20as%20the%20Graph%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-813599%22%20slang%3D%22en-US%22%3ERe%3A%20Inconsistent%20Date%20Values%20and%20Attribute%20Names%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-813599%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20AAD%20one%2C%20via%26nbsp%3B%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EGet-AzureADMSGroup%3C%2FFONT%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-813611%22%20slang%3D%22en-US%22%3ERe%3A%20Inconsistent%20Date%20Values%20and%20Attribute%20Names%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-813611%22%20slang%3D%22en-US%22%3E%3CP%3Ethanks%2C%20so%20what%20is%20the%20difference%20between%20that%20one%20and%20Get-AzureADGroup%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20found%20a%20note%20stating%20that%20%22%3CSPAN%3EGoing%20forward%2C%20all%20cmdlets%20that%20call%20Microsoft%20Graph%20will%20have%20%E2%80%9CMS%E2%80%9D%20in%20their%20cmdlet%20names%2C%20as%20in%20%E2%80%9CGet-AzureADMSGroup%E2%80%9D.%20The%20cmdlets%20that%20call%20Azure%20AD%20Graph%20will%20not%20change%2C%20so%20there%20is%20also%20a%20%E2%80%9CGet-AzureADGroup%E2%80%9D%20cmdlet.%22%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EUnfortunately%2C%20the%20docs%20at%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fazuread%2FGet-AzureADMSGroup%3Fview%3Dazureadps-2.0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fazuread%2FGet-AzureADMSGroup%3Fview%3Dazureadps-2.0%3C%2FA%3E%26nbsp%3Bdon't%20make%20any%20mention%20of%20this.%20These%20modules%20and%20their%20associated%20documentation%20are%20still%20very%20confusing%20to%20me.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Dean Gross
Respected Contributor

When I use the Graph Explorer https://graph.microsoft.com/v1.0/groups/{ID} it returns  "createdDateTime": "2016-03-17T13:37:42Z",

When I use Get-UnifiedGroup -Identity ID -IncludeAllProperties it returns

WhenCreated : 8/9/2018 12:40:08 PM.

 

How come what appears to be the same attribute, has 2 different names and 2 different values for the same group?

4 Replies

I'm guessing it's because they represent different objects - the "parent" object in AAD and the workload-specific representation in ExO. In particular, if you have some very old ones, you might see that they all have a very similar creation dates in ExO, corresponding to the time around which Microsoft changed their recipient type, while the AAD value is a very different one.

Is there a powershell module/cmdlet that returns the same data as the Graph?

The AAD one, via Get-AzureADMSGroup.

thanks, so what is the difference between that one and Get-AzureADGroup?

 

I found a note stating that "Going forward, all cmdlets that call Microsoft Graph will have “MS” in their cmdlet names, as in “Get-AzureADMSGroup”. The cmdlets that call Azure AD Graph will not change, so there is also a “Get-AzureADGroup” cmdlet." 

 

Unfortunately, the docs at https://docs.microsoft.com/en-us/powershell/module/azuread/Get-AzureADMSGroup?view=azureadps-2.0 don't make any mention of this. These modules and their associated documentation are still very confusing to me. 

Related Conversations
Extentions Synchronization
Deleted in Discussions on
3 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
36 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
9 Replies