Remove case sensitive for "Search to add members" in Distribution lists
When adding members to any groups like 365 it gives you the option to search for members in any case, however when trying to add a member to a "Distribution list" nothing is returned, unless you type the correct case of their name.
Please remove case sensitive for "Search to add members" in Distribution lists. No other "group" has this and is inconsistent with the use of 365 admin portal
Seng U commented
@Tim, it may be that your lowercase email addresses may have upper case display names. It will search both email and display name strings. Still, search result shouldn't be case sensitive.
Calum Morrison commented
User@mydomain.com is the same as firstname.lastname@example.org so why have case sensitive searches unless MS is running the backend on Unix..? Seriously, it's pointless at best; it's cost me time and hassle, and it's cost MS support time as I tried to get to the bottom of it. If it was even documented with a tool tip it would at least just be an inconvenience. Struggling to see what the benefit is.
Interestingly, I've got multiple similar email addresses in the GAL, some all in lower case, some starting with an uppercase letter. If I search using a partial string with lower case, it only finds matches with lower case. If I make the first character in my search string upper case, it finds *both* the lower case and upper case results. This *can't* be a feature... Just saying.
Search for "test" returns 1 and 2, search for "Test" returns all three.
I opened a support case with Microsoft on this issue because I assumed that it couldn't be this simple, but no - He confirmed that for adding users to any lists, groups, etc., it is case sensitive. This should be a simple fix, but I have very little faith Microsoft will fix it quickly.
This is also true for Shared mailboxes. Previously you could search based on UPN but now it only works on Users Proper name and is case sensitive and requires punctuation. When you have over 300K current users this is a bit tedious. UPN's are unique and are only 9 characters for us. Prior to Jan 1 2019 approximately this was the key search field.
Ah good to see this has been raised. I came across the issue searching for existing members in a Distribution List. I agree that the inconsistency is frustrating. I was going to submit the following after MS Support identified the issue as a design decision (wtf?!!), so will add as a comment in support of your "suggestion" - even though I think we all agree that the distinction between "omission by design" (the Microsoft opinion on this) and a "bug" is a matter of perspective!
Improve search for a Group Member within a Distribution List
Office365 Admin Centre Groups - Searching for a Group Member within a Distribution List fails to find the User when: (a) Searching by User's last name (b) Searching by User's first name without capitilisation that matches how user name is capitalised. This search behaviour is inconsistent with general User search and leads to false negatives. Any chance the search behaviour could be improved?
Brendan Walker commented
I don't even know what to write here I'm so confused by the logic here. Every other part of the portal and Microsoft products (Active directory) Ignore Case Sensitivity. What's the point!?
I raised a support case for this and the Microsoft Support Tech was like "oh....erm Yeah that's weird, I found someone raised a community post about this, you should express your Opinion there" So here I am, expressing my opinion about this illogical inconsistency.
"We don't want people to use Distribution lists anymore so we'll start making them really weird" Perhaps?
I have the same problem, and it's incredibly frustrating. The whole O365 Admin Center is affected as soon as a search function is chosen to entitle a user. The usual procedure in searching field without paying attention to the case always leads to the error message: No result found
Carol Moreno commented
I am having the same issue and it is incredibly frustrating. Nowhere else have I encountered cases-sensitivity as an issue with the search function. This should be addressed for better consistency.