The initial setup is pretty simple. It's not overly difficult or too complex. 

Creating blocks or containers is easy. We can deploy according to a rule-based access controller policy. For example, when you are adding some documents for your owner or administrator, but somebody accesses your log or something, it prevents them from deleting or it or modifying that content because it might be sensitive. 

Creating the block itself is straightforward. Then we create a shared access policy to allow us to manage access directly. If I'm doing development, I can limit it so that we can make it read-only. That is possible, but we need to plan accordingly. 

I rate the tool's initial setup a nine on a scale of one to ten, where one means it is difficult and ten means it is easy.

The initial setup of the tool was easy.

The solution is deployed on the cloud services offered under Microsoft Azure.

During the installation process, my company first indulges in the preparation phase, then the testing process, and finally gets involved in the production and deployment parts.

Two people are required to take care of the tool's deployment process.

The solution can be deployed in two to three days after its testing phase.

The implementation process is very simple and straightforward. I do not find it to be complex. There might be a few things here or there during setup that may be a little complex. However, it is not hard to get up and running. 

Initially, it took us three or four days to begin deployment as we had to watch some videos and go through the documentation. 

To deploy the solution, we had to first log in the Azure, then we had to create an Azure account. Once we created the account, we had to start creating storage and setting up the configuration of the storage logs. It takes time during the initial phase.

While we do not need any technical staff at this time, in the coming months, we are planning to enhance things and add in new requirements. We'll be increasing our infra and our storage, and that may require two or three more people to handle that process. 

Setting up Azure Block Storage is more complex than it should be.

The initial setup is very simple and straightforward. It's not very complex. It's much easier if you do some planning and can anticipate some outcomes. Doing that work makes everything easier as you do the implementation. Those with IT backgrounds will find it easier to handle the setup as opposed to those who are not so technical.

The initial setup is straightforward. The deployment takes one to two hours. We use our applications to structure the folder and put the files in the product. We do not need to create the storage. We just need to design the folder structure for our ADLS. It is pretty simple.

The solution is easy to set up.

The initial setup is straightforward. Opening a service does not require much effort, as it is already automated. However, if we plan to use other services such as a Python library or storage account, there is a certain process we need to follow. The REST APIs and shared keys will be needed for this purpose. This information is already available in the forum.

The initial setup was straightforward, not that complex. 

Setting up was probably a month's time, not more.

The DevOps engineers would be required for the deployment. In fact, data engineers can do it if there's no proper CIC mechanism, however, any DevOps expert can do it.

The product's initial setup phase was straightforward, and if you need extra security, you have to do more probing. I believe the setup phase to start the product is pretty straightforward.

The product's setup phase with the whole of Azure and the documentation part took a few hours.

Microsoft Azure Block Storage's deployment process is not directly tied to Microsoft Cloud Storage, as it allows for the issue of APIs. Unless you are talking about deploying our company's applications, which would lead to a different conversation at this point, I can say that Microsoft Azure Block Storage's deployment process is a simple plug-and-play, after which you have access to the product.

Microsoft Azure Block Storage is a service provided by Microsoft, so it is not something that you deploy. If you already have the whole Azure infrastructure in place, then all you have to do is deal with the provisioning of an account and take care of the usage part of the solution to let Azure know if you want the services to be billed or not before you get it up and running. Azure manages the infrastructure where its products are used, so it's not deployed on an on-premises model or anything like that, as it is considered to be a managed service.

For the deployment and maintenance phases of Microsoft Azure Block Storage, you need a developer to write the codes to do whatever function you want. Then, you would need a DevOps person to ensure that the infrastructure provisioning is correct.

The initial setup is difficult. It is very difficult to identify the things we need. I rate the ease of setup an eight out of ten. Deploying the solution takes less than a minute, but the process is difficult.

The initial setup for the production areas was on-premises, which is very simple.

The initial setup was straightforward. We did the deployment ourselves. They have good online documentation.  Producing the storage account took about 10 minutes max. The overall configuration took maybe 10 minutes. To make it work properly took around one hour.

It only took one person to deploy it.

Most of the users use it as the default storage. We have close to 1,000 users using this solution.  

It requires one person per team to maintain it. so maybe one person per team, it would be a maximum of a hundred people. 

It's used across the organization by the technology team and the data science team. We're not looking to expand the usage because I feel that at least this part of the solution has reached the desired audience.

The solution’s initial setup is simple and straightforward.

Setting up Microsoft Azure Block Storage was easy, and it only took two minutes. I researched how to do it, but before you set up Microsoft Azure Block Storage, you must create your agile accounts first, and inside the agile accounts, you'll find different types of storage. In my case, I chose Microsoft Azure Block Storage for data storage and extraction. It was easy to set up.

