Fix doc formatting issues

docs-mslearn/.markdownlint.json

@@ -0,0 +1,5 @@
+{
+  "line-length": false,
+  "no-inline-html": false,
+  "single-h1": false
+}

docs-mslearn/best-practices/library.md

@@ -3,15 +3,14 @@ title: FinOps best practices library
 description: Discover essential FinOps best practices to optimize cost efficiency and governance for your Azure resources.
 author: flanakin
 ms.author: micflan
-ms.date: 04/02/2025
+ms.date: 02/24/2026
 ms.topic: concept-article
 ms.service: finops
 ms.subservice: finops-learning-resources
 ms.reviewer: arclares
 #customer intent: As a FinOps user, I want to understand what FinOps best practices I should use with Microsoft Cloud services.
 ---
 
-<!-- markdownlint-disable-next-line MD025 -->
 # FinOps best practices library
 
 The FinOps best practices library is a collection of essential proven practices to manage and optimize cost, usage, and carbon efficiency across your Microsoft Cloud environment. Guidance is organized using the service category. Use the following categories to explore FinOps practices for different services.
@@ -31,13 +30,17 @@ The FinOps best practices library is a collection of essential proven practices
 
 Let us know how we're doing with a quick review. We use these reviews to improve and expand FinOps tools and resources.
 
