<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ibukunoluwa Samuel on Medium]]></title>
        <description><![CDATA[Stories by Ibukunoluwa Samuel on Medium]]></description>
        <link>https://medium.com/@ibukunsamuel7?source=rss-7fb307ed6e1e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fhlAeMNWKx1h0tT741xjMA.jpeg</url>
            <title>Stories by Ibukunoluwa Samuel on Medium</title>
            <link>https://medium.com/@ibukunsamuel7?source=rss-7fb307ed6e1e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 02:43:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ibukunsamuel7/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Azure cloud services: pricing models, and billing structures]]></title>
            <link>https://medium.com/@ibukunsamuel7/azure-cloud-services-pricing-models-and-billing-structures-be49945b10fa?source=rss-7fb307ed6e1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/be49945b10fa</guid>
            <category><![CDATA[billing]]></category>
            <category><![CDATA[microsoft-azure]]></category>
            <category><![CDATA[finops]]></category>
            <category><![CDATA[pricing]]></category>
            <category><![CDATA[azure-free-account]]></category>
            <dc:creator><![CDATA[Ibukunoluwa Samuel]]></dc:creator>
            <pubDate>Thu, 21 May 2026 14:43:08 GMT</pubDate>
            <atom:updated>2026-05-21T14:49:29.071Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Avoid unexpected charges</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/1*11V3J-XFZRzqRuhP_MwbZA.png" /></figure><p>When using services and resources from public cloud service provider, settle with this truth: you pay for the resources you provisioned, whether you “use” them or not. I wrote an explainer on all you need to know about <a href="https://medium.com/@ibukunsamuel7/explainer-all-you-need-to-know-about-creating-a-microsoft-azure-account-6a2d61df4f13">creating a Microsoft Azure account</a>. Feel free to check that out too.</p><p>In the course of my interaction, I came across such things as:</p><p>“<em>I believed the services were cancelled”</em></p><p>“<em>the app service does not have human traffic”</em></p><p>“<em>I have not logged into the portal since x month</em>”</p><p>I would be rich if I had a dollar for every time I heard one of the reasons a person who has just received unexpected charges gives. However cute these reasons may be, the point remains that once a resource is deployed either by a programmatic way or GUI, the billing meter starts to read.</p><p>Cloud service providers advertised a PAYG model and while that is true, the lines start to get blurry when a pregnant woman learning to use the cloud forgot a service bus resource in the portal when she went to delivered her baby or the inexperienced user who left an idle resource from a tutorial.</p><p>This essay is targeted at new and inexperienced azure cloud user who want to avoid unexpected charges. The essay addresses misconception and general confusion associated with the pricing and billing structure of individual account.</p><p>On the <a href="https://azure.microsoft.com/en-us/pricing/purchase-options/azure-account">Create Your Azure Free Account Or Pay As You Go | Microsoft Azure</a> page shown above, the journey into individual Azure account starts with either pay-as-you-go or Azure free Trial. While the latter is for learning/training/PoC, the former is for users who are ready to build out their workload.</p><ol><li>Azure Free Account/ Azure Free Trail is one where $200 credit (or its equivalent in local currency) is assigned upon sign up to new eligible azure customer to use on Azure services within 30 days.</li><li>Pay-as-you-go account takes it name from the standard pricing rate for individual azure account where services are charged based on what you use. Pay-as-you-go account is not tied to the validity of free credit term and guarantees access to full catalog of services with no cap on service usage.</li></ol><p>Both accounts come with free monthly amounts of 20+ popular services for 12 months (new Azure customers only) and free monthly amounts of 65+ always-free services</p><p>On both accounts, you can opt out at whatever time by clicking the cancel button on the subscription overview page.</p><h3><strong>What happens when you don’t upgrade Azure Free Trial to PAYG</strong></h3><p>The lack of upgrade means a credit/debit card was not added. The lack of upgrade keeps the account as Azure free trial and guarantees spending protection. This means the subscription will be deactivated on day 30 or when credit is used up whichever occurs first. Why? Upon sign-up, the azure credit becomes the default payment instrument as it were. When the subscription reaches expiry, because the “live” keeping the subscription active is expired or used up as the case maybe, the subscription has nothing to thrive on and by design, it gets deactivated.</p><h3><strong>What happens when you upgrade Azure Free Trial to PAYG</strong></h3><p>An upgrade occurs the moment a credit/debit card is added to an azure free trial. This causes the azure account to become billable. If one or more of these conditions occurs: 1) you exhaust the 200USD sign-up credit 2) the sign-up credit is expired 3) use above the free service limit, the credit/debit card is billed. As I would later touch on in the course of this essay, the credit/debit card added during sign-up is for identity verification; it is not billable until an upgrade happens. An upgrade can take place within the first 30days or after. An upgrade within the first 30days upon sign-up, ensures continued access to azure services without limit in addition to the two categories of free services within their respective validity.</p><p>Both the azure credit and the card added at the point of upgrade becomes the payment instrument on file. Within its validity, Azure credit is used to settle charges first. When they are used up, expired or credit ineligible service are purchased, the credit card kicks in and used to settle charges. As a result, see upgrade as a point of formal consent authorizing the cloud service provider to settle charges using the PI on file.</p><p>Moving to pay-as-you-go to continue beyond 30 days or after credit is used up could be for any reasons. Chiefly is to take advantage of the free monthly amounts of 20+ popular services for 12 months (new Azure customers only). Free monthly amounts of 65+ always-free services. PAYG pricing gives access to full catalog of services with no cap on service usage. No notification or alert would go off when usage exceed free services limit and services start to bill on PAYG standard pricing. I recommend paying attention to the free monthly amounts.</p><p>Each month you receive specified free amounts of certain types of services. With pay-as-you-go pricing, if you exceed your monthly free amounts for any services, you’ll be billed for them at pay-as-you-go rates. For the services that are free for 12 months, any services you’re using after 12 months has expired will continue to run and you’ll be billed for them at pay-as-you-go rates.</p><p>PAYG account whether upgraded or started out outrightly by definition is pay only for what is used beyond free monthly amounts. A resource could be listed as a free services yet you receive a bill for its use. Wondering what happened? PAYG pricing kicked in the moment the free monthly amounts is used up. Deploying multiple instance of a resource and exploring capacities newly? Remember, services are free up to the monthly amount or covered by $200 credit if you are still within the validity of Azure free trial. To avoid getting charged, keep your usage within the limits.</p><h3><strong>Avoid charges with your Azure free account</strong></h3><p>Now that we got the definition out of the way, let’s explore ways to avoid unexpected charges on an azure (free) account.</p><p>Azure sign-up credit is non-transferrable and cannot roll over.</p><p>You are not charged as long as there is an active credit and when the credit expired, maintain the use of only free services within the allowable limit.</p><p>Track and monitor the credit from the day of sign-up. The credit is available for use for 30 days. Depending on the date of sign-up and usage will be used to settle charges across one or two billing periods. You either run out or reach expiry. With azure free account, when any one of these happens, the subscription and services are disabled when an upgrade has not taken place. when upgrade is set to true, the subscription remains active and uninterrupted.</p><p>Avoid using services that are not free when you are not ready to get charged.</p><p>Pay close attention to the expiration date of 12 months. Free services and quantities expire at the end of 12 months. You can find out when your free services expire in the Azure portal.</p><ol><li>Sign in to the Azure portal.</li><li>In the left navigation area, select All services.</li><li>Select Subscriptions.</li><li>Select the subscription that was created when you signed up for free account.</li><li>Scroll down to find free services grid. Select the tooltip located on the top left of the grid.</li></ol><h3><strong>Plan to manage Azure costs</strong></h3><ol><li>Take advantage of pricing calculator to get an estimate of cost<br>: <a href="https://azure.microsoft.com/pricing/calculator/">https://azure.microsoft.com/pricing/calculator/</a>. Take the calculator as an opportunity to plan and budget based on anticipated usage. Anticipated usage may not be equal to actual usage. Monthly bills are prepared based on actual usage.</li><li>Set up budget, alerts and track cost as you go from cost analysis. Alerts are purely notification, letting the recipient know to login into the portal to take a proactive action.</li><li>In the process of deployment and creating a service, you can view the estimated cost. When you choose the size of a VM, right there on the “create a virtual machine” page, in the size tab, a “change size” is displayed. When clicked opens a much bigger window to browse VM sizes.</li></ol><p><strong>Additional resources:</strong></p><p><a href="https://azure.microsoft.com/en-us/pricing/free-services/">Explore Free Azure Services | Microsoft Azure</a></p><p><a href="https://azure.microsoft.com/en-us/pricing/offers/ms-azr-0044p/">Azure Free Trial | Microsoft Azure</a></p><p><a href="https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/check-free-service-usage">Monitor and track Azure free service usage — Microsoft Cost Management | Microsoft Learn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be49945b10fa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Azure Reservations: Utilization and Cost Reports]]></title>
            <link>https://medium.com/@ibukunsamuel7/azure-reservations-utilization-and-cost-reports-abcace8ec7ff?source=rss-7fb307ed6e1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/abcace8ec7ff</guid>
            <category><![CDATA[finops]]></category>
            <category><![CDATA[reservations]]></category>
            <category><![CDATA[amortized]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[utilization]]></category>
            <dc:creator><![CDATA[Ibukunoluwa Samuel]]></dc:creator>
            <pubDate>Mon, 11 May 2026 19:23:09 GMT</pubDate>
            <atom:updated>2026-05-11T19:23:09.118Z</atom:updated>
            <content:encoded><![CDATA[<p>Under this broad topic, I will examine post purchase frequently asked questions such as how to view reservation utilization, how to view reservation transactions? An organization matured in its FinOps practice may also have questions about charge back for the purpose of internal reporting. These and more will be addressed in this essay.</p><h3><strong>View reservation utilization after purchase</strong></h3><p>The utilization percentage of reservation as well as the benefiting resources can be viewed in the Azure portal. The role a user has and how they navigate through the Azure portal determines the utilization view presented. If you try to view reservation utilization and are unable to you may want to check 1) user access 2) navigation through the portal Navigating through the path: Azure Portal &gt;&gt;Reservations with any one of the under listed roles opens the utilization window</p><ol><li>Azure RBAC access to the reservation</li><li>An elevated access to manager all Azure subscriptions and management groups.</li><li>Reservation administrator or reader</li></ol><p>In a Microsoft Customer Agreement (MCA) billing account, a user with billing administrator can view the utilization from Cost Management + Billing&gt;&gt;Reservations.</p><h3><strong>Amortized benefit costs.</strong></h3><p>Amortization is the process of breaking one-time cost into periodic costs. When charge back or show back is an organization’s priority, amortization helps to show the partial cost of the benefit to users or departments that use it, there is need to determine what the monthly or daily cost of the benefit is.</p><p>Using cost analysis to view amortized costs. Let’s lead with some basic information</p><ol><li>reservation or savings plan are referred to as benefit</li><li>when you buy benefit, you are normally committing to a 1-year or 3-year plan to save money compared to pay-as-you-costs.</li><li>You can choose to pay for the benefit up front or with monthly payments</li><li>If you pay up front, the one-rime payment is charged to your subscription</li></ol><h3><strong>The character of cost analysis working with benefit</strong></h3><ol><li>Actual cost and amortized cost views show different total numbers.</li><li>Depending on your view in cost analysis, the total cost of months with a RI purchase decrease when viewing amortized costs, and months following a reservation purchase increase.</li><li>Amortization is available only for reservation purchases and does not apply to azure marketplace purchase currently.</li><li>Virtual machine software usage reservations available in the Azure Marketplace are supported.</li><li>Benefit costs displayed in cost analysis takes after the view in cost analysis.</li><li>cost analysis shows charges as they appear on your bill; showing charges as actual costs or amortized</li></ol><h3><strong>How Azure calculates amortized costs:</strong></h3><p>Illustration</p><p>A 1-year virtual machine reservation purchased on January 1. Depending on your view, instead of seeing a $365 purchase on January 1, 2022, you’ll see a $1.00 purchase every day from January 1, 2022 to December 31, 2022.</p><p>From the illustration:</p><p>Actual cost: $365</p><p>Amortized cost: a $1.00 (=$365/365days)</p><h3><strong>Characteristics of Amortized cost</strong></h3><ol><li>Amortized cost are reallocated and associated to the specific resources that used the reservation.</li><li>To describe this more vividly, if the $1.00 daily charge was split between two virtual machines, you’d see two $0.50 charges for the day</li><li>What happens if part of the reservation isn’t utilized? The daily charge not utilized shows as type “<em>UnusedReservation”</em>.</li><li>Unused reservation costs are supported only when viewing amortized cost</li><li>Amortized cost factors the varying number of days in a month. This causes the month cost to vary.</li><li>Amortized cost is divided by 366 if a leap year is involved.</li><li>In a 365-calendar year, the daily cost is the same for every day.</li><li>While you can purchase reservation with a PAYG subscription, cost analysis does not support amortized reservation cost for a PAYG subscription. Interpreted loosely means, if you don’t own RI, don’t expect to see amortized cost</li></ol><h3>Metrics affect how costs are shown</h3><p>In cost analysis, you view costs with a metric. They include actual cost and amortized cost. Each metric affects how data is shown for your benefit charges.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/451/1*ETnI5wDy2uCuZ2kO-Hg_kA.png" /></figure><h3><strong>View amortized costs</strong></h3><p>Context: a 1-year benefit purchased for $12016 purchased on Oct 23, 2019, with a term end date on Oct 23, 2020, and a leap year day is included in the term, so the term’s duration is 366 days.</p><p>In the Azure portal, navigate to cost management&gt;cost analysis</p><ol><li>Select a date range that includes a period of the benefit term</li><li>Add a filter for Pricing Model:Reservation</li><li>Set granularity to daily.</li></ol><p>A visual representation showing the purchase with the date range set from October through November 2019</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0r24GXhsgH7x1k9Yoxq4Zw.png" /></figure><p>When the switch is flipped by setting the scope to Amortized cost metric. Below is an example demonstrating the daily cost of all reservations for the selected date range. The image below shows daily cost is about $37.90</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CIqZ48dXXBS-Rg8q8EHQXg.png" /></figure><p><strong>Accounting for multiple reservation</strong></p><p>Use the Group by list to group the results by Reservation name. the image below shows daily amortized cost of the reservation named VM_WUS_DS3_Upfront for $32.83 (=$12016/366) 366, because the reservation term includes a leap year (2020)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8t7jCaPMQKR7DygGKuMhcw.png" /></figure><p>Next, change the Granularity to Monthly and expand the date range. The following example shows varying monthly costs for reservations. The cost varies because the number of days in each month differs. November has 30 days, so the daily cost of $32.83 * 30 = ~$984.90.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MWPLVW7Nqq4jWEhnI0YWhQ.png" /></figure><h3><strong>View benefit resource amortized costs</strong></h3><p>To charge back or show back costs for a benefit, you need to know which resource used the benefit. Use the following steps to see amortized costs for individual resources. In this example, we examine November 2019, which was the first month of full reservation use.</p><ol><li>Select a date range in the benefit term where you want to view resources that used the benefit.</li><li>Add a filter for Pricing Model: Reservation to see only reservation costs.</li><li>Set Granularity to Monthly.</li><li>Under Scope and next to the cost shown, select the down arrow symbol and then select the Amortized cost metric.</li><li>If you have multiple reservations, use the Group by list to group the results by Reservation name.</li><li>In the chart, select a reservation. A filter is added for the reservation name.</li><li>In the Group by list, select Resource. The chart shows the resources that used the reservation. In the following example image, November 2019 had eight resources that used the reservation. There’s one unused item, which is the subscription that was used to buy the reservation.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dbgn8WBWqU9RMr9-gz6K1g.png" /></figure><p>To see the cost more easily for individual resources, select Table in the chart list. Expand items as needed. Here’s an example for November 2019 showing the amortized reservation costs for the eight resources that used the reservation. The highlighted cost is the unused portion of the reservation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mwMzF72X12De3_w8yRw_lQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abcace8ec7ff" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud Cost Allocation Guide]]></title>
            <link>https://medium.com/@ibukunsamuel7/cloud-cost-allocation-guide-7c69e615044f?source=rss-7fb307ed6e1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c69e615044f</guid>
            <category><![CDATA[cost-allocation]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[azure-portal]]></category>
            <category><![CDATA[tag]]></category>
            <category><![CDATA[cloud]]></category>
            <dc:creator><![CDATA[Ibukunoluwa Samuel]]></dc:creator>
            <pubDate>Fri, 27 Mar 2026 17:37:33 GMT</pubDate>
            <atom:updated>2026-03-27T17:37:33.741Z</atom:updated>
            <content:encoded><![CDATA[<h4>Azure tools and features for cost allocation</h4><figure><img alt="a flow chart showing Microsoft Azure billing hierarchy for MCA customers" src="https://cdn-images-1.medium.com/max/1024/1*6nJ0pPrkXWzwpDzmPIW2nw.png" /><figcaption>Microsoft Azure billing hierarchy</figcaption></figure><p>Microsoft Azure as a cloud service providers uses a modern billing system (Microsoft Customer Agreement -MCA) that generates a consolidated monthly invoice. This is a sharp contrast to a legacy billing system where users get invoices for each of the subscriptions in an azure account. Just the thought of managing invoices of tens or hundreds of subscriptions in an account coming at different billing cycles is enough to make my head spin. Whew! <em>How did account with several subscriptions, Partner account survive that era!?</em></p><p>The MCA invoices arrive on a specific day of the month containing Azure Usage as well as charges for products and asset for all the subscriptions created in a billing scope — Marketplace charge, Reservation charges, Savings Plan, Support Plan, Office Product. This can range from 2 to nth pages where n depends on the size of an environment. By design, the first page contains a summary of the bill followed by page(s) of compact breakdown of what the bill is made up of.</p><p>When a consolidated monthly invoice is generated from the cloud service provider, it is accompanied by a usage report (CustomerLed) or recon file (PartnerLed) where a lot more details not available on the invoice are documented. Depending on the workload in the azure account, this can run into thousands of rows. For every resource you have consumed during the month, there will be details about the resource identifier, region, service family, pricing currency, billing currency, quantity, the rate you were charged, tax, discounted pricing etc.</p><p>As detailed as these documents are, they are missing details about who owns it, who should pay for it, what business service the resource belongs to, and this is because cloud service providers cannot be expected to add this detail to a bill; all of these questions are customer specific. How do we bridge this gap? How do we achieve visibility and add business context to cloud bill? Enters Cost Allocation.</p><p>Cost allocation is the practice of using hierarchies, tags, and labels to accurately assign technology costs to different teams, LOB, departments, groups, projects within an organization based on how much resource they consumed for visibility, accounting and reporting purposes.</p><h4>The benefits of cost allocation are appreciated in the underlisted ways:</h4><ol><li>Visibility into costs. If I will pay for a bill, I should know and see what I am paying for.</li><li>Track and optimize spending. With visibility comes accountability. I am able to optimize the spend that I am made aware of.</li><li>Improve budgeting and forecasting</li><li>Increase accountability and transparency</li><li>Control the spending and generate data for internal reporting system</li></ol><h4><strong>Tools and features of cost allocation</strong></h4><p>Together or individually, the underlisted tools help to reach cost allocation maturity</p><ol><li>Azure resource hierarchy, including management groups, subscriptions, and resource groups</li><li>Azure billing hierarchy</li><li>Tags</li><li>Cost allocation rules</li></ol><h3>Azure resource hierarchy and Azure billing hierarchy</h3><p>These are representation of the high-level flow of cost and resource management in the cloud.</p><p>Azure resource hierarchy — represent an organizational structure of resources used in Azure.</p><p>Azure billing hierarchies — shows hierarchical construct of the account owner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YgyKghVPt-IxGLgfZRTW2g.png" /><figcaption>An overview of Azure resource hierarchy</figcaption></figure><p><strong>Management groups </strong>seats beneath the top-level as a logical bucket where subscriptions and other management groups are held in a cascading flow. As a logical bucket, cost allocation, policies and access controls are applied at Management group scope; when weighed against individual subscription across a cloud estate saves time and labour. A FinOps Practitioner answering my questions during a community call mentioned what worked in her organization is a one subscription/per workload approach. While that is great, it falls flat in a case of shared workload or years of overlapping usage. Management groups aid cost allocation by allowing organizations wrap 2 or more subscriptions that fits or share a criterion such business units, departments, environments etc. A management group containing subscriptions for EMEA business division assigned budgets, tags, and cost alerts can be used to reap the dividend highlighted in the opening paragraph</p><p><strong>Subscriptions </strong>are a way of grouping azure resources that might or might not share a common billing relationship. Subscriptions are typically what you interact with during deployment. It is the first required field when you use azure portal to deploy a resource. Even when you do so programmatically, a subscription is specified. In addition to resource deployment, subscriptions are used for cost allocation. By design, you can have a maximum of five subscriptions in a Microsoft Customer Agreement purchased directly through Azure.com however on a need basis, subscriptions limit may be reviewed when support is contacted. For example, you can create subscriptions for different departments, projects, or environments within your organization.</p><p><strong>Resource groups </strong>are not only used for managing and “holding” resources. They are for allocating costs. Budgets, tags, and cost alerts can be specified against a resource group to control the costs. You can create a resource group for each department, application, or stage of the development lifecycle.</p><h3>Cost allocation rules</h3><p>Right within the azure portal, you can split shared cost by moving costs between subscriptions, resource groups and tags. Allocation rules are useful when you have shared resources and a single consolidated bill is what cloud service providers provides.</p><p><strong>Driving cost allocation home</strong></p><ol><li>Large enterprises often centrally manage Azure services or resources</li><li>Different internal department or business units use them.</li><li>The centrally managing teams wants to reallocate the cost of the shared services back out to the internal departments or organizational business units who are actively using the services.</li></ol><p>Cost allocation doesn’t affect your billing invoice. Billing responsibilities don’t change. The primary purpose of cost allocation is to help you charge back costs to others. Cost allocation doesn’t support purchases, including reservations and savings plans.</p><h3>Tags</h3><p>Tags are key-value pairs that you can apply to Azure resources to group and allocate costs based on business needs. Enforce tagging compliance with Azure Policy. Azure Policy provides built-in and custom policy definitions to enforce your tagging requirements consistently across all regions. Automated policy enforcement ensures tagging compliance without manual oversight. Generally, tags are assigned to resources in order to assign ownership, describe a resource, and ultimately allocate costs for the purpose of financial accounting.</p><p><strong>Let’s double click on Tag …</strong></p><ol><li>You may find that some usage records are missing tags because not all Azure resources emit tags in their usage</li><li>We would talk more on tag inheritance in a little as a way to apply subscription and resource group tags to underlying child resources.</li><li>You don’t need to rely on resources emitting tags in their usage or tag every resource for your cost allocation needs.</li><li>Inherited tags are applied to child resource usage records and not the resources themselves.</li><li>When a resource tag matches the inherited tag being applied, the resource tag is applied to its usage record by default. You can change the default behavior to have the inherited tag override the resource tag.</li><li>After the tag inheritance setting is updated, it takes about 8–24 hours for the child resource usage records to get updated. Any update to the setting or the tags being inherited takes effect for the current month.</li><li>If there are purchases or resources that don’t emit usage at a subscription scope, they will not have the subscription tags applied even if the setting is enabled.</li><li>Tags are stored as plain text. Never add sensitive values to tags. Sensitive values could be exposed through many methods, including cost reports, commands that return existing tag definitions, deployment histories, exported templates, and monitoring logs. Don’t store sensitive values such as passwords, personal information, or confidential business data in resource tags.</li><li>When you enable the Tag inheritance setting at the billing profile level, tags from billing profile and invoice sections are applied to usage records for all child resources.</li><li>Understand case sensitivity in tags:tag names(keys) are case insensitive, but tag values are case sensitive. Case sensitivity differences can create confusion when you filter resources or generate report based on tag values. Use lowercase for tag names (keys) and maintain consistent capitalization for tag values. For example, Environment: production and environment: production represent the same tag name (the first part). However, environment: Production and environment: production are different tag values (second part), and they appear separately in cost reports and resource queries.</li><li>Include tags that indicate region. Multi-region Azure operations need clear regional visibility to support compliance, cost allocation, and operational management requirements. Add region-specific tags like “region: eastus” to maximize operational efficiency and enable accurate regional reporting across your deployments.</li></ol><h4><strong>Tag inheritance setting in Cost Management</strong></h4><p>Tag inheritance are not enabled by default, but when they are, inheritance applies billing, resource group, and subscription tags to child resource usage records.</p><p>I work from the Cost Management +Billing page most of the time; when I was ready to enable tag inheritance setting in the Azure portal, I was on CM +B page looking around before zooming in on the guide to see that for Tag, Cost Management is the page to be. If you find yourself looking around for Tag Inheritance or Configuration page after changing billing scope, make sure you are in Cost Management page and that you have a scope selected where Tag(s) existed.</p><p>It is important to point out that scope is super important and determines what you are presented on the configuration page when Tag inheritance is enabled. Depending on the hierarchy in your account, I was able to drill through Default Directory&gt;&gt;billing account&gt;&gt;billing profile&gt;&gt;invoice section and Root management&gt;&gt;management group&gt;&gt;Azure subscription &gt;&gt;Resource Group.</p><p>A view showing zero tags. Before moving to enable inheritance, one or more tag must exist. Otherwise, there is nothing to enable inheritance on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qyAiwrFxzcB1DhE2eqIlVA.png" /></figure><p>A view showing a tag (I didn’t even realize I had one) on the subscription scope and navigating through tag inheritance. Navigate through Cost Management&gt;&gt; change scope&gt;&gt;Configuration(under the settings tab)&gt;&gt; Under Tag inheritance, select Edit. In the Tag inheritance window, select Automatically apply billing, subscription and resource group tags to new usage data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tgKVgWt0iHzMR-gMKU0XQQ.png" /></figure><p>Right on the same page, you can create a new tag or modify existing tag.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LiWdDxCIY36YMqVN5OnRKA.png" /></figure><h4>View costs grouped by tags</h4><p>You can use Cost analysis to view the costs grouped by tags.</p><p>In the Azure portal, navigate to Cost Management. In the left menu, select Cost Analysis. Select a scope. In the Group by list, select the tag you want to view costs for. You can also view the inherited tags by downloading your Azure usage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*b46sDT3eHEILpsu0" /><figcaption><a href="https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/enable-tag-inheritance#view-costs-grouped-by-tags">https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/enable-tag-inheritance#view-costs-grouped-by-tags</a></figcaption></figure><h4>Tag application on billing profile and Invoice section</h4><p>Go to <a href="https://portal.azure.com./">https://portal.azure.com.</a></p><ol><li>Search for and select Cost Management + Billing.</li><li>Select the billing profile where you want to set the tags.</li><li>On the left menu, select Properties under Settings and then select Add or Update tags.</li></ol><p>For Invoice Section, from step 3,</p><ol><li>On the left menu, select Invoice sections under Billing.</li><li>Select the invoice section where you want to set the tags.</li><li>On the left menu, select Properties under Settings and then select Add or update Tags.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oISages3yUNLKkE_eWIl-g.png" /><figcaption>Billing profile view showing Tags</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iBnM-PkYe26d_eSMfyF6rw.png" /><figcaption>Invoice Section view showing Tags</figcaption></figure><h4>Define your tagging requirements</h4><ol><li>Evaluate existing company policy. Tagging approach are not created in isolation of existing organizational standards. To maintain consistency, tagging practices must align with naming convention (if available), and any other governance framework.</li><li>Identify operational and compliance requirement: resource tags capture critical operational metadata that supports automation and compliance reporting. Different resources require different operational details such as backup schedules, security classifications, or regulatory compliance status.</li><li>Determine your mandatory tag requirements and establish guidelines for optional tags to balance governance with team autonomy.</li><li>What are your cost allocation needs? Tags form a foundation or is a fundamental for detailed cost tracking for chargeback or showback reporting across departments and business units</li></ol><h4>Use foundational tagging categories</h4><p>Tagging categories are standardized approach for organizing azure resources based on specific business and operational dimensions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/892/1*yA6L9S-SQ96LdZn7OvBajQ.png" /><figcaption><a href="https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-tagging#tag-examples">https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-tagging#tag-examples</a></figcaption></figure><p><strong>Functional tags </strong>to support deployment automation, monitoring and troubleshooting activities. Functional tags categorize resources by their technical role, environment, and deployment characteristics within your workloads.</p><p><strong>Classification tags </strong>identify the sensitivity level, compliance requirement, and usage policies that apply to each resource.</p><p><strong>Accounting tags</strong> associate resources with specific organizational units, projects or cost centers to enable accurate financial tracking and reporting. FinOps Team need detailed cost attribution to support chargeback, showback, and budget management processes.</p><p><strong>Purpose tags </strong>connect resources to specific business functions, processes, and impact levels to support investment decisions and priority management.</p><p><strong>Ownership tags</strong> identify the business units and operational teams responsible for each resource to ensure clear accountability and effective communication.</p><p>We have seen a high-level view of how Cost Allocation tools help to <strong>identify, categorize, and assign </strong>the costs of cloud computing resources to <strong>specific users, departments, projects</strong>, or any other relevant grouping within an organization through the <strong>use of structural hierarchies and tags,</strong> available from cloud service providers.</p><p>An effective cost allocation process lays a solid foundation for chargeback, showback and any other organizational and reporting effort.</p><h4>Resources</h4><p><a href="https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/cost-allocation-introduction">Introduction to cost allocation — Microsoft Cost Management | Microsoft Learn</a></p><p><a href="https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-tagging">Define your tagging strategy — Cloud Adoption Framework | Microsoft Learn</a></p><p><a href="https://www.finops.org/wg/cloud-cost-allocation/">Cloud Cost Allocation</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c69e615044f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[FinOps Framework 2026]]></title>
            <link>https://medium.com/@ibukunsamuel7/finops-framework-2026-83fef1508a16?source=rss-7fb307ed6e1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/83fef1508a16</guid>
            <dc:creator><![CDATA[Ibukunoluwa Samuel]]></dc:creator>
            <pubDate>Sat, 21 Mar 2026 21:27:32 GMT</pubDate>
            <atom:updated>2026-03-21T21:27:32.051Z</atom:updated>
            <content:encoded><![CDATA[<p>The FinOps Framework has been updated. In addition to putting up a new poster on my wall, here are my takeaway from the recent virtual summit where the update was unveiled alongside other evolving conversations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_15qoldF_u3jPC2yz5aPGw.png" /><figcaption>curled from <a href="https://www.finops.org/framework/">FinOps Framework Overview</a></figcaption></figure><p>Broadly, we see that FinOps has evolved and the update recognizes the pivotal role of FinOps in organizations working to get the most of technology investment. Practitioners are invited to manage technology value beyond public cloud.</p><p>FinOps practitioners are collaborating with teams who manage adjacent responsibilities further breaking the institutional silo: IT Service Management (ITSM), IT Asset Management (ITAM), IT Financial Management (ITFM), Sustainability, Security, and Enterprise Architecture teams.</p><h3>New definition alert</h3><p>This is to align with FinOps Foundation’s newly minted mission. The definition remains intact saved for technology passed off for cloud to mirror the fact that FinOps may have started with public cloud and still at the core of the practice, however, there is need to account for personas and categories across other technology categories. We see practitioners starting with public cloud but are invited to make sense of SaaS, Data center investment etc.</p><p>Old:</p><p><em>FinOps is an operational framework and cultural practice which maximize the business value of </em><strong><em>cloud</em></strong><em> and technology, enable timely data driven decision making and creates financial accountability through collaboration between engineering, finance and business team.</em></p><p>New:</p><p><em>FinOps is an operational framework and cultural practice which maximizes the business value of </em><strong><em>technology</em></strong><em>, enables timely data-driven decision making, and creates financial accountability through collaboration between engineering, finance, and business teams.</em></p><h3>Capabilities</h3><p>Out of the four domains, understand usage and cost remained as is while the other three had one capability or the other updated, merged; and an addition.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/950/1*cMVBTkBo9mDFfcWDil8ljw.png" /></figure><h3>Executive strategy Alignment</h3><p>This capability was added to capture the connection between FinOps and executive decision-making. It reflects the reality that technology value has becomes a board-level conversation spanning Public Cloud, SaaS, Data Center, AI, and other categories, with pricing models that are increasingly complex and consumption-driven.</p><p>FinOps may have started off the back of optimization strategy where the spotlight was on cost reporting and reactive optimization today, it has graduated to proactive strategic partnership with leadership, shaping the decisions that determine how technology investment creates business value.</p><p>The new capability stems from the second FinOps principle -Business value drives technology decisions</p><p>Executive Strategy Alignment Capability is organized around four areas:</p><ol><li>Executive Priority Alignment</li><li>Multi-Year Investment Strategy</li><li>Facilitate Product Prioritization Strategy</li><li>Enable Strategic Decision Support</li></ol><h3>FinOps scopes also had a touch up both in definition and coverage.</h3><p>In 2026, Scope has a new definition that captures it as a practical mechanism through which business strategy is translated into FinOps activities rather than a means to just split spending.</p><h4>What Scope is not:</h4><ol><li>FinOps Scope is not simply a view of spending by infrastructure type.</li><li>Scopes are not from an interesting topic or because someone is in the mood to spotlight a new area of spend</li></ol><h4><strong>What Scope is:</strong></h4><ol><li>Scopes are initiated in response to business expectations of specific outcomes coming from leadership</li><li>It is a decision context. This means, a view of specific initiatives or applications that may be in one technology category like cloud, or across many — that determines which Personas are engaged, which Capabilities are applied, and what measures of success are appropriate.</li></ol><p>Previously, Scope was defined as a way to give context for practitioners to apply the FinOps Framework in public cloud (IaaS) SaaS, data center, PaaS, AI.</p><p>In 2026, a <em>FinOps Scope is a defined segment of spending across technology categories, aligned to business constructs — such as products, cost centers, or environment — that guide the application of FinOps to maximize technology value.</em></p><h3>In 2026, framework includes Technology Categories:</h3><ol><li>FinOps for Public Cloud</li><li>FinOps for SaaS</li><li>FinOps for Data Center</li><li>FinOps for Data Cloud Platforms</li><li>FinOps for AI</li></ol><h3>Intersection between Technology Category and Scope</h3><p>There is an interconnectivity between Scopes and Technology Categories. The Technology Category is the “what.” The Scope is the “why.” While Technology Categories describe the broadening of the application of FinOps to more types of technology being reported in many organizations, Scopes describe the subcategory of spending and to which the FinOps practice needs to be applied based on particular business objective.</p><h4>FinOps Foundation Resource:</h4><p><a href="https://www.finops.org/insights/2026-finops-framework/?utm_source=slack&amp;utm_medium=post&amp;utm_campaign=26framework">FinOps Framework 2026: Executive Strategy, Technology Categories, and Converging Disciplines</a></p><p>The State of FinOps on <a href="https://data.finops.org/">https://data.finops.org/</a> documents that AI dominates the forward-looking agenda and FinOps is no longer just explaining usage rather it is involved in future technology decisions before commitments are made.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83fef1508a16" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A guide to Adopting FinOps]]></title>
            <link>https://medium.com/@ibukunsamuel7/a-guide-to-adopting-finops-191d70cdc782?source=rss-7fb307ed6e1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/191d70cdc782</guid>
            <category><![CDATA[cloud-cost-optimization]]></category>
            <category><![CDATA[gcp]]></category>
            <category><![CDATA[finops]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Ibukunoluwa Samuel]]></dc:creator>
            <pubDate>Sat, 14 Mar 2026 19:36:46 GMT</pubDate>
            <atom:updated>2026-03-14T19:36:46.009Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/641/1*tl2OoTY_3xZcsqeG8bzp5A.png" /></figure><p>The financial complexities that accompany innovations becomes apparent today than ever. This essay is a guide to navigate financial considerations and best practices to ensure a cost-effective cloud investment. Adopting FinOps typically involves four stages: <strong>Research, Propose, Prepare, and Launch</strong>. It is not uncommon to see practitioners begin FinOps adoption with the cloud then scope expansion to SaaS, PaaS, Data Center, AI, and Data Cloud platforms. Consequently, you may find these stages translated into scopes beyond cloud.</p><p>Historically, the guy who settles the bill and the one whose usage contribute to the bill scarcely interface. This is made possible by payment innovation like scheduled settlement of invoices on specific day of the month without lifting a finger. This convenient arrangement makes it possible for the payment instrument on file to settle invoices uninterrupted for years without anyone sitting down to look over the line items in the invoice as long as the customers get served and there are no downtimes. Fluctuations and spikes could go unnoticed not because parties involved care less but because it’s not a priority.</p><p>A scenario, one I have seen many a time goes thus: Alex pays the bill. His payment instrument was setup during account creation and has conceptual roles. Raj is the Dev guy, added as a user on the organizations’ directory, assigned RBAC role on the subscription scope to build apps that will serve millions of users. I will reconnect to this scenario in the Research stage, but it makes for a good foundation here.</p><p>When should I consider adopting FinOps practices? Is my organization ripe for framework and cultural practice which maximizes the business value of cloud? These are some of the initial questions posed by stakeholders in engineering, finance and business teams. Well, adopt Finops in four iterative stages:</p><h3><strong>Research</strong></h3><p>Research is the most logical way to kick start a project/venture of any scale and this is true for FinOps. This is the stage where you:</p><p>Take a step back to evaluate your current cloud estate. The goal at this stage is information gathering to understand the state of the investment of cloud, SaaS, AI, and data center. Gather information about resources across resource groups living in subscriptions created in one or more of public cloud with footprint. Use tools such as the Google Cloud Billing Reports, AWS Cost Explorer, Azure Cost Management + Billing, AWS Cost and Usage Reports, Azure usage and charges, GCP billing reports and cost trends, monthly invoices are great for collecting cost data.</p><p>The research stage is great for Alex (who pays the invoice) and Raj(whose usage make up the invoice) to come together to review how much cloud bill is incurred and resource usage in the period under review and how related information is shared and used for decision making across the organization.</p><p>Depending on by governance adopted by the organization, Raj may not see the invoice or the payment instrument at best he sees the cost as you go on cost analysis or estimate. Hence, he barely has visibility into the financial implication of horizontal or vertical scaling. Alex is a businessperson whose schedule does not include rummaging through resource groups in the portal or console as the case maybe. Thus, the duo work in silos for years!</p><p>The research stage is a step in the right direction to break this silo that has existed before FinOps had a name. Think of the research stage as the stage where important (formal and informal) conversations are had for the purpose of information sourcing. Key stakeholders you may collaborate with are the application team, development team or engineering team whose work contribute to usage and cost.</p><p>What the usage report and invoice mentioned earlier would do is consolidation. Data analysis tools come in handy here but feel free to start with one you most familiar with and branch out when things get complex. The data collected in let you know enough about where the organization is; providing a base to build a strategy and vision for adopting FinOps, outline the activities that occur, including rough timelines, to bring this vision to life.</p><p>Highlighted below are information you might seek for public cloud:</p><ol><li>Review the current cloud hierarchy and tagging data. If none exist before now, you know now to include this as low-hanging fruit to reap when you launch.</li><li>Usage reports contain thousands of rows, but they are the first point of data source to review current spending trends. You could identify rate optimization opportunities to determine month-on-month spend total on a development workload, a specific resource or even an entire estate.</li><li>Data visibility let you track actual spend against forecasts and budget. Usage data are expository. You can analyze what you are able to see for patterns and identify possible efficiencies that can be implemented in the environment (terminating idle resources, power scheduling, rightsizing resources, etc.)</li><li>Build FinOps KPI and other industry-appropriate metrics that would in turn be measured and evaluated for success and sustenance. Quantifying where the organization is now and where the organization is going; this will help get buy-in</li></ol><p>Be open minded. Adopting a cultural and organizational shift is gradual and often involves a village. You would need supporters, formal or informal in the organization.</p><h3><strong>Propose</strong></h3><p>After completing the research stage and data collected, the next stage is describing how FinOps can provide relief. FinOps practitioners collaborate with several FinOps personas to achieve efficiency and value in cloud investment; as such buy-in, conviction, funding and other necessities are necessary to make progress towards adoption. A practitioner I engaged in the community recounts how the initiatives and impacts made in their company was easier because they got buy-in from leadership and they carried their team along (as leverage). While they still have other “finopsy” initiatives in the works, everyone with influence needs to be onboard.</p><p>Bring other members of the organization armed with the quantifiable need identified from the research stage. Depending on the size of the organization, it is recommended to take a small portion rather than the entire scope by piloting FinOps using a small segment of the organization. As results and learning point emerges, cover more spread progressively in scope and iterate. Proposing to a subset provide the basis for initial data where early success is recorded for wider buy-in. While a formal engagement involving presentation slides is desirable for a group, an informal approach may produce better result for another group.</p><p><strong>Defining opportunity in the Propose Stage</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/615/1*D_vnN6KL5P34lOp9Yt1dUg.png" /></figure><p>Opportunity defined and you have pitched to supporters and personas now what? From here, you know who is in and who’s not or the version of the proposal accepted or altered. If the proposal was not accepted, FinOps is iterative even at the adoption stage; imply go back to the architecture, roll back to stage one. Organizations are starting to warm up to the practice and attendant dividend of FinOps. I recall a community call where one of the participants mentioned they went to an event with their manager and midway during a presentation, the manager leaned to whisper “yeah, we are doing this thing”. That was their buy-in after months. Don’t be afraid to reposition your arguments for adopting FinOps, reach out to other individuals to join your coalition of support for FinOps, pitch to a different person(s), simply wait and try again at a later time.</p><p>Getting a buy-in is not legs off the pedal; continuously reinforce the essence as you progress to keep everyone’s eye on the road. Say making a monthly chart or tracking a KPI that shows the success of FinOps activities over time. Because of the newness, stakeholders need assurances of the values and benefit derived from FinOps activities; this should be cascaded throughout the organization to keep the practice alive.</p><h3>Prepare</h3><p>Lots of progress is made! In this phase, as you draw near to launch, equipped with information from the research stage and propose stage, define the operating model, team structure, and the execution processes. This is the stage where you get ready to execute against an approved proposal. Translating approved roadmap into actionable steps. For example, if approved roadmap included addressing bloated monthly invoices, you would now look to:</p><ol><li>Questioning resource deployment for business justification</li><li>Booking sessions with the engineering team</li><li>Identify who needs to be in the session etc</li></ol><p>In the Prepare stage, you move from drawing board to designing operations while preparing for formal launch. There are a number of things to tick off at this stage</p><ol><li>Set up FinOps team and responsibility</li><li>Develop processes for executing capabilities</li><li>Collaborate and align goals</li><li>Who to involve</li></ol><p>There are nearly 2 dozen different capabilities, each with their own unique nuances, adopting FinOps can seem like a daunting task. However, adopting an iterative process will not only define how to start but also how to sustainable the journey.</p><p>If it’s the first iteration, selecting three to five FinOps capabilities as a starting point. Selecting the right FinOps capabilities based on role, experience, and current priorities:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/605/1*LKD8Ddo0JYx7YWHCBbKGrQ.png" /></figure><h3>Launch</h3><p>We got approval, prepared and are ready to launch! The strategy on paper is translated to “doings”, rolling out reports, action quick wins to show leadership and teams tangible business value in this stage. The launch stage closely follows the prepare stage because those actionable insights are provisioned. Kind of like the “Go” time after counting down 1,2, 3. The people, the tools, process, policies running together simultaneous towards a common goal. This milestone marks the beginning of normal and ongoing FinOps operations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PfzGYSy6DthutKvqiZO3wA.png" /><figcaption><a href="https://www.finops.org/wg/adopting-finops/">https://www.finops.org/wg/adopting-finops/</a></figcaption></figure><p>Finops adoption story is unique to every organization but generally, adoption springs from need that may or not be immediately apparent but crystalizes and take shape as the practice involves. The four stages are documented as a guide and are in no way restrictive. FinOps is a continuous and iterative process. Embrace the challenges and opportunities ahead. Leverage feedback from teams to improve operations.</p><p>Resource:</p><p><a href="https://www.finops.org/wg/adopting-finops/">Adopting FinOps — Getting Started</a></p><p><a href="https://learn.microsoft.com/en-us/training/modules/adopt-finops-on-azure/">Adopt FinOps on Azure — Training | Microsoft Learn</a></p><p><a href="https://azure.microsoft.com/en-us/solutions/finops#tabs-pill-bar-oc7135_tab1">FinOps on Azure | Microsoft Azure</a></p><p><a href="https://learn.microsoft.com/en-us/cloud-computing/finops/">FinOps documentation — Cloud Computing | Microsoft Learn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=191d70cdc782" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Azure Reservation]]></title>
            <link>https://medium.com/@ibukunsamuel7/azure-reservation-892d309a8f89?source=rss-7fb307ed6e1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/892d309a8f89</guid>
            <category><![CDATA[reserved-instances]]></category>
            <category><![CDATA[azure-reservations]]></category>
            <category><![CDATA[finops]]></category>
            <dc:creator><![CDATA[Ibukunoluwa Samuel]]></dc:creator>
            <pubDate>Thu, 01 Jan 2026 16:42:31 GMT</pubDate>
            <atom:updated>2026-01-01T16:42:31.937Z</atom:updated>
            <content:encoded><![CDATA[<p>A wrote about <a href="https://medium.com/@ibukunsamuel7/azure-savings-plan-d548d2f4529c?source=your_stories_outbox---writer_outbox_published-----------------------------------------">Azure Savings Plan</a> two post before this as one of the cloud cost optimization strategies. In this issue, the spotlight is on Azure Reservations.</p><p>Just like the ASP, Azure Reservations is a billing discount that helps to save money by committing to a discount for a fixed term on resources with a reduction of up to 72% from PAYG prices.</p><h3><strong>High-level overview</strong></h3><ol><li>As seen with ASP, Reservations does not affect the runtime of resource.</li><li>After purchase, no further action is required, the discount automatically applies to resource usage with matching attributes selected during the purchase experience.</li><li>Reservation is restrictive. The restrictive nature is what fetches the significant savings in compared to other cost saving plan. During purchase, purchasers are encouraged to pay attention to attributes such as SKU, regions, and scope. A mismatch from this point may lead to underutilization.</li><li>Reservation supports up front or monthly payment. A monthly payment term does not attract extra fees such that when you sum up, total cost in both payment term is the same.</li><li>After purchase, such things as scope, who can manage the reservation, split a reservation, change instance size flexibility can be managed.</li><li>Unlike ASP, Azure Reservation can be returned (cancelled) and exchanged for another reservation of the same type. Return/cancel/refund a reservation are synonymous and are used interchangeably in documentations. A reservation determined to longer be needed can be returned up to $50,000 USD in a 12 month rolling window.</li><li>Autorenew is turned on by default for all new reservations while you’re in the reservation purchase experience. Optionally, you can manually turn it off or back on after purchase. When tuned off, at the end of the reservation term, the billing discount expires, and the resources are billed at the pay-as-you go price.</li></ol><h3><strong>Why by reservation?</strong></h3><p>Consider your workload; does it paint a picture of consistent resource usage over a foreseeable future? Say you continuously run instances of a service over a period and no visibility of change in sight, taking advantage of reservation discount where the services are no longer charged at the PAYG rate is a good cloud cost decision.</p><h3><strong>New to reservation purchase?</strong></h3><p>There is reservation recommendations generated based on a programmatic analysis. You may also download and analyze usage data for the resource or group of resources that have consistent usage. Having ascertained what to buy, you can buy reservations from the Azure portal, APIs, PowerShell, and CLI.</p><p>The payment instrument tied to the Azure subscription such as credit card, azure prepayment or invoice payment are all accepted for reservation purchase. The credit card you have on your account is billed immediately for up front purchases. Monthly payments appear on your invoice and your credit card is charged monthly.</p><h3><strong>The concept of instance size flexibility or capacity priority.</strong></h3><p>With a reserved virtual machine instance that’s optimized for instance size flexibility, the reservation can apply to the virtual machines&#39; sizes in the same instance size flexibility group. When you buy a reservation, the discount can apply to other instances with attributes that are</p><p>Within the same size group. This feature is known as instance size flexibility. The flexibility of the discount coverage depends on the type of reservation and the attributes you pick when you buy the reservation</p><p>For example, if you buy a reservation for a VM size that’s listed in the DSv2 series, say Standard_DS3_v2, the reservation discount can apply to the other sizes that are listed in that same instance size flexibility group:</p><p>Standard_DS1_v2</p><p>Standard_DS2_v2</p><p>Standard_DS3_v2</p><p>Standard_DS4_v2</p><p>This same reservation does not apply to VMs sizes that are listed in different instance size flexibility groups, like SKUs in DSv2 Series High Memory:Standard_DS11_v2, Standard_DS12_v2, and so on.</p><p>Within the instance size flexibility group, the number of VMs the reservation discount applies to depends on the VM size you pick when you buy a reservation. It also depends on the sizes of the VMs that you have running.</p><h3><strong>Reservation recommendations</strong></h3><p>Reservation recommendations are provided through Azure Consumption Reservation Recommendation API, Azure Advisor, and through the reservation purchase experience in the Azure portal. The following steps define how recommendations are calculated:</p><ol><li>The recommendation engine evaluates the hourly usage for your resources in the given scope over the past 7, 30, and 60 days.</li><li>Based on the usage data, the engine simulates your costs with and without reservations.</li><li>The costs are simulated for different quantities, and the quantity that maximizes the savings is recommended.</li><li>If your resources are shut down regularly, the simulation can’t find any savings, and no purchase recommendation is provided.</li><li>The recommendation calculations include any special discounts that you might have for your on-demand usage rates.</li></ol><p>In the reservation purchase experience of azure portal, recommendations are shown in the “Recommended quantity” column. While any quantity can be bought, the recommended quantity gives maximum savings and any deviation may cause savings to not be optimal. The quantity recommended is calculated for the highest possible usage and it’s based on historical usage. The responsibility is on purchaser to ensure a consistent usage to achieve 100% utilization. A deviation from the recommended quantity causes reduced savings. Say for instance the quantity is increased, you end up with reduced reservation use. In other words, you pay for reservations that are not fully used.</p><p>In the same vein, a reduced quantity also amounts to reduced savings. Although utilization is increased, there might be periods when reservations don’t fully cover the use. By decreasing, usage beyond reservation quantity is used by more expensive PAYG resource. Best practice to achieve an optimal savings with reservations, make purchase choice close to the recommendation as close as possible.</p><h3><strong>What happens after reservation is purchased?</strong></h3><p>Reservation discounts are automatically applied therefore no extra effort is required from the purchaser. Reservation discount applies to the resource usage matching the attributes selected when you buy the reservation. As defined in the high-level overview of reservation, attributes include SKU, regions, and scope. To achieve reservation discount utilization on 4 standard D2 virtual machines in the west US region will see the scope selected during purchase experience as the subscription where the VMs are running. Reservation discount is popularly defined as “use-it-or-lose-it”. In any hour, if there are no matching resources, you lose a reservation quantity for that hour. You can’t carry forward unused reserved hours.</p><h3><strong>Reservation scope</strong></h3><p>Scope is defined as where the matching VMs, SQL databases, Azure Cosmos DB, or other resources run. If the virtual machines are running in different subscriptions within your enrollment/account, then select the scope as shared during purchase experience. You can also use the management group scope. It applies the reservation discount to the matching resource in the list of subscriptions that are a part of both the management group and billing scope across subscriptions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=892d309a8f89" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud FinOps Collaborative, Real-Time Cloud Financial Management]]></title>
            <link>https://medium.com/@ibukunsamuel7/cloud-finops-collaborative-real-time-cloud-financial-management-84456a7b5980?source=rss-7fb307ed6e1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/84456a7b5980</guid>
            <category><![CDATA[finops]]></category>
            <category><![CDATA[cloud-finops]]></category>
            <dc:creator><![CDATA[Ibukunoluwa Samuel]]></dc:creator>
            <pubDate>Sat, 27 Dec 2025 23:26:59 GMT</pubDate>
            <atom:updated>2025-12-27T23:42:07.551Z</atom:updated>
            <content:encoded><![CDATA[<h4>A study note</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/531/1*_7YsTwGps43-Yl1FD8Nm6w.png" /></figure><h4>A case for a new cloud financial management operating model-FinOps.</h4><p>Engineering teams spend more than they need to on cloud deployment often time without realizing it until well into the billing period. Finance teams struggle to understand and keep up with what teams are spending. In the corner office is leadership who doesn’t have enough input into company spending.</p><p>As organizations move into the cloud, however, the pay-as-you-go model aka variable spend models, allows engineers to easily spinoff the shiniest compute resources bypassing the procurement approval process. With thousands of SKUS offered by cloud service providers and plethora of new features introduced each year, a new cloud financial management becomes necessary.</p><p>FinOps came into being slowly, all over the world, as the financial and accountability challenges of cloud presented themselves at scale in each territory.</p><h4><strong>Dividend of FinOps</strong></h4><ol><li>Enterprises get huge savings over what they would have paid in a pre-FinOps world.</li><li>Engineers deliver innovation at faster speeds.</li><li>Procurement has shifted to strategic sourcing and owning the relationship with the cloud provider.</li><li>No longer removed from the process, the finance team is a proactive partner who has become technically enabled and is focusing on unit economics.</li><li>And leadership is making intentional and frequent strategic choices among speed, quality, and cost</li></ol><h4><strong>FinOps Is Evolving</strong></h4><p>Over the past few years, what we call FinOps today has been evolving — and it will continue to evolve. As the cloud service providers offer more and more services and continue to offer different ways to optimize their platforms, FinOps will keep adapting.</p><h4><strong>What Is FinOps?</strong></h4><p>FinOps is not something that one person or company came up with; it’s a movement that evolved spontaneously, around the world, due to the environment created by on-demand cloud resources requiring a new management methodology.</p><p>In its simplest terms, FinOps brings financial accountability to the variable spend model of cloud. However, this description is flawed because it merely hints at the outcome.</p><h4><strong>Where Did FinOps Come From?</strong></h4><p>In the early days, companies were simply calling the practice “cloud cost management.” Later, “cloud cost optimization” began to take hold, although it didn’t speak to the allocation challenges of cloud. AWS and other cloud providers began using the phrase “cloud financial management,” a catch-all title that was eventually replaced by “FinOps.”</p><p>It is a cultural change and set of processes that has been — and likely will be — called other names. The definition of FinOps has evolved and broadened, but it has retained the all-important principles of driving a collaborative working relationship between teams, making iterative changes using data-driven insights, and improving unit economics.</p><p>The definition of DevOps from Gene Kim, author of The Phoenix Project: <em>The term “DevOps” typically refers to the emerging professional movement that advocates a collaborative working relationship between development and IT operations, resulting in the fast flow of planned work (i.e., high deploy rates) while simultaneously increasing the reliability, stability, resilience, and security of the production environment</em>.</p><p>A definition of FinOps based on Kim’s:</p><p><em>The term “FinOps” typically refers to the emerging professional movement that advocates a collaborative working relationship between DevOps and Finance, resulting in an iterative, data-driven management of infrastructure spending (i.e., lowering the unit economics of cloud) while simultaneously increasing the cost efficiency and, ultimately, the profitability of the cloud environment.</em></p><h4><strong>The Definition</strong></h4><ol><li>FinOps is the practice of bringing financial accountability to the variable spend model of cloud, enabling distributed teams to make business trade-offs between speed, cost, and quality.</li><li>At its core, FinOps is a cultural practice. It’s the most efficient way in the world for teams to manage their cloud costs, where everyone takes ownership of their cloud usage supported by a central best-practices group. Cross-functional teams work together to enable faster delivery, while at the same time gaining more financial and operational control.</li><li>FinOps is all about removing blockers; empowering engineering teams to deliver bet ter features, apps, and migrations faster; and enabling a cross-functional conversation about where to invest and when. Sometimes a business will decide to tighten the belt; sometimes it’ll decide to invest more. But now teams know why they’re making those decisions.</li></ol><p>Real-Time Reporting (The “Prius Effect”)</p><p>There are three parts to a successful FinOps practice: Real time reporting + just-in-time processes + teams working together = FinOps</p><p>You should provide engineers with feedback on the impacts of their actions as close as possible to the time those actions occur. This tends to create automatic behavioral changes for the better.</p><p>Using electric car analogy to explain the Prius Effect: When you put your foot down heavily on the pedal, the car’s display shows energy flowing out of the battery into the engine. When you lift your foot up, energy flows back into the battery. The feedback loop is obvious and instantaneous. You can see how the choice you’re making in the moment — one that in the past may have been unconscious — is impacting the amount of energy you’re using.</p><p>This real-time data-driven decision enablement is what FinOps delivers. In the data center world, engineers take individual actions that can’t easily be traced to their financial impact on the company.</p><p>FinOps is about helping the business make better decisions while moving more quickly. And it achieves this by forcing IT, finance, and business professionals to work together in unfamiliar ways.</p><p><strong>When Should You Start FinOps?</strong></p><p>Based on the information available on cost optimization in the open wide, many people believe that the right time to implement FinOps should be measured by the amount of their cloud spend. And this does make sense on some levels.</p><p>A successful FinOps practice doesn’t require sizeable cloud deployments or a multimillion-dollar cloud bill. <strong>Starting FinOps sooner will make it much easier for an organization to make more informed decisions about cloud spend, even as its operations scale.</strong> Therefore, it is essential to understand a FinOps concept we call <strong>Crawl, Walk, Run</strong>.</p><p>Despite the rich resource available, it is important to note that no organization can proceed directly from zero FinOps to perfectly efficient FinOps. Every organization and team must implement FinOps processes incrementally, taking the time to learn from each other as they go.</p><p>Like DevOps before it, FinOps is, ultimately, a cultural shift, and the earlier it starts, the sooner an organization can achieve successful cloud cost management. Do FinOps from day one, but you engage more of the processes as you scale up. There are typically two times when companies implement FinOps:</p><ol><li>The most common is when things go off the rails. In this scenario, spending hits a point where an executive forces a hard stop on cloud growth and demands that a new managing model be implemented. Despite it being the most common driver, this is not the ideal way to approach FinOps adoption. Innovation and migrations slow down — or even stop temporarily — during this executive fire drill.</li><li>The less common (and wiser) approach is taken by executives who have seen the cloud journey play out and aligns to the Crawl, Walk, Run model. The practice needs to develop at a pace that matches the company’s position in the FinOps maturity cycle.</li></ol><p>No matter how a company arrives at the decision to implement FinOps, the first critical step is to get visibility in a near-real-time manner, so everyone can see what’s happening and catch cost overruns before they become too large. While that visibility is being achieved, the FinOps teams start educating the entire business. As cross functional teams work together, finance people will learn more of the language of cloud, while engineers begin to grasp financial concepts.</p><h3>Starting with the End in Mind: Unit Economics</h3><p>One of the most important concepts in FinOps is unit economics. The idea is to measure cloud spend against a business metric (total revenue, shipments made, paid sub scribers, customer orders completed, etc.). Unit economics relies on almost every aspect of FinOps, including tagging, cost allocation, cost optimization, and FinOps operations. The business metric is important, because it allows you to change the conversation from one that is just about dollars spent to one about efficiency and the value of cloud spend. Being able to say “It costs $X to serve customers who bring in $Y in revenue” brings a context that helps you make the decision whether $X and $Y are reasonable for the organization. Then, as services evolve or change entirely with new features, companies are able to measure the impact of these changes via these business metrics. The result is companies that can determine the difference between good cloud spend and bad — and that trend those decisions over time.</p><p><strong>Cloud FinOps Book — </strong><a href="https://learning.oreilly.com/library/view/cloud-finops-2nd/9781492098348/"><strong>10-day Digital Access</strong></a><strong> provided by O’Reilly</strong></p><p><strong>Cloud FinOps Book — </strong><a href="https://www.amazon.com/Cloud-FinOps-J-R-Storment-ebook/dp/B0BSP52MHL/ref=tmm_kin_swatch_0?_encoding=UTF8&amp;dib_tag=se&amp;dib=eyJ2IjoiMSJ9.ehvywaGi1icWkg6FNWpXazkeMVDEcv_2feKLb0Qu1wIZZ6zxqkxadV6U82EzKg5YR2p8Nql7rLRkDqeQq1yMCf96RhrTxN2iw0H5ReGMvH7_ZciNw127tJn6mlq2-P8kE_R_VmzAOk8flmVSwjzPhA.46yxNTij4B6GF-4e7zodhAsyg4C2L38J6-0xQX2ySgE&amp;qid=1710524070&amp;sr=8-1"><strong>Amazon</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84456a7b5980" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Azure Savings Plan]]></title>
            <link>https://medium.com/@ibukunsamuel7/azure-savings-plan-d548d2f4529c?source=rss-7fb307ed6e1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d548d2f4529c</guid>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[azure-savings-plan]]></category>
            <category><![CDATA[finops]]></category>
            <category><![CDATA[cloud-cost-optimization]]></category>
            <dc:creator><![CDATA[Ibukunoluwa Samuel]]></dc:creator>
            <pubDate>Thu, 27 Nov 2025 16:23:10 GMT</pubDate>
            <atom:updated>2025-11-27T16:23:10.218Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5h06o8ixldLOXa1GURZo4w.png" /></figure><p>As more and more companies turn to the cloud for scalability and innovation, cloud spend has hit a tipping point causing cloud spend to impact profit and loss. Cloud service providers like Microsoft Azure provides 2 options to save on usage by committing for a fixed term. The decision to buy a savings option largely depend on the enterprise workload pattern. In this essay, I explored Azure Savings Plan (ASP) as a cost optimization strategy.</p><h3><strong>What is Azure savings plans for compute?</strong></h3><p>Azure savings plans enable cloud users to reduce eligible compute usage costs by making an hourly spend commitment for a period of 1 or 3-year. The savings can significantly reduce resource costs by up to 65% from PAYG prices.</p><p>ASP is a billing discount. This means it only cover the compute part aka infrastructure costs of a resource usage. It doesn’t cover software, networking, or storage charges. For instance, if you use windows VMs or SQL Database in the absence of Azure Hybrid benefit, monthly invoice will include cloud services software meters and windows software meters as the case may be.</p><p>You can buy ASP from the Azure portal or Savings plan API and pay up front or monthly. The total cost of upfront and monthly savings plans is the same. Monthly payment option simply divides the total cost of the savings plan into 12 or 36 equal payments.</p><p>When savings plan term expires, the billing discount expires, and the resources are billed at the pay-as-you go price. By default, the savings plans aren’t set to renew automatically. You can choose to enable automatic renewal of a savings plan by selecting the option in the renewal settings during the purchase experience of afterwards in the configuration tab.</p><h3><strong>Why should you consider ASP?</strong></h3><p>Buy savings plans when workloads are <strong>dynamic or evolving</strong> (as opposed to being stable), particularly if they use various instance families or compute services. ASP becomes desirable in the face of <strong>consistent compute spend but disparate resources</strong>. For example, if you consistently spend at least $3 every hour, but your usage comes from different resources and/or different datacenter regions. After purchase, in each hour, eligible compute usage is discounted until commitment amount is reached. After this threshold, resource usage is priced at PAYG rates and any unused commitment from any hour is lost.</p><p><strong>Point to note on ASP</strong></p><ol><li>A resource within the savings plan’s scope must generate the usage to be eligible for a savings plan benefit</li><li>Each hour’s benefit is use-it-or-lose-it and can’t be rolled over to another hour. Maximum utilization is recommended at all times</li><li>Benefit is first applied to the product that has the greatest savings plan discount when compared to the equivalent PAYG rate. This is called application prioritization and it’s done to ensure that the maximum benefit from savings plan investment is received.</li><li>A savings plan discount only applies to resources associated with Enterprise Agreement, Microsoft Partner Agreement, and Microsoft Customer Agreements. Resources that run in a subscription with other offer types don’t receive the discount. Azure users on legacy offer types have Microsoft Customer Agreements billing account created in the process of purchasing ASP.</li><li>Savings plan discounts are influenced by product and by commitment term (1- or 3-years).</li><li>Each hour, eligible compute usage (VM, App Service) within the benefit scope of the savings plan, up to commitment amount, is discounted and used to deplete the hourly commitment.</li><li>For usage covered by ASP, you no longer charged at the pay-as-you-go rates. However, usage charges above the commitment are billed at your on-demand rate.</li><li>There is no extra effort required from you after purchasing a savings plan, the benefit is applied automatically to all eligible compute usage that matches the savings plan scope.</li></ol><h3><strong>How are savings plan recommendation made?</strong></h3><p>Azure looks at hourly and total on-demand usage costs incurred from savings plan-eligible resources in the last 7, 30, and 60 days to generate the most cost-effective commitment recommendation. The recommendations are generated using actual on-demand and costs (including any negotiated on-demand discounts). Commitment recommendations are found in Azure advisor, the savings plan purchase experience in the Azure portal and benefit recommendation APIs.</p><p><strong>Points to note about recommendations</strong></p><ol><li>Recommendations are refreshed several times a day</li><li>The savings plan recommendation for a specific scope is reduced on the same day that you purchase a savings plan for that scope. However, updates to recommendations for other scopes can take up to 25 days.</li><li>Recommendations in Advisor currently only consider last 30days of usage.</li><li>A recently purchased savings plan or reserved instance may take up to 5days for the purchases to affect recommendations in advisor and azure portal.</li></ol><h3><strong>Reservation trade-in</strong></h3><p>Savings plan purchases are final. After purchase, by design, they can’t be cancelled or exchanged for reservation. What is supported is the trade-in of selected Azure reservations for a new savings plan.</p><p>When you trade in VM reservations for a savings plan, the reservation is cancelled, a pro-rated refund for them is issued, any future payments are also cancelled. Thereafter, a new savings plan is purchased.</p><p>Apart from Azure Virtual Machines, Dedicated Hosts , or Azure App Service reservations, no other reservations, or prepurchase plans are eligible for trade-in. You can trade in your reservation from Azure portal.</p><h3><strong>Savings plan scopes</strong></h3><p>While applying savings plan benefit to usage, savings plans are processed in an ordered scope. A scope refers to where the benefit applies:</p><ol><li>Resource group scope: ASP scoped to a RG applies benefit to eligible resources in the selected RG</li><li>Subscription scope: applies benefit to eligible resources in the selected subscription.</li><li>Management group: applies benefits to eligible resources from all subscriptions that are in both: the management group and the same Enrollment/Billing Profile as the subscription used to purchase the benefit</li><li>Shared scope: applies benefits to eligible resources within subscriptions that are in the EA Enrollment or MCA Billing Profile.</li></ol><p>Rescoping a savings plan after purchase is not a commercial transaction. Hence after purchase, in the configuration tab, scope can be updated.</p><p><strong>Decide between a savings plan and a reservation</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5h06o8ixldLOXa1GURZo4w.png" /></figure><p><strong>Buy a savings plan in the Azure portal</strong></p><ol><li>Sign in to the Azure portal.</li><li>In the Search area, enter Savings plans. Then select Savings plans.</li><li>Select Add to purchase a new savings plan.</li><li>Complete all the required fields:</li></ol><p>a. Name: Friendly name for the new savings plan.</p><p>b. Billing subscription: Subscription used to pay for the savings plan. The payment instrument of this subscription is used in ASP purchase.</p><p>c. Apply to any eligible resource: Scope of resources that are eligible for savings plan benefits.</p><p>d. Term length: One year or three years.</p><p>e. Hourly commitment: Amount available through the plan each hour. In the Azure portal, up to 10 recommendations might appear. Recommendations are scope specific. Each recommendation includes:</p><p>i. An hourly commitment.</p><p>ii. The potential savings percentage compared to on-demand costs for the commitment.</p><p>iii. The percentage of the selected scopes compute usage that is covered by the new savings plan. It includes the commitment amount plus any other previously purchased savings plan or reservation.</p><p>f. Billing frequency: All upfront or Monthly. The total cost of the savings plan is the same regardless of the selected frequency.</p><p>g. Auto-renew: On or Off. The savings plan will automatically renew at the end of its term if it is On. By default, this option is set to Off.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d548d2f4529c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[African Tech Conference]]></title>
            <link>https://medium.com/@ibukunsamuel7/african-tech-conference-31d8b296d430?source=rss-7fb307ed6e1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/31d8b296d430</guid>
            <category><![CDATA[lagos]]></category>
            <category><![CDATA[moonshots]]></category>
            <category><![CDATA[tech-cabal]]></category>
            <category><![CDATA[tech-conference]]></category>
            <dc:creator><![CDATA[Ibukunoluwa Samuel]]></dc:creator>
            <pubDate>Sat, 15 Nov 2025 10:50:38 GMT</pubDate>
            <atom:updated>2025-11-15T10:50:38.238Z</atom:updated>
            <content:encoded><![CDATA[<h4>Moonshot by Techcabal</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*upINXywL4BETr-u-sENMtg.jpeg" /></figure><h3>High-level view</h3><p>Moonshot by Techcabal is a multi-stage conference targeted at a range of audience whose interest or stake borders: Future of Commerce, Creative Economy, Entering Tech/ Emerging Tech, Clean &amp; Climate Tech, Big Tech &amp; Enterprise, Startup, Government &amp; Policy, Investor, Deal, Round etc. These tracks are the coverage, article or essay you would find on the techcabal’s site. The conference is easily a physical extension of its journalism business and stages were curated to mirror that. Each day had a packed schedule to deliver between 9am-6pm with 1hour lunch time.</p><p>Each day had a theme and conversations in the sessions aligned accordingly. A person who does not want the whole conference experience, may come on a selected day for the sessions that matters to them. While Technical Workshop, Fuel: The Investor Conference and Roundtable Room had the same use on both days, other stages were repurposed for the day’s theme. This was not immediately clear and it took a merry-go-round; the stage for emerging tech on day one was on day two, entering tech. The startup stage on day one was creative stage on day two. Early reservations was though the map says future stage, at the door, it is emerging tech stage on day one and entering tech stage on day two.</p><p>The main stage, as the name implies is the largest stage at the conference. It is the central point where conversation started by way of keynote and opening speech and ended i.e. closing speech and vote of thanks on the last day. Whatever stage you find yourself, there is something happening, you may not like it and you are at liberty to shop around for the next one. The main stage was allocated to conversations on big tech, enterprise audience and partner/sponsor pitches.</p><p>Due to the independence of each stage coupled with the constraint of time and availability, it might be helpful to note sessions of interest ahead while leaving room for uncontrollable lags, exhibition booth tour, networking, and casual exchange with the next-seat person or pre-planned chat with your fav. My take away would be; strict with time, swift to run, but flexible to accommodate. One of the things to settle with is that one can’t be in all the sessions and that is what I described as availability. The session where someone whose work you admire could conflict with a promising topic happening 10minutes into a technical workshop that will wrap up in 15mins on the creative economy stage; not to forget the main stage where a session on what it takes to build and scale in Africa will start in 5mins. The hard work lies in maximizing whatever session you are while wading off the thought of dashing out of the room mid-way to another because of FOMO. Figuring out what matters and being in that room; moving quickly to a new room where necessary and hopefully, they don’t tell you they are out of headset and seats.</p><h3>Technical Workshop</h3><p>This didn’t turn out as advertised. What I found on day one was a panel session and what is best described as a product presentation by one of CSP solution partner. When you hear technical workshop, what comes to mind is followed along demonstration or maybe even some live coding but that was not exactly the case.</p><h3>Post conference activity.</h3><p>On each day, there was a mixer, a perk included in non-regular ticket. I heard it was the place where conversations continued and networking peaked over finger food and drinks.</p><p>On each stage, there is a line-up of agenda (a little too much if I were asked) that had to be presented by 6pm. Through nobody’s fault, the conversation went past allotted time. Someone’s last word might leave no room for further questions from the audience. The commemorative picture time may take longer than necessary thus managing the time against a published agenda becomes real work. There were sessions I wished had more time but there is a lineup of speakers and moderators waiting to climb the stage for marketing, visibility, insights or whatever purpose. It’s a production, and it had to keep rolling. To put it mildly, time is a currency and it counts down fast.</p><p>Suddenly, the 10mins, 15mins, 20mins, 30mins weren’t sufficient. There were sessions, whose time elapsed while I was still settling into the room let alone grasp the topic of discourse. Not to mention the throng you got to push through in the hallway to get through the next room/stage. You are conflicted between hurrying to be seated for a session that will end in 15ims or stopping mid-way for a chat or networking. For this one, you have got to get priority right and drown any though of missing out on what is happening in another room to enable you settle in and get the most out of the one where you are.</p><h3>Exhibition</h3><p>A real time marketplace. Literally everyone had a booth. While some were lined up along the hallway, a whole lot were concentrated in a room sandwiched between the main stage and creative/startup stage. What is a conference without one after all? I mean, where are you are going to get merch, freebies and oversized t-shirt. A large room was allocated for the exhibitors; arguably a major part of the conference. I stopped by some booth to chat and was left inspired by the sight of daring men and women building technology enabled solutions/services/products for a piece of the billion-dollar African market.</p><p>You may want to bring along a backpack to stuff the branded freebies if you like that sort of thing. Some exhibitor want you to sign up or get your commitment in exchange for pen, cup etc. but feel free to shop around. I remember seeing a booth with some sort of arcade game. Someone even said they shared money or won money at a booth. While I can’t very their claim, one thing is clear, the exhibitors came -ready! From the deep=pocketed industry players serving bourgeois experience to the subtle new-comer who’s trying to conserve runway. Some exhibitors clinched bigger booth than others. From stylishly roomy space with lounge chairs to desk and chair setup. Being in a room alive with such energy and ambitious chatters; I tell you, days after the conference, you could replay it, vividly. From the fellow helping to insure luxury and priced collections (but they are not an insurance company) to the payment solution for cloud services, the security company, trans-mobility, the crypto product solutions etc. There is someone at every booth eager to thrust you a handbill or engage you about the finest feature. It is one endless sea of solutions by Africans for Africans.</p><h3>The sessions</h3><p>Getting audience with a speaker after their presentation or session is a calculated move not just because there are several others making the same move, but they are quick to escape into an inner room away from the preying eyes. I sat through and enjoyed sessions from:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/882/1*tO5KBsl269IYY_-8v-e4pg.png" /></figure><p>The event kicked off at the main stage on day 1 with the Opening Speech and closed there on day 2 with Closing remarks and Vote of Thanks.</p><h3>Observations/ general note</h3><ol><li>Branded t-shirt are still a great marketing tool. Think about the hundreds of people that will see you as you move about. It is not just people who paid for a booth that wore them, I noticed people deliberately wore them with call to action (QR code, a link, a logo or a name).</li><li>The rooms were packed and the hallway could barely contain the happy feet of participants who were posing for a photo, making connection or rushing to a session. Colorful backdrop, lights, camera, conversations, there was something for everyone. It might take a moment for the dust to settle and get your bearing. A tech conference with many moving parts. You would require a purpose and strict scheduling to make the most of it.</li><li>I recommend early arrival to avoid being caught in the check-in queue, I recall seeing what appears to be a queue snaking through the front of the convention center at midday when I arrived. Check-in was quick for me but may not be for everybody. A staff of the event management company flashed my mobile phone displaying a QR code in front of what appears to be an electronic scanner then I went to the next desk where I was handed a paper bag containing a notebook, pen, stickers and tag.</li><li>The conference was in full swing by the time I arrived at noon. From the Check-in desk, I stepped into a tunnel adorned on both sides by signage and decor boldly announcing the conference and its lineup of sponsors and partners. The tunnel, from floor to ceiling doubles as publicity and versatile photo booth for the conference sassy participants eager to pose and post. I soon got to understand the disclaimer on the website stating by attending the event, you consent to your images being taken and used in promotional materials. Naively, I was unprepared for an overwhelming number of camera in my face.</li><li>Considering you need internet to navigate the conference, connection was spotty in some part but organizers provided Wi-Fi for the 2 days.</li><li>The period leading to the conference are equally important as the conference itself, and for one as packed as this, days after reserved for recovering and chasing down conference lead and joining an offshoot events. There are several of them; officially and unofficially.</li><li>Conference schedule was managed by a legacy app called Whova. Besides event schedules, it sort of a fine mix of LinkedIn and Twitter for event participants. I used it to pre-plan for sessions, speakers, moderator, time etc. It’s a community building app and an informal marketplace for reunion, lost and found etc. The app is central to the event side-by-side those newsletters from the organizers leading up to the day.</li><li>There were many things happening at the same time in different places sometimes conflicting or competing. One has to have a purpose and strictly know what matters.</li><li>Right in the middle of the hallway was a map, you would find helpful. The map is also accessible from the event management app. the ushers were also helpful in pointing to the right places.</li><li>Breakfast was served but it finishes fast. Fascinating scenes of bold fashion choices. It’s wide-legged pants season and the runway of moonshot was sufficiently graced.</li><li>The event hosts were full of life and jolly.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31d8b296d430" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Idanre Hills]]></title>
            <link>https://medium.com/@ibukunsamuel7/idanre-hills-55ffa1915829?source=rss-7fb307ed6e1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/55ffa1915829</guid>
            <category><![CDATA[akure]]></category>
            <category><![CDATA[idanre-hills]]></category>
            <category><![CDATA[hike]]></category>
            <category><![CDATA[nigeria]]></category>
            <dc:creator><![CDATA[Ibukunoluwa Samuel]]></dc:creator>
            <pubDate>Mon, 09 Sep 2024 20:04:44 GMT</pubDate>
            <atom:updated>2024-09-09T20:21:32.194Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LEcpbB9cL54SJwE3m4eQXA.jpeg" /></figure><p>I’ve visited several tourist sites in Nigeria, including going on a safari in <a href="https://medium.com/@ibukunsamuel7/summer-getaway-yankari-game-reserve-bauchi-state-nigeria-b5a217c8dd11">Yankari Game Reserve</a>, chasing the layered <a href="https://medium.com/@ibukunsamuel7/what-to-do-on-a-2-day-trip-in-osogbo-osun-state-nigeria-26442017a7d8">waterfalls of Erin Ijesha</a>, and enjoying the panoramic view of Abeokuta from the<a href="https://medium.com/@ibukunsamuel7/olumo-rock-abeokuta-02e21e251a2d"> top of Olumo Rock</a>. However, none of these experiences compare to hiking Idanre Hills.</p><p>The decision to go on any road trip start as subtly, followed by researching the destination, ensuring I have enough supplies for the road then I inform family and friends. While preparing for this trip, there were concerns around security and the state of the nation. In addition, rising fuel cost accompanied by shortage of supply raise questions about whether sightseeing is worth the risks and troubles. It also raises the question of whether it should be a priority. At this time, it seems rather unusual for anyone to pack their bags and travel several kilometers away from the comfort of home just to see a new place — just like that. Overcoming these concerns, however valid, determines whether a trip becomes a reality or remains just a noble idea. There will never be a better time to do something than the moment you decide to rise up and do it, as long as you do so with awareness and full preparedness.</p><p>On the departure date, I arrived at the park hoping to board the first bus but by 7:20am, what appeared to be the first bus was filled up and getting ready to drive out. Being the 2nd person on the next available bus, I endured a 2 hour wait entertained by the views and scenes from the morning rush while more people arrived.</p><p>Three mobile preachers came to teach and pray. Women with trays balanced diligently on their head parade the bus in turns (sometimes concurrently) to call out items from their wares; bread, biscuit, minerals (soft drinks), POS. A woman adorned in white clothing that has undoubtedly been marinated in blue dye (aro) and an accessory typical of a traditional worshipper came along jiggling a piece of metal for a brief performance. A dark man selling herbal mixtures in a bottle, advertised the capabilities and sang testimonies of it; that it cures literally every disease. He carefully worded the composition of the mixture, prescription and praises of the Akure People into his lines and delivered the presentation with the rhythm and accuracy of a telemarketer. I found the act fascinating, and he eagerly took my curiosity for interest because he waved the bottle, vigorously, in my direction.</p><p>During the wait, I collected a sports newspaper from one of the men waiting on the bus. I can’t remember the last time I held one of those in my hands. Large margins filled with columns of letters so tiny and distributed they spilled easily into each other. I glanced through the headlines on the front page and read about Pep gifting Manchester City’s support staff before he came to retrieve it.</p><p>At 09:23 am the bus finally drove out of the park and this woman said a specific prayer request in respect to the journey in Yoruba. I paid 8000 naira each for a return journey.</p><p>Shortly after departure, we found ourselves in a slowly moving traffic and I chided myself again for missing the first bus. As a result of the ongoing fuel scarcity, there was a queue of vehicles waiting to get served from the filling stations spilled outside taking up a lane of the narrow road leading to the express.</p><p>The journey to Akure via Benin-Sagamu expressway is estimated at 4 hr. 47 min (296 km) but pockets of poor road and several police checkpoints made the journey even longer. The checkpoints are usually quick moments of handshake between the driver and armed member of the force. Delighted hawkers took advantage of either the brief exchange or the poor road (sometimes both) to sell water, plantain chips, kolanut, groundnut, boli (in traffic!?), walnut, energy drink etc.</p><p>I stayed wide awake throughout the trip even though I had expected to doze off from the start. We traveled all morning and only arrived at Ondo Garage in Akure at about 4pm. On the return journey, it took less than that. I would say improved vehicle and minimal delays.</p><p>Once the long road trip was over, it was easy to settle into my host city. Signature cabs dubbed in blue-yellow color and tricycle plied selected routes, but it became apparent that motorcycle is the primary medium of transportation; they not only flooded the roads, but they also made the suburbs accessible. The price of a Bike ride ranges from 200–700 naira depending on the distance.</p><p>The use of POS is ultimately how financial transactions get done. In Akure, it is a common occurrence to visit ATM points with no luck in getting cash. Fueled by the disappointment and unreliability, people turned to and now heavily rely on POS vendors- whose presence greatly outnumber the Banks and ATM points. In the remote town of Idanre where there is almost no physical bank presence, POS vendors have become the last resort.</p><p>Once I got in, it was easy to forget the hustling and bursting I just left behind. Time moved slowly, maybe I turned in early or it was simply the character of the new city I found myself in.</p><p>I recommend checking the weather before setting out for the outdoors. It’s the rainy season in Nigeria and while some states have clear skies, Ondo State at this time still witnessed non-stop rain.</p><p>For a road trip and hiking experience, the under listed items are essential:</p><ul><li>Hiking shoes (emphasis on the sole; ensure it has a firm grip)</li><li>Because it rained during my visit, a waterproof shoe is recommended.</li><li>Nose mask and hand sanitizer (handy while using public transportation)</li><li>Your hiking bag (if you must carry one) must be light. Nobody needs the extra load, but you may want to keep your personal effect. I took a tote bag which was not much use. If you must use a carry-on, ensure it is light.</li><li>Phone for the camera and map</li><li>Cash</li><li>Items of clothing. Something light for ease of movement and some colors to make the photos pop. At this time of the year, my red ankara kimono paired with a blue jean complimented the surrounding greenery.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CZi0gLDl3vxPuxnjBC_y2Q.jpeg" /></figure><p>Besides the transportation and picking a coordinated fashion piece, another item to plan around is accommodation. Idanre Resort can be accessed easily either from Akure or Ondo Town; feel free to lodge in any of these places. The hike was immersive even for a rainy day hence, you want to arrive the resort at such time that is not too early but not too late to accommodate the fact you are on holiday.</p><p>Idanre Resort, home to the tourist site of interest is a 40 minute drive from Akure. It took a disappointing ride to another location to validate that Idanre Motor Park is located at Oke Aro. I would later understand that depending on the time of the day, there are informal (read roadside) loading points in other parts of Akure but the park at Oke Aro is reliable.</p><p>Upon arriving at Oke Aro Garage, a blue-yellow cab was ready and quickly filled up. It made the most of every bit of space, seating four people in the back and two in the front, with each seat costing 1200 naira. Music floated gently from the stereo, filling the air as the driver navigated closer to the hillside on the single-lane road leading to Idanre. I recognized the voice of Orlando Owoh, a popular Nigerian highlife musician. Singing along to the chorus, I wondered, could this trip be any more quintessentially southwest?</p><p>As we drove closer to Idanre, it was impossible to miss the undulating mountains shrouded in clouds, forming a natural wall around the dense forests of southwest Nigeria. Their heights were truly enormous, and the view was an escape.</p><p><strong>Idanre Resort</strong></p><p>A black gate opens widely into the resort, where a large tree stands in the middle of the yard, providing shade. I walked past the open gate without noticing the signboards or realizing that we had arrived at the destination. A larger sign announcing arrival at the resort would be great.</p><p>Two men greeted us warmly upon arrival. While we exchanged pleasantries, I took in the surrounding environment. I quickly realized the resort is insufficiently funded and lacks an organized management structure. It’s evident that the resort’s glory days are well behind it, given its current underwhelming state. While the hills and mountains remain an inherent feature of the town, the ambiance and other elements that once made the site a tourist attraction are long gone. The house overlooking the gate has lost its roof, and the yearly rainfall further damages the termite-ridden wood, causing it to give way gradually. I looked through the broken window to see a makeshift stage on one end and a tennis table sat in the middle of the ruin. You can tell the building was intended for a purpose; a recreational center maybe unfortunately, the remains of raffia bamboo and carved wood used to adorn it were all that was left.</p><p>In my opinion, the resort could use some investment, or perhaps someone attempted sometimes long ago, but there was no continued support. The bushes near the reception conveniently obscure the molded letters, which I believe read “Welcome to Idanre Resort” or something similar, as parts of the letters have fallen off.</p><p>The resort receives tourist, and the locals also use the site for farming activities and traditional festivals. One would expect the bushes near the steps and footpath to be lawn especially during the rainy season to open up the road for safe navigation but clearly, that is not anyone’s priority.</p><p>The two men at the reception took turns to engage us about the cost of visiting the resort. A registration fee of 1000 naira per adult paid to a registrar who at 12pm was not available but promised to be by the time we returned from sightseeing. She would later come in on a motorcycle before we set off. A tour service fee is also imposed. They won’t accept bank transfers at first and were quick to show me a nearby POS vendor.</p><p>I remember the tour guides at Olumo rock negotiating with tourists at the end of the climb for a tip. At Idanre Resort, they added it to the cost breakdown and had to be settled before takeoff. At first no specific amount was mentioned because they branded it as anything to thank the tour guide who will walk us up the hill and show us around the forest. This opened up a negotiation with the tour guide who boasted about a good job he was set to do and an adventurous experience he was going to deliver. We later settled for a price. I and Bamidele were the tourists on ground but thankfully, a dad and son combo arrived making it a party of 5 including Mr. Gbenga, our tour guide.</p><p>We started off the hike amidst rainfall The consequence of the rain was that it afforded us cool weather during the hike but at the cost of a muddy path which was difficult to navigate.</p><p>We began the climb up the 600+ concrete steps after a quick orientation by the guide. The step is made of 5 resting points leading up to the ancient town. Each climb takes us farther away from the town. It wasn’t until the 3rd resting point before, we began getting some elevated view of the town miles below.</p><p>Due to the rain, we made use of the resting point a lot to both catch our breath and as a shed from the downpour. We pushed further, often ignoring the rain while the guide told stories associated with each landmark.</p><p>The 600+ steps deliver tourists to a footpath to access the ancient town thus making it a 2-part journey. The ancient town is at best the remains of primitive lifestyle and cultural heritage which the people still revere and appreciate. While some structures and landmarks in the ancient town now lay in ruins, I understand from the tour guide that the township come up to observe traditional rites. It is not out of place to see litters everywhere, a testament to human activity and farm work.</p><p>During the hike, we were treated to a scenic view of southwest forest, tall, majestic trees like the baobab, wild plants, spring water, and mesmeric sight of the smoking mountains kissing the cloud in the distance. We took pictures as we walked by.</p><p>The ancient town and its components were accessed, we saw the oldest and first primary school is now overgrown with tall bushes, leaving only the roof visible, the cave-like entrance to the ancient town dubbed <em>ese o gbeji</em> and security measures adopted by the locals, the prison, market square, courthouse and mausoleum. We continued walking the footpath around the ancient town while the guide pointed out the remains of the shelter that housed the chiefs right up to the King’s elaborate courtyard. We saw the stone that was once used as a test of manhood before civilization. Located in the heart of the ancient town, men of marriageable age would take turns lifting the stone to their chest to prove their readiness for marriage.</p><p>By the time we wrapped up at the king’s courtyard, it had stopped drizzling, and the hills were accessible for a climb. We walked to the base of a hill that would deliver us to a short exit instead of going by a longer route to exit the ancient town.</p><p>Supported by our experienced tour guide, we took turns to climb the hill, an act so scary it became the highlight of the entire adventure. For me, I was unsure of my shoe sole as such whilst the guide yelled out instructions, I laid on my chest and crawled-climbed my way uphill.</p><p>Each stop, more laborious than the last. Climbing the hill was even more physical and strenuous than the steps. Gosh, it happened so fast, and I remember fighting hard to lift my weight up to grab anything. Thankfully, we all made it and so began the descent. This was nothing like any of the other places I have been. Even when I walked the Savanna and saw wild animals from a distance in Bauchi, I maintained my composure throughout.</p><p>I had a moment of `wetin carry me come here` at times when we had to jump down an elevated ground, dodge muddy grounds and watch for a safe landing. There were exciting times, but I can’t say climbing hills was my favorite part.</p><p>I would say the hike took about 3 hours; it was easy to lose track of time up there. Probably not up to that on a day with clear skies.</p><p>The hike downhill was uneventful. Each one preoccupied with the thought of the past 3 hours and walking briskly to the nearest shelter because it has started raining again. The tour guide leading the pack, told stories of tourists he worked with who wore heels and ended up walking barefooted.</p><p>Back at the resort, there were more cars than we left, and a new pack was waiting to begin their adventure. The registrar was also ready to collect our details in her notebook with no receipt or evidence of payment.</p><p>We made our way to Akure Garage where we took a cab to Akure at the rate of 1000 each.</p><p><em>Big shout out to Raizo, for taking time to edit this story.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55ffa1915829" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>