แก้ไข

แชร์ผ่าน

Modify the accounts supported by an application

  • บทความ

When you registered your application with the Microsoft identity platform, you specified who--which account types--can access it. For example, you might've specified accounts only in your organization, which is a single-tenant app. Or, you might've specified accounts in any organization (including yours), which is a multi-tenant app.

In the following sections, you learn how to modify your app's registration to change who, or what types of accounts, can access the application.

Prerequisites

Change the application registration to support different accounts

Tip

Steps in this article might vary slightly based on the portal you start from.

To specify a different setting for the account types supported by an existing app registration:

  1. Sign in to the Microsoft Entra admin center as at least an Application Developer.

  2. If you have access to multiple tenants, use the Settings icon in the top menu to switch to the tenant containing the app registration from the Directories + subscriptions menu.

  3. Browse to Identity > Applications > App registrations.

  4. Select your application, and then select Manifest to use the manifest editor.

  5. Download the manifest JSON file locally.

  6. Now, specify who can use the application, sometimes referred to as the sign-in audience. Find the signInAudience property in the manifest JSON file and set it to one of the following property values:

    Property value Supported account types Description
    AzureADMyOrg Accounts in this organizational directory only (Microsoft only - Single tenant) All user and guest accounts in your directory can use your application or API. Use this option if your target audience is internal to your organization.
    AzureADMultipleOrgs Accounts in any organizational directory (Any Microsoft Entra directory - Multitenant) All users with a work or school account from Microsoft can use your application or API. This includes schools and businesses that use Office 365. Use this option if your target audience is business or educational customers and to enable multitenancy.
    AzureADandPersonalMicrosoftAccount Accounts in any organizational directory (Any Microsoft Entra directory - Multitenant) and personal Microsoft accounts (such as Skype, Xbox) All users with a work or school, or personal Microsoft account can use your application or API. It includes schools and businesses that use Office 365 as well as personal accounts that are used to sign in to services like Xbox and Skype. Use this option to target the widest set of Microsoft identities and to enable multitenancy.
    PersonalMicrosoftAccount Personal Microsoft accounts only Personal accounts that are used to sign in to services like Xbox and Skype. Use this option to target the widest set of Microsoft identities.

  7. Save your changes to the JSON file locally, then select Upload in the manifest editor to upload the updated manifest JSON file.

Why changing to multi-tenant can fail

Switching an app registration from single- to multi-tenant can sometimes fail due to Application ID URI (App ID URI) name collisions. An example App ID URI is https://contoso.onmicrosoft.com/myapp.

The App ID URI is one of the ways an application is identified in protocol messages. For a single-tenant application, the App ID URI need only be unique within that tenant. For a multi-tenant application, it must be globally unique so Microsoft Entra ID can find the app across all tenants. Global uniqueness is enforced by requiring that the App ID URI's host name matches one of the Microsoft Entra tenant's verified publisher domains.

For example, if the name of your tenant is contoso.onmicrosoft.com, then https://contoso.onmicrosoft.com/myapp is a valid App ID URI. If your tenant has a verified domain of contoso.com, then a valid App ID URI would also be https://contoso.com/myapp. If the App ID URI doesn't follow the second pattern, https://contoso.com/myapp, converting the app registration to multi-tenant fails.

For more information about configuring a verified publisher domain, see Configure a verified domain.

Next steps

Learn more about the requirements for converting an app from single- to multi-tenant.