New feature for Microsoft Entra ID Connector (4383737)

Customer is setting up a “Microsoft Entra ID Connector” with One Identity. Access to the internet from their network must be routed via a proxy server. Synchronization Editor can browse Entra ID but the initial synchronization fails with login.microsoftonline.com:443 not resolvable.

A workaround involving allowing the service account to log on interactively is successful. However, interactive logon for a service account is not an option for customer for security reasons.

In .NET Core, the option to define individual proxy settings directly in the respective <application>.exe.config is no longer available.
In theory, this would have to be configured in .NET Core via the appsettings.json.
However, this is not possible on a per-application basis.

Additionally, the code would need to explicitly be extended to ensure that the proxy settings are loaded from the appsettings.json.
This is currently not the case, which explains why it is not working.

New feature will be implemented as an Enhancement Request (#721873).

The feature will be considered for a future release.

As a temporary Workaround, suggestion is to configure proxy handling for the applications involved, especially the One Identity Manager Service process (viNetworkService.exe.config), because the synchronization itself runs through the service, not through the editor session.