I would rate the product an eight out of ten. There are two types of containers, Windows and Linux containers. This solution is best for those with Windows containers since it is less complicated, easy to maintain, and has lower overheads. 

I'm in the consulting space. I'm not into coding or implementation. I am a cloud consultant in that sense. I look into the planning, the overall cloud migration, the cloud strategy, cloud operating model for the client.

I'd advise new users to not go big. They need to first identify the short-term goals and start with a POC first. The company needs to have an alignment with its team. Make sure to have a complete understanding of the product. Before going ahead and investing significantly, invest in some areas of the application landscape that you want to test out which are not very critical in order to understand the pros and cons. Once you weigh in the benefits you can then go for a significant investment into Azure, or any environment in that manner.

If your organization is mainly Microsoft, this is a very good product. However, other things to consider are AI (and how much AI you want to use) and regional aspects, as connectivity may not be as good everywhere. There are, for example, some areas where AWS works better.

When we work with clients, we take it on a case-by-case basis and see what makes sense. However, I would advise companies to wait until they have 90% surety before they seriously dive in.

I'd rate the solution eight out of ten.

We are partners with Microsoft.

I'm not sure which version number we are on right now. 

I'd rate the solution eight out of ten. As a hybrid solution, it's very good. The solution updates quite often and are improving all of the time. 

Before implementing this solution you have to consider is the internet connectivity to the Azure environment. For some countries that have sanctions, moving data on the cloud environment might not be allowed due to local regulation. In general, Azure Container Service and competitors, such as Google or Amazon, are more than beneficial in comparison with local on-premise environments.

I am working in a few companies as a consultant. I advise them on whether to move to the Azure environment cloud or on-premise and ultimately they choose the option based on my advice. One of the companies migrated on-premise workloads to Azure and uses container services. However, in another company, we do not need to go to the cloud due to some local regulation and therefore we have to establish an on-premise environment.

I rate Microsoft Azure Container Service a nine out of ten.

My advice to anybody who is considering this solution is that it is a good option to use because it is more secure. You can secure your images and your code, which are stored on that cloud. You have dedicated access and you can integrate it with Azure Active directory. 

It is also a PaaS offering, which means that you don't need to manage your repositories. You only need to manage your data within them. Finally, it is cost-effective in terms of storing data.

I would rate this solution an eight out of ten.

This is a very good solution and I would recommend it to others.

I would rate this solution nine out of ten.

Of course, I can recommend this program to others, but they must first do an overall study and analyze the program to verify that it is business-driven, not technology-driven. In the next version, I would like to see better security because it is rather limited in this version. Updating the security would be great, as well as more integration of capabilities.

On a scale from one to 10, I will rate this program an eight. This is simply because I only use it in a lab environment - I don't have any other experience of the program.