🪲 Handling #EXT# in Get-EntraUser powershell cmdlet.

[SteveMutungi254]

Customer verbatim:

Hello,

I'm working on behalf of a client that has a local ADLDS implementation, they use powershell to create and update users in Azure.
Recently they asked me to help them migrate to the Microsoft.Entra module from old AzureAD and MSOL.

There's a flow that looks for users based on various criteria to create in the Entra tenant.
Most of them are created as guest members and that's fine, but some users are to be invited as guests for whatever reason.

Those users are guests and get the #EXT# added to their upn.
like: john.doe_gmail.com#EXT#@___ etc

The problem occurs when we query Entra for the user based on UPN to find their UserID to update the local ADLDS field for the azure unique id..

We get an unterminated string literal error. Anyone else got experience with that bit?

Internal tracking link: Teams link

Thanks for reporting the bug. Please ensure you've gone through the following checklist before opening an issue:

• Make sure you can reproduce this issue using the latest released version of Microsoft.Entra or Microsoft.Entra.Beta.
• Please search the existing issues to see if there has been a similar issue filed.

Describe the bug

To Reproduce

Steps to reproduce the behavior:

1. Execute -Entra with ...
2. See error at ...

Expected behavior

Debug Output

⚠ ATTENTION: Be sure to remove any sensitive information that may be in the logs.

Debug Output

Module Version

Environment Data

Screenshots

Additional context