The initial setup was a fairly straightforward process. Our implementation was pretty basic. I was able to handle the setup myself. 

There is a bit of maintenance in the form of checking for updates and firewall definitions. One or two admins can handle maintenance duties. 

It was very easy.

It's a PaaS offering, always on the cloud. It's tightly connected to Azure. It's quite simple when it comes to creating it, but the configuration, the fine-grain specific needs, is more difficult. If you have a standard way of working, it would work very well. But when you have different applications and integrations, Fortinet might be a better choice.

Our implementation strategy is based on designing the architecture for the application. Then we look at cost estimation so that it fits into the budget. Then we implement it and maintain it and evaluate it yearly.

There is functional maintenance involved but not technical maintenance because that is done by Azure. Things like upgrading the OS are handled by the Capgemini and Accenture technicians.

The implementation process is easy. It is not overly complex or difficult in terms of the setup process.

I do not have direct experience with technical support. My colleagues in operations were involved in the setup. My role was to define and decide what kind of service we needed.

The deployment was in different regions, including in the USA and Virginia. It was a combination of on-premises and hybrid cloud between the two regions. 

I don't recall the solution needing maintenance.

The initial setup was pretty easy. 

In terms of configuration, we haven't faced much of an issue.

The deployment and configuration took two to three hours.

The maintenance parameter is supported by Microsoft. Being a cloud product is very simple in terms of maintenance; we don't need to worry about any kind of patching activity or anything else. On other products, we must check the vendor and follow the OEM recommendation. This is an area that Azure has simplified.

Its initial setup was pretty straightforward. With its native portal and User Guide, you can very quickly do the implementation. Its UI is very user-friendly. 

We made it an enterprise shared service for our use case. We studied and designed the cloud-native Azure Firewall service from scratch and packaged it as a standard service in our environment. We wanted to maintain the Azure service like the DNAT network rule and application rule. We wanted it to be always manageable in its lifecycle. So, we chose the infrastructure mode to manage our service. We have a delivery pipeline, and we also use the DevOps mode to maintain the Azure Firewall configuration in its lifecycle. For this part, the API is good, and the native Terraform and Ansible have relevant predefined modules. It is working fine. So, for this part, it is very good. It doesn't matter whether you are a junior technical guy or an advanced technical guy. You can always find a comfortable way to deploy, manage, and maintain it.

Its deployment is very quick. It takes a few minutes. In order to make it the deployer pipeline, you need to spend some time because you need to think about the integration, such as how to integrate with GitLab CI, and how to make Azure Workbook so that it can monitor the usage and user performance. We wanted it as a managed service. So, the duration also depends on your use case.

The initial setup is straightforward; Azure Firewall does not have a complex implementation process. It is very simple; you just need to enable the service within Azure.

It does not require any maintenance because it is managed by Microsoft, that is, it is a fully managed service.

Setting up Azure Firewall was easy because all you were doing was configuring source, destination, port, and action. However, there was something weird. You have to number your rules set, and depending on your numbering system, that's how you would have to apply the filtering of the logic of the policy. And in that sense, it's a little bit quirky. I don't think that most firewalls work that way. It just reads the policy, and the algorithm is based on it filtering down through the policies until it hits a truth or a match. And then it makes a decision based on that.

There are no big challenges when it comes to implementing this solution.

It takes approximately two hours to deploy.

Compared to other firewall products, the setup is complex. I have faced problems setting up the DNAT, and there are some issues with setting up the certificates. I have also had trouble with service tag issues.

The basic deployment takes one day or two days at the maximum. The fine-tuning, where we have to monitor and identify the proper traffic, takes place over two or three weeks. Fine-tuning is an extensive part of it. It is important that the configuration is set up correctly.

The initial setup is straightforward. There is nothing complex about it. Within 20 minutes, you have the firewall up and running.

Two or three people are sufficient for deployment and maintenance in a small organization. One should be at least a SOC analyst who understands security, and one could be an Azure admin with good knowledge of the Azure infrastructure, PaaS, and security aspects.

The initial setup is a piece of cake. You just provision it. You need to know your requirements because there are two versions, Standard and Premium, which affect your costs.

The initial setup was simple.

The deployment of the firewall took about five minutes and full deployment through the Azure mechanism lasted around an hour.

The solution does not require any maintenance. 

From the virtual machine perspective, it's quite easy to set up. You can choose the image file from the public market, and then you can setup. However, the account, the Microsoft Azure identity, the whole creation process was very complex and it is not that user friendly. Users usually use their Azure ID, as well as sometimes providing the live ID. That's a second ID, and it confuses people.

The product's deployment was straightforward. 

The initial setup was straightforward.

We had another tool which was FortiGate. We migrated from FortiGate to the Azure Firewall.

It was a straightforward migration.

The deployment took approximately three to four weeks.

The implementation strategy would include copying over rules, ensuring that all the services are able to run, and also ensuring that both firewalls were running in parallel. Until we are sure that the Azure Firewall can handle the workload, both firewall products will continue to operate.

After that, we were able to power down the virtual appliance that was on the FortiGate Firewall.

We had it running for quite some time, approximately a month and a half. Because there were no issues, we stopped using the FortiGate Firewall altogether, once that process was complete.

We have a server team, a cloud team, and a network team to administer and maintain this solution. It's approximately eight to ten people, some are network security engineers, a network security manager, and network engineers.

I was involved in its setup. I deployed it with Bicep pipelines. The maintenance was also via pipelines. Its setup was straightforward, especially with Terraform and Bicep. It was done in 10 minutes to 15 minutes.

It is a one-man job, but that is not our advice. It is better to have three or four people who have knowledge of the firewall system. If you have only one person and that person is sick, then you have a problem. You block the internet, and sometimes, you have to open it. So, it is better to do it with a small team. If there are a lot of changes, two to three people should be fine.

In terms of maintenance, there is only the maintenance of new ports or IP addresses, but that's operational management. That's not firewall management as such.

It is pretty straightforward for what I'm using it for.

The tool's deployment is straightforward. 

Azure Firewall has an easy installation.

The solution doesn't have a complex installation process. It's pretty straightforward to implement. When we went forward with the solution we didn't face any setup issues.

Our initial deployment took about three months, and, now that it's a managed service, we've handed the deployment over to them.

I'm not sure how many staff members we used for deployment and how many handle any maintenance aspects.

The initial setup is straightforward and very easy.

It is easy to set up. It took around 1 hour.

The initial setup is simple. 

The initial setup is straightforward. We define the setup on templates, we haven't had any specific issues.

The initial setup was quite difficult.