Setting up Microsoft Azure is generally straightforward, but from a non-technical standpoint, Microsoft Azure File Storage can be somewhat challenging. I have helped others who simply wanted to use it as a central storage system, and it can be difficult for other people within the company to utilize it due to its somewhat complicated nature.

The deployment of the solution is quick because we use DevOps in our pipelines which reduces the time to 15 to 20 minutes to deploy.

The setup of Azure File Storage is undertaken by the delivery team, but from a pre-sales perspective I haven't heard anything untoward regarding the setup, or anything that suggests it is very challenging. We have a partnership with Microsoft, so whenever we have challenges with setup or implementation, we invoke our alliance and somebody from Microsoft comes along to help us.

The initial setup phase of Microsoft Azure File Storage was not easy.

The deployment process was completed in two weeks.

The initial setup is straightforward.

The initial setup is easy. The deployment model depends on the customer. Some want cloud, but if it's not suitable, it's deployed on-premises. Most customers are hybrid.

Moreover, the deployment time depends on the workload. Some take minutes, and some take weeks.

The initial setup of Microsoft Azure File Storage is simple. Someone with basic technical knowledge can handle the task.

The deployment of this solution is not carried out by my team but I believe the implementation required five people. 

The solution's initial setup process was straightforward.

Around two weeks were needed for the solution's deployment process. Also, the deployment process is something which one can do by themselves.

Only one technical person is required to deploy and maintain the solution.

The initial setup was easy from the user's side. They could quickly get access to the data. The deployment takes some time. First, we need to buy the storage and implement the policies per our network design. Whether it will take one week, two weeks, or one month depends on the network design. If we are on-premises, we must buy hardware according to our requirements. For the deployment, we had a technical team consisting of an assistant manager for network, system, or micro administrators. Also, there is a network engineer or system engineer. The solution is deployed on the cloud and on-premises.

Microsoft Azure File Storage deployment is quick but depends on your connection. A good connection takes one or two clicks, and the deployment time also depends on the data you have in Microsoft Azure File Storage.

If you have more data, then that takes more time. Still, Microsoft has improved the capabilities, quality, and protocol to help enterprises transfer even massive amounts of data many times. I don't have much data, though, just around 500MB.

Implement the service is quite easy, managing permissions can be tricky when starting from zero on this topic.

The initial setup is easy, straightforward, and quick.

The solution is deployed on the cloud.

The setup itself is straightforward. It's not difficult to implement. 

The public cloud service makes the initial setup easy and straightforward.

The setup is easy and easily doable. As long as the steps recommended by Microsoft are applied, it is not very complex. 

The product’s initial setup process has medium complexity. We review the code and share the details with the DBA team. Further, they execute the deployment. It takes five minutes to complete.

It was always very easy to implement. The self-storage was connected to a logic app and the part of the logic app was tricky to configure. However, in the end, after the learning path was completed, it was very easy. 

The file storage was always very easy to connect to the old tools that we needed to complete the POC.

The deployment itself was very quick.

In terms of an implementation strategy, the goal of the POC was to transfer files from a third-party company to our internal network. We implemented several file storage items for each country and we distributed the files that came from the third-party company to all of them.

We have a team of five that can handle maintenance, however, only one engineer is really needed. 

Microsoft Azure File Storage's deployment is straightforward and takes only five minutes to complete. 

The initial setup is fairly simple. If a customer needs help with the integration, we will re-do the whole process with them.

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.

The initial setup is simple.

The initial setup is pretty simple, and we completed it using documentation. The documentation in Azure is good because we have migration and containerization. In addition, the Azure migration hub is pretty detailed.

The setup was easy. When implementing, it is important to pay attention to the volume of data and different requirements for the synchronization of data.

It's a cloud solution. Its setup is a bit complex, but once you get started, you don't have any issues going forward. In terms of setup duration, I wasn't around when it was deployed. It was already deployed when I came to work here, so I'm not sure how long it took.

The solution's initial setup contains a moderate amount of complexity. I can't say it's easy. I cannot say it's complex. However, if people know the solution, they likely have a good idea of the product and what to expect. It's not very hard, but, again, when you can go and set up, especially if it's a big infrastructure environment, you have to understand the storage and the network and to know the framework you are working in. 

The deployment took a couple of days. 

The setup process for the solution is simple.

The solution is easy to set up. It requires three to four executives to deploy and takes 15-20 minutes to complete.

The initial setup was complex. There is a lot to do to build it out. There are a lot of nuances to how the MDM works and that makes Intune a little bit harder to work with. Unless you have done it a few times and paved the pain points of some of the things that you have to do in configuring it, it is going to be hard.  

At the same time, it is hard to say how long a deployment takes. That is because you can roll out Intune in a matter of a few minutes, but building it out to function the way you want it to is the part that impacts the speed in which you implement it.  

The initial setup is simple. I would rate the setup a five out of ten. Consultants are required for the deployment of the solution. 

The initial setup is straightforward. We find it easy to implement.

The setup was easy and straightforward and the deployment didn't take too long. It is a static plan, so we have to see it first and then we organize. We did have some help from a consultant when we did the deployment. 

The initial setup is fairly easy.

The initial setup is straightforward. Deployment time depends on the size of the project but it's easy and simple.  

The initial setup is straightforward. Two of us did the pilot testing before the deployment.

Microsoft Azure File Storage's deployment is not complex.