Quickstart: Register an app with the Azure Active Directory v1.0 endpoint
Enterprise developers and software-as-a-service (SaaS) providers can develop commercial cloud services or line-of-business applications, that can be integrated with Azure Active Directory (Azure AD) to provide secure sign-in and authorization for their services. To integrate an application or service with Azure AD, a developer must first register the application with Azure AD.
Any application that wants to use the capabilities of Azure AD must first be registered in an Azure AD tenant. This registration process involves giving Azure AD details about your application, such as the URL where it’s located, the URL to send replies after a user is authenticated, the URI that identifies the app, and so on.
This quickstart shows you how to add and register an application in Azure AD using the existing App registrations experience in the Azure portal.
Registering a new app? Try out the new App registrations (Preview) experience in the Azure portal. See Register an app (Preview) to get started.
To get started, make sure have an Azure AD tenant that you can use to register your apps to. If you don't already have a tenant, learn how to get one.
Register a new application using the Azure portal
Sign in to the Azure portal.
If your account gives you access to more than one, select your account in the top right corner, and set your portal session to the desired Azure AD tenant.
In the left-hand navigation pane, select the Azure Active Directory service.
Select App registrations and then select New application registration.
When the Create page appears, enter your application's registration information:
Name: Enter a meaningful application name
- Select Native for client applications that are installed locally on a device. This setting is used for OAuth public native clients.
- Select Web app/API for client applications and resource/API applications that are installed on a secure server. This setting is used for OAuth confidential web clients and public user-agent-based clients. The same application can also expose both a client and resource/API.
Sign-On URL: For "Web app / API" applications, provide the base URL of your app. For example,
http://localhost:31544might 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.
Redirect URI: For "Native" applications, provide the URI used by Azure AD to return token responses. Enter a value specific to your application, for example
If you'd like specific examples for web applications or native applications, check out the Quickstarts in our documentation.
When finished, select Create.
Azure AD assigns a unique Application ID to your application, and you're taken to your application's main registration page. Depending on whether your application is a web or native application, different options are provided to add additional capabilities to your application.
By default, a newly registered web application is configured to allow only users from the same tenant to sign in to your application.
- See Azure AD consent framework for an overview of consent.
- To enable additional configuration features in your application registration--such as credentials, permissions, enable sign-in for users from other tenants--see Update an application in Azure AD.
- 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.
- Learn more about the branding guidelines you should use when developing applications with Azure Active Directory, see Branding guidelines for applications.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.