The initial setup was straightforward. I would rate it eight out of ten.

The initial deployment is done by Microsoft's partners/hardware vendors. It was quite straightforward for us because we just had to provide our tenant credentials, and network resources and start using the platform after it was deployed. It took about a week to deploy it and it was done by a systems engineer.

The initial setup is straightforward and simplified, particularly when following the available documentation.

The initial setup is easy. It is in the clear. We have a multi-tenant environment. 

I can set it up in a few hours, but configuring everything may take a few days.

The solution was initially deployed on an on-premises model, and currently, my company is shifting the product to the cloud.

The solution's implementation phase took place over a span of approximately two and a half months.

People from Azure managed the deployment of the solution in our company from their end, so I don't know the efforts people put in to deploy the solution.

The tool is very simple to deploy. The deployment takes two to three hours. It is easy to maintain the product. We need a team of two to three persons with expertise in networking, storage and server setup, virtualization, and Kubernetes.

If you want to do setup right, then it requires time and is complex. The risks are high if you deploy too quickly. 

Fortunately, we used a partner to set up Azure Stack instead of doing it ourselves. It was relatively simple for them to set up the solution. If we had done it ourselves, it would be pretty complex. The partners who set up Azure Stack for us have done it for a number of organizations. It was pretty quick, and it took a matter of weeks to set it up.

The setup is easy with no challenges but upgrades are complex. We have experienced challenges when upgrading components from one plan to another plan. Setup does not have these challenges. 

It is easy to set up. It takes you minutes to set it up.

The initial setup is moderate, not extremely simple but not very complex. It is hybrid but depends on the requirements of the client. The percentage of workloads on Azure Stack varies across our customers, ranging from ten percent to sixty percent. We opt for Azure Stack as a hybrid solution when a customer has some workloads on the public cloud. Typically, we set up Azure Stack in an on-premises data center and migrate workloads from existing environments, such as VMware or Hyper-V, to Azure Stack. 

However, if the workloads are primarily for the public cloud, we migrate them directly to the public cloud. The choice between Azure Stack and public cloud migration depends on various factors, including connectivity, compliance, costs, and other specific requirements. In essence, our Azure Stack environments are hybrid, with around thirty to forty percent of workloads residing on-premises and the remaining fifty to sixty percent in the public cloud.

I would rate it a seven out of ten. 

The initial setup depends on the situation. Typically, it is simple. Suppose you're buying and provisioning Azure Cloud sources from the Microsoft website and have the online payment through Mastercard. In that case, you can build up your own customized cloud through the Microsoft website, and they will provision your cloud for you, and it'll be ready within a few minutes or hours, depending on the requirement. 

In some cases, it depends on the customer's solution and what our customer is looking for. Sometimes, there are some compatibility feature sets from other service providers that have to be deployed in the Azure Cloud, and how much time Azure Cloud would take to complete its provisioning. 

It is simple if you need one virtual machine or block storage from Azure, and you need to have the Windows operating system and the RAM or memory you require. It's one click away and done within a few seconds.

However, if you are building up a solution for some product that requires, for example, 300 virtual machines and there are a lot of resources that involve some third-party SaaS, this might take some time. 

Overall, it is straightforward, and I'd rate the implementation process eight out of ten. With cloud service providers, many things are automated, and everything is happening virtually. That relieves a lot of the complexity. Anyone who understands cloud technology should have very many issues. 

We have ten to 15 people who can handle deployment and maintenance tasks.

I would rate the initial setup a seven, where one is difficult, and ten is easy. The deployment took around two to three months. 

The initial setup is straightforward if you are familiar with some of the architecture. The complexity may increase if you have a large amount of data that needs to be migrated. 

I rate the product's deployment a six out of ten. It took about a month's time to complete. 

The initial setup of Azure Stack is simple.

The solution is deployed on the cloud.

The solution doesn't need configuration as it is prebuilt on hyper-converged infrastructure. Its deployment takes two to four months to complete. The process involves installing the hardware and network requirements. 

The solution is deployed on Azure Cloud.

The deployment part was a bit difficult, but the document helped me to get it done. While configuring it, we faced issues with its network interfaces, along with some security issues and vulnerabilities.

It took me around 40 days to implement Azure Stack.

