question

AlbertoLeonor-7672 avatar image
0 Votes"
AlbertoLeonor-7672 asked ·

Azure AD: Main User Corrupted

I was working well with my Azure credential before the Azure AD outage on Monday 15, 2021. Today I can access well to the Azure Portal but when I connect via PowerShell I found that it's not connecting to the correct Tenantid. When I look for the user in Azure AD I see the user has been altered showing a username with a weir structure and #EXT# in the middle.

The issue is that the user can access well to the AZ portal, can't access to my corresponding Tenantid via PowerShell and the user see changed.

Any idea?
Thanks,

78466-azureerror3.jpg

78480-image.png


78532-image.png


azure-active-directory
azureerror3.jpg (17.7 KiB)
image.png (1.8 KiB)
image.png (22.2 KiB)
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

amanpreetsingh-msft avatar image
0 Votes"
amanpreetsingh-msft answered ·

Hi @AlbertoLeonor-7672 · The text #EXT# in the UPN refers to external (guest) user. All guest users' UPNs are in this format. It doesn't mean that user is corrupted. It is sometimes confusing when we see User type as member for these users, which happens when we convert guest user to member user.

A user can be added as guest user to multiple tenants and when we connect via Connect-AzureAD PowerShell cmdlet, it gets connected to one of those tenants. In order to connect to a specific tenant, we need specify tenant name by using -TenantId switch, when connecting to Azure AD, as shown below:

 Connect-AzureAD -TenantId tenant_name.onmicrosoft.com

You can also specify the TenantID as GUID as well in the cmdlet.


Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

· 3 ·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks @amanpreetsingh-msft it help me to connect to the correct tenant in PowerShell cmdlet.

My question is, if it was the main user, the user I create the Azure Account, why it convert like a guest?

There's a way I can convert this user like it was in the past?

Thanks,

0 Votes 0 ·

Hi @AlbertoLeonor-7672 · There is no change happened in the user account. If you use user@outlook.com to create a tenant, a user will always be created with UPN: user_outlook.com#ext#@yourtenant.onmicrosoft.com in Azure AD. In the past, portal used to display Alternate email attribute of the guest users as UPN but now it is showing the actual UPN. I am experiencing the same behavior in my tenant as well. There seems to be some change happened which impacted the way in which the information was displayed in the portal. This won't cause any functional impact.

0 Votes 0 ·

Ok understand.

And I always will need to specify tenant name while connecting via PowerShell?

Thanks,

0 Votes 0 ·