We were looking for a five-part solution that scales well, is fast, and has the ability to be quickly provisioned in the Azure Kubernetes Service (AKS) environment. Our product requires it to be quick because It is a memory database that also has persistence, which has to be real-time.

We are an enterprise performance management (EPM) company. As an 18-year-old company, we have a lot of legacy systems. Around 2011 to 2012, we decided to move to the cloud. We have pretty ambitious plans to lift and shift all of our customers to the cloud. For the past three years, we've been aggressively pushing our cloud offering. It is a fully managed cloud EPM solution that we are providing to our customers. The whole infrastructure, platform, and product are totally managed by us. We are partnering with Microsoft and running it on Microsoft Azure. 

We are in the process of modernizing the whole offering and making it cloud native. We've been modernizing for the past year and a half. One of the problems that you need to solve is also storage. This is where we bumped into NetApp. It's not only about compute. It's also about storage and networking. The storage becomes quite an important role. 

We use this solution as file storage for SAP HANA. It serves as both local storage and shared storage.

In my role as a solutions architect, I often work with clients who have demanding performance needs for their VDI. Recently, I had a client managing language telephone line data with a requirement for extremely high IOPS, reaching up to 45,000-48,000. In such cases, where Azure Files' premium option falls short, we recommended Azure NetApp Files due to its ability to provide the necessary performance and seamless integration with Azure services. This tailored approach ensured the client's VDI solution met their specific performance and data management criteria, especially when considering their plans to use Azure database solutions.

Some of the instances in the cloud, they needed NFS mount, and Microsoft did not have anything. That's why we are using Azure NetApp Files, we need to export NFS shares across multiple clients.

We are using version 1, which is the best version in my opinion.

This product is deployed in the Microsoft Azure Cloud. 

We are using it for virtualized SAP systems in Azure, running our SAP systems in Azure.

We primarily use the solution for Azure Virtual Desktop (AVD), our main use case, which involves storing user profiles and related data.

We are using Azure NetApps Files for our houses.com solution.

The primary use case for Azure NetApp Files is unstructured data.

We have this solution deployed both on Microsoft Azure and on-premises.

We have implemented Azure NetApp Files in our lab, and we have tested the NFS and CIFS protocols. We are looking for the multi-protocol approach, where the clients can leverage both protocols to access files, whether they are using Windows or Linux. Once we have this, and the data protection is in place, will we begin using this solution internally.

We use this solution for SQL backups and restores.

Right now, we've stopped using this solution because we finished our migration. We are looking to work with Microsoft and NetApp to see what other innovations we can do with this solution, on other practical problems in our infrastructure that it can solve.

We are using it for some of the workloads related to SAP. We are also using it to store data related to videos coming from some of the cameras in the customer facilities.

We have been using its latest version.

We use Azure NetApp Files mainly to collect events and for configuration.