Skip to content

Bug in Update-MgUser: Lowercase "rn" in String Causes Truncated Output in Entra #3183

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
benpaddick1 opened this issue Feb 25, 2025 · 1 comment
Labels
status:duplicate A duplicate issue type:bug A broken experience

Comments

@benpaddick1
Copy link

Describe the bug

When using the Update-MgUser cmdlet from the latest module update, there appears to be an issue where any user field containing the lowercase string "rn" is truncated at that point when updated in Entra. If the same string is provided in uppercase ("RN"), the issue does not occur.

Expected behavior

Expected Behaviour:

The FaxNumber field should display the complete string:

"Test string with rn in it"

Actual Behaviour:

The FaxNumber field shows the truncated string:

"Test string with in it"

How to reproduce

Steps to Reproduce:

Update-MgUser -UserId $User.Id -FaxNumber "Test string with rn in it"

Check the updated FaxNumber field in Entra.

SDK Version

No response

Latest version known to work for scenario above?

No response

Known Workarounds

Workaround:

Changing "rn" to uppercase ("RN") prevents the truncation:

Update-MgUser -UserId $User.Id -FaxNumber "Test string with RN in it"

Impact

This issue could affect user updates where "rn" appears naturally in strings, potentially leading to data loss or corruption in user attributes.

Can anyone else reproduce the error.

Debug output

Click to expand log ```
</details>


### Configuration

Windows 10 Build 19405
Module: 2.26.0

### Other information

_No response_
@benpaddick1 benpaddick1 added status:waiting-for-triage An issue that is yet to be reviewed or assigned type:bug A broken experience labels Feb 25, 2025
@timayabi2020
Copy link
Contributor

timayabi2020 commented Feb 26, 2025

Hi @benpaddick1 apologies for this experience. Please update to version 2.26.1. I'll also close this as a duplicate of a similar issue that had been reported here #3178

Image

@timayabi2020 timayabi2020 added status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close status:duplicate A duplicate issue and removed status:waiting-for-triage An issue that is yet to be reviewed or assigned status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close labels Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:duplicate A duplicate issue type:bug A broken experience
Projects
None yet
Development

No branches or pull requests

2 participants