Skip to content
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

When editing a User, the username field shows an alias rather than the primary username #3477

Open
incedIT opened this issue Jan 27, 2025 · 5 comments
Labels
bug Something isn't working unconfirmed-by-user

Comments

@incedIT
Copy link

incedIT commented Jan 27, 2025

Description

Identity Management, Users, Edit a user. The email address printed in blue under the display name is correct, but the editable username field shows an alias rather than the primary username on the account. If I manually change this field to the correct value and save, it succeeds but the username reverts to the alias. This is cosmetic only, on the View User tab the User Principal Name is correct.

I have encountered this twice now, once with a user where I used CIPP to change the primary username, and now with a user where several years ago (before using CIPP) the primary username was changed in M365 Admin.

Environment data

Non-sponsored
Front: 7.1.1
Back: 7.1.0
Tried Tenant Cache Clear: false
Tried Token Cache Clear: false
@incedIT incedIT added bug Something isn't working unconfirmed-by-user labels Jan 27, 2025
Copy link

Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://docs.cipp.app/
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug."

Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".

@incedIT
Copy link
Author

incedIT commented Jan 27, 2025

I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.

@incedIT
Copy link
Author

incedIT commented Jan 28, 2025

"I confirm that I have checked the documentation thoroughly and believe this to be an actual bug."

@matt-novus
Copy link

Hey IncedIT, we had this issue as well a few years ago and it turns out to be this issue here:

https://learn.microsoft.com/en-us/microsoft-365/troubleshoot/miscellaneous/reports-show-anonymous-user-name

If that is indeed what's causing your issue, then that can be resolved by implementing the first standard listed on this page https://docs.cipp.app/user-documentation/tenant/standards/list-standards/global-standards

Enable Usernames instead of pseudo anonymised names in reports

Microsoft announced some APIs and reports no longer return names, to comply with compliance and legal requirements in specific countries. This proves an issue for a lot of MSPs because those reports are often helpful for engineers. This standard applies a setting that shows usernames in those API calls / reports.

Update-MgBetaAdminReportSetting -BodyParameter @{displayConcealedNames = $true} AnonReportDisable

@incedIT
Copy link
Author

incedIT commented Jan 29, 2025

Hey IncedIT, we had this issue as well a few years ago and it turns out to be this issue here:

https://learn.microsoft.com/en-us/microsoft-365/troubleshoot/miscellaneous/reports-show-anonymous-user-name

If that is indeed what's causing your issue, then that can be resolved by implementing the first standard listed on this page https://docs.cipp.app/user-documentation/tenant/standards/list-standards/global-standards

Enable Usernames instead of pseudo anonymised names in reports

Microsoft announced some APIs and reports no longer return names, to comply with compliance and legal requirements in specific countries. This proves an issue for a lot of MSPs because those reports are often helpful for engineers. This standard applies a setting that shows usernames in those API calls / reports.

Update-MgBetaAdminReportSetting -BodyParameter @{displayConcealedNames = $true} AnonReportDisable

Thanks for the info. Unfortunately, I already have display concealed user, group and site names disabled in M365 admin, so that isn't the cause in this case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working unconfirmed-by-user
Projects
None yet
Development

No branches or pull requests

2 participants