Teams 4.3.1 Get-CSOnlineUser incorrect InterpretedUserType

[paulsysadmin]

trafficstars

Checking the user on older versions of the Teams Module produces AADConnectEnabledOnlineTeamsOnlyUser

Same user on 4.3.1 now showing as DirSyncEnabledOnlineTeamsOnlyUser

[isrumnon]

@paulsysadmin I'll get back to you on this by Monday eod

[isrumnon]

Hi @paulsysadmin the pre-fix "AADConnectEnabledOnline" in the IUT value has now been renamed to "DirSyncEnabledOnline" We're updating documentation to reflect the same

[paulsysadmin]

Thanks @isrumnon . Did I miss something ? I thought DirSync was deprecated and long since replaced by AADConnect ?

[yogkumgit]

@isrumnon

[yogkumgit]

@isrumnon Kindly update, thanks.

[isrumnon]

Hi @paulsysadmin DirSync is deprecated only for TeamsOnly organizations but still remains for Tenants that are Hybrid (have an OpPremise deployment)

[paulsysadmin]

Hi @isrumnon I am aware of that as we are still a hybrid and we use AAD Connect to synchronise objects to Azure. My question is why in all previous versions of the module are the InterpretedUserTypes using AADConnect and now in 4.3.1 they have been switched to DirSync ?

Dirsync was replaced by AADConnect several years ago. Am I missing something ?

[yogkumgit]

@isrumnon

[paulsysadmin]

Any update ?

[paulsysadmin]

Still seeing InterpretedUserType : DirSyncEnabledOnlineTeamsOnlyUser on 4.5.0

[yogkumgit]

@isrumnon Please comment. Thanks

[shivtorov]

@isrumnon, do you know if any work is in progress to fix incorrect InterpretedUserType values reported by Get-CsOnlineUser, when it is used without -Identity parameters. It is broken since v.3.x.x

Taking into account that v.2.6.0 stopped connecting to our tenants mid June, we have no viable means to use this very useful InterpretedUserType value. (Querying Get-CsOnlineUser one-by-one is not an option when dealing with tenants containing even just a few thousand users)

[isrumnon]

Hi @paulsysadmin apologies for the delayed response, Dirsync was replaced by AADConnect a while back but still applies for organizations with an On-Prem presence. For the sudden change for your specific tenant - we'll need to look into it. Will contact you separately regarding the same.

@shivtorov For InterpretedUserType values in the output of Get-CsOnlineUser when it is used without -Identity vs when it is used with -Identity we're currently looking into it and investigating whether it is limited to a few organizations or widespread. Will updated this thread on findings

[shivtorov]

Thanks @isrumnon I worked with several tenants in the last couple of months. The issue is consistent in all of them.

The most visible case for me is the users still homed in on-premises SFBS - for them Get-CsOnlineUser without -Identity always incorrectly report InterpretedUserType = HybridOnline* (e.g. HybridOnlineSfBUserWithTeamsLicense) instead of HybridOnpremSfBUserWithTeamsLicense

[yogkumgit]

@isrumnon Please comment.

[isrumnon]

@yogkumgit am working with both customers offline to resolve

[zaichornik]

Hi @isrumnon,

Are you planning to support again the filtering by whenCreated Azure AD attribute as part of Get-CsOnlineUser command (for human - based accounts)?

I assume that, this slot is intended for the date/time of the first sync (in hybrid mode) / creation (in cloud-only mode) of the user.

Thanks.

[yogkumgit]

@isrumnon Please comment and advise for closure. Thanks

[yogkumgit]

@isrumnon as you are working offline on this, can we clear it from here. Kindly guide us or close it if suitable. Thanks

[isrumnon]

Hi @zaichornik we are not going to add WhenCreated but we will expose WhenChanged but even for this we are not going to expose this property for everyone but you can raise a support ticket to get it enabled for your tenant

[isrumnon]

@yogkumgit we can close this ticket if there are no further questions