Configure proxies for on-premises environments
Some organizations require that all server traffic goes through a proxy server for tracking or packet inspection. This section describes how we recommend configuring your environment in these cases.
Configure the proxy
Perform the following steps in each node of type OrchestratorType in the Microsoft Azure Service Fabric cluster.
Use remote access to connect to the Orchestrator virtual machine (VM).
Execute the following PowerShell script to retrieve the path of the
machine.config
file.[System.Runtime.InteropServices.RuntimeEnvironment]::SystemConfigurationFile
Edit the
machine.config
file to add the following code example.<system.net> <defaultProxy> <proxy usesystemdefault="true" proxyaddress="http://<PROXYADDRESS>:<PROXYPORT>" bypassonlocal="true" /> </defaultProxy> </system.net>
Save the file.
Restart the virtual machine.
The above procedure must be performed for all Orchestrator node VMs.
Safe list URLs
The LocalAgent needs to communicate with Azure resources and Microsoft Dynamics Lifecyle Services (LCS). As a result, some URLs need to be added to a safe list on the proxy or firewalls so that all OrchestratorType nodes can access them. The urls will vary depending which LCS region your environment is being deployed from.
LCS Global
- lcsapi.lcs.dynamics.com
- login.windows.net
- uswelcs1lcm.queue.core.windows.net
- www.office.com
- login.microsoftonline.com
- dc.services.visualstudio.com
- uswelcs1lcm.blob.core.windows.net
LCS EU
- lcsapi.eu.lcs.dynamics.com
- login.windows.net
- euweprodlcm.queue.core.windows.net
- www.office.com
- login.microsoftonline.com
- dc.services.visualstudio.com
- euweprodlcm.blob.core.windows.net
Geri Bildirim
https://aka.ms/ContentUserFeedback.
Çok yakında: 2024 boyunca, içerik için geri bildirim mekanizması olarak GitHub Sorunları’nı kullanımdan kaldıracak ve yeni bir geri bildirim sistemiyle değiştireceğiz. Daha fazla bilgi için bkz.Gönderin ve geri bildirimi görüntüleyin