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/howto-app-gallery-listing.md
+52-56Lines changed: 52 additions & 56 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,9 +22,9 @@ ms.custom: aaddev, seoapril2019
22
22
ms.collection: M365-identity-device-management
23
23
---
24
24
25
-
# How to: List your application in the Azure Active Directory application gallery
25
+
# List your application in the Azure Active Directory application gallery
26
26
27
-
This article shows how to list an application in the Azure AD application gallery, implement single sign-on (SSO), and manage the listing.
27
+
This article shows how to list an application in the Azure Active Directory (Azure AD) application gallery, implement single sign-on (SSO), and manage the listing.
28
28
29
29
## What is the Azure AD application gallery?
30
30
@@ -33,106 +33,102 @@ This article shows how to list an application in the Azure AD application galler
33
33
- A quick search finds your application in the gallery.
34
34
- Free, Basic, and Premium Azure AD customers can all use this integration.
35
35
- Mutual customers get a step-by-step configuration tutorial.
36
-
- Customers who use SCIM can use provisioning for the same app.
36
+
- Customers who use the System for Cross-domain Identity Management (SCIM) can use provisioning for the same app.
37
37
38
38
## Prerequisites
39
39
40
-
- For Federated applications (Open ID and SAML/WS-Fed), the application must support the SaaS model for getting listed in Azure AD gallery. The enterprise gallery applications should support multiple customer configurations and not any specific customer.
41
-
42
-
- For Open ID Connect, the application should be multi-tenanted and [Azure AD consent framework](consent-framework.md) should be properly implemented for the application. The user can send the login request to a common endpoint so that any customer can provide consent to the application. You can control user access based on the tenant ID and the user's UPN received in the token.
43
-
44
-
- For SAML 2.0/WS-Fed, your application needs to have the capability to do the SAML/WS-Fed SSO integration in SP or IDP mode. Please ensure this is working correctly before submitting the request.
45
-
46
-
- For password SSO, please ensure that your application supports form authentication so that password vaulting can be done to get single sign-on work as expected.
47
-
48
-
- Need a permanent account for testing with atleast 2 users registered.
40
+
- For federated applications (Open ID and SAML/WS-Fed), the application must support the software-as-a-service (SaaS) model for getting listed in the Azure AD app gallery. The enterprise gallery applications must support multiple customer configurations and not any specific customer.
41
+
- For Open ID Connect, the application must be multitenanted and the [Azure AD consent framework](consent-framework.md) must be properly implemented for the application. The user can send the sign-in request to a common endpoint so that any customer can provide consent to the application. You can control user access based on the tenant ID and the user's UPN received in the token.
42
+
- For SAML 2.0/WS-Fed, your application must have the capability to do the SAML/WS-Fed SSO integration in SP or IDP mode. Make sure this capability is working correctly before you submit the request.
43
+
- For password SSO, make sure that your application supports form authentication so that password vaulting can be done to get single sign-on to work as expected.
44
+
- You need a permanent account for testing with at least two users registered.
49
45
50
46
## Submit the request in the portal
51
47
52
-
After you've tested that your application integration works with Azure AD, submit your request for access on our[Application Network Portal](https://microsoft.sharepoint.com/teams/apponboarding/Apps). If you have an Office 365 account, use that to sign in to this portal. If not, use your Microsoft account (such as Outlook or Hotmail) to sign in.
48
+
After you've tested that your application integration works with Azure AD, submit your request for access in the[Application Network portal](https://microsoft.sharepoint.com/teams/apponboarding/Apps). If you have an Office 365 account, use that to sign in to this portal. If not, use your Microsoft account, such as Outlook or Hotmail, to sign in.
53
49
54
-
If the following page appears after sign in, contact the [Azure AD SSO Integration Team](<mailto:[email protected]>) and provide the email account which you want to use for submitting the request. Then Azure AD team will add the account in the Microsoft Application Network Portal.
50
+
If the following page appears after you sign in, contact the [Azure AD SSO Integration Team](<mailto:[email protected]>). Provide the email account that you want to use for submitting the request. The Azure AD team will add the account in the Microsoft Application Network portal.
55
51
56
-
52
+
57
53
58
-
Once the account is added, you can sign in to the Microsoft Application Network Portal.
54
+
After the account is added, you can sign in to the Microsoft Application Network portal.
59
55
60
-
And if the following page appears after sign in, provide a business justification for needing access in the text box, and then select **Request Access**.
56
+
If the following page appears after you sign in, provide a business justification for needing access in the text box. Then select **Request Access**.
61
57
62
-
58
+
63
59
64
-
Our team reviews the details and gives you access accordingly. Once your request is approved, you can sign in to the portal and submit the request by clicking the **Submit Request (ISV)** tile form the home page.
60
+
Our team reviews the details and gives you access accordingly. After your request is approved, you can sign in to the portal and submit the request by selecting the **Submit Request (ISV)** tile on the home page.
65
61
66
-
62
+
67
63
68
64
> [!NOTE]
69
-
> If you have any issues regarding access, contact the [Azure AD SSO Integration Team](<mailto:[email protected]>).
65
+
> If you have any issues with access, contact the [Azure AD SSO Integration Team](<mailto:[email protected]>).
70
66
71
-
## Implementing SSO using federation protocol
67
+
## Implement SSO by using the federation protocol
72
68
73
-
To list an application in the Azure AD app gallery, you first need to implement one of the following federation protocols supported by Azure AD and agree with Azure AD application Gallery terms and conditions. Read the terms and conditions of the Azure AD application gallery from [here](https://azure.microsoft.com/support/legal/active-directory-app-gallery-terms/).
69
+
To list an application in the Azure AD app gallery, you first need to implement one of the following federation protocols supported by Azure AD. You also need to agree to the Azure AD application gallery terms and conditions. Read the terms and conditions of the Azure AD application gallery on [this website](https://azure.microsoft.com/support/legal/active-directory-app-gallery-terms/).
74
70
75
-
-**OpenID Connect**: To integrate your application with Azure AD using the Open ID Connect protocol, follow the [developers' instructions](authentication-scenarios.md).
71
+
-**OpenID Connect**: To integrate your application with Azure AD by using the Open ID Connect protocol, follow the [developers' instructions](authentication-scenarios.md).
76
72
77
-
73
+
78
74
79
-
* If you want to add your application to list in the gallery using OpenID Connect, select **OpenID Connect & OAuth 2.0** as above.
80
-
* If you have any issues regarding access, contact the [Azure AD SSO Integration Team](<mailto:[email protected]>).
75
+
* If you want to add your application to list in the gallery by using OpenID Connect, select **OpenID Connect & OAuth 2.0** as shown.
76
+
* If you have any issues with access, contact the [Azure AD SSO Integration Team](<mailto:[email protected]>).
81
77
82
-
-**SAML 2.0** or **WS-Fed**: If your app supports SAML 2.0, you can integrate it directly with an Azure AD tenant by using the [instructions to add a custom application](../active-directory-saas-custom-apps.md).
78
+
-**SAML 2.0** or **WS-Fed**: If your app supports SAML 2.0, you can integrate it directly with an Azure AD tenant by following the [instructions to add a custom application](../active-directory-saas-custom-apps.md).
83
79
84
-
80
+
85
81
86
-
* If you want to add your application to list in the gallery using **SAML 2.0** or **WS-Fed**, select **SAMl 2.0/WS-Fed** as above.
87
-
* If you have any issues regarding access, contact the [Azure AD SSO Integration Team](<mailto:[email protected]>).
82
+
* If you want to add your application to list in the gallery by using **SAML 2.0** or **WS-Fed**, select **SAML 2.0/WS-Fed** as shown.
83
+
* If you have any issues with access, contact the [Azure AD SSO Integration Team](<mailto:[email protected]>).
88
84
89
-
## Implementing SSO using password SSO
85
+
## Implement SSO by using the password SSO
90
86
91
-
Create a web application that has an HTML sign-in page to configure [password-based single sign-on](../manage-apps/what-is-single-sign-on.md). Password-based SSO, also referred to as password vaulting, enables you to manage user access and passwords to web applications that don't support identity federation. It is also useful for scenarios in which several users need to share a single account, such as to your organization's social media app accounts.
87
+
Create a web application that has an HTML sign-in page to configure [password-based single sign-on](../manage-apps/what-is-single-sign-on.md). Password-based SSO, also referred to as password vaulting, enables you to manage user access and passwords to web applications that don't support identity federation. It's also useful for scenarios in which several users need to share a single account, such as to your organization's social media app accounts.
92
88
93
-
89
+
94
90
95
-
* If you want to add your application to list in the gallery using Password SSO, select **Password SSO** as above.
96
-
* If you have any issues regarding access, contact the [Azure AD SSO Integration Team](<mailto:[email protected]>).
91
+
* If you want to add your application to list in the gallery by using password SSO, select **Password SSO** as shown.
92
+
* If you have any issues with access, contact the [Azure AD SSO Integration Team](<mailto:[email protected]>).
97
93
98
-
## Requesting for User Provisioning
94
+
## Request for user provisioning
99
95
100
-
Follow the below process to request for user provisioning-
96
+
Follow the process shown in the following image to request user provisioning.
101
97
102
-
98
+
103
99
104
-
## Update/Remove existing listing
100
+
## Update or remove an existing listing
105
101
106
-
To update or remove an existing application in the Azure AD app gallery, you first need to submit the request in the [Application Network Portal](https://microsoft.sharepoint.com/teams/apponboarding/Apps). If you have an Office 365 account, use that to sign in to this portal. If not, use your Microsoft account (such as Outlook or Hotmail) to sign in.
102
+
To update or remove an existing application in the Azure AD app gallery, you first need to submit the request in the [Application Network portal](https://microsoft.sharepoint.com/teams/apponboarding/Apps). If you have an Office 365 account, use that to sign in to this portal. If not, use your Microsoft account, such as Outlook or Hotmail, to sign in.
107
103
108
-
- Select the appropriate option as shown in the following image:
104
+
- Select the appropriate option as shown in the following image.
109
105
110
-
106
+
111
107
112
-
*If you want to update an existing application, select appropriate option as per your requirement.
113
-
*If you want to remove an existing application from the Azure AD gallery, select **Remove my application listing from the gallery**.
114
-
* If you have any issues regarding access, contact the [Azure AD SSO Integration Team](<mailto:[email protected]>).
108
+
*To update an existing application, select the appropriate option as per your requirement.
109
+
*To remove an existing application from the Azure AD app gallery, select **Remove my application listing from the gallery**.
110
+
* If you have any issues with access, contact the [Azure AD SSO Integration Team](<mailto:[email protected]>).
115
111
116
-
## Listing requests by customers
112
+
## List requests by customers
117
113
118
-
Customers can submit the request of listing an application by clicking**App requests by Customers**-> **Submit new request**.
114
+
Customers can submit a request to list an application by selecting**App requests by Customers** > **Submit new request**.
119
115
120
-
116
+
121
117
122
-
Below is the flow of customerrequested applications-
118
+
Here's the flow of customer-requested applications.
123
119
124
-
120
+
125
121
126
122
## Timelines
127
123
128
-
The timeline for the process of listing a SAML 2.0 or WS-Fed application in the gallery is 7-10 business days.
124
+
The timeline for the process of listing a SAML 2.0 or WS-Fed application in the gallery is 7 to 10 business days.
129
125
130
-
126
+
131
127
132
-
The timeline for the process of listing an OpenID Connect application in the gallery is 2-5 business days.
128
+
The timeline for the process of listing an OpenID Connect application in the gallery is 2 to 5 business days.
133
129
134
-
130
+
135
131
136
132
## Escalations
137
133
138
-
For any escalations, send email to the [Azure AD SSO Integration Team](mailto:[email protected]) which is [email protected] and we'll respond as soon as possible.
134
+
For any escalations, send email to the [Azure AD SSO Integration Team](mailto:[email protected])at [email protected], and we'll respond as soon as possible.
0 commit comments