SearchString parameter documentation issue for Get-MsolUser (MSOnline module, Office 365)

SearchString parameter documentation issue for Get-MsolUser (MSOnline module, Office 365) by Sarah Dutkiewicz

Active

Type:	Bug
ID:	769500
Opened:	11/1/2012 12:57:54 PM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

In example 5, the text suggests that SearchString searches in the email address and display name.

DisplayName, FirstName, and LastName are separate properties on the user, and it appears that SearchString is specifically searching FirstName and LastName and not the DisplayName field.

Details (expand)

Always Happens

I don't know if this issue existed previously

Finding the bug:
Assuming you have access to the Office 365 cmdlets:
1. Import-Module MSOnline
2. Get-Help Get-MsolUser -examples
- Look at EXAMPLE 5

Reproducing the situation I'm seeing:
Assuming you have adminstrator access to Office 365:
1. Import-Module MSOnline
2. (connect to Office 365)
3. New-MsolUser -UserPrincipalName sjones@yourdomain.com -DisplayName "Sam Jones"
4. New-MsolUser -UserPrincipalName sajones@yourdomain.com -DisplayName "Sarah Jones"
5. Get-MsolUser -SearchString "Jones"
-- At this point, neither of the users created in steps 3 & 4 appear.
6. Set-MsolUser -UserPrincipalName sjones@yourdomain.com -LastName "Jones"
7. Get-MsolUser -SearchString "Jones"
-- At this point, sjones@yourdomain.com should appear
8. Set-MsolUser -UserPrincipalName sajones@yourdomain.com -FirstName "Jones"
9. Get-MsolUser -SearchString "Jones"
-- At this point, both accounts should appear

After step 5, I'd anticipate both accounts from steps 3 & 4 to appear based on the documentation in Example 5.

Can the wording be changed to specifically call out the first name and last name fields, since display name is a separate field altogether?

On the box help (available with get-help)

0 attachments

This bug has also been discussed on the Office 365 community (http://community.office365.com/en-us/forums/150/p/80413/313577.aspx) and the PowerShell forums (http://social.technet.microsoft.com/Forums/en/winserverpowershell/thread/2ef06bd6-059a-4976-a08d-15b9efbeec56).