116
We are integrating with an on premise solution and we're looking to lockdown the traffic coming from BC to a specific set of IP addresses or hostnames. We have written customization that makes a web service request from BC SaaS to an On Prem server. The Security Team who are responsible for the on premise infrastructure would like to lock down the incoming traffic to either a set of IP addresses or hostnames. This is not possible at the moment but we would like to be improved.
STATUS DETAILS
Completed
Ideas Administrator

Thank you for this suggestion! We have introduced the Dynamics365BusinessCentral Service Tag to address this idea. See service tags list here: https://learn.microsoft.com/en-us/azure/virtual-network/service-tags-overview

Best regards,
Business Central team

Comments

N

Revisiting this. The Idea is marked as completed, but not really implemented. The Service Tag addition does not really cover anything else but services within Azure itself. Typically this need comes from other, lecacy, and often on premises systems. We have also used the Proxy Azure Function method, but it's not very pretty.Instead of having service tags only, could we have attached the business central service to a VNET or assigned a static IP to an environment, like for a number of other Azure services, I would have been happy

Category: Tenant Administration

N

We also have several customers with this need, there has to be a way for a BC SaaS to provide an non-changing address of som kind for security protocols.

Category: Tenant Administration

N

I had this same requirement recently. Ended up writing an Azure function to serve as a proxy because those have only 3 outgoing IPs that are known upfront (as long as the traffic is relatively light). Telling someone they essentially have to whitelist all of Azure doesn't work for most security people.

Category: Tenant Administration