web

You’re offline. This is a read only version of the page.

Microsoft Azure | Share your Ideas

Community

Loading...

This forum

Home
Networking

Networking

201 Ideas

Most votes



Allow ability with Azure Firewall to select the Public IP for outbound connections

The Azure Firewall randomly selects the source public IP address to use for a connection on outbound connections.When you have multiple Public IPs associated to the Azure Firewall this means that when you connect to external sources, they may have to whitelist the full set of the Public IPs. So you have to use IP Prefix or load balancer to try workaround this.

Azure Firewall geo based rules

Support for geo based Rules in azure firewall. IE Any traffic from Country A will be blocked

Company Response

Valid suggestion subject to customer upvote

Disable source NAT on incoming sessions on Azure Firewall

Company Response

valid suggestion subject to upvote

FQDN tags for Office365 on Azure Firewall

Office365 has plenty of domains. In case we need Office365 traffic via Azure Firewall, we have to retrieve all URLs and then add application rule accordingly. This will lead waste a lot of times.

Add Effective Routes blade to Azure Firewall

We are currently evaluating the use of Azure Firewall as our core firewall between on-prem and an Azure Hub/Spoke architecture via ExpressRoute.

X-Forwarded-For from firewall should be sending the external IP of the incoming connection.

X-Forwarded-For is being overwritten by the firewall, so our internal servers cannot check the external IP of the incoming connection.

Add Azure Firewall compatibility with Application Gateway

I have an architecture with multiple subscriptions, virtual networks and connectivity to on-premises. In the hub subscription we use(d) Azure Firewall to filter network traffic between networks.

Diagnostic log for Azure Firewall includes rule collection name and priority for each entry

The current log format for Azure Firewall as following, Rule Name and Priority Number is not supported by Azure Firewall diagnostic log yet.

Add ASG support on Azure Firewall

Currently it's not possible to utilize ASGs in the Azure Firewall which limits the possibility of having an autoscaling environment and at the same time limit the network access to only what is necessary by specific resources.

Remove requirement for public IP on Azure Firewall.

Our organization requires access to Azure cloud only via VPN for internal users. We would prefer to use the Azure firewall however currently a public IP is required. The requirement for a public IP should be eliminated as from a security perspective, this is unacceptable if the firewall is used for internal traffic only.

Filters (1)

Categories (1)



(Select all)



Application Gateway



Application Gateway for Containers



Azure Firewall



Azure Front Door Service

Stages



(Select all)



Archived



Completed



Declined



In Review

Powered by Dynamics 365 Customer Service. Learn more here.

Privacy Terms of use

© Microsoft 2021