The initial setup is easy. There won’t be any hiccups. Even a beginner who is interested in learning the cloud will have any issues setting it up.

The solution can be deployed manually from the Azure portal, or it can be done programmatically, via code. The setup is very easy and straightforward. It only takes a few minutes. I rate it a five out of five. 

Azure Blob Storage is very straightforward to setup. It is just about setting up a storage account, putting in a container, and that is all. It is pretty easy. It really takes just a few minutes.  

The solution was not deployed by me directly. 

I rate Microsoft Azure Block Storage a nine out of ten for the ease of its initial setup.

The setup is not as simple as File Storage, and it requires a lot of investment because block storage requires a high-speed network, and you have to deploy a lot of fibre cables. It is also costly and not cheap compared to Internet-based networks. So the initial investment cost for deploying the block storage is very expensive.

The initial setup for Microsoft Azure Block Storage is simple. It's more of tweaking the connection settings or connecting it to your DB.

Deploying the product took two hours.

The setup process is pretty straightforward.  The documentation from Microsoft is clear enough for anyone to set up a storage account. Two or three people are enough to maintain the solution we've built. It's a stable solution that more or less works on its own.

Microsoft Azure Block Storage's setup is straightforward. You need to create a storage account and give a unique name to it. We have deployed the solution on the cloud. 

The initial setup of Microsoft Azure Block Storage does not take long to deploy. Each service can take 10 to 15 seconds to set up.

With an Azure level of understanding, the solution is relatively straightforward to implement. However, from a technical standpoint, it is not the most straightforward to configure, and so I would rate it a seven out of ten.

The initial setup of Microsoft Azure Block Storage is simple.

Setup was easy.

The tool's deployment is simple. 

The initial setup of Microsoft Azure Block Storage is more complex than Google Drive, but it is still not too difficult.

The initial setup is straightforward.

My engineer can complete an installation in one or two days. I don't directly deal with it as it's quite complex. You need to be technical. It’s not for non-technical people.

We have five people that can handle deployment and maintenance. They are systems and ops engineers.

The initial setup was straightforward, we had assistance from a third party.

The tool's deployment is easy since it is a Microsoft cloud-based product. 

The initial setup of Microsoft Azure Block Storage is simple.

The installation of Microsoft Azure Block Storage is simple.

Setup was simple. Between 5-10 people are required for maintenance.

The initial setup was straightforward.

The initial setup is very simple and straightforward. It's not difficult.

The initial setup is easy. 

The ease of setup is the primary reason we use Azure Block Storage. The setup takes one or two days, and we had help from Microsoft. We had five people on our team.

Initially, we had some issues but we were not trained. We were used to the legacy environment, so we had challenges. But anyone who has technical knowledge will be able to set it up and understand it, once they start reading about how to set it up and how to use it. 

There are a few challenges, especially when we are setting up block storage or setting up the network. There are complexities of the network environment, such as creating the virtual networks, etc. It's complex.

I would say the setup is simple. 

It is quite straightforward. You can set it up even when you don't know much about it. You log into Azure.com, which is free for one year, and take a virtual machine and storage and then run your own website through Microsoft Azure Block Storage. You can store your image files, videos, and other document files from there. It is very easy. Oracle Cloud and AWS also provide the same ease of use, not only Azure.

Our setup is rather complex. It is easier for our customers - they simply get the tenants in our products and within the tenants, we just plug in all the drivers on-prem and then he gets a complete insight of the overall workload. 

I am, however, not involved in the installation. Another difficult thing is to create a good architecture that's strong on networking and that will enable customers to deploy or provide all those different environments in an easy way. So the thinking is critical, and architecture is very important, which is kind of complex. 

Deployment takes between two to five days, depending on the customer and the speed on the cloud.

We have a power desk with three people who are responsible for support and maintenance, customer queries, etc. 

Its installation is okay. It takes around one hour.

The initial setup is simple for me because I have a lot of experience. There are some frustrating elements with the solution that require the updating of PowerShell modules each day and that requires a lot of work. 

Installation is simple. You don't need an integrator or consultant for setup.

The initial setup was easy. All I needed to do was create an account and begin configuration.

The initial setup of Microsoft Azure Block Storage is easy.

The initial setup is straightforward. It's not very complicated. We handled the deployment in stages. It took, at maximum, just over a week.

Setting up Block Storage is simple. We handled it ourselves, and it only took around an hour. After deployment, all the maintenance is done by the provider.

The initial setup was smooth and straightforward. The deployment took very little time. The main time frame taken was on the SAP side. We put SAP on the Azure cloud which took some time.