When considering the suitability of Azure, it largely depends on the complexity of the use case. For data analytics teams with a headcount ranging from ten thousand to fifteen thousand, Azure proves to be a highly effective solution. However, for large-scale processing, the choice might vary, especially depending on the industry. Sectors like automotive or pharmaceutical could comfortably opt for Azure as their primary platform, although specific teams within these industries might still require high-end processing solutions like Google BigQuery or Amazon Redshift. Azure stands out for its user-friendliness and intuitiveness, making it an excellent choice for those looking to get started quickly. It's notably easier to use compared to AWS and Google Cloud, offering straightforward solutions that require minimal training. I would rate it eight out of ten.

My advice to new users would be to consider the business objectives, if you have a Microsoft environment, want to consolidate on a cloud platform, and have sovereign requirements. Apart from that, you need to focus on the value it brings to the operations, rather than the cost of the platform. It's a value approach. If you look at the convenience and speed of implementation, it adds value to the business. 

Overall, I would rate the solution an eight out of ten.

My primary advice would be that if your organization or a client decides to embark on an Azure journey, it's essential to start by going through the Microsoft Learn portal. This resource will provide you with a strong foundation and a head start in understanding and using it effectively. Overall, I would rate it eight out of ten.

I would advise you to clearly define your objectives and what you want to get out of it. It may not be the silver bullet that you might be looking for, as it requires shared responsibility.

Overall, I would rate the solution a seven out of ten. If you look at the documentation set, there are rims and rims of it. You try to drive something from the console, and it's quite complex. It's not it's not easy and straightforward. You've gotta sit down and review it, look at the documentation, and work your way through it. It's not intuitive.

I am satisfied with the overall product.

I recommend those who plan to use the product in the future to do their homework and learn everything about it before purchasing it.

I rate the overall product a seven out of ten.

We are using Microsoft products. We also bundle it with some of the solutions we provide to our customers. We don't need compliance at this moment. Azure Stack is not very popular in the HCI industry. We have used VMware and Nutanix. Compared to them, Azure Stack is a better solution. When it comes to Kubernetes, Microsoft is a leader in Gartner. It is very mature. Overall, I rate the products a nine out of ten.

The solution has been working very well for our company. For financial institutions, I recommend its use along with Microsoft Identity.

I rate the solution a nine out of ten. 

We have a Microsoft Edge device to transfer data between the cloud and on-premise. However, the backing for Azure Stack is purely cloud-based.

The deployment of Azure Stack was done through an integrator. The first step in deploying Azure Stack was to set up the Azure platform in the back end, to put down temporary Edge devices, and then later on, the actual dedicated Edge devices were shipped from Microsoft.

Fortunately, the deployment and maintenance of Azure Sack are done by an integration partner. They maintain it, and we pay them a service level agreement. I don't know what they've got operating in the back end, but a relatively small team of no more than five people keeps it running.

Regarding Azure Stack, I would ask users to be very mindful of what services they consume. It is like a buffet. So the more services you subscribe to, the higher the cost. So, the cost can escalate quite rapidly. There's a lot of convenience, but it comes at a cost.

Overall, I rate Azure Stack an eight out of ten.

Before choosing the solution or AWS, it is important to reach out to relevant engagement or sales teams to get product clarity. 

I rate the solution a seven out of ten. 

I would definitely advise others to implement it as an infrastructure service only because you get to learn more. You get to explore the code more and know different steps. You can automate more and better. You can get automation done on top of what is already there, which could lead to another invention. 

I would rate it an eight out of ten.

I would overall rate it an eight out of ten. 

We have a partnership with Microsoft.

We are likely using the latest version of the solution. Typically, we get scheduled updates from the cloud. 

As far as my experience is concerned, Azure is a very flexible and very stable solution. If you want quality and stability, you should move to the Azure Stack.

Of course, everything depends on the customer's requirements and what exactly he is looking for in the Azure Stack. Not all customers will use the full Azure Stack. Most likely, they will have third-party applications based on their current infrastructure, which they will want to deploy in the Azure Stack. 

I'd rate the solution eight out of ten overall. Amazon has more market share than Azure. Alibaba is beginning to challenge both.

Overall, I would rate the product a nine out of ten because Azure Stack is very reliable. It's highly available and provides the requirements needed by the customers' applications. It's also very secure.

You need to focus on what your end goal to achieve and build the system in a way that makes it easy to maintain from a software, perspective, and platform perspective.