The deployment is probably not easy. Certain elements are easy to deploy, but certain elements aren’t. The ease of deployment depends on the maturity of the technical teams. If they're quite mature and experienced, then it's not too much of an issue. If there is a knowledge or skill gap, then, obviously, it'll be quite an issue. However, if it is a large organization, engaging with Microsoft is probably fine since it can fill in all the gaps for the organization.

The initial setup is pretty straightforward. It is a lean, shallow learning curve. They can quickly grasp it and can start working on deployment. The deployment was pretty smooth because we set up the CI/CD pipeline and Azure pipeline, which automatically builds the solution. It does the unit test and performance test, and if everything goes well, it is scheduling the deployments for production quickly.

One or two people are needed to maintain this solution.

The product has been simple to set up. The deployment is quick and takes an hour. It's not complex or difficult to implement. It's really quite easy. It's a next, next, next flow where you click through and run the software. When you implement it, you attach it to your Azure account and that's when the real work starts, of course, as then you have it up and running.

I would say the initial setup is medium. It all depends on who is using it, but most customers rate it as a medium. It's not easy, but it's also not difficult. It's average. It's a medium.

The initial setup was a little complicated but not too much. 

Azure Stack’s initial setup is easy.

I rate the ease of initial setup a four out of ten.

Setting up Azure Stack isn't as straightforward as IBM's Cloud Pack for Apps. IBM's solution uses OpenShift implementation, so it's fully automated, whereas the Microsoft solution has some hardware issues, so we had to some manual configurations. The total time for deployment was around one week, I guess.

The setup and integration are straightforward.

Azure Stack is also in the cloud, so it's easy. We also use the Internet Information Server. If you use the node server, it's going to be local and based on the technology you're using. We can choose between one or the other.

For example, we use Mongo Atlas service on Azure and on-premises. Both use the MongoDB Atlas service. It is architecture bound, so you have the choice of going through Azure or the on-premise solution because both have advantages.

The initial setup wasn't as easy as AWS, which has a much simpler deployment.

We ran into issues in terms of migration. Not everything was fully migrated, originally, and that caused us a lot of problems. It's still not quite set up how I would like it to be.

It's not complex at all. Based on the customer's requirements, we implement the solution. The deployment usually takes approximately 15 days.

The initial setup is easy. 

Installation is straightforward and not very involved. It can even be automated. 

The deployment was straightforward and really nice. While creating a system and configuring a cluster is possible, it would be really beneficial to do this in the reverse, since the cluster can be pushed in using the hardware management ID. 

The initial setup was quite a long time ago, so I don't remember the details of the implementation.

The initial setup of Azure Stack is very simple. It takes approximately 48 hours to build a complete platform.

The initial setup was straightforward. We have a business unit that specializes in this and they set it up from scratch.

We've found the initial setup to be quite straightforward and simple to execute.

The installation is easy, there are only a few clicks.

The setup for Azure becomes more complex when you have multiple users. When you have multiple organizations, with multiple users working or using the same solution, data storage needs to be very well separated because of privacy. That is a piece of complexity that is embedded in the way we provide our services. There is no link to Microsoft or any software provider service. We defined how to make it work that way.  

The initial setup started in a straightforward manner, but I faced some issues during the deployment. I was able to solve these problems with the information that I found on the Microsoft website when I searched for the errors using Google. Once I followed the steps the solution seems to be fine.

The initial setup is very, very simple because it comes fully integrated from HP with Microsoft integration. That makes the setup very straightforward.

The initial setup is not complex.

The initial setup was really simple. We did not face any difficulty when we deployed the SAP solution with the Microsoft SA.

I think that the initial setup is okay.

The initial setup was simple. It took a few hours.

The initial setup is straightforward.

I cannot answer this question because I joined the project when they had installed Azure Stack on computers used for the projects.

It is not too complex to set up Azure Stack. It was faster to deploy than the AWS solution that we tried.

The setup isn't complex and is faster than AWS.

The initial setup was easy, I didn't find it to be complex. Because it's validated hardware and software, any patches that have been released are validated by Microsoft itself.

Azure Stack is a closed box, but it is compliant. It doesn't permit you to customize the network or the features. You have to take what Microsoft is offering and just simply obey it.

We are using a connected model, as opposed to a disconnected model.

The initial setup is straightforward, not complex. 

It took a week to deploy this solution.

Setting up Azure Stack is easy.