It might be beneficial if Microsoft could introduce a more cost-effective data lake feature within their product. Currently, organizations often partner Azure with Databricks to access Spark clusters and in-memory processing capabilities. Databricks, as the creator of Apache Spark and a leading player in distributed computing, is a significant part of many data workflows. If Microsoft could integrate such capabilities into its product offering at a reduced cost, it would enhance competitiveness compared to services like Amazon Redshift and Google BigQuery.

Azure Stack Hub could use some improvement when it comes to seamless support for disaster recovery scenarios or high availability regarding multi-regions (not including global Azure). 

With Azure Stack Hub, your expansion is limited. If you need to expand your infrastructure, you can't just expand the computing power or the storage capacity. You have to expand both since it is a hyper-converged solution. There are third-party solutions that would allow you to expand storage via iSCSI, but it involves setting configs on third-party systems too.  

The next release should have improved scalability in terms of having multiple stamps as part of the same region or having the capability to replicate workloads to multiple regions of Azure Stack Hub. 

If I were to mention an area that could be enhanced, it might be technical support, as there have been observations that the response time is not as fast as some of its competitors like Google.

There is room for improvement in terms of security. The security tooling could be better. It could be easy to drive. The alerts could be a lot quicker in delivery because it's coming out of Azure Stack, it's coming out of their tools. It it could could be a lot better.  It could could be a lot more straightforward. Okay.

Additionally, having clear pricing in the marketplace would be beneficial. In this marketplace, everything comes with a price tag. If something isn't initially priced, you can try it for free, but we'll let you know the cost after the trial period.  

I feel that Azure Stack has so many different variables which are not very clear. Unless you have a great deal of knowledge or a really good integrator, you may encounter a few surprises when you begin with the implementation phase of Azure Stack. In general, the initial setup phase of Azure Stack is an area with concern that needs improvement. The initial setup affected me the most from the point of view of the cost structures related to Azure Stack.

I can't comment if I would like to see any additional functionalities added to the solution since I currently don't use even 10 percent of its capabilities.

Some tools do not run without the internet. If we have connectivity problems or need to install an application without the internet, we cannot do it.

The solution could be less expensive. 

So many new features are added at a fast pace that it is sometimes hard to keep up with all the solution offers. 

Azure Stack is an expensive product that should be made more cost-effective.

Overall support needs improvement because they are not agile across services. 

It should be improved in terms of integrations. It could be integrated more with external tools. 

We have Azure Purview for governance, but that is for data governance. For code governance, we have to use SonarQube or WhiteSource for vulnerabilities and license management. We would like to have a native code compliance tool.

One aspect that I consider a drawback is the cost associated with Azure Stack, as its deployment expenses tend to be on the higher side compared to other solutions. Another significant challenge is integration, especially with third-party products. While Azure Stack seamlessly integrates with Microsoft's own tools and platforms, there is room for improvement in its compatibility with third-party solutions. Lastly, although updating and patching Azure Stack is more straightforward than in older Windows versions, there is still room for enhancement in the upgrade and patch management process.

Improvement is already happening based on the strategy of Microsoft. 

Normally, in many countries, especially in the Middle East, there are government regulations for information technology itself. If government organizations want to host the cloud, they cannot take it from Microsoft directly; they must go through the local internet service providers, ISPs, or cloud solution providers locally. They should have a local data center in the Middle East, and the data should not move out of the Middle East. This is one of the restrictions we face.

Having said that, Microsoft is working with the governments in the Middle East. 

At the end of the day, it's all about the composition between the cloud service provider giants, including Microsoft. There is a growing market for Alibaba Cloud in the Middle East. It's growing more popular compared to Azure. The reason is that the governments are more focused on Chinese technology rather than Microsoft in certain areas.

When it comes to room for improvement, there should be more focus on the user interface, specifically for the management console.

In the future release, I would like to see better UI. 

From a security perspective, there are certain things which could be improved. We have that option of enabling the datacenter which sits on the Azure site. The solution is difficult to manage if this particular feature is disabled. 

Azure Stack needs to improve integrations. 

I think the monitoring and operational part, including more administration, must be simplified to simplify user adoption. The challenge in Azure Stack begins at an individual level when you try to monitor every service from Azure Stack that gets consumed. The more the configuration capacity is available in Azure Stack, the more configurable it becomes while becoming easier at a user level and administrator level, thereby helping to optimize the consumption cost.

With the road map of Azure Stack, I have, everything looks great. Looking at the way Azure Stack has matured in the market, I feel that the roadmap of Azure Stack is planned pretty well by Azure's product managers.

The visibility of the solution's SDN feature and transmission policy needs improvement.

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.

The solution's price is high, and the implementation process is difficult. I would like to see a lower price and simpler implementation for Azure Stack.

Certain elements are difficult to deploy.

I would like to see the AI side come to one hundred percent in the near future. I would love to see a more reliable SAP improved.

There's Azure SQL Database on the cloud for small loads, but now they're moving to Synapse, which has a combination of the storage plus the analytics. 

The fact that it is completely integrated into Azure, while positive, is also a downside. 

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.

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

Azure Stack's pricing could be improved.

Azure Stack doesn't have all the services available in Microsoft Azure. It would be useful if Azure Stack could be developed to be like Microsoft Azure with all the services. Although Microsoft manages it, not all of Microsoft Azure’s services are available on Azure Stack. 

