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/manage-apps/add-application-portal.md
+23-18Lines changed: 23 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
8
8
ms.subservice: app-mgmt
9
9
ms.topic: quickstart
10
10
ms.workload: identity
11
-
ms.date: 04/09/2019
11
+
ms.date: 10/29/2019
12
12
ms.author: mimart
13
13
14
14
ms.collection: M365-identity-device-management
@@ -38,24 +38,26 @@ To test the steps in this tutorial, we recommend using a non-production environm
38
38
To add a gallery application to your Azure AD tenant:
39
39
40
40
1. In the [Azure portal](https://portal.azure.com), on the left navigation panel, select **Azure Active Directory**.
41
-
1. In the **Azure Active Directory** pane, select **Enterprise applications**.
42
-
1. The **All applications** pane opens to show a random sample of the applications in your Azure AD tenant. Select **New application** at the top of the **All applications** pane to add a gallery app to your tenant.
41
+
42
+
2. In the **Azure Active Directory** pane, select **Enterprise applications**. The **All applications** pane opens and displays a random sample of the applications in your Azure AD tenant.
43
+
44
+
3. To add a gallery app to your tenant, select **New application**.
43
45
44
46
45
47
46
-
1. In the **Categories** pane, you'll see icons under the **Featured applications** area that are a random sample of gallery applications. To see more applications, you could select **Show more** but we don't recommend searching this way because there are thousands of applications in the gallery.
48
+
4. Switch to the new gallery preview experience: In the banner at the top of the **Add an application page**, select the link that says **Click here to try out the new and improved app gallery**.
47
49
48
-
50
+
5. The **Browse Azure AD Gallery (Preview)** pane opens and displays tiles for cloud platforms, on-premises applications, and featured applications. Note that the applications listed in the **Featured applications** section have icons indicating whether they support federated single sign-on (SSO) and provisioning.
49
51
50
-
1. To search for an application, under **Add from the gallery**, enter the name of the application you want to add. Select the application from the results and select **Add**. The following example shows the **Add app** form that appears after searching for github.com.
52
+
51
53
52
-
54
+
6. You can browse the gallery for the application you want to add, or search for the application by entering its name in the search box. Then select the application from the results. In the form, you can edit the name of the application to match the needs of your organization. In this example we've changed the name to **GitHub-test**.
53
55
54
-
1. In the application-specific form, you can change property information. For example, you can edit the name of the application to match the needs of your organization. This example uses the name **GitHub-test**.
55
-
1. When you've finished making changes to the properties, select **Add**.
56
-
1. A getting started page appears with the options for configuring the application for your organization.
56
+
57
57
58
-
You've finished adding your application. Feel free to take a break. The next sections show you how to change the logo and edit other properties for your application.
58
+
7. Select **Create**. A getting started page appears with the options for configuring the application for your organization.
59
+
60
+
You've finished adding your application. The next sections show you how to change the logo and edit other properties for your application.
59
61
60
62
## Find your Azure AD tenant application
61
63
@@ -76,17 +78,17 @@ Now that you've found the application, you can open it and configure application
76
78
To edit the application properties:
77
79
78
80
1. Select the application to open it.
79
-
1. Select **Properties** to open the properties pane for editing.
81
+
2. Select **Properties** to open the properties pane for editing.
80
82
81
83
82
84
83
-
1. Take a moment to understand the sign-in options. The options determine how users who are assigned or unassigned to the application can sign into the application. And, the options also determine if a user can see the application in the access panel.
85
+
3. Take a moment to understand the sign-in options. The options determine how users who are assigned or unassigned to the application can sign into the application. And, the options also determine if a user can see the application in the access panel.
84
86
85
-
-**Enabled for users to sign-in** determines whether users assigned to the application can sign in.
86
-
-**User assignment required** determines whether users who aren't assigned to the application can sign in.
87
-
-**Visible to user** determines whether users assigned to an app can see it in the access panel and O365 launcher.
87
+
-**Enabled for users to sign-in?** determines whether users assigned to the application can sign in.
88
+
-**User assignment required?** determines whether users who aren't assigned to the application can sign in.
89
+
-**Visible to users?** determines whether users assigned to an app can see it in the access panel and O365 launcher.
88
90
89
-
1. Use the following tables to help you choose the best options for your needs.
91
+
4. Use the following tables to help you choose the best options for your needs.
90
92
91
93
- Behavior for **assigned** users:
92
94
@@ -126,10 +128,13 @@ To use a custom logo:
126
128
1. Since you've already found your application, select the application.
127
129
1. In the left pane, select **Properties**.
128
130
1. Upload the logo.
129
-
1. When you're finished, select **Save**.
131
+
1. When you're finished, select **Save**.
130
132
131
133
132
134
135
+
> [!NOTE]
136
+
> The thumbnail displayed on this **Properties** pane doesn't update right away. You can close and reopen the properties to see the updated icon.
137
+
133
138
## Next steps
134
139
135
140
Now that you've added the application to your Azure AD organization, [choose a single sign-on method](what-is-single-sign-on.md#choosing-a-single-sign-on-method) you want to use and refer to the appropriate article below:
3. To add a gallery app to your tenant, select **New application**.
37
36
38
-
1. Under **Add from the gallery**, in the search box, enter the name of the application you want to add.
37
+
39
38
40
-
39
+
4. Switch to the new gallery preview experience: In the banner at the top of the **Add an application page**, select the link that says **Click here to try out the new and improved app gallery**.
41
40
42
-
1. Select the application from the results.
41
+
5. The **Browse Azure AD Gallery** pane opens and displays tiles for cloud platforms, on-premises applications, and featured applications. Note that the applications listed in the **Featured applications** section have icons indicating whether they support federated single sign-on (SSO) and provisioning.
43
42
44
-
1. (Optional) In the application-specific form, you can edit the name of the application to match the needs of your organization.
43
+
45
44
46
-
1. Select **Add**. The application **Overview** page opens.
45
+
6. Browse the gallery for the application you want to add, or search for the application by entering its name in the search box. Then select the application from the results. (Optional) In the form, you can edit the application name to match the needs of your organization.
46
+
47
+
48
+
49
+
7. Select **Create**. A getting started page appears with the options for configuring the application for your organization.
47
50
48
51
## Configure user sign-in properties
49
52
50
53
1. Select **Properties** to open the properties pane for editing.
1. Set the following options to determine how users who are assigned or unassigned to the application can sign into the application and if a user can see the application in the access panel.
55
58
@@ -89,7 +92,7 @@ Azure Active Directory (Azure AD) has a gallery that contains thousands of pre-i
89
92
90
93
1. To use a custom logo, create a logo that is 215 by 215 pixels, and save it in PNG format. Then browse to your logo and upload it.
91
94
92
-
95
+
2. (Optional but recommended) In the **Add from the gallery** search box, enter the display name of the application. If the application appears in the search results, select it and skip the rest of this procedure.
33
-
3. Select **Non-gallery application**. The **Add your own application** page appears.
5. Start typing the display name for your new application. If there are any gallery applications with similar names, they'll appear in a search results list.
41
+
42
+
> [!NOTE]
43
+
> We recommend using the gallery version of your application whenever possible. If the application you want to add appears in the search results, select the application and skip the rest of this procedure.
44
+
45
+
6. Under **What are you looking to do with your application?** choose **Integrate any other application you don't find in the gallery**. This option is typically used for SAML and WS-Fed applications.
46
+
47
+
> [!NOTE]
48
+
> The other two options are used in the following scenarios:
49
+
>***Configure Application Proxy for secure remote access to an on-premises application** opens the configuration page for Azure AD Application Proxy and connectors.
50
+
>***Register an application you're working on to integrate with Azure AD** opens the **App registrations** page. This option is typically used for OpenID Connect applications.
51
+
52
+
7. Select **Create**. The application **Overview** page opens.
38
53
39
54
## Configure user sign-in properties
40
55
41
56
1. Select **Properties** to open the properties pane for editing.
1. Set the following options to determine how users who are assigned or unassigned to the application can sign into the application and if a user can see the application in the access panel.
60
+
2. Set the following options to determine how users who are assigned or unassigned to the application can sign into the application and if a user can see the application in the access panel.
46
61
47
62
-**Enabled for users to sign-in** determines whether users assigned to the application can sign in.
48
63
-**User assignment required** determines whether users who aren't assigned to the application can sign in.
@@ -78,11 +93,11 @@ This article describes how to add a non-gallery application to **Enterprise Appl
78
93
79
94
*Can the user see the application in the access panel and the Office 365 app launcher?
80
95
81
-
1. To use a custom logo, create a logo that is 215 by 215 pixels, and save it in PNG format. Then browse to your logo and upload it.
96
+
3. To use a custom logo, create a logo that is 215 by 215 pixels, and save it in PNG format. Then browse to your logo and upload it.
82
97
83
-
98
+
Copy file name to clipboardExpand all lines: articles/active-directory/manage-apps/application-proxy-add-on-premises-application.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
8
8
ms.subservice: app-mgmt
9
9
ms.workload: identity
10
10
ms.topic: tutorial
11
-
ms.date: 09/30/2019
11
+
ms.date: 10/24/2019
12
12
ms.author: mimart
13
13
ms.reviewer: japere
14
14
ms.collection: M365-identity-device-management
@@ -137,7 +137,7 @@ To confirm the connector installed and registered correctly:
137
137
1. In the left navigation panel, select **Azure Active Directory**, and then select **Application Proxy** under the **Manage** section. All of your connectors and connector groups appear on this page.
138
138
1. View a connector to verify its details. The connectors should be expanded by default. If the connector you want to view isn't expanded, expand the connector to view the details. An active green label indicates that your connector can connect to the service. However, even though the label is green, a network issue could still block the connector from receiving messages.
139
139
140
-
140
+
141
141
142
142
For more help with installing a connector, see [Problem installing the Application Proxy Connector](application-proxy-connector-installation-problem.md).
143
143
@@ -150,7 +150,7 @@ To confirm the connector installed and registered correctly:
- **Microsoft AAD Application Proxy Connector Updater** is an automated update service. The updater checks for new versions of the connector and updates the connector as needed.
1. If the status for the services isn't **Running**, right-click to select each service and choose **Start**.
156
156
@@ -159,10 +159,10 @@ To confirm the connector installed and registered correctly:
159
159
Now that you've prepared your environment and installed a connector, you're ready to add on-premises applications to Azure AD.
160
160
161
161
1. Sign in as an administrator in the [Azure portal](https://portal.azure.com/).
162
-
1. In the left navigation panel, select **Azure Active Directory**.
163
-
1. Select **Enterprise applications**, and then select **New application**.
164
-
1. Select **On-premises application**.
165
-
1. In the **Add your own on-premises application** section, provide the following information about your application:
162
+
2. In the left navigation panel, select **Azure Active Directory**.
163
+
3. Select **Enterprise applications**, and then select **New application**.
164
+
4. In the **On-premises applications** section, select **Add an on-premises application**.
165
+
5. In the **Add your own on-premises application** section, provide the following information about your application:
166
166
167
167
| Field | Description |
168
168
| :---- | :---------- |
@@ -172,7 +172,7 @@ Now that you've prepared your environment and installed a connector, you're read
172
172
| **Pre Authentication** | How Application Proxy verifies users before giving them access to your application.<br><br>**Azure Active Directory** - Application Proxy redirects users to sign in with Azure AD, which authenticates their permissions for the directory and application. We recommend keeping this option as the default so that you can take advantage of Azure AD security features like Conditional Access and Multi-Factor Authentication. **Azure Active Directory** is required for monitoring the application with Microsoft Cloud Application Security.<br><br>**Passthrough** - Users don't have to authenticate against Azure AD to access the application. You can still set up authentication requirements on the backend. |
173
173
| **Connector Group** | Connectors process the remote access to your application, and connector groups help you organize connectors and apps by region, network, or purpose. If you don't have any connector groups created yet, your app is assigned to **Default**.<br><br>If your application uses WebSockets to connect, all connectors in the group must be version 1.5.612.0 or later.|
174
174
175
-
1. If necessary, configure **Additional settings**. For most applications, you should keep these settings in their default states.
175
+
6. If necessary, configure **Additional settings**. For most applications, you should keep these settings in their default states.
176
176
177
177
| Field | Description |
178
178
| :---- | :---------- |
@@ -183,7 +183,7 @@ Now that you've prepared your environment and installed a connector, you're read
183
183
| **Translate URLs in Headers** | Keep this value as **Yes** unless your application required the original host header in the authentication request. |
184
184
| **Translate URLs in Application Body** | Keep this value as **No** unless you have hardcoded HTML links to other on-premises applications and don't use custom domains. For more information, see [Link translation with Application Proxy](application-proxy-configure-hard-coded-link-translation.md).<br><br>Set this value to **Yes** if you plan to monitor this application with Microsoft Cloud App Security (MCAS). For more information, see [Configure real-time application access monitoring with Microsoft Cloud App Security and Azure Active Directory](application-proxy-integrate-with-microsoft-cloud-application-security.md). |
185
185
186
-
1. Select **Add**.
186
+
7. Select **Add**.
187
187
188
188
## Test the application
189
189
@@ -196,11 +196,11 @@ Before adding a user to the application, verify the user account already has per
196
196
To add a test user:
197
197
198
198
1. Select **Enterprise applications**, and then select the application you want to test.
199
-
1. Select **Getting started**, and then select **Assign a user for testing**.
200
-
1. Under **Users and groups**, select **Add user**.
201
-
1. Under **Add assignment**, select **Users and groups**. The **User and groups** section appears.
202
-
1. Choose the account you want to add.
203
-
1. Choose **Select**, and then select **Assign**.
199
+
2. Select **Getting started**, and then select **Assign a user for testing**.
200
+
3. Under **Users and groups**, select **Add user**.
201
+
4. Under **Add assignment**, select **Users and groups**. The **User and groups** section appears.
0 commit comments