In Azure, there is a principle or concept called cloud-first. Inside the cloud, the most important thing is to use a fully managed solution, and this is what gives the cloud the advantage over other options. In Azure, for example, as a designer or an architect, all the time, I am looking for built-in features fully managed by Microsoft called SaaS and PaaS tools, and then we have to go to the third option, which is IaaS inside the cloud. The platform as a service is something that is very interesting on the cloud. Speaking about the scalability impact of the tool on your client's day-to-day operations, I would say that from my last experience, I saw that we are leveraging this solution to limit the time for the cloud journey, to use it as a first step to move to the cloud and it is very interesting. For me, it is not a solution that we consider to be the final goal. For me, the tool is something to move to the cloud, being on the same configuration and pattern, and to keep it like this back to the cloud is called the transformational modernization of the applications. I am not using the solution. The tool is just a recommendation for integration purposes. We did the assessment for the on-premise infrastructure, and the client asked our company to help them get to the cloud as soon as possible. The strategy that we put in place is to move as a first step to Azure VMware solution and, after this, as a second step, to do the transformation and go to Azure to use Azure services, like the PaaS, IaaS, and other SaaS areas. There was no AI involved in the project. The client was not ready to hear about AI. The project involved standard migrations. We have workloads on-prem. The clients ask to move the workload to Azure and, as a first step, to put them on Microsoft Azure VMware solution. The next step was to have this through with the transformation to use the standard Azure services. AI was not a part of the proposal. As a consulting company, we are seeing that people are moving to other tools to avoid paying because my understanding from this experience is that with the new licensing model with VMware after the Broadcom acquisition, the pricing of the licensing model gets higher and more complicated. There are a lot of people to whom we are moving to Microsoft Azure VMware solution. The tool is for those who still want to use VMware at the right price. Another recommendation from me for others is for migration. The tool offers a great migration path to start with Microsoft Azure VMware, and after that, they can move to Azure on the Paas, IaaS, and everything. It will give a lot of flexibility during the migration. For example, our client's infrastructure team was spending for storage management, and it was, like, 20 percent for two people working to manage the storage. Storage acquisition for an organization has to do a kind of assessment of which store and which solution they have to buy, go to the market, and analyze everything. After this implementation, it becomes a project. With Microsoft Azure VMware, I need another storage, and that is it, so you have it for 24 hours. At the end of the year, regarding infra management, we will have at least two or three FTEs of money that will be saved, which is a lot of money in the end. It's like we have two or three salaries that we get rid of and use in some other areas. The other thing with the tool is the usage of computing, so it is flexible. When we are using it, it's like a pay-as-you-go model. Suppose I need one hundred vCPU. I will buy them all. But on-premises, when you need one hundred vCPU, you have to buy a lot of servers, and you have to put this on two areas, and then you have to buy for the next three, four, or five years. We cannot buy what we need today by checking all the growth, including the growth, and buying what we need for the next five years. However, when using services like Azure, we have to buy what we need today. Tomorrow, if I need more, I can request more, and that is it. These are the two areas that we saw where the tool helps with saving money and ensuring ROI. The agreement that Microsoft had with VMware regarding the pricing and the model licensing has helped many since a lot of people struggled with the licensing when they were buying VMware after Broadcom's acquisition. When people are facing Microsoft and using the same licensing model for Microsoft Azure VMware, I would say that it is a good thing that it was added under Azure. I rate the tool an eight and a half to nine out of ten.
Hybrid Cloud Computing Platforms are solutions that allow organizations to combine and integrate their on-premises infrastructure with public cloud services. These platforms provide a unified management and orchestration layer, enabling seamless workload portability and consistent operations across multiple cloud environments.
In Azure, there is a principle or concept called cloud-first. Inside the cloud, the most important thing is to use a fully managed solution, and this is what gives the cloud the advantage over other options. In Azure, for example, as a designer or an architect, all the time, I am looking for built-in features fully managed by Microsoft called SaaS and PaaS tools, and then we have to go to the third option, which is IaaS inside the cloud. The platform as a service is something that is very interesting on the cloud. Speaking about the scalability impact of the tool on your client's day-to-day operations, I would say that from my last experience, I saw that we are leveraging this solution to limit the time for the cloud journey, to use it as a first step to move to the cloud and it is very interesting. For me, it is not a solution that we consider to be the final goal. For me, the tool is something to move to the cloud, being on the same configuration and pattern, and to keep it like this back to the cloud is called the transformational modernization of the applications. I am not using the solution. The tool is just a recommendation for integration purposes. We did the assessment for the on-premise infrastructure, and the client asked our company to help them get to the cloud as soon as possible. The strategy that we put in place is to move as a first step to Azure VMware solution and, after this, as a second step, to do the transformation and go to Azure to use Azure services, like the PaaS, IaaS, and other SaaS areas. There was no AI involved in the project. The client was not ready to hear about AI. The project involved standard migrations. We have workloads on-prem. The clients ask to move the workload to Azure and, as a first step, to put them on Microsoft Azure VMware solution. The next step was to have this through with the transformation to use the standard Azure services. AI was not a part of the proposal. As a consulting company, we are seeing that people are moving to other tools to avoid paying because my understanding from this experience is that with the new licensing model with VMware after the Broadcom acquisition, the pricing of the licensing model gets higher and more complicated. There are a lot of people to whom we are moving to Microsoft Azure VMware solution. The tool is for those who still want to use VMware at the right price. Another recommendation from me for others is for migration. The tool offers a great migration path to start with Microsoft Azure VMware, and after that, they can move to Azure on the Paas, IaaS, and everything. It will give a lot of flexibility during the migration. For example, our client's infrastructure team was spending for storage management, and it was, like, 20 percent for two people working to manage the storage. Storage acquisition for an organization has to do a kind of assessment of which store and which solution they have to buy, go to the market, and analyze everything. After this implementation, it becomes a project. With Microsoft Azure VMware, I need another storage, and that is it, so you have it for 24 hours. At the end of the year, regarding infra management, we will have at least two or three FTEs of money that will be saved, which is a lot of money in the end. It's like we have two or three salaries that we get rid of and use in some other areas. The other thing with the tool is the usage of computing, so it is flexible. When we are using it, it's like a pay-as-you-go model. Suppose I need one hundred vCPU. I will buy them all. But on-premises, when you need one hundred vCPU, you have to buy a lot of servers, and you have to put this on two areas, and then you have to buy for the next three, four, or five years. We cannot buy what we need today by checking all the growth, including the growth, and buying what we need for the next five years. However, when using services like Azure, we have to buy what we need today. Tomorrow, if I need more, I can request more, and that is it. These are the two areas that we saw where the tool helps with saving money and ensuring ROI. The agreement that Microsoft had with VMware regarding the pricing and the model licensing has helped many since a lot of people struggled with the licensing when they were buying VMware after Broadcom's acquisition. When people are facing Microsoft and using the same licensing model for Microsoft Azure VMware, I would say that it is a good thing that it was added under Azure. I rate the tool an eight and a half to nine out of ten.
I rate the overall solution an eight out of ten.