What is our primary use case?
We have a hybrid Microsoft Azure File Storage deployment. One of the models is running onto the cloud where all the images and KYC data is uploaded onto the cloud platform, and that is stored onto the file storage.
We have developed our own payment solutions on a mobile platform, where we have two modules for our solutions. In the first model, we host it as an entire SaaS solution where clients will bring their merchants and will use our solutions. The second model is where we sell this solution to the clients, offshore, and the client will host it on their premises or onto the cloud. My clients are Indian banks and overseas banks
Another model of the solution we sell is for offshore clients, the client will host it on their infrastructure or onto the cloud. My clients are Indian banks and overseas banks. Many banks are connected and are using our solutions over the cloud. For example, if a customer with the corporation wants to onboard their own merchant to use these solutions, they have to onboard the merchants and confirm the KYC.
We have developed a digital platform where sales and the other staff can go to the merchants, and upload their KYC data, such as identity verification and address verification. All this data will go out through the mobile phones by clicking the pictures. All of the images will be uploaded via the API calls at the backend application, which is Microsoft Azure File Storage, and all those images get stored, encrypted onto the file storage.
What is most valuable?
We have not explored the desktop performance analysis of the file storage, but the user interface, API, and the response that we receive over the file storage are very good. We have a lot of customers that connect to the client-side, click the images, and upload them. The beauty of the solution is that we can mount the file storage into a critical server as well as an external drive. The speed that we receive with the images is pretty good.
What needs improvement?
In our use cases, we see the weakness in mobile internet connectivity.
When the user clicks the pictures of the identification and verification, addresses, those images have different sizes. If you click via the HD camera, it takes four to six Mbps. The issue is not with the Microsoft Azure File Storage, but the issue is at the front end when it is uploaded from the mobile network. This is the main pain area for us, and we are looking for a way to compress the images to the best possible minimum size, to allow them to be uploaded without any issues, without any dependencies on the external network.
For how long have I used the solution?
I have been using Microsoft Azure File Storage for approximately two years.
Buyer's Guide
Microsoft Azure File Storage
April 2024
Learn what your peers think about Microsoft Azure File Storage. Get advice and tips from experienced pros sharing their opinions. Updated: April 2024.
769,976 professionals have used our research since 2012.
What do I think about the stability of the solution?
We have not seen any problems with the stability of the solution.
What do I think about the scalability of the solution?
Microsoft Azure File Storage is scalable. Using the cloud, the entire model is scalable.
By using the load balancer, we have our in-built APIs for all the applications, which are Microsoft Azure File Storage, which is very scalable. We are using Microsoft Azure File Storage to receive and to have access at very fast speeds globally. The backend, modules, and the application on virtual machines, which is again scalable. We find it's very easy to host it on the cloud, because when it's already an on-premise server, they have many constraints, such as time, hardware, availability, and labor force. The solution is very easy to scale, you can scale out or scale in on demand. It can even be automated on the cloud.
We have many customers that are using our solution which uses Microsoft Azure File Storage. For example, there are five overseas banks that are using their own solutions, the Commercial Bank of Qatar, the National Bank of Dubai, RAKBANK Dubai, and Network International Dubai. Our solution is one of the very first solutions in India where you can accept your payments on NFC-enabled mobiles using our applications. We have approximately 10 to 15 Indian banks that are using the solution.
Which solution did I use previously and why did I switch?
Our payment solution, it's a complete hybrid model. There are many models running on-premise, and many models running on the cloud, such as AWS and Azure. My payment application is not hosted in one vertical. There are many verticals to it and different product portfolios. The core payment application is on-premise, and certain verticals are hosted onto the AWS platform, but the digital merchant onboarding platform is on the Microsoft Azure File Storage.
The main difference between AWS and Microsoft Azure File Storage which we have found from our compliance perspective since we are in the highly regulated payment industry is that AWS only has the presence in the Mumbai region in India, but Azure has two presence in Chennai and in Mumbai. From the compliance point of view, we found that since our on-premise is again in Mumbai region, we cannot have disaster recovery in the Mumbai region. This is one of the cons for AWS, for which we hosted the merchant onboarding platform on Azure.
How was the initial setup?
The initial installation of Microsoft Azure File Storage was straightforward. The process was not difficult for the implementation of the solution with the module, it took approximately 30 minutes.
I rate the initial installation of Microsoft Azure File Storage a four out of five.
What about the implementation team?
There was a team that was doing the implementation of the Microsoft Azure File Storage. The team consisted of system administrators.
What was our ROI?
We have not seen a return on investment with Microsoft Azure File Storage because we are running a small infrastructure with this project. We have not increased to the level where we have seen a return on investment. However, we have seen a return on investment for the AWS platform.
What's my experience with pricing, setup cost, and licensing?
In Microsoft Azure File Storage we only pay for what we use. We don't have to pay for what we are expecting to use or what we are locating, we only pay for what we are using. This is the advantage of the cloud.
One of the major benefits for AWS is that they have a very large customer representative base where clients can be picked from, they offer large discounts and credit. We were not able to receive the same kind of offers from Microsoft Azure File Storage. We tried to approach Azure while hiring for our disaster recovery discussion, but we didn't receive anything from Azure.
If we use a Microsoft Windows computer we will have to pay additional fees for the license for Microsoft Windows.
I rate the price of Microsoft Azure File Storage a five out of five.
What other advice do I have?
We are focused on the Indian market and we have a lot of SMEs and enterprise customers. The most difficult aspect of capturing more customers is for Microsoft Azure File Storage to offer higher discounts and credits. They do not provide enough discounts.
I rate Microsoft Azure File Storage an eight out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.