Azure Stack Reviews

I don't have a specific feature, my customers use all of the features that are available and the entire stack.

I believe the only room for improvement is that I am based in Nairobi, if it has even a local node for Azure, I believe most customers will prefer that to reduce latencies and everything else when using the Azure Stack. They'll be better off if they can set up a local node in Nairobi, Kenya.

There are local things specific to the Kenya market, which are integrated into local development platforms available in Kenya, which would be helpful if it could be integrated with Azure Stack. We have a solution called M-Pessa, for example. If that can be done on a regular basis, I believe it is time to look for customers who want to use that channel today.

I have been working with Azure Stack for six years.

Azure Stack is a stable product.

Azure Stack is a scalable solution.

Technical support is okay. My customers have not complained about the technical support.

I actually work for an integrator company that specializes in UiPath. I primarily use UiPath, but I also use Automation Anywhere and Microsoft Power Automate.

We use Power Automate, but we also use Power BI for dashboard visualization. Then there's the standard Office 365, and we do have customers who use Azure.

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.

In terms of pricing, my customers believe AWS is slightly more reasonably priced than Azure. They believe it is significantly less expensive than what Azure offers. It is simply a matter of pricing.

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.

We use Azure Stack primarily for hosting customer applications .NET applications. We use mainly App Service, Blob Storage, and Cognitive Services. 

We develop applications on the Microsoft platform, infrastructure, and servers. Our servers are Windows, and we use the .NET framework and C# programming language. Everything is easier in Azure.

Azure Stack integrates well with Microsoft. It's also good for transitioning from an on-premise or hybrid setup to the cloud. It's seamless. 

Microsoft is changing the Azure Stack interface all the time, so it's sometimes hard to find the functionality or the service you're looking for. A feature was in one place and now it has moved somewhere else. 

It's because the product is quickly evolving, so they're changing constantly. I understand, but it's difficult to find things when we don't use Azure every day. It's not a big issue.

We've been using Azure Stack for seven or eight years.

Azure Stack is highly stable.

We have had a good experience with scalability. Azure Stack's replication is well-written. It's flexible. For example, you can scale it differently on workdays and weekends to reduce operating costs. We automatically reduce the sizing of the solution. We stop some services like VMs on the weekends if we can. Scaling up and stopping resources is automated based on a set schedule. This is useful.

Microsoft support is very good.

We switched from AWS to Azure. The main issues were costs and some bad experiences with temporary disks. This was a long time ago, so I cannot say if AWS is currently better or worse than Azure.

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.

Azure is relatively expensive, but on the other hand, you get excellent support, stability, and security, so I think it's worth it. 

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. 

Currently, we are just using it to plan for our proof of concept and internal testing, not for production.

I've been using Azure Stack for more than a year.

It's not stable as IBM solutions. It fully supports all the .NET solutions, but our main applications are based in Java. So in those cases, we've had some minor problems with Azure, but Microsoft always says that it can handle this stuff.

Microsoft's support isn't as good as IBM's. They are fast, but they aren't knowledgeable enough.

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.

I believe our license is yearly.

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.

The solution is geared towards customers with large Microsoft footprints, in which it is very advanced. There is tight integration in respect of Microsoft workloads and extremely intelligent performance. Customers can use it to run SQL Server, Active Directory, VDI, Windows Server and other workloads. Many users use it for their dynamics, although I am not aware of a lot of deployments with SAP HANA. One who has a 60 or 70 percent footprint in the data center with Microsoft can save a lot. 

Azure Stack is a really good product when it comes to the functionality and the Azure Stack offer. Its most attractive feature is the licensing. The virtualization is in-built and free and it offers almost all the functionalities someone looks for from the Azure platform. 

Now that the solution is transitioning to a hybrid cloud approach, the licensing is not determined by the number of instances and this can result in huge savings. 

A subscription model customer will not need to do much up front purchasing. He can obtain all the up to date features offered on public cloud and grow at the rate he feels is best, with the attendant savings. 

I would like to see better network integration. 

While they are working on security, several things can be brought in on the networking side, such as extending to networks stretching in between data centers. These are absent at the moment. It would be good to have a single control plane for the networking.

I have around two years of experience with Azure Stack. 

