The initial setup is straightforward. You just have to create a storage account. You can automate that also. You have different mechanisms. You can use Azure templates, like SQL, or you can use the Terraform as well. To automate the creation of that object storage or any account. Or, if you have different APIs, like Python-based API, you can easily create what you need.

The solution's initial setup is easy.

The initial setup is very straightforward. It did not take more than an hour. To deploy the solution, we must prepare Azure Storage on Azure Portal. If the end-user or the customer doesn't have an Azure subscription, we create a subscription from our distributor channel. Then, we create the storage for our customers after granting the necessary permissions. For Veeam customers, we go to the Veeam management dashboard, create a backup job in the configuration settings, and point to Azure Object Storage.

I found Microsoft Azure Object Storage simple to set up, but it depends on how well you know the service. If you know the service, then setting it up is pretty straightforward, but if you do not know Microsoft Azure Object Storage, you first need to understand how it's meant to be implemented. For me, setting up the solution is easy.

The initial setup is usually easy.

The solution’s initial setup is easy.

I rate the product's setup a nine out of ten. The deployment team had around 20 members. 

We haven't been actively maintaining the product from our end. Currently, our technical team comprises 20 engineers.

There's not really an installation. It's a mapping solution. It's on the cloud. 

We have a common cloud team. They do any maintenance. It's a common cloud team who provisions the server, who manages the storage, who assigns the storage to the server. They do everything. We don't have a separate team.

The solution's initial setup is straightforward.

It is a very simple process.

The setup is straightforward.

Microsoft Azure Object Storage's deployment is straightforward. 

The initial setup was quick. You definitely need some help with that, and Microsoft provides resources for learning. I have in the past attended workshops that came in handy when working with this solution. It's easy to use if you have some hands-on experience. There are online courses with hands-on labs available in some cases on Microsoft Learn which makes understanding and using this solution easier.

Regarding the integration and setup of Public Storage, it was a bit complex. The upgrade process was okay. In terms of time, I'm not sure about the exact duration of the deployment. We use object storage for data related to different customers. I'm still learning about the steps involved in deployment.

The process is not that complex. There is a challenge finding resources who understand the cloud, however. With most of the technologies, there is enough documentation, however, what happens is, when you are looking at the whole ecosystem as such, you need resources that know what is happening. Generally, there are articles that can assist you with the setup. Therefore, for those who have knowledge with the solution, it's straightforward, however, newer users would find it possibly a bit complex. 

I'm not sure how many people would be required to maintain the solution. 

During the initial setup of Microsoft Azure Object Storage, we used File Explore, so it was not that difficult. It was via GUI, which was helpful. One challenge was when using the command CLI because it was new to us. Over time, we are ok with CLI too.

It is easy to set up. You just sign in. You have to have a cloud subscription. Once you deploy a disk or any sort of object that can be manipulated in the cloud on a cloud-based model, all you do is sign in, and access should be granted to that resource.

The initial setup is somewhat complex. I provide the networking or underlay for services and other team members deploy the solution. 

The initial setup is straightforward. We had no issues with the deployment because we used GitHub Action, Azure DevOps, terraforms as well as AMS scripts to build and deploy. Deployment did not take more than a minute.

The initial setup is fairly easy. It's not difficult. It is mainly a hybrid solution.

The initial setup is straightforward. It’s deployed on the cloud.

I rate the initial setup a five out of ten.

The initial setup is fairly simple.

The setup was complex. We created an account and decided on ways to retrieve passwords. We must also add our mobile number to the account.

The solution is very easy to set up. It's not overly complex. 

The initial setup is easy. For the deployment we have we have Data Form Scripts. So there are  CDs for deploying everything in the in the cloud. Three to four software engineers  are required for the maintenance of the solution. 

The initial setup is straightforward and it is not complex.

It is very easy to migrate all of the mail processes.

Knowledge is very important, which is why we used the help of Microsoft integrators.

As with everything from Microsoft, the initial setup is straightforward.

It took about two months for us to deploy for our client.

The initial setup was of medium difficulty. I would not say that it is simple or complex, and they have good documentation to help.

It took more than six months to fully migrate to the Azure environment.

I rate the initial setup process a seven out of ten. You need to understand many things by referring to the documentation before implementing it.

The initial installation of Microsoft Azure Object Storage is easy.

The initial setup of Microsoft Azure Object Storage for me is easy, but it depends on the person. If you do not have much experience it is not as easy. The whole process of implementation took 15 to 20 minutes. We have automated a lot of the processes.

When doing the deployment of Microsoft Azure Object Storage we have experienced some issues with our scripts and the automation.

The initial setup was straightforward and took a couple of hours.

The complexity of the setup depends on what your requirements are. If you are deploying from scratch versus needing to migrate data, it is different.

For the most part, it is fully automated. We have written some scripts to assists us and the deployment normally takes between 20 minutes and an hour. It also depends on what region Azure is being used in.

The initial set up is easy. It's not overly complicated. That said, we have a lot of problems in the implementation with the partner, the company that we hired to do the service. We had a lot of errors and a lot of time was consumed in uploading the backup to the cloud, as there was a lot of information. 

We have about 10 terabytes of data. For some companies, it may only be a few terabytes. However, for us, we had a lot of information. We were affected by internet speeds, and, if something failed, it was necessary to repeat the process. It was extremely time-consuming.

The initial setup is straightforward. It requires a little bit of technical expertise. Not everyone can configure Azure. You will need some amount of technical skills or help from a Microsoft Expert. We have been using Microsoft products for many years, and that's why it is easier for us to implement. It may be a little bit tricky if you are not using the Microsoft environment.

We deployed it in ten days because we have to install our own software and do a few other things. Otherwise, it should take only one or two days. 

The initial setup is pretty straightforward and it probably takes a couple of days to deploy.

The initial setup is straightforward.

The initial setup was easy and straightforward, not at all complex.

It took us about a week to deploy. There were four people involved to help with the deployment, one architect and three engineers.

For maintenance, most of it is automated, you only two or three to monitor and support it.

The initial setup for the solution is straightforward. It's simple, in fact. It's not complex at all. Deployment is fast and easy too. It only takes about 20 minutes.

In our company, the maintenance of the solution is outsourced. We have a team of four outside the organization that handles it for us. They're like a support team and handle everything 24/7.

The initial setup was simple.