Skip to content

Commit a851292

Browse files
committed
version-update
1 parent 140fa0d commit a851292

File tree

3 files changed

+6
-5
lines changed

3 files changed

+6
-5
lines changed

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

Lines changed: 2 additions & 2 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
---
@@ -36,7 +36,7 @@ The server needs to have TLS 1.2 enabled before you install the Application Prox
3636
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2]
3737
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client] "DisabledByDefault"=dword:00000000 "Enabled"=dword:00000001
3838
[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
39+
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.7.1+] "SchUseStrongCrypto"=dword:00000001
4040
```
4141
4242
A `regedit` file you can use to set these values follows:

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: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ User identities must be synchronized from an on-premises directory or created di
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

3030
- 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.0.30319.
31+
- The minimum .NET version required for the connector is v4.7.1+.
3232
- For more information, see [App Proxy connectors](../active-directory/app-proxy/application-proxy-connectors.md#requirements-and-deployment)
3333

3434
### Prepare your on-premises environment

0 commit comments

Comments
 (0)