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/app-proxy/application-proxy-connectors.md
+5-3Lines changed: 5 additions & 3 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-proxy
9
9
ms.workload: identity
10
10
ms.topic: conceptual
11
-
ms.date: 11/17/2022
11
+
ms.date: 08/09/2023
12
12
ms.author: kenwith
13
13
ms.reviewer: ashishj
14
14
---
@@ -28,6 +28,8 @@ To deploy Application Proxy successfully, you need at least one connector, but w
28
28
### Windows Server
29
29
You need a server running Windows Server 2012 R2 or later on which you can install the Application Proxy connector. The server needs to connect to the Application Proxy services in Azure, and the on-premises applications that you're publishing.
30
30
31
+
Starting from the version 1.5.3437.0, having the .NET version 4.7.1 or greater is required for successful installation (upgrade).
32
+
31
33
The server needs to have TLS 1.2 enabled before you install the Application Proxy connector. To enable TLS 1.2 on the server:
32
34
33
35
1. Set the following registry keys:
@@ -36,7 +38,7 @@ The server needs to have TLS 1.2 enabled before you install the Application Prox
Copy file name to clipboardExpand all lines: articles/global-secure-access/how-to-configure-connectors.md
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: shlipsey3
5
5
ms.author: sarahlipsey
6
6
manager: amycolannino
7
7
ms.topic: how-to
8
-
ms.date: 06/27/2023
8
+
ms.date: 08/09/2023
9
9
ms.service: network-access
10
10
ms.custom:
11
11
ms.reviewer: katabish
@@ -27,7 +27,10 @@ User identities must be synchronized from an on-premises directory or created di
27
27
28
28
To use Application Proxy, you need a Windows server running Windows Server 2012 R2 or later. You'll install the Application Proxy connector on the server. This connector server needs to connect to the Application Proxy services in Azure, and the on-premises applications that you plan to publish.
29
29
30
-
For high availability in your environment, we recommend having more than one Windows server.
30
+
- For high availability in your environment, we recommend having more than one Windows server.
31
+
- The minimum .NET version required for the connector is v4.7.1+.
32
+
- For more information, see [App Proxy connectors](../active-directory/app-proxy/application-proxy-connectors.md#requirements-and-deployment)
33
+
- To determine what version of .NET framework...
31
34
32
35
### Prepare your on-premises environment
33
36
@@ -71,6 +74,8 @@ To use Private Access, install a connector on each Windows server you're using f
71
74
> Setting up App Proxy connectors and connector groups require planning and testing to ensure you have the right configuration for your organization. If you don't already have connector groups set up, pause this process and return when you have a connector group ready.
72
75
>
73
76
>The minimum version of connector required for Private Access is **1.5.3417.0**.
77
+
>Starting from the version 1.5.3437.0, having the .NET version 4.7.1 or greater is required for successful installation (upgrade).
0 commit comments