แก้ไข

แชร์ผ่าน

Microsoft Entra private network connector: version release history

  • บทความ

This article lists the versions and features of the Microsoft Entra private network connector. The Microsoft Entra ID team regularly updates the private network connector with new features and functionality. Look into the release notes for information on whether the connector version will be pushed for automatic update or available for download and manual update only.

Important

Microsoft Entra application proxy and Microsoft Entra Private Access use the private network connector.

Make sure that auto updates are enabled for your connectors to get the latest features and bug fixes. Microsoft Support might ask you to install the latest connector version to resolve a problem.

Here's a list of related resources:

Resource Details
How to enable application proxy Prerequisites for enabling application proxy and installing and registering a connector are described in this tutorial.
Understand Microsoft Entra private network connectors Find out more about connector management and how connectors autoupgrade.
Microsoft Entra private network connector Download Download the latest connector.

Version 1.5.3925.0

Release status

July 3, 2024: Released for download. This version is only available for install via the download page in the Microsoft Entra admin center.

New features and improvements

  • Bug fixes and minor improvements

Version 1.5.3890.0

Release status

May 29, 2024: Released for download. This version is only available for install via the download page in the Microsoft Entra admin center.

New features and improvements

  • General Availability of support for outbound proxy for Private Access flows.
  • Memory issue fix for application proxy flows.
  • Miscellaneous bugs and logging improvements.

Version 1.5.3829.0

Release status

April 2, 2024: Released for download. This version is only available for install via the download page in the Microsoft Entra admin center.

Updated brand

The new name is now the Microsoft Entra private network connector. The updated brand emphasizes the connector as a common infrastructure for accessing any private network resource. The connector is used for both Microsoft Entra Private Access and Microsoft Entra application proxy. The new name appears in the user interface components.

New features and improvements

  • Support for User Datagram Protocol (UDP) and Private Domain Name System (DNS) features for Private Access flow. *Requires the Early Access Preview.
  • Support for outbound proxy in connector for Private Access flow. *Requires the Early Access Preview.
  • Improved resiliency and performance.
  • Improved logging and metrics reporting.

Note

A reboot is required when you install or upgrade the connector.

*Submit request for onboarding to the Early Access Preview here.

Refer to the table for updated paths.

Category Old name New name
Installer file AADApplicationProxyConnectorInstaller.exe MicrosoftEntraPrivateNetworkConnectorInstaller.exe
Install location C:\Program Files\Microsoft AAD App Proxy Connector C:\Program Files\Microsoft Entra private network connector
C:\Program Files\Microsoft AAD App Proxy Connector\Modules\AppProxyPSModule C:\Program Files\Microsoft Entra private network connector\Modules\MicrosoftEntraPrivateNetworkConnectorPSModule
C:\Program Files\Microsoft AAD App Proxy Connector Updater C:\Program Files\Microsoft Entra private network connector Updater
C:\ProgramData\Microsoft\Microsoft AAD Application Proxy Connector C:\ProgramData\Microsoft\Microsoft Entra private network connector
Application ApplicationProxyConnectorService.exe MicrosoftEntraPrivateNetworkConnectorService.exe
ApplicationProxyConnectorUpdaterService.exe MicrosoftEntraPrivateNetworkConnectorUpdaterService.exe
CONFIG file ApplicationProxyConnectorService.exe.config MicrosoftEntraPrivateNetworkConnectorService.exe.config
ApplicationProxyConnectorUpdaterService.exe.config MicrosoftEntraPrivateNetworkConnectorUpdaterService.exe.config
PowerShell module AppProxyPSModule.psd1 MicrosoftEntraPrivateNetworkConnectorPSModule.psd1
PowerShell command Register-AppProxyConnector Register-MicrosoftEntraPrivateNetworkConnector
Log file AadAppProxyConnector_{GUID}.log MicrosoftEntraPrivateNetworkConnector_{GUID}.log
AadAppProxyConnectorUpdater_{GUID}.log MicrosoftEntraPrivateNetworkConnectorUpdater_{GUID}.log
Services Microsoft AAD Application Proxy Connector Microsoft Entra private network connector
Microsoft AAD Application Proxy Connector Updater Microsoft Entra private network connector updater
Registries Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft AAD App Proxy Connector Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Entra private network connector
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft AAD App Proxy Connector Updater Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Entra private network connector Updater
Event logs Microsoft-AadApplicationProxy-Connector/Admin Microsoft-Microsoft Entra private network-Connector/Admin
Microsoft-AadApplicationProxy-Updater/Admin Microsoft-Microsoft Entra private network-Updater/Admin