When we try to build a solution on Azure Stack, there are some limitations with the services available, most of which are available on Microsoft Azure. Adding more services to Azure Stack will be beneficial for customers. The product doesn’t have a DR solution available locally. The product does not support a local DR either.

Azure Stack could be improved with more integration, governance tools, monitor tools, and lift and shift tools. We also have problems with the capacity usage. In the next release, Azure should include a tool to manage the journey during the lift and shift process and identify where integration is needed.

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 started to get issues in May of this year.  We didn't know that the one side of Azure was not fully migrated. There's two Azure on-premise solutions in our organization.

I needed to migrate everything that wasn't migrated over quickly. I needed someone who was knowledgable to assist to get it done. Therefore, I asked Windows and was looking into our budget.

We told them to go ahead and do it, and that we had two thus far, one for memory, one for CPU, and that's all. I only wanted two point areas. I wanted my Azure to point to only one, however, now it's set up to point to two point areas, which is not what we want.

The solution is not user friendly. I'd prefer to move over to AWS, which is much easier in this sense.

The product could improve its manageability.

The user experience could be improved to make it more comfortable.

We have experience in Azure Stack. Internally, the cost increases when you use Azure Stack because you have to buy services from providers like HP, for instance. So, more or less, it's more profitable to use the non-Azure Stack cloud services servers.

In some cases, we've seen that some financial software is not working correctly or compatible with Azure Stack. Many companies build this, but some third-party products may not be compatible with Azure Stack. So these are some areas of improvement. 

In future releases, there's some incompatibility with third-party software or connectors that need to be created.

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.

The solution should be more open to allowing access to other tools and environments.

Technical support also needs a lot of improvement.

When you compare AWS to Azure adding on all the security components you require to protect your application and data AWS is by far the cheaper alternative, like the cost of Defender and ATPm, MCAS, ADFS, etc.

I can't think of any area in which the solution is currently lacking.

The solution could use more training materials to help users understand how to use the product effectively. Online training would also be a beneficial addition to the product.

The user interface could be more user friendly.

As far as what we would like to see added, there are no burning issues right now. If we are looking for certain areas of improvement and we want to have specific features or functions, the flexibility of the environment allows us to easily add the functionality we want.  

There are always things that you have to find out for yourself. That creates complexity. Could Microsoft make the product easier to use? Probably by adding more scenarios, but Microsoft already has guidelines on when to use what feature. In the area of training, Microsoft already offers a lot of opportunities to further your skills with its products. These resources make it possible to get started quickly. The product is never going to do your learning for you in that way.  

I do not have any recommendations as to how the product should be enhanced as some of that is the user's responsibility and opportunity.  

Azure Stack is relatively new and lacks the features compared to public Azure. Hopefully, it will provide more core on the VM and support multi-scale units.

I would like to see better support for containers.

Containers and the IoT hub that exists in Azure Stack should be usable on-premises.

Pricing is always a hot topic, so the pricing can always improve. And I'm not too sure if the Microsoft technical capabilities are very good because I don't make use of it. So, for me personally, pricing would probably be the only factor that needs to improve.

I also think the monitoring tools needs some improvement.

One of the problems is that systems still have to be developed and as things move forward, we have to build a lot of our Azure Stack solutions from scratch. It does not give you a complete, production-ready setup.

The reporting for the interim monitoring purpose could be improved. Right now Windows Admin Center is on the level with Victor Server 2019. But we need to work on the same tool, so we provide them some code features on the same tool. It's very useful for any organization and an administrator.

Additionally, customers need to consider Disaster Recovery. Microsoft tech is only providing support to Azure. We would like to see it available for other services and solutions on the cloud, too, as well as a solution for Oracle backup.

Having more options and customization would be an improvement.

They can provide more integration with other services, such as
components, open source, because I use these services.

The price of the OCR could be more competitive with Google.

It depends on the type of user, as some users prefer an easy tool and environment for management. Other users prefer a detailed setting of the environment and console. I can tell you what would be better from the point of view of different users. It is one of the programs we are finding a proper solution for to know if a user finds it easy using only pictures and the possibility of what they can do in this environment.

I would like to have access to more services and more functionality.

In the future, I would like to see more machine learning features.

We need an expressway from a different network to allow for connectivity purposes. For example, If we want to have remote storage on-premises or off-site, I have to go through the public cloud. That is the only way.

There is a dependency. They don't encourage having it on-premises in different networks. 

I have an HCI model hyper-converged infrastructure. It's a minimum of four nodes with Microsoft Azure and I want to attach additional storage, but I cannot attach it without connecting directly and finding a new network.

There are limits to the bandwidth and sizing of the images.

Kubernetes as a service is there, but not as a platform as a service. I would like to have a Kubernetes cluster in a PaaS. They have it in the Azure public cloud, but they haven't released it in the Azure Stack.

In PaaS Model, they are only offering MS SQL as a service, web applications as a service, and containers as a service. When it comes to containers, I could not find how to use the functionality. Recently, one of our customers wanted to have Sybase as the database for their SAP applications, but it was not in the Azure Stack Marketplace.

It is closed and It doesn't allow you to customize networks or any new features.

Better flexibility in the network is needed.

If they could integrate with Jira, this would be very useful for someone using Jira and TFS. This would make it easier to use.

Our only issue with Azure Stack so far is that the networking is very closed. You need to have the extended LAN to connect the internal LAN to the Azure Stack. Any connection we have needs site-to-site VPN connectivity instead of an internal connection, so Azure Stack has room for improvement in the networking area.