{"id":23523,"date":"2021-08-10T06:48:05","date_gmt":"2021-08-10T10:48:05","guid":{"rendered":"https:\/\/devopsnews.online\/?p=23523"},"modified":"2021-08-10T09:06:51","modified_gmt":"2021-08-10T13:06:51","slug":"devops-in-microsoft-finops","status":"publish","type":"post","link":"https:\/\/devopsnews.online\/devops-in-microsoft-finops\/","title":{"rendered":"DevOps in Microsoft FinOps"},"content":{"rendered":"

When discussing DevOps, people can easily mistake it with the Microsoft DevOps tool that is used for project management, version control, deployment, etc. You may think \u201cHow is that even possible?!\u201d, but the practice itself is a new concept to projects implementing the Microsoft ERP, it is something that the engineers are used to, but not the customers.<\/p>\n

The whole idea of a practice that combines software development and IT operations and makes your project work on continuous delivery, in theory, is what every customer asks for, but in practice, you may find it difficult.<\/p>\n

This article will provide some insides into what are the most common mistakes the Microsoft FinOps implementations have, and what should be considered when planning your project.<\/p>\n

 <\/p>\n

Planning your project<\/strong><\/h3>\n

Working with Microsoft ERP FinOps, from the old to the latest version, it is quite common to find projects where people do not understand the concept of DevOps, and everything is considerate IT operations, from the development up to deployment.<\/p>\n

As a normal practice, a technical architecture will put together resources, machine sizing, and what is needed for the technical ALM (Application Lifecycle Management) of the project. This is the moment that continuous delivery is discussed, and the strategy of the project is determined.<\/p>\n

Considering budget and time in a short-term solution it is easier to go for the cheapest approach where you can use a resource to manually deploy across environments, bring business users to test, and have a few environments as possible. This is where most of the projects face their first issue, as the variables chosen are not considering multiple deployments across environments, and the customers will start to ask for faster deployments, will complain about resources available and the extra costs to get the work done after working hours.<\/p>\n

The scenario above is quite common, and it is the right moment to discuss a long-term solution and the issues with the current approach. When discussing DevOps practices, keep in mind the lead time as the following:<\/p>\n