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
Copy file name to clipboardExpand all lines: articles/active-directory/develop/active-directory-how-applications-are-added.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.devlang: na
14
14
ms.topic: article
15
15
ms.tgt_pltfrm: na
16
16
ms.workload: identity
17
-
ms.date: 04/18/2018
17
+
ms.date: 06/04/2019
18
18
ms.author: ryanwi
19
19
ms.custom: aaddev
20
20
ms.reviewer: elisol, lenalepa
@@ -29,9 +29,9 @@ There are two representations of applications in Azure AD:
29
29
Service principals generally reference an application object, and one application object can be referenced by multiple service principals across directories.
30
30
31
31
## What are application objects and where do they come from?
32
-
You can manage [application objects](app-objects-and-service-principals.md#application-object) in the Azure portal through the [App Registrations](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ApplicationsListBlade) experience. Application objects describe the application to Azure AD and can be considered the definition of the application, allowing the service to know how to issue tokens to the application based on its settings. The application object will only exist in its home directory, even if it's a multi-tenant application supporting service principals in other directories. The application object may include any of the following (as well as additional information not mentioned here):
32
+
You can manage [application objects](app-objects-and-service-principals.md#application-object) in the Azure portal through the [App Registrations](https://aka.ms/appregistrations) experience. Application objects describe the application to Azure AD and can be considered the definition of the application, allowing the service to know how to issue tokens to the application based on its settings. The application object will only exist in its home directory, even if it's a multi-tenant application supporting service principals in other directories. The application object may include any of the following (as well as additional information not mentioned here):
33
33
* Name, logo, and publisher
34
-
*Reply URLs
34
+
*Redirect URIs
35
35
* Secrets (symmetric and/or asymmetric keys used to authenticate the application)
36
36
* API dependencies (OAuth)
37
37
* Published APIs/resources/scopes (OAuth)
@@ -71,7 +71,7 @@ Like application objects, service principals can also be created through multipl
71
71
* When you subscribe to Office 365 or begin a trial, one or more service principals are created in the directory representing the various services that are used to deliver all of the functionality associated with Office 365.
72
72
* Some Office 365 services like SharePoint create service principals on an ongoing basis to allow secure communication between components including workflows.
73
73
* When an admin adds an application from the app gallery (this will also create an underlying app object)
74
-
* Add an application to use the [Azure AD Application Proxy](https://msdn.microsoft.com/library/azure/dn768219.aspx)
74
+
* Add an application to use the [Azure AD Application Proxy](/azure/active-directory/manage-apps/application-proxy)
75
75
* Connect an application for single sign on using SAML or password single sign-on (SSO)
76
76
* Programmatically via the Azure AD Graph API or PowerShell
77
77
@@ -98,8 +98,8 @@ Applications that you add yourself (represented as **App (yours)** in the diagra
98
98
* Claims transformation rules
99
99
* Attribute mappings (User provisioning)
100
100
* For more detailed information on the service principal and application objects, see the Azure AD Graph REST API reference documentation:
0 commit comments