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/application-proxy-configure-custom-home-page.md
+11-5Lines changed: 11 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -24,12 +24,12 @@ This article discusses how to configure an app to direct a user to a custom home
24
24
25
25
When a user launches the app, they're directed by default to the root domain URL for the published app. The landing page is typically set as the home page URL. Use the Azure AD PowerShell module to define a custom home page URL when you want an app user to land on a specific page within the app.
26
26
27
-
Here's one example of why your company would set a custom home page, and why it would be different depending on the type of user:
27
+
Here's one scenario that explains why your company would set a custom home page, and why it would be different depending on the type of user:
28
28
29
-
-Inside your corporate network, users go to `https://ExpenseApp/login/login.aspx` to sign in and access your app.
30
-
-Because you have other assets (such as images) that Application Proxy needs to access at the top level of the folder structure, you want to publish the app with `https://ExpenseApp` as the internal URL instead.
31
-
- The default external URL is `https://ExpenseApp-contoso.msappproxy.net`, which doesn't take your users to the sign-in page.
32
-
- You want to set `https://ExpenseApp-contoso.msappproxy.net/login/login.aspx` as the external home page URL instead.
29
+
-Because you have other assets (such as images) that Application Proxy needs to access at the top level of the folder structure, you publish the app with `https://ExpenseApp` as the internal URL.
30
+
-However, inside your corporate network, a user goes to `https://ExpenseApp/login/login.aspx` to sign in and access your app.
31
+
- The default external URL is `https://ExpenseApp-contoso.msappproxy.net`, which doesn't take an external user to the sign-in page.
32
+
- You want to set `https://ExpenseApp-contoso.msappproxy.net/login/login.aspx` as the external home page URL instead, so an external user sees the sign-in page first.
33
33
34
34
>[!NOTE]
35
35
>When you give users access to published apps, the apps are displayed in the [Azure AD Access Panel](../user-help/my-apps-portal-end-user-access.md) and the [Office 365 app launcher](https://www.microsoft.com/microsoft-365/blog/2016/09/27/introducing-the-new-office-365-app-launcher/).
@@ -62,6 +62,12 @@ To change the external and internal home pages of your app through the Azure AD
62
62
63
63
## Change the home page with PowerShell
64
64
65
+
To configure the home page of an app using PowerShell, you need to:
66
+
67
+
1. Install the Azure AD PowerShell module.
68
+
2. Find the ObjectId value of the app.
69
+
3. Update the app's home page URL using PowerShell commands.
70
+
65
71
### Install the Azure AD PowerShell module
66
72
67
73
Before you define a custom home page URL by using PowerShell, install the Azure AD PowerShell module. You can download the package from the [PowerShell Gallery](https://www.powershellgallery.com/packages/AzureAD/2.0.2.16), which uses the Graph API endpoint.
Copy file name to clipboardExpand all lines: articles/active-directory/manage-apps/application-proxy-configure-native-client-application.md
+9-7Lines changed: 9 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -85,13 +85,15 @@ httpClient.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("
85
85
HttpResponseMessage response = await httpClient.GetAsync("< Proxy App API Url >");
86
86
```
87
87
88
-
Replace the variables in the sample code as follows:
89
-
90
-
-**Tenant ID** can be found in the Azure AD portal. Go to **Azure Active Directory** > **Properties**, and copy the Directory ID.
91
-
-**External Url of Proxy App** is the front-end URL you entered in the proxy application. To find this value, go to the **Application proxy** section of the proxy application.
92
-
-**App ID of the Native app** can be found on the **Properties** page of the native application.
93
-
-**Redirect URI of the Native App** can be found on the **Redirect URIs** page of the native application.
94
-
-**Proxy App API Url** is the URL associated with the proxy application API that the native application is accessing. First go to **Azure Active Directory** > **App registrations**, and select your native application name. Then select **API permissions**, select the name of the proxy application API, and copy the URL of the API.
88
+
The required info in the sample code can be found in the Azure AD portal, as follows:
89
+
90
+
| Info required | How to find it in the Azure AD portal |
91
+
| --- | --- |
92
+
|\<Tenant ID> |**Azure Active Directory** > **Properties** > **Directory ID**|
After you edit the ADAL with these parameters, your users can authenticate to native client applications even when they're outside of the corporate network.
Copy file name to clipboardExpand all lines: articles/active-directory/manage-apps/change-name-or-logo-portal.md
+8-6Lines changed: 8 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -29,18 +29,20 @@ It's easy to change the name or logo for a custom enterprise application in Azur
29
29
3. Select an application. The application overview page appears.
30
30
4. In the application overview pane, under the **Manage** heading, select **Properties**. The **Properties** page appears.
31
31
5. If you want to change the name, select the **Name** box, type the new name, and press Enter.
32
-
6. If you want to change the logo, find the **Logo** field, and select the folder icon next to the **Select a file** box, which is below the application's current logo image. The file picker appears.
32
+
6. If you want to change the logo, find the **Logo** field, and select the folder icon next to the **Select a file** box, which is below the application's current logo image.
33
33
34
34

35
-
7. Select the file you want as the new logo. The name of the file appears in the box below the current logo image.
36
35
37
-
> ![NOTE]
36
+
Otherwise, if you aren't changing the logo, go to step 8.
37
+
7. In the file picker, select the file you want as the new logo. The name of the file appears in the box below the current logo image.
38
+
39
+
> [!NOTE]
38
40
> Azure requires the logo image to be a PNG file, and it applies limits on width, height, and file size.
39
41
8. Select **Save**. If you chose a new logo, the **Logo** field's image changes to reflect the new logo file.
40
42
41
43
## Next steps
42
44
43
45
*[Quickstart: View your organization's groups and members in Azure Active Directory](../fundamentals/active-directory-groups-view-azure-portal.md)
44
-
*[Assign a user or group to an enterprise application in Azure Active Directory](assign-user-or-group-access-portal.md)
45
-
*[Remove a user or group assignment from an enterprise application in Azure Active Directory](remove-user-or-group-access-portal.md)
46
-
*[Disable user sign-ins for an enterprise application in Azure Active Directory](disable-user-sign-in-portal.md)
46
+
*[Assign a user or group to an enterprise app](assign-user-or-group-access-portal.md)
47
+
*[Remove a user or group assignment from an enterprise app](remove-user-or-group-access-portal.md)
48
+
*[Disable user sign-ins for an enterprise app](disable-user-sign-in-portal.md)
0 commit comments