Error - Logging - Azure portal

Elman Seferli 0 Reputation points
2024-08-26T06:18:43.8166667+00:00

"Выделенная учетная запись пользователя не существует в клиенте "Microsoft Services" и не может обращаться к приложению "74658136-14ec-4630-ad9b-26e160ff0fc6" в этом клиенте. Необходимо сначала добавить учетную запись в качестве внешнего пользователя для клиента. Используйте другую учетную запись."

I received this error when I wanted to log into my account on the Azure portal

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
21,448 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Akhilesh 8,950 Reputation points Microsoft Vendor
    2024-08-28T14:32:03.7+00:00

    Hi @Elman Seferli

    Thank you for reaching us!

    Error AADSTS16000 is thrown when the user not found in the tenant used for authentication. In your case, this error usually occurs when you sign in to Azure Portal using your personal account which is not added as an external/guest user to an Azure AD tenant. Due to this, you by default get connected to the Microsoft Services tenant.

    Since you are connected to the Microsoft Services tenant as a standard user with restricted access, you cannot perform actions such as creating new users, groups, enterprise applications, and so on. To perform administrative actions, you must have administrative access to the tenant.

    For this purpose, you need to create your own tenant rather than using the Microsoft Services tenant. When you create a new tenant, you by default become the Global Administrator of the new tenant and have full access to all the options in that tenant.

    To create a new tenant, open in-private/incognito browser window (just to avoid SSO), access https://azure.microsoft.com/en-us/free/ to create a free Azure account.

    Once the new account is created, you should be able to see and switch to the new tenant by clicking on the settings icon as highlighted below:

    User's image
    In some cases, the user might already have an active session that uses a different personal account than the one that's intended to be used. Or they have a session that uses their organization account although they intended to use a personal guest account (or vice versa).

    In that scenario, try signing in to the Azure Portal trough a tenant-specific URL using the following format:

    https://portal.azure.com/<tenant domain name>

    Eg.

    https://portal.azure.com/constoso.onmicrosoft.com

    Hope this helps. Do let us know if you any further queries by responding in the comments section.

    Thanks,

    Akhilesh.


    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.