I haven't come across missing items. It does what I need it to do.

The pricing is a little bit high.

The UI should be a little bit better from a usability perspective. The endpoint, if you are outsourcing to a third party, should have easier APIs. I'd like to have more destination sources available to us. 

I'm not sure if there are any areas that are lacking

The initial setup is complex. It should be easier for new users who may not have too much Azure experience. 

The solution’s customer support could be improved.

The solution's query languages must be more comprehensive. Also, its features for event imports and architecture need enhancement.

One area that could use improvement is the handling of data validation. Currently, there is a review process, but sometimes the validation fails even before the job is executed. This results in wasted time as we have to rerun the job to identify the failure. It would be beneficial to have better error handling and early detection mechanisms in place. 

Additionally, there should be improved support for data joining and ensuring that customer matching is accurate. It's crucial to address these issues and add enhancements on top of the existing solution.

Easier scalability and more detailed job monitoring features would be helpful.

Another room for improvement is the ingestion of data. 

With Azure specifically, the drawback is it is a very Azure-specific product. You can't connect it to external things out of Azure. For example, Spark or Databricks can be used in any cloud and can be used in AWS. This product doesn't work that way and is very Azure-specific. It's not a hybrid solution and it's not a cloud-agnostic solution, where you put it on other clouds, et cetera. 

We had some connections which we wanted to make with AWS, which we couldn't do with this. We had to use something else for that.

Early in the process, we had some issues with stability.

You cannot do joins on streams of data. For example, one stream joining with another stream. Real-time to real-time joins, you're not able to do that. You can only join your stream with static data from your Azure storage. 

I would like to have a contact individual at Microsoft and the price is high.

We would like to have centralized platform altogether since we have different kind of options for data ingestion. Sometimes it gets difficult to manage different platforms. 

Sometimes when we connect Power BI, there is a delay or it throws up some errors, so we're not sure. We try to resolve it on an issue-by-issue basis. For some reason, Microsoft Power BI and Azure Stream Analytics have connection issues, but I can't say what the problem is at a product level. 

Azure Stream Analytics was not meeting our company's expectations because it was tedious to change the job, write queries, or if I needed to change something, I needed to stop the entire stream processing to change the job so that the changes could take effect. The aforementioned reasons were concerning, but I think that many of the issues related to the product have been resolved with the help of Microsoft Fabric.

The only challenge was that the streaming analytics area in Azure Stream Analytics could not meet our company's expectations, making it a component where improvements are required.

The solution doesn't handle large data packets very efficiently, which could be improved upon.

We would also like more variation in the output types that this solution can produce.

There may be some issues when connecting with Microsoft Power BI because we are providing the input and output commands, and there's a chance of it being delayed while connecting.

Azure Stream Analytics could improve by having clearer metrics as to the scale, more metrics around the data set size that is flowing through it, and performance tuning recommendations.

We would like to have something that includes the desktops, and perhaps the main system, so we can protect our systems before a threat happens.

The product could be improved by providing more detailed analytics. For example, a graph to identify the past, present and current users. Additionally, UI and UX testing could be supported on this solution.

The solution's interface could be simpler to understand for non-technical people. Also, the chart feature could be more user-friendly. Presenting or elaborating on an incident to management or executives from other non-technical departments becomes challenging. We have to create another graph and include it in the presentation slides.

Some features require logical thinking. For example, if you want to write an integrative custom script, then it will be more convenient. Automation is available.

It is not complex, but it requires some development skills. When the data is sent from Azure Stream Analytics to Power BI, I don't have the access to modify the data. I can't customize or edit the data or do some queries. All queries need to be done in the Azure Stream Analytics. 

While it depends on the business scenario, in some cases AWS offers better features. It's hard to speak to missing features at it really depends on the business case. However, in general, it has all the features a typical company might need.

The solution needs to be marketed better. Developers should be pushed or enticed to use the solution more to get it more well-known on the market. It needs more of a presence.

The solution offers a free trial, however, it is too short. You can't really properly test it before you have to start paying. They need to give companies a longer period of time to try it out risk-free. Also, the functionality is very limited. If you want to do a POC, you need the solution to offer more flexibility. Right now, you get a 14-day window, and that's not enough for a proper test.

The collection and analysis of historical data could be better. We use historical data and an assimilating algorithm to give us insights into the entire business process. 

We can collect all the historical data periodically to get insights into current business trends. For example, which area is getting emptied most of the time or which area is getting underutilized, and so on. 

There are some improvements that could be made, first of all in pricing, because right now the pricing is a bit unclear. It's hard to estimate how much of that is a local issue but you can't figure out how prices are calculated or the proprietary part of the cost. Another area that could be improved is that if something does go wrong, it's very hard to investigate what caused it and why. The logging is available but it lacks detail and doesn't provide much information.