You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Quickstart: Register an application with the Microsoft identity platform
20
20
21
-
Enterprise developers and software-as-a-service (SaaS) providers can develop commercial cloud services or line-of-business applications that can be integrated with Microsoft identity platform to provide secure sign-in and authorization for their services.
21
+
In this quickstart, you register an application using the **App registrations** experience in the Azure portal. Your app is integrated with the Microsoft identity platform. Enterprise developers and software-as-a-service (SaaS) providers can develop commercial cloud services or line-of-business applications that can be integrated with Microsoft identity platform. Integration provides secure sign-in and authorization for such services.
22
22
23
-
This quickstart shows you how to add and register an application using the **App registrations** experience in the Azure portal so that your app can be integrated with the Microsoft identity platform. To learn more about the new features and improvements in the new app registrations experience, see [this blog post](https://developer.microsoft.com/graph/blogs/new-app-registration/).
23
+
## Prerequisites
24
+
25
+
* An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio).
24
26
25
27
## Register a new application using the Azure portal
26
28
27
29
1. Sign in to the [Azure portal](https://portal.azure.com) using either a work or school account or a personal Microsoft account.
28
-
1. If your account gives you access to more than one tenant, select your account in the top right corner, and set your portal session to the Azure AD tenant that you want.
29
-
1. Search for and select **Azure Active Directory**. On the **Active Directory** page, select **App registrations** and then select **New registration**.
30
-
1. When the **Register an application** page appears, enter your application's registration information:
30
+
1. If your account gives you access to more than one tenant, select your account in the upper right corner. Set your portal session to the Azure AD tenant that you want.
31
+
1. Search for and select **Azure Active Directory**. Under **Manage**, select **App registrations**.
32
+
1. Select **New registration**.
33
+
1. In **Register an application**, enter a meaningful application name to display to users.
34
+
1. Specify who can use the application, as follows:
31
35
32
-
-**Name** - Enter a meaningful application name that will be displayed to users of the app.
33
-
-**Supported account types** - Select which accounts you would like your application to support.
36
+
| Supported account types | Description |
37
+
|-------------------------|-------------|
38
+
|**Accounts in this organizational directory only**| Select this option if you're building a line-of-business (LOB) application. This option isn't available if you're not registering the application in a directory.<br><br>This option maps to Azure AD only single-tenant.<br><br>This option is the default unless you're registering the app outside of a directory. In cases where the app is registered outside of a directory, the default is Azure AD multi-tenant and personal Microsoft accounts. |
39
+
|**Accounts in any organizational directory**| Select this option if you would like to target all business and educational customers.<br><br>This option maps to an Azure AD only multi-tenant.<br><br>If you registered the app as Azure AD only single-tenant, you can update it to be Azure AD multi-tenant and back to single-tenant through the **Authentication** page. |
40
+
|**Accounts in any organizational directory and personal Microsoft accounts**| Select this option to target the widest set of customers.<br><br>This option maps to Azure AD multi-tenant and personal Microsoft accounts.<br><br>If you registered the app as Azure AD multi-tenant and personal Microsoft accounts, you can't change this setting in the UI. Instead, you must use the application manifest editor to change the supported account types. |
34
41
35
-
| Supported account types | Description |
36
-
|-------------------------|-------------|
37
-
|**Accounts in this organizational directory only**| Select this option if you're building a line-of-business (LOB) application. This option is not available if you're not registering the application in a directory.<br><br>This option maps to Azure AD only single-tenant.<br><br>This is the default option unless you're registering the app outside of a directory. In cases where the app is registered outside of a directory, the default is Azure AD multi-tenant and personal Microsoft accounts. |
38
-
|**Accounts in any organizational directory**| Select this option if you would like to target all business and educational customers.<br><br>This option maps to an Azure AD only multi-tenant.<br><br>If you registered the app as Azure AD only single-tenant, you can update it to be Azure AD multi-tenant and back to single-tenant through the **Authentication** blade. |
39
-
|**Accounts in any organizational directory and personal Microsoft accounts**| Select this option to target the widest set of customers.<br><br>This option maps to Azure AD multi-tenant and personal Microsoft accounts.<br><br>If you registered the app as Azure AD multi-tenant and personal Microsoft accounts, you cannot change this in the UI. Instead, you must use the application manifest editor to change the supported account types. |
42
+
1. Under **Redirect URI (optional)**, select the type of app you're building: **Web** or **Public client (mobile & desktop)**. Then enter the redirect URI, or reply URL, for your application.
40
43
41
-
-**Redirect URI (optional)** - Select the type of app you're building, **Web** or **Public client (mobile & desktop)**, and then enter the redirect URI (or reply URL) for your application.
42
-
- For web applications, provide the base URL of your app. For example, `https://localhost:31544` might be the URL for a web app running on your local machine. Users would use this URL to sign in to a web client application.
43
-
- For public client applications, provide the URI used by Azure AD to return token responses. Enter a value specific to your application, such as `myapp://auth`.
44
+
* For web applications, provide the base URL of your app. For example, `https://localhost:31544` might be the URL for a web app running on your local machine. Users would use this URL to sign in to a web client application.
45
+
* For public client applications, provide the URI used by Azure AD to return token responses. Enter a value specific to your application, such as `myapp://auth`.
44
46
45
-
To see specific examples for web applications or native applications, check out our [quickstarts](https://docs.microsoft.com/azure/active-directory/develop).
47
+
For examples for web applications or native applications, see the quickstarts in [Microsoft identity platform](https://docs.microsoft.com/azure/active-directory/develop).
46
48
47
49
1. When finished, select **Register**.
48
50
49
-
[](./media/quickstart-add-azure-ad-app-preview/new-app-registration-expanded.png#lightbox)
51
+

50
52
51
-
Azure AD assigns a unique application (client) ID to your app, and you're taken to your application's **Overview** page. To add additional capabilities to your application, you can select other configuration options including branding, certificates and secrets, API permissions, and more.
53
+
Azure AD assigns a unique application, or client, ID to your app. The portal opens your application's **Overview** page. To add capabilities to your application, you can select other configuration options including branding, certificates and secrets, API permissions, and more.
52
54
53
-
[](./media/quickstart-add-azure-ad-app-preview/new-app-overview-page-expanded.png#lightbox)
55
+

54
56
55
57
## Next steps
56
58
57
-
- Learn about the [permissions and consent](v2-permissions-and-consent.md).
58
-
- To enable additional configuration features in your application registration, such as credentials and permissions, and enable sign-in for users from other tenants, see these quickstarts:
59
-
-[Configure a client application to access web APIs](quickstart-configure-app-access-web-apis.md)
60
-
-[Configure an application to expose web APIs](quickstart-configure-app-expose-web-apis.md)
61
-
-[Modify the accounts supported by an application](quickstart-modify-supported-accounts.md)
62
-
- Choose a [quickstart](https://docs.microsoft.com/azure/active-directory/develop) to quickly build an app and add functionality like getting tokens, refreshing tokens, signing in a user, displaying some user info, and more.
63
-
- Learn more about the two Azure AD objects that represent a registered application and the relationship between them, see [Application objects and service principal objects](app-objects-and-service-principals.md).
64
-
- Learn more about the branding guidelines you should use when developing apps, see [Branding guidelines for applications](howto-add-branding-in-azure-ad-apps.md).
59
+
Advance to the next article to learn how to access web APIs.
60
+
> [!div class="nextstepaction"]
61
+
> [Quickstart: Configure a client application to access web APIs](quickstart-configure-app-access-web-apis.md)
62
+
63
+
* To learn about the permissions, see [Permissions and consent in the Microsoft identity platform endpoint](v2-permissions-and-consent.md).
64
+
65
+
* To expose web APIs, see [Quickstart: Configure an application to expose web APIs](quickstart-configure-app-expose-web-apis.md).
66
+
67
+
* To manage supported accounts, see [Quickstart: Modify the accounts supported by an application](quickstart-modify-supported-accounts.md).
68
+
69
+
* To build an app and add functionality, see the quickstarts in [Microsoft identity platform](https://docs.microsoft.com/azure/active-directory/develop).
70
+
71
+
* To learn more about the two Azure AD objects that represent a registered application and the relationship between them, see [Application objects and service principal objects](app-objects-and-service-principals.md).
72
+
73
+
* To learn more about the branding guidelines you should use when developing apps, see [Branding guidelines for applications](howto-add-branding-in-azure-ad-apps.md).
0 commit comments