Important

.NET Framework

You must have .NET version 4.7.2 or higher to install, or upgrade, application proxy version 1.5.3437.0 or later. Windows Server 2012 R2 and Windows Server 2016 do not have this by default. For more information, see How to: Determine which .NET Framework versions are installed.

Version 1.5.3437.0

Release status

June 20, 2023: Released for download. This version is only available for install via the download page.

New features and improvements

  • Updated partner notices.

Fixed issues

Important

.NET Framework

You must have .NET version 4.7.2 or higher to install, or upgrade, application proxy version 1.5.3437.0 or later. Windows Server 2012 R2 and Windows Server 2016 may not have this by default. For more information, see How to: Determine which .NET Framework versions are installed.

Version 1.5.2846.0

Release status

March 22, 2022: Released for download. This version is only available for install via the download page.

New features and improvements

  • Increased the number of HTTP headers supported on HTTP requests from 41 to 60.
  • Improved error handling of TLS failures between the connector and Azure services.
  • Updated the default connection limit to 200 for connector traffic when going through outbound proxy. To learn more about outbound proxy, see Work with existing on-premises proxy servers.
  • Deprecated the use of Active Directory Authentication Library (ADAL) and implemented Microsoft Authentication Library (MSAL) as part of the connector installation flow.

Fixed issues

  • Return original error code and response instead of a 400 Bad Request code for failing websocket connect attempts.

Version 1.5.1975.0

Release status

July 22, 2020: Released for download. This version is only available for install via the download page.

New features and improvements

Fixed issues

  • Fixed a websocket issue that forced lowercase strings.
  • Fixed an issue that caused connectors to be occasionally unresponsive.

Version 1.5.1626.0

Release status

July 17, 2020: Released for download. This version is only available for install via the download page.

Fixed issues

  • Resolved memory leak issues present in previous version.
  • Completed general improvements for websocket support.

Version 1.5.1526.0

Release status

April 07, 2020: Released for download. This version is only available for install via the download page.

New features and improvements

  • Connectors only use Transport Layer Security (TLS) 1.2 for all connections. For more information, see connector prerequisites.
  • Improved signaling between the connector and Azure services. The signaling supports reliable sessions for Windows Communication Foundation (WCF) communication between the connector and Azure services and Domain Name System (DNS) caching improvements for WebSocket communications.
  • Support for configuring a proxy between the connector and the backend application. For more information, see Work with existing on-premises proxy servers.

Fixed issues

  • Removed falling back to port 8080 for communications from the connector to Azure services.
  • Added debug traces for WebSocket communications.
  • Resolved preserving the SameSite attribute when set on backend application cookies.

Version 1.5.612.0

Release status

September 20, 2018: Released for download.

New features and improvements

  • Added WebSocket support for the QlikSense application. To learn more about how to integrate QlikSense with application proxy, see this walkthrough.
  • Improved the installation wizard to make it easier to configure an outbound proxy.
  • Set TLS 1.2 as the default protocol for connectors.
  • Added a new End-User License Agreement (EULA).

Fixed issues

  • A bug that caused memory leaks in the connector was fixed.
  • Azure Service Bus version updated, which includes a bug fix for connector timeout issues.

Version 1.5.402.0

Release status

January 19, 2018: Released for download.

Fixed issues

  • Added support for custom domains that need domain translation in the cookie.

Version 1.5.132.0

Release status

May 25, 2017: Released for download.

New features and improvements

Improved control over connectors' outbound connection limits.

Version 1.5.36.0

Release status

April 15, 2017: Released for download.

New features and improvements

  • Simplified onboarding and management with fewer required ports. Application proxy now requires opening only two standard outbound ports: 443 and 80. Application proxy continues to use only outbound connections, so you still don't need any components in a public facing network. For more information, see our configuration documentation.
  • If supported by your external proxy or firewall, you can now open your network by DNS instead of IP range. Application proxy services require connections to *.msappproxy.net and *.servicebus.windows.net only.

Earlier versions

If you're using a private network connector version earlier than 1.5.36.0, update to the latest version to ensure you have the latest fully supported features.

Next steps