Forum Discussion
Inconsistent Date Values and Attribute Names
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.
- VasilMichevAug 20, 2019MVP
The AAD one, via Get-AzureADMSGroup.
- Dean_GrossAug 20, 2019Silver Contributor
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.