I would rate this solution a seven out of ten. 

I rate the solution a seven out of ten. 

I recommend Azure Stack to those planning to use it. Most of our company's customers who use Azure Stack are happy.

I rate the overall solution an eight out of ten.

I advise others to appoint premise engineers to manage day to day activity of the solution. I rate it a ten as it is business-friendly and has all the features prebuilt.

My advice for anybody who is implementing Azure Stack is to start looking into DevOps early. There are a lot of things that can be done using the portal, and people tend to follow this process because it is easy. It's true that this approach may get things done fast, but it will only get you so far. Working with the DevOps capabilities, such as automation with Terraform, should be done sooner rather than later.

Every cloud has its pros and cons.

I would rate this solution a nine out of ten.

Azure Stack is a good solution since it allows you to explore more things, especially on the ML or DevOps sides. I would recommend Azure Stack to anybody planning to use it.

My company has attempted to integrate Azure Stack with products from other vendors. We haven't faced any difficulties integrating Azure Stack with products from other vendors. We provide solutions with Azure platform.

Overall, I rate the solution an eight and a half out of ten.

I work for the government in a department related to leasing infrastructure. We are using the latest version of the product. Intune has recently opened a lot of functionality very similar to Jamf. There's quite a big gap between what Jamf offers and what Intune offers.

People planning to use the product should engage with Microsoft quite early on and see what products would benefit them rather than trying to figure it out themselves. It would be good if Intune would offer features aligning with enrollment and asset discovery. Jamf provides these features.

Overall, I rate the solution a seven out of ten.

I think that anybody who wants to move on to Azure Stack, needs to assess their requirements, and what business needs they have. I would rate Azure Stack an eight out of ten.

I would rate this solution 9 out of 10.

We're resellers. 

I'd recommend the solution, however, for those considering it, the most important thing is to get ahold of somebody who knows what they're doing, for example, a consultant.

I'd rate the solution seven out of ten.

I would advise them to conduct a thorough assessment of the types of applications they want to host on Azure Stack before beginning the migration process. They must be absolutely certain. Then there are all kinds of local policies, security policies, on migrating data into the Cloud, to put it mildly. They should be on the lookout for such things. So, first and foremost, a proper assessment of what types of applications should be moved entirely to Azure Stack. Then, examine the policies, security policies, and cybersecurity that are associated with all of that.

I would rate Azure Stack an eight out of ten.

Azure Stack is deployed on-cloud in our organization. I would recommend Azure Stack to other users.

Overall, I rate Azure Stack a nine and a half out of ten.

I am using the latest version of the product. Azure Stack is an on-premise solution that gives cloud services to customers. We give it as a cloud service to customers. Although it is a fully managed solution from Microsoft, it has limitations. Overall, I rate the product a six out of ten.

I would rate Azure six out of 10. I don't have a lot of opinions on it yet, but when we start using it in production, then I'll have a better idea.

For those thinking about implementing Azure Stack, it's important to understand the customer's workflow and whether you're talking about IaaS, PaaS, or SaaS. I would rate Azure Stack as five out of ten.

I rate Azure Stack nine out of 10. It is a great tool if the technology you use is a Microsoft-based stack because Azure is Microsoft's cloud provider. 

I would only recommend this solution to smaller organizations like ours because I cannot really speculate what big issues that the bigger organizations will face. For a small or medium-sized college, it's quite good — I can't see any negative sides. In particular, our staff and students don't really use our computers. That means they are bringing their own devices and using their own computers. Because of Office 365, they don't need to come here (to campus) and they don't need to connect to any kind of VPN in order to access their emails or order their course materials or even the information that we provide on the internet, for that matter. Everything is on the cloud.

On a scale from one to ten, I would give this solution a rating of ten — strictly because I have nothing to compare it to.

Honestly, if I were to compare the two, I'd say that AWS is much better. It's so much easier to deal with and easier to understand. It's also easier to deploy and has a shorter learning curve overall. On top of that, AWS provides 20% of the traffic to the site. You don't need to update your processor for CPU and RAM. They do all of that for free. There's just way more up-sides to AWS than Azure, unfortunately.

Azure is just average. I'd rate it five out of ten. As an end-user, I find it far too difficult to manage, and it's not really worth the effort, especially when there are other solutions that make it so much easier.

My company is not very involved in the cloud, but Azure Stack is a product that we recommend depending on the customer. If their budget and requirements are appropriate, and they want the flexibility that this solution offers, then we can implement it.

I do not have experience with all of the products on the market, but from my perspective, Azure Stack is a good one.

I would rate this solution an eight out of ten.

From my experience, this solution is suitable for enterprise companies because of the higher price, the cost is huge.

It has to do with capability. If you need all the features, you don't need to buy all the stuff upfront; you can go to the cloud service of Azure. So, in terms of cost, this is the only thing.

Overall, I would rate the solution a seven out of ten. 

I work with Lenovo as a consultant, which means I handle deployment for others. 

We have a handlful of customers, most of whom are using Microsoft products, but some of whom use Windows. Many go with the Azure Stack solution. 

I would recommend the solution to others. 

I rate Azure Stack as an eight out of ten. 

We are using the on-premises deployment model.

I would advise others considering implementing the solution to ensure they understand the solution to a high degree, as they won't get much help from technical support if they have questions.

I would rate the solution eight out of ten.

I would recommend this solution to others.

I rate Azure Stack an eight out of ten.

My only comment would be to look at your use case and just weigh up both AWS and Azure to see which one best suits your use case and your budget. If you go with Microsoft Azure and you use all the security tools and everything that Azure offers, it will be an expensive proposition. Whereas AWS gives you all the security tools but it's less expensive. They both offer a similar service. It's just the cost differential.

I would rate it a nine out of ten. Not a perfect ten because of the price. 

I'd advise those who don't want to spend money on hardware to try the solution out. I'd recommend it to others.

I'd rate the solution eight out of ten overall.

I would recommend the solution to others.

I rate Azure Stack a nine out of ten.

Given the current direction and strategy of Microsoft, I think Azure Stack is one of the most comprehensive solution platforms available today.  

On a scale from one to ten where one is the worst and ten is the best, I would rate this product as an eight of ten. In my case, there really is very little Microsoft can do to make the score better. I could really never give a software product a perfect score. There is always something that can be improved. If you work in a flexible, dynamic environment, you have to make choices in terms of how to design things. You have to decide which additional components to use or incorporate, or to not use what are considered standard features that most other people use. Users' choices will be different depending on their needs, application, and adaptation.  

I think that this is a good tool for cloud operating systems.

I would rate this solution an eight out of ten.

I will definitely recommended this solution to others, especially for large companies, because I think it's a wonderful solution. It will also work great for people that has multiple companies inside the group. One should use Azure Stack as an on-premise private cloud solution because it is a very effective solution.

On a scale of one to ten, this solution earns a good eight. In the next version I would like to see an improvement in the monitoring tools.

My advice for anybody who is implementing this solution is to first look at the people within the community. They have provided details about their experience and it's a good place to start understanding and analyzing, before beginning the implementation. It will give you an idea as to costs, as well as how to integrate with your environment.

I would rate this solution a seven out of ten.

On a scale of 1 - 10, I can give Microsoft Azure Stack a 9.

This is definitely a product that I recommend. It has every feature that we need and overall, it's pretty good.

I would rate this solution a nine out of ten.

I would recommend this solution. I would rate Azure Stack an eight out of ten. 

My advice for anybody who is implementing this solution is to start small. As you gain experience and confidence with the platform, you can expand to larger tasks.

I would rate this solution an eight out of ten.

I would recommend Azure Stack because it is one of the best technologies in this environment and the programs are easy to use.

I would rate this solution an eight out of ten.

I would give Azure Stack an eight out of ten.

In the Middle East, we deal with a company called Logicom that Microsoft promoted and suggested to us. We are customers of Logicom and Logicom has a relationship with Microsoft.

I don't see any levels of risk involved unless there are different levels of risk that I am not aware of.

We have concepts called foil domain, availability domain, and geo-location. If you have this large domain in one rack and it is hyper-converged, and if one rack goes down then it's gone. You have to invest more money to get another rack to distribute the load amongst the two and make it high availability.

The more that you invest the more availability you get.

If you have applications running in a Microsoft-oriented platform then you have to be very clever, especially with architecture and design. It depends on your requirements. 

It's an expensive solution and even if you don't have the instances up and running, you are having to pay for the storage.

If the company is established with good returns and they are looking for a secure, safe, and reliable system, Azure Stack is a good choice.

Cost matters, no one wants to pay for virtualization. It is now available for free with the OS.

Assessing cost and reliability, I would rate this solution a seven out of ten.

It is very good. I would rate the solution an eight (out of 10).

I rate Azure Stack seven out of 10.