Skip to content

Commit 62f22fa

Browse files
Merge pull request #247817 from shlipsey3/gsa-update-080923
gsa-update-080923
2 parents cba2d9d + e1bd623 commit 62f22fa

File tree

3 files changed

+15
-7
lines changed

3 files changed

+15
-7
lines changed

articles/active-directory/app-proxy/application-proxy-connectors.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.subservice: app-proxy
99
ms.workload: identity
1010
ms.topic: conceptual
11-
ms.date: 11/17/2022
11+
ms.date: 08/09/2023
1212
ms.author: kenwith
1313
ms.reviewer: ashishj
1414
---
@@ -28,6 +28,8 @@ To deploy Application Proxy successfully, you need at least one connector, but w
2828
### Windows Server
2929
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.
3030

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+
3133
The server needs to have TLS 1.2 enabled before you install the Application Proxy connector. To enable TLS 1.2 on the server:
3234

3335
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
3638
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2]
3739
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client] "DisabledByDefault"=dword:00000000 "Enabled"=dword:00000001
3840
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server] "DisabledByDefault"=dword:00000000 "Enabled"=dword:00000001
39-
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001
41+
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.8.4250.0] "SchUseStrongCrypto"=dword:00000001
4042
```
4143
4244
A `regedit` file you can use to set these values follows:
@@ -51,7 +53,7 @@ The server needs to have TLS 1.2 enabled before you install the Application Prox
5153
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server]
5254
"DisabledByDefault"=dword:00000000
5355
"Enabled"=dword:00000001
54-
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
56+
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.8.4250.0]
5557
"SchUseStrongCrypto"=dword:00000001
5658
```
5759

articles/global-secure-access/how-to-compliant-network.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Learn how to require known compliant network locations in order to
55
ms.service: network-access
66
ms.subservice:
77
ms.topic: how-to
8-
ms.date: 07/27/2023
8+
ms.date: 08/09/2023
99

1010
ms.author: joflore
1111
author: MicrosoftGuyJFlo
@@ -64,7 +64,8 @@ The following example shows a Conditional Access policy that requires Exchange O
6464
1. Under **Include**, select **All users**.
6565
1. Under **Exclude**, select **Users and groups** and choose your organization's [emergency access or break-glass accounts](#user-exclusions).
6666
1. Under **Target resources** > **Include**, and select **Select apps**.
67-
1. Choose **Office 365 Exchange Online** and **Office 365 SharePoint Online**.
67+
1. Choose **Office 365 Exchange Online** and/or **Office 365 SharePoint Online**.
68+
1. Office 365 apps are currently NOT supported, so do not select this option.
6869
1. Under **Conditions** > **Location**.
6970
1. Set **Configure** to **Yes**
7071
1. Under **Include**, select **Any location**.

articles/global-secure-access/how-to-configure-connectors.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: shlipsey3
55
ms.author: sarahlipsey
66
manager: amycolannino
77
ms.topic: how-to
8-
ms.date: 06/27/2023
8+
ms.date: 08/09/2023
99
ms.service: network-access
1010
ms.custom:
1111
ms.reviewer: katabish
@@ -27,7 +27,10 @@ User identities must be synchronized from an on-premises directory or created di
2727

2828
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.
2929

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...
3134

3235
### Prepare your on-premises environment
3336

@@ -71,6 +74,8 @@ To use Private Access, install a connector on each Windows server you're using f
7174
> 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.
7275
>
7376
>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).
78+
7479

7580
**To install the connector**:
7681

0 commit comments

Comments
 (0)