Skip to content

Commit e3975ab

Browse files
authored
Merge pull request #85526 from msmimart/mm-issue34467
[App Mgmt] Clarify link translation not supported for Javascript URLs in any of the 3 options
2 parents 11c836a + fa6a858 commit e3975ab

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

articles/active-directory/manage-apps/application-proxy-configure-hard-coded-link-translation.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,9 +12,9 @@ ms.workload: identity
1212
ms.tgt_pltfrm: na
1313
ms.devlang: na
1414
ms.topic: conceptual
15-
ms.date: 05/04/2018
15+
ms.date: 08/15/2019
1616
ms.author: mimart
17-
ms.reviewer: harshja
17+
ms.reviewer: japere
1818
ms.custom: it-pro
1919
ms.collection: M365-identity-device-management
2020
---
@@ -26,13 +26,16 @@ Azure AD Application Proxy makes your on-premises apps available to users who ar
2626
The best way to make sure that links work the same both inside and outside of your corporate network is to configure the external URLs of your apps to be the same as their internal URLs. Use [custom domains](application-proxy-configure-custom-domain.md) to configure your external URLs to have your corporate domain name instead of the default application proxy domain.
2727

2828

29-
If you can't use custom domains in your tenant, there are several other options for providing this functionality. All of these are also compatible with custom domains and each other, so you can configure custom domains and other solutions if needed.
29+
If you can't use custom domains in your tenant, there are several other options for providing this functionality. All of these are also compatible with custom domains and each other, so you can configure custom domains and other solutions if needed.
30+
31+
> [!NOTE]
32+
> Link translation is not supported for hard-coded internal URLs generated through Javascript.
3033
3134
**Option 1: Use the Managed Browser or Microsoft Edge** – This solution is only applicable if you plan to recommend or require that users access the application through the Intune Managed Browser or Microsoft Edge Browser. It will handle all published URLs.
3235

3336
**Option 2: Use the MyApps Extension** – This solution requires users to install a client-side browser extension, but it will handle all published URLs and works with most popular browsers.
3437

35-
**Option 3: Use the link translation setting** – This is an admin side setting that is invisible to users. However, it will only handle URLs in HTML and CSS. Hard-coded internal URLs generated through Javascript (for example) will not work.
38+
**Option 3: Use the link translation setting** – This is an admin side setting that is invisible to users. However, it will only handle URLs in HTML and CSS.
3639

3740
These three features keep your links working no matter where your users are. When you have apps that point directly to internal endpoints or ports, you can map these internal URLs to the published external Application Proxy URLs.
3841

0 commit comments

Comments
 (0)