+<!-- prettier-ignore-start -->
 > [!div class="nextstepaction"]
 > [Give feedback](https://portal.azure.com/#view/HubsExtension/InProductFeedbackBlade/extensionName/FinOpsToolkit/cesQuestion/How%20easy%20or%20hard%20is%20it%20to%20use%20FinOps%20toolkit%20tools%20and%20resources%3F/cvaQuestion/How%20valuable%20is%20the%20FinOps%20toolkit%3F/surveyId/FTK/bladeName/Guide.BestPractices/featureName/Overview)
+<!-- prettier-ignore-end -->
 
 If you're looking for something specific, vote for an existing or create a new idea. Share ideas with others to get more votes. We focus on ideas with the most votes.
 
+<!-- prettier-ignore-start -->
 > [!div class="nextstepaction"]
 > [Vote on or suggest ideas](https://github.com/microsoft/finops-toolkit/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%252B1-desc)
+<!-- prettier-ignore-end -->
 
 <br>
 

docs-mslearn/best-practices/web.md

@@ -3,15 +3,14 @@ title: FinOps best practices for Web
 description: This article outlines a collection of proven FinOps practices for web services, focusing on cost optimization, efficiency improvements, and resource insights.
 author: flanakin
 ms.author: micflan
-ms.date: 04/02/2025
+ms.date: 02/24/2026
 ms.topic: concept-article
 ms.service: finops
 ms.subservice: finops-learning-resources
 ms.reviewer: arclares
 #customer intent: As a FinOps user, I want to understand what FinOps best practices I should use with web services.
 ---
 
-<!-- markdownlint-disable-next-line MD025 -->
 # FinOps best practices for Web
 
 This article outlines a collection of proven FinOps practices for web services. It provides strategies for optimizing costs, improving efficiency, and using Azure Resource Graph (ARG) queries to gain insights into your web resources. By following these practices, you can ensure that your web services are cost-effective and aligned with your organization's financial goals.
@@ -87,13 +86,17 @@ resources
 
 Let us know how we're doing with a quick review. We use these reviews to improve and expand FinOps tools and resources.
 
+<!-- prettier-ignore-start -->
 > [!div class="nextstepaction"]
 > [Give feedback](https://portal.azure.com/#view/HubsExtension/InProductFeedbackBlade/extensionName/FinOpsToolkit/cesQuestion/How%20easy%20or%20hard%20is%20it%20to%20use%20FinOps%20toolkit%20tools%20and%20resources%3F/cvaQuestion/How%20valuable%20is%20the%20FinOps%20toolkit%3F/surveyId/FTK/bladeName/Guide.BestPractices/featureName/Web)
+<!-- prettier-ignore-end -->
 
 If you're looking for something specific, vote for an existing or create a new idea. Share ideas with others to get more votes. We focus on ideas with the most votes.
 
+<!-- prettier-ignore-start -->
 > [!div class="nextstepaction"]
 > [Vote on or suggest ideas](https://github.com/microsoft/finops-toolkit/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%252B1-desc)
+<!-- prettier-ignore-end -->
 
 <br>
 

docs-mslearn/conduct-iteration.md

@@ -3,26 +3,28 @@ title: Tutorial - Conduct an iteration
 description: This tutorial helps you learn how to take an iterative approach to FinOps adoption.
 author: flanakin
 ms.author: micflan
-ms.date: 04/04/2025
+ms.date: 02/24/2026
 ms.topic: tutorial
 ms.service: finops
 ms.subservice: finops-learning-resources
 ms.reviewer: kedelaro
 # customer intent: As a finops practitioner, I want to adopt FinOps in my organization so that we can create a plan to adopt.
 ---
 
-<!-- markdownlint-disable MD032 -->
-<!-- markdownlint-disable-next-line MD025 -->
 # Tutorial: Conduct a FinOps iteration
 
 <a name="about"></a>
 In this tutorial, you learn that FinOps is an iterative, hierarchical process that requires cross-functional collaboration across business, technology, and finance teams. When you consider the 18 different capabilities, each with their own unique nuances, adopting FinOps can seem like a daunting task. However, in this tutorial, you learn how to take an iterative approach to FinOps adoption where you:
 
+<!-- prettier-ignore-start -->
+<!-- markdownlint-disable -->
 > [!div class="checklist"]
 > - Define the right scope for your next FinOps investments.
 > - Identify measurable goals to achieve over the coming weeks or months.
 > - Select the right actions to get to the next maturity level.
 > - Review progress at the end of the iteration and identify goals for the next.
+<!-- markdownlint-enable -->
+<!-- prettier-ignore-end -->
 
 Use this tutorial as a guide when you start each iteration of the FinOps lifecycle.
 
@@ -41,42 +43,42 @@ Before you start your next iteration, it's important to define the bounds for wh
 Use the following information as a guide to select the right FinOps capabilities based on your role, experience, and current priorities. It isn't an all-inclusive list of considerations. We encourage you to select all from one group or pick and choose across groups based on your current needs. The following order presented is a suggestion, not a requirement. It's merely an aid to help you get started.
 
 1. If your team is new to FinOps with little to moderate experience with cost management and optimization, we recommend starting with the basics:
-    1. Reporting and analytics
-    2. Forecasting
-    3. Budgeting
-    4. Workload optimization
-    5. Anomaly management
+   1. Reporting and analytics
+   2. Forecasting
+   3. Budgeting
+   4. Workload optimization
+   5. Anomaly management
 2. If you're building a new FinOps team or interested in driving awareness and adoption of FinOps, start with:
-    1. FinOps practice operations
-    2. Onboarding workloads
-    3. FinOps assessment
-    4. FinOps education and enablement
-    5. Forecasting
+   1. FinOps practice operations
+   2. Onboarding workloads
+   3. FinOps assessment
+   4. FinOps education and enablement
+   5. Forecasting
 3. If your team knows Microsoft Cloud's FinOps tools well and needs to manage costs in a large company where ownership is sometimes shared, consider the following items:
-    1. Allocation
-    2. Invoicing and chargeback
-    3. Rate optimization
+   1. Allocation
+   2. Invoicing and chargeback
+   3. Rate optimization
 4. If your team is experienced with Microsoft Cloud's FinOps tools and needs to manage costs in a large organization with distributed and shared ownership, consider the following items:
-    1. Allocation
-    2. Invoicing and chargeback
-    3. Rate optimization
+   1. Allocation
+   2. Invoicing and chargeback
+   3. Rate optimization
 5. If your team needs to build more advanced reporting, like managing costs across clouds or merging with business data, consider:
-    1. Tools and services
-    2. Data ingestion
-    3. Allocation
-    4. Reporting and analytics
+   1. Tools and services
+   2. Data ingestion
+   3. Allocation
+   4. Reporting and analytics
 6. If your team has a solid understanding of the basics and wants to focus on deeper optimization through advanced automation, consider:
-    1. Architecting for the cloud
-    2. Workload optimization
-    3. Rate optimization
-    4. Licensing and SaaS
-    5. Cloud sustainability
-    6. Policy and governance
+   1. Architecting for the cloud
+   2. Workload optimization
+   3. Rate optimization
+   4. Licensing and SaaS
+   5. Cloud sustainability
+   6. Policy and governance
 7. If your team has a solid understanding of the basics and needs to map cloud investments back to business value, consider:
-    1. Unit economics
-    2. Allocation
-    3. Budgeting
-    4. Planning and estimating
+   1. Unit economics
+   2. Allocation
+   3. Budgeting
+   4. Planning and estimating
 
 Note the capabilities you select for future use.
 
@@ -86,6 +88,7 @@ Note the capabilities you select for future use.
 
 Next, you identify specific, measurable goals based on your current experience with the capabilities you selected. Consider the following points when you identify goals for this iteration:
 
+<!-- prettier-ignore-start -->
 - **Knowledge** – How much do you know about the capability?
   - If you're new to the capability, focus on learning the purpose, intent, and how to implement the basics. Knowledge is often the first step of any capability.
 - **Process** – Is a repeatable process defined, documented, and verified?
@@ -95,15 +98,17 @@ Next, you identify specific, measurable goals based on your current experience w
   - If you know the basics, but didn't identify success metrics, they're a must-have for your next step. Focus on identifying metrics that are relevant for your business and help you make trade-off decisions for this capability. To maximize efficiency, build these metrics and decisions into your process.
   - If you have metrics identified, focus on getting a baseline for where you're at today. Seek to automate wherever possible, which will save you time in the future. Use tools like Power BI to generate reports you can share with stakeholders and celebrate your collective successes.
 - **Adoption** – How many teams adopted the defined process and metrics?
+
   - If you have a process that was only tested on a small scale, share it with others. Experiment with the process and incorporate a feedback loop for continuous improvement.
-  - As your process matures, you notice less input from the feedback loop. Less input is a sign that your process is ready to be scaled out more and potentially be established as an official governance policy for new teams. If you're in a large organization that doesn't have a dedicated FinOps team, you might want to consider establishing one to drive this effort.  
+  - As your process matures, you notice less input from the feedback loop. Less input is a sign that your process is ready to be scaled out more and potentially be established as an official governance policy for new teams. If you're in a large organization that doesn't have a dedicated FinOps team, you might want to consider establishing one to drive this effort.
 
-    > [!IMPORTANT]
-    > _Before establishing a dedicated FinOps team, consider how much time each individual team is spending on FinOps efforts, what the potential business value is with more savings and efficiency (or lost opportunity), and how much a dedicated team can accelerate those goals. A dedicated team is not for everyone. Ensure you have the right return on investment._
+  > [!IMPORTANT]
+  > _Before establishing a dedicated FinOps team, consider how much time each individual team is spending on FinOps efforts, what the potential business value is with more savings and efficiency (or lost opportunity), and how much a dedicated team can accelerate those goals. A dedicated team is not for everyone. Ensure you have the right return on investment._
 
 - **Automation** – Has the capability been automated to minimize manual effort?
   - If you're developing a process, we recommend identifying automation opportunities as you go. You might identify low-hanging fruit that could lead to large efficiency gains at scale or even find partner teams willing to contribute time in those areas and share resources.
   - As you experiment with your process, keep your list of automation opportunities updated and share them with others as part of the feedback loop. Prioritize automating success metrics and look for opportunities to implement the most repeated tasks for maximum efficiency.
+<!-- prettier-ignore-end -->
 
 In general, we recommend short iterations with targeted goals. Select one to three highly related goals listed previously. Avoid long iterations that cover a broad spectrum of work because they're harder to track, measure, and ultimately deliver.
 
@@ -129,21 +134,27 @@ After you close out on the iteration, remember that this tutorial can help guide
 
 Let us know how we're doing with a quick review. We use these reviews to improve and expand FinOps tools and resources.
 
+<!-- prettier-ignore-start -->
 > [!div class="nextstepaction"]
 > [Give feedback](https://portal.azure.com/#view/HubsExtension/InProductFeedbackBlade/extensionName/FinOpsToolkit/cesQuestion/How%20easy%20or%20hard%20is%20it%20to%20use%20FinOps%20toolkit%20tools%20and%20resources%3F/cvaQuestion/How%20valuable%20is%20the%20FinOps%20toolkit%3F/surveyId/FTK/bladeName/Guide.General/featureName/ConductAnIteration)
+<!-- prettier-ignore-end -->
 
 If you're looking for something specific, vote for an existing or create a new idea. Share ideas with others to get more votes. We focus on ideas with the most votes.
 
+<!-- prettier-ignore-start -->
 > [!div class="nextstepaction"]
 > [Vote on or suggest ideas](https://github.com/microsoft/finops-toolkit/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%252B1-desc)
+<!-- prettier-ignore-end -->
 
 <br>
 
 ## Next step
 
 Review and refine the FinOps capabilities that are most critical to you:
 
+<!-- prettier-ignore-start -->
 > [!div class="nextstepaction"]
 > [FinOps capabilities](./framework/capabilities.md)
+<!-- prettier-ignore-end -->
 
 <br>