Apr 15 2019
03:34 AM
- last edited on
Jan 14 2022
04:39 PM
by
TechCommunityAP
Apr 15 2019
03:34 AM
- last edited on
Jan 14 2022
04:39 PM
by
TechCommunityAP
Doing some PowerShell scripting and ran into a problem using
Get-AzureADUser -SearchString "[Really anything here]"
Last week it was fine. I have not updated my AzureADPreview module. Today my search errors out with a Request_UnsupportedQuery with the following message: Unsupported or invalid query filter clause specified for property 'userState' of resource 'User'.
Can anyone confirm or deny this as a local problem (ie, a problem on my machine vs a problem you can replicate on your machine)?
Using AzureADPreview 2.0.2.17
Apr 15 2019 12:25 PM
Yup, same issue here.
Apr 19 2019 06:48 AM
@Mats_Warnolf I'm seeing the same problem for the past couple days. I have a case open with Microsoft, but they're still investigating at this time. I've tested with both the current AzureAD module and the current AzureADPreview module, same result either way.
Apr 20 2019 10:42 AM
Apr 24 2019 09:50 AM
@Mats_Warnolf No update so far, but my ticket is sitting with the AzureAD PowerShell Product Group. I'll reply back again whenever we get resolution on the issue.
May 05 2019 06:00 AM
May 07 2019 06:46 AM
It's crazy that this issue is still an issue for multiple versions of the AzureAD module. I thought it was only occurring for the past week, but it's looking closer to a month now. I had tested 2.0.2.15, .16, and .17 before I found this, all with the same issue. Interestingly the MSOL module version 1.1.183.8 still works. I know it's lazy, but I've been using it to search by SearchString, then taking the object id and pumping it into Get-AzureADUser.
Get-AzureADUser -ObjectId $(Get-MsolUser -SearchString name@domain.tld).ObjectID
May 15 2019 10:10 AM
May 15 2019 11:03 AM
May 15 2019 11:04 AM
May 15 2019 11:06 AM
May 16 2019 12:12 PM
May 16 2019 12:18 PM
Jun 16 2019 12:08 PM
Same problem with AzureADPreview 2.0.2.17 modules
Jun 20 2019 09:59 AM
Jul 22 2019 01:52 PM
Jul 22 2019 02:23 PM
@Josh Vader you should be able to update that any time by running Update-Module as an administrator in PowerShell.