The solution is certainly stable. 

The solution is definitely scalable. 

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. 

While deployment is straightforward, it would require a good skill set with Microsoft technologies and a certain amount of networking knowledge to handle any trouble which may arise. 

The licensing is one of the solution's most attractive features. 

Subscription model customers need not make large expenditures on upfront purchasing. 

A customer must purchase the software needed for Microsoft support, if he wishes to have this. This would incur a monthly fee. But, the upcoming Azure Stack HCl, which is hybrid cloud, does not involve an upfront purchase, only a subscription-based fee. 

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. 

I recommend Azure Stack 100% for hybrid cases, dev & test, banking, financial (banking, insurance) , healthcare, public sector.

Also, The assessments include the following standards:

•PCI-DSS addresses the payment card industry.

•CSA Cloud Control Matrix is a comprehensive mapping across multiple standards, including FedRAMP Moderate, ISO27001, HIPAA, HITRUST, ITAR, NIST SP800-53, and others.

•FedRAMP High for government customers.

The compliance documentation can be found on the Microsoft Service Trust Portal. The compliance guides are a protected resource and require you to sign in with your Azure cloud service credentials.

The main pillars, on which Binbox is now developing, are Cloud Solutions (public, private and hybrid Cloud) using Azure and our DataCenters (built on state-of-the-art technology), Microsoft 365 and Binbox Managed Services (including 24/7/365 support). These being said, the Azure stack has come to complete our service portfolio like a glove.

The most valuable features that make Azure Stack different are low latency (<9 ms, high performance), data sovereignty, cloud readiness, public Azure features in the private cloud. Considering all the features, the quality of service / price ratio is superior compared to any cloud option.

It would be great when Microsoft will enable WDI, AI and Cognitive Services in Azure Stack.

Binbox Global Services has been using Azure Stack since 2018 when we deployed the first Azure Stack in Central and Eastern Europe. We were the second Microsoft partener that deployed an Azure Stack in Europe.

Now we have 7+ Azure Stacks and other Azure Stacks dedicated to Public Sector.

Azure Stack is stable. 

Azure Stack Hub provides on-demand, scalable computing resources.

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

We went through both a private vendor and Microsoft. The private vendor handled one part of the deployment; a Microsoft team did another. They both taught us how to manage Azure Stack. We have a large team of technical engineers who received Azure Stack certification. They know Azure Stack very well. Overall, it was not hard for us to deploy. 

I use a lot of services in Azure.  I have worked with completely isolated environments, building infrastructure from scratch using Terraform, Chef, Puppet, and other such tools.

The Platform as a Service (Paas) environment is the most valuable feature.

The Web App service is very valuable.

It is helpful from a security point of view because we can create our own isolated, private environments that contain virtual networks, and we can put security rules in place. We can also specify application rules, which is something that is also useful.

There are a lot of services in Azure that are not stable.

Azure Messaging services are in need of improvement.

I would like to see better monitoring capability, as we have in Dynatrace and other APM tools. The functionality is there, but it is not as detailed as it is in other tools.

I have about three years of experience with Azure, on and off.

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.

We have an application that is working on Azure Stack. It is a Microsoft application that we wrote for our customers. 

Azure Stack is easy to use. Its major benefit is that it doesn't need its infrastructure. We didn't face any issues integrating it with our infrastructure. 

The product needs to improve its pricing. 

Azure Stack is stable and I rate it an eight out of ten. 

The tool is scalable. We have one customer working with it. 

The solution's customer service is fine. 

Depending on your setup, the tool's deployment can be complex and take a few hours to complete. I need to select the services and resources to deploy the tool. Though I have a team, only one engineer works on the product. 

I am using my Microsoft license, and it costs monthly. You need to pay additional costs apart from the standard costs. 

We are in the process of obtaining co-pilots to integrate AI into our infrastructure. I rate the overall solution a seven out of ten. 

We use Azure Stack for migration, application modernization, and cloud-native modernization.

Azure Stack's pricing could be improved.

I have been working with Azure Stack for around four to five years.

I rate Azure Stack a nine out of ten for stability.

Azure Stack is a very scalable solution.

I rate Azure Stack ten out of ten for scalability.

Azure Stack’s initial setup is easy.

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.