There are many ways to update multiple records of a dynamics CRM entity, in this blog let’s see one of the easiest and faster way to do it that is by using excel online.  Let’s consider an example, let’s say you have a fixed number of account records and you manually want to update the account number.  Step 1: Go to the entity’s home page who’s records you want to update.  Step 2: On the All-Accounts view (or any view) clicks on edit columns and add the columns as which you want to update in my case it is Account Number.  Step 2 : Once your view is ready click on Export to Excel Button on the top left and select Open in excel online.  Step 3:  This will open all your accounts in an excel sheet in a pop-up window.  Step 4: Now you just need to update the columns which you want to update and hit save (I am adding all the account numbers).  Step 6: You will get a Popup about your data being submitted for import, hit Track Progress.  Step 7: You will see your data has been submitted for updating and is parsing. (It will take couple of minutes to hours depending upon the amount of data you have submitted keep refreshing to see the progress of the records).  Step 8: Once the import job is completed you will see how many records were created successfully and how many failed or partially failed. You can open the import job and check failed entries, correct the entries and re-import (All my reports where successfully updates)  Failed records (Sample from some older imports)  All the successfully parsed records will be updated in your system.  Before Update:   After Update:   Hope this helps! 😊  I Hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudFronts.com.

Working with Microsoft Dataverse Connector in Power BI is usually straightforward—until you encounter a table that simply refuses to load any rows, even though the data clearly exists in the environment. This happens especially with hidden, virtual, or system-driven tables (e.g. msdyn_businessclosure, msdyn_scheduleboardsetting) which are commonly used in Field Service and Scheduling scenarios. Before jumping to a workaround, it’s important to understand why certain Dataverse tables don’t load in Power BI, what causes this behavior, and why the standard Dataverse connector may legitimately return zero rows. Causes – 1] The Table Is a Virtual or System Table with Restricted AccessSystem-managed Dataverse tables like msdyn_businessclosure are not exposed to the Dataverse connector because they support internal scheduling and platform functions. 2] No Records Exist in the Root Business Unit Data owned by child business units is not visible to Power BI accounts associated with a different BU, resulting in zero rows returned. 3] The Table Is Not Included in the Standard Dataverse Connector Some solution-driven or non-standard tables are omitted from the Dataverse connector’s supported list, so Power BI cannot load them. Solution: Export Dataverse Data Using Power Automate + Excel Sync Since Power BI can read:-> OneDrive-hosted files-> Excel files-> SharePoint-hosted spreadsheets …a suitable workaround is to extract the restricted Dataverse table into Excel using a scheduled (When the records are few) / Dataverse triggered (When there are many records and you only want a single one, to avoid pagination) Power Automate flow. What it can do –-> Power Automate can access system-driven tables.-> Excel files in SharePoint can be refreshed by Power BI Service.-> we can bypass connector restrictions entirely.-> The method works even if entities have hidden metadata or internal platform logic. This ensures:-> Consistent refresh cycles-> Full visibility of all table rows-> No dependency on Dataverse connector limitations Use case I needed to use the Business Closures table (Dataverse entity: msdyn_businessclosure) for a few calculations and visuals in a Power BI report. However, when I imported it through the Dataverse Connector, the table consistently showed zero records, even though the data was clearly present inside Dynamics 365. There are 2 reasons possible for this –1] It is a System/Platform Tablemsdyn_businessclosure is a system-managed scheduling table, and system tables are often hidden from external connectors, causing Power BI to return no data. 2] The Table Is Not Included in “Standard Tables” Exposed to Power BIMany internal Field Service and scheduling entities are excluded from the Dataverse connector’s metadata, so Power BI cannot retrieve their rows even if they exist. So here, we would fetch the records via “Listing” in Power automate and write to an excel file to bypass the limitations that hinder the exposure of that data; without compromising on user privileges, or system roles; we can also control or filter the rows being referred directly at source before reaching PBI Report. Automation steps – 1] Select a suitable trigger to fetch the rows of that entity (Recurring or Dataverse, whichever is suitable). 2] List the rows from the entity (Sort/Filter/Select/Expand as necessary). 3] Perform a specific logic (e.g. clearing the existing rows, etc.) on the excel file where the data would be written to. 4] For each row in the Dataverse entity, select a primary key (e.g. the GUID), provide the path to the particular excel file (e.g. SharePoint -> Location -> Document Library -> File Name -> Sheet or Table in the Excel File), & assign the dynamic values of each row to the columns in the excel file. 5] Once this is done, import it to the PBI Report by using suitable Power Query Logic in the Advanced Editor as follows – -> a) Loading an Excel File from SharePoint Using Web.Contents() – Source = Excel.Workbook(Web.Contents(“https://<domain>.sharepoint.com/sites/<Location>/Business%20Closures/msdyn_businessclosures.xlsx”),null,true), What this step does: -> Uses Web.Contents() to access an Excel file stored in SharePoint Online.-> The URL points directly to the Excel file msdyn_businessclosures.xlsx inside the SharePoint site.-> Excel.Workbook() then reads the file and returns a structured object containing:All sheets, Tables, Named ranges Parameters used: null → No custom options (e.g., column detection rules)true → Indicates the file has headers (first row contains column names) -> b) Extracting a Table Named “Table1” from the Workbook – msdyn_businessclosures_Sheet = Source{[Item=”Table1″, Kind=”Table”]}[Data], This would search inside the Source object (which includes all workbook elements), and look specifically for an element where: Item = “Table1” → the name of the table in the Excel fileKind = “Table” → ensures it selects a table, not a sheet with the same name & would extract only the Data portion of that table. As a result, we get Power Query table containing the exact contents of Table1 inside the Excel workbook, to which we can further apply our logic filter, clean, etc. To conclude, when Dataverse tables refuse to load through the Power BI Dataverse Connector—especially system-driven entities like msdyn_businessclosure—the issue is usually rooted in platform-level restrictions, connector limitations, or hidden metadata. Instead of modifying these constraints, offloading the data through Power Automate → Excel → Power BI provides a controlled, reliable, and connector-independent integration path. By automating the extraction of Dataverse rows into an Excel file stored in SharePoint or OneDrive, you ensure: This method is simple to build, stable to maintain, and flexible enough to adapt to any Dataverse table -whether standard, custom, or system-managed. For scenarios where Power BI needs insights from hidden or restricted Dataverse tables, this approach remains one of the most practical and dependable solutions. I Hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudFronts.com.

The Integration Shift No Enterprise Can Ignore For more than a decade, legacy 3rd-party integration platforms served as the backbone of enterprise operations. But in a world being redefined by AI, cloud-native systems, and real-time data, these platforms are no longer keeping pace. Across industries, CIOs and digital leaders are facing the same reality: What was once a dependable foundation has now become a barrier to modern transformation. This is why enterprises around the world are accelerating the shift to Azure Integration Services (AIS) a cloud-native, modular, and future-ready integration backbone. From our field experience including the recent large-scale migration from TIBCO for Tinius Olsen one message is clear: Modernizing integration is not an IT upgrade. It is a business modernization initiative. 1. Why Integration Modernization Is Now a Business Imperative Digital systems are more distributed than ever. AI and automation are accelerating. Data volumes have exploded. Customers expect real-time experiences. Yet legacy middleware platforms were built for a world before: The challenges CIOs consistently report include: • Escalating licensing & maintenance costs: Annual renewals, hardware provisioning, and forced upgrades drain budgets. • Limited elasticity: Legacy platforms require you to over-provision capacity “just in case,” increasing cost and reducing efficiency. • Rigid, code-heavy orchestration: Every enhancement takes longer, requiring specialized skills. • Poor monitoring and operational visibility: Teams struggle to troubleshoot issues quickly due to decentralized logs. • Slow deployment cycles: Innovation slows down because integration becomes the bottleneck. This is why the modernization conversation has moved from “Should we?” to “How soon can we?”. 2. Why Azure Is Becoming the Digital Backbone for Modern Enterprises Azure Integration Services brings together a powerful suite of cloud-native capabilities: This is not a one-to-one replacement for middleware. It is an entirely new integration architecture built for the future. 3. What We Learned from the TIBCO → Azure Migration Journey Across the Tinius Olsen modernization project and similar enterprise engagements, six clear lessons emerged. 1. Cost Optimization Is Real and Immediate Moving to Azure shifts integration from a heavy fixed-cost model to a lightweight consumption model. Clients consistently see: Integration becomes a value driver not a cost burden. 2. Elastic Scalability Gives Confidence During Peak Loads Legacy platforms require expensive over-provisioning. Azure scales automatically depending on demand. The result: Scalability stops being a constraint and becomes an advantage. 3. Observability Becomes a Competitive Advantage Azure’s built-in monitoring ecosystem dramatically changes operational visibility: Tasks that once required hours of log investigations now take minutes.Root-cause analysis speeds up, uptime improves, and teams can proactively govern critical workflows. 4. Developer Experience Improves Significantly Modern integration requires both: Azure enables both through Logic Apps + Functions, enabling teams to build integrations: Developers can finally innovate instead of wrestling with legacy tooling. 5. The Platform Becomes AI- and Data-Ready Migration to Azure doesn’t just replace middleware.It unlocks new modernization pathways: The integration layer becomes a strategic enabler for enterprise-wide transformation. 6. The Strategic Message for CIOs and Digital Leaders Modernizing integration is not simply about technology replacement. It is about: In short: It is about building a future-ready enterprise. Modernizing Integration Is No Longer Optional The next decade will be defined by AI-driven systems, composable applications, and hyper automation.Legacy integration platforms were not built for this future, Azure is. Enterprises that modernize their integration layer today will be the ones that innovate faster, scale smarter, and operate more efficiently tomorrow. Read the Microsoft-published case study:CloudFronts Modernizes Tinius Olsen with Microsoft Dynamics 365 Talk to a Cloud ArchitectDiscuss your integration modernization roadmap in a 1:1 strategy session. I Hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudFronts.com.

If you’ve been building reports in Power BI for a while, you’ve probably come across two features that sound similar but behave very differently: Drill-Through and Drill-Down. Many new users—even experienced ones, often get confused about when to use each option. Think of it like this: Both features are powerful, both help users understand data better, and both can make your reports feel more interactive. In this blog, I’ll break them down in the simplest way possible—what they are, how they work, and when to pick one over the other. When to Use Drill-ThroughUse it when: Think of Drill-Through as going from a “summary dashboard” to a “deep dive report.” Source: Microsoft A simple way to remember:Drill-Down stays in the chart. Drill-Through takes you to another page. Drill-Down vs. Drill-Through: Quick Comparison Table Feature Best Used For Where It Happens User Action Drill-Down Exploring hierarchies Inside the same visual Click on drill icons Drill-Through Opening detailed pages Across pages Right-click → Drill Through Real-World Examples 1.Drill-Down Example A sales manager wants to look at Yearly Sales, then break it down by Quarter, then by Month.No page changes, just clicking inside the same visual. 2. Drill-Through Example A CEO wants to know why a specific customer’s revenue dropped.Right-click → “Customer Details Page” → All insights in one place. To conclude, both Drill-Down and Drill-Through help users explore data, but they solve different problems. By choosing the right feature at the right time, you make your Power BI reports not only interactive, but also intuitive and enjoyable for your audience. I Hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com.

Many growing companies work with multiple legal entities. Each month, they exchange bills, services, or goods between companies. Doing this manually often leads to delays and mistakes. Microsoft Dynamics 365 Business Central helps fix that through Intercompany Automation. This feature lets you post one entry in a company, and the system automatically creates the same transaction in the other company. Let’s see how you can set it up and how it works with a real example. Why Intercompany Automation Matters If two companies within the same group trade with each other, both sides must record the same transaction, one as a sale and one as a purchase. When done manually, the process is slow and can cause mismatched balances. Automating it in Business Central saves time, reduces errors, and keeps both companies’ financials in sync automatically. Step 1: Setup Process 1. Turn on Intercompany Feature Open Business Central and go to the Intercompany Setup page. Turn on the setting that allows the company to act as an Intercompany Partner. 2. Add Intercompany Partners Add all related companies as partners. For example, if you have Company A and Company B, set up each as a partner inside the other. 3. Map the Chart of Accounts Make sure both companies use accounts that match in purpose. Example: 4. Create Intercompany Customer and Vendor 5. Create Intercompany Journal Templates Use IC General Journals to record shared expenses or income regularly. You can automate them using job queues or recurring batches. Step 2: Automation in Action Once the setup is complete, every time a user posts a sales invoice or general journal related to an Intercompany Customer or Vendor, Business Central creates a matching entry in the partner company. Both companies can see these transactions in their IC Inbox and Outbox. You can even add automation rules to post them automatically without approval if desired. Step 3: Use Case – Monthly IT Service Charges Scenario: The Head Office provides IT services to a Subsidiary every month for ₹1,00,000. Steps: Both companies now have matching entries, one as income and one as expense, without any manual adjustments. Result: Transactions are accurate, time is saved, and your accountants can focus on analysis rather than repetitive posting. To conclude, automating intercompany postings in Business Central makes financial management simple and reliable. Once configured, it ensures transparency, reduces errors, and speeds up reporting. I Hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com.

For data-driven companies, data insights are only as valuable as the platform that delivers them. As organizations modernize their technology stack, choosing the right reporting solution- whether SSRS, Power BI, or Paginated Reports – becomes a critical decision. With multiple options available, establishing clear evaluation criteria is essential to avoid costly missteps and future migration challenges. Are you struggling to decide which reporting tool fits your specific needs? If you’re evaluating SSRS, Power BI, or Paginated Reports for your organization, this article is for you. I’m confident this framework will help you make the right reporting tool decision and avoid common pitfalls that waste time and money. Understanding the Three Options Before we dive into the decision framework, let’s clarify what each tool actually is: SSRS (SQL Server Reporting Services) – The traditional Microsoft reporting platform that’s been around since 2004. It’s pixel-perfect, print-oriented, and runs on-premises. Power BI – Microsoft’s modern cloud-based analytics platform focused on interactive dashboards, data exploration, and self-service analytics. Paginated Reports in Power BI – The evolution of SSRS technology integrated into Power BI Service, combining traditional reporting with modern cloud capabilities. Step 1: Identify Your Primary Use Case Ask yourself this fundamental question: What is the report’s main purpose? Use Case A: Interactive Exploration and Analysis Best Choice: Power BI Choose Power BI when: Example Scenarios: Sales performance dashboards, Executive KPI monitoring, Marketing analytics platforms, Operational metrics tracking Use Case B: Precise Formatted Documents Best Choice: Paginated and SSRS Reports Choose Paginated Reports when: Example Scenarios: The Feature Comparison Matrix Power BI Standard Reports Strengths: Limitations: Paginated and SSRS Reports Strengths: Limitations: Cost Analysis: Making the Business Case Power BI & Power BI Paginated Reports Licensing Power BI Pro: $14/user/month SSRS Costs Important Note: If you’re already using Microsoft Dynamics 365 or Dynamics CRM, SSRS functionality is included at no additional cost. When SSRS is Already Available: Infrastructure Costs (If Not Using Dynamics): To conclude, I encourage you to take a systematic approach to your reporting tool decision. Identify your top 5 most important reports and categorize them by use case. This systematic approach will reveal the right decision for your organization and help you build a business case for stakeholders. Need help evaluating your specific reporting scenario? Connect with us at transform@cloudfronts.com for personalized guidance on choosing and implementing the right reporting solution. Making the right decision today will save you years of headaches and wasted resources.

Are you struggling to build secure, low-latency APIs on Azure without spinning up expensive always-on infrastructure? Traditional serverless models like the Azure Functions Consumption Plan are great for scaling, but they fall short when it comes to VNET integration and consistent low latency. Enterprises often need to connect serverless APIs to internal databases or secure networks — and until recently, that meant upgrading to Premium Plans or sacrificing the cost benefits of serverless. That’s where the Azure Functions Flex Consumption Plan changes the game. It brings together the elasticity of serverless, the security of VNETs, and latency performance that matches dedicated infrastructure — all while keeping your costs optimized. What is Azure Functions Flex Consumption? Azure Functions Flex Consumption is the newest hosting plan designed to power enterprise-grade serverless applications. It offers more control and flexibility without giving up the pay-per-use efficiency of the traditional Consumption Plan. Key capabilities include: Why This Matters APIs are the backbone of every digital product. In industries like finance, retail, and healthcare, response times and data security are mission critical. Flex Consumption ensures your serverless APIs are always ready, fast, and safely contained within your private network — ideal for internal or hybrid architectures. VNET Integration: Security Without Complexity Security has always been the biggest limitation of traditional serverless plans. With Flex Consumption, Azure Functions can now run inside your Virtual Network (VNET). This allows your Functions to: In short: You can now build fully private, VNET-secure APIs without maintaining dedicated infrastructure. Building a VNET-Secure Serverless API: Step-by-Step Step 1: Create a Function App in Flex Consumption Plan Step 2: Configure VNET Integration Step 3: Deploy Your API CodeUse Azure DevOps, GitHub Actions, or VS Code to deploy your function app just like any other Azure Function. Step 4: Secure Your API How It Compares to Other Hosting Plans Feature Consumption Premium Flex Consumption Auto Scale to Zero ✅ ❌ ✅ VNET Integration ❌ ✅ ✅ Cold Start Optimized ⚠️ ✅ ✅ Cost Efficiency ⭐⭐⭐⭐ ⭐⭐ ⭐⭐⭐⭐ Enterprise Security ❌ ✅ ✅ Flex Consumption truly combines the best of both worlds – the agility of serverless and the power of enterprise networking. Real-World Use Case Example A large retail enterprise needed to modernize its internal inventory API system.They were running on Premium Functions Plan for VNET access but were overpaying due to idle resource costs. After migrating to Flex Consumption, they achieved: This allowed them to maintain compliance, improve responsiveness, and simplify their architecture — all with minimal migration effort. To conclude, in today’s API-driven world, you shouldn’t have to choose between speed, cost, and security. With Azure Functions Flex Consumption, you can finally deploy VNET-secure, low-latency serverless APIs that scale seamlessly and stay protected inside your private network. Next Step:Start by migrating one of your internal APIs to the Flex Consumption Plan. Test the latency, monitor costs, and see the difference in performance. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudFronts.com

Sometimes, it becomes necessary to correct a posted transaction. Instead of manually adjusting or attempting to delete it, you can utilize the reverse functionality. Reverse journal postings are helpful for correcting mistakes or removing outdated accrual entries before creating new ones. A reversal mirrors the original entry but uses the opposite sign in the Amount field. It must use the same document number and posting date as the original. After reversing, the correct entry must be posted. Only entries created from general journal lines can be reversed, and each entry can be reversed only once. To undo a receipt or shipment that hasn’t been invoiced, use the Undo action on the posted document. This applies to Item and Resource quantities. You can undo postings if an incorrect negative quantity was entered (for example, a purchase receipt with the wrong item quantity and not yet invoiced). Similarly, incorrect positive quantities posted as shipped but not invoiced, such as sales shipments or purchase return shipments. can also be undone. Pre-requisites Business Central onCloud Steps: Open the transaction you wish to reverse. In this case, we aim to reverse the payment for the customer shown below. Click on Ledger Entries to view all transactions associated with this customer. As shown, this payment has already been applied to an invoice. Therefore, you must first unapply the payment before proceeding. Use the Unapply Entries action button to unapply the entries for the selected customer. Once you successfully unapplied payment you can see “remaiing amount” is equal to “Amount” field. Now click on “Reverse Transaction”. You can view the related entries for this transaction. Click the Reverse button, and a pop-up will appear once the reversal entries have been posted for the selected transaction. The reverse entry has now been created, reflecting the same document number and amount. Leveraging the reverse transaction functionality in Business Central enables businesses to correct errors seamlessly, improve operational efficiency, and uphold the integrity of their financial data. Whether managing invoices, payments, or other ledger entries, this feature is an essential tool for maintaining transparency and accuracy in your financial workflows. To Conclude, the reverse transaction feature in Business Central is a powerful tool that simplifies the process of correcting posted transactions. Instead of manually adjusting or deleting entries, you can efficiently reverse them, ensuring your financial records remain accurate and consistent. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Tax Deducted at Source (TDS) with concessional rates on threshold limits is a provision that enables eligible taxpayers to benefit from lower TDS rates, as permitted by government-issued certificates. These certificates are granted to individuals or entities that meet specific criteria, such as lower tax liability or involvement in designated transactions. By implementing concessional rates, taxpayers can effectively manage their immediate tax burden, enhance cash flow, and ensure compliance with regulatory requirements. This guide outlines the step-by-step process for configuring concessional TDS rates in Microsoft Dynamics 365 Finance & Operations (D365 F&O) to facilitate accurate tax calculations and ensure seamless compliance. Step-by-Step Configuration of TDS in D365 F&O 1. Setting Up the Withholding Tax Code Navigate to Tax → Indirect Taxes → Withholding Tax → Withholding Tax Code and either select an existing tax code or create a new one. Ensure all required details are entered accurately. 2. Defining Concessional TDS Rates Click on Values and insert the applicable TDS rates as per government guidelines. 3. Configuring Threshold Limits Access Tax → Indirect Taxes → Withholding Tax → Withholding Tax Code and select Threshold Designer. Enter the threshold limits for TDS rates, specifying the applicable conditions when these limits are reached. 4. Establishing Post-Threshold Tax Treatment Provide details regarding the applicable tax rate once the threshold limit is exceeded to ensure proper compliance. 5. Assigning Threshold References Navigate to Tax → Indirect Taxes → Withholding Tax → Withholding Tax Code and select Threshold Reference. Assign the relevant Vendor, specific group, and threshold code to ensure accurate tax calculations. 6. Creating a TDS Group Define a new TDS Group and link it with the recently created withholding tax code to streamline tax application across transactions. 7. Configuring the Tax Code in Designer Use the Designer tool to reassign the withholding tax code, ensuring correct integration within tax processing workflows. 8. Associating the Tax Group with Vendors Assign the defined Tax Group to the relevant vendor. Once this is set up, proceed with Vendor Invoice postings or Purchase Order creation, ensuring that the concessional TDS rates are accurately applied to financial transactions. Proper configuration of TDS with concessional rates in D365 F&O ensures compliance with tax regulations while optimizing cash flow for eligible taxpayers. By implementing the correct withholding tax setup, organizations can streamline their tax processes and minimize unnecessary deductions. This structured approach enhances financial accuracy and simplifies tax management, contributing to more efficient business operations. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Building low-latency, VNET-secure APIs with Azure Functions Flex Consumption is only the beginning.The next step toward modernization is setting up a DevOps release pipeline that automatically deploys your Function Apps-even across multiple regions – using Azure CLI. In this blog, we’ll explore how to implement a CI/CD pipeline using Azure DevOps and Azure CLI to deploy Azure Functions (Flex Consumption), handle cross-platform deployment scenarios, and ensure global availability. Step-by-Step Guide: Azure DevOps Pipeline for Azure Functions Flex Consumption Step 1: Prerequisites You’ll need: Step 2: Provision Function Infrastructure Using Azure CLI Step 3: Configure Azure DevOps Release Pipeline Important Note: Windows vs Linux in Flex Consumption While creating your pipeline, you might notice a critical difference: The Azure Functions Flex Consumption plan only supports Linux environments. If your existing Azure Function was originally created on a Windows-based plan, you cannot use the standard “Azure Function App Deploy” DevOps task, as it assumes Windows compatibility and won’t deploy successfully to Linux-based Flex Consumption. To overcome this, you must use Azure CLI commands (config-zip deployment) — exactly as shown above — to manually upload and deploy your packaged function code. This method works regardless of the OS runtime and ensures smooth deployment to Flex Consumption Functions without compatibility issues. Tip: Before migration, confirm that your Function’s runtime stack supports Linux. Most modern stacks like .NET 6+, Node.js, and Python run natively on Linux in Flex Consumption. Step 4: Secure Configurations and Secrets Use Azure Key Vault integration to safely inject configuration values: Step 5: Enable VNET Integration If your Function App accesses internal resources, enable VNET integration: Step 6: Multi-Region Deployment for High Availability For global coverage, you can deploy your Function Apps to multiple regions using Azure CLI: Dynamic Version (Recommended): This ensures consistent global rollouts across regions. Step 7: Rollback Strategy If deployment fails in a specific region, your pipeline can automatically roll back: Best Practices a. Use YAML pipelines for version-controlled CI/CDb. Use Azure CLI for Flex Consumption deployments (Linux runtime only)c. Add manual approvals for productiond. Monitor rollouts via Azure Monitore. Keep deployment scripts modular and parameterized To conclude, automating deployments for Azure Functions Flex Consumption using Azure DevOps and Azure CLI gives you: If your current Azure Function runs on Windows, remember — Flex Consumption supports only Linux-based plans, so CLI-based deployments are the way forward. Next Step:Start with one Function App pipeline, validate it in a Linux Flex environment, and expand globally. For expert support in automating Azure serverless solutions, connect with CloudFronts — your trusted Azure integration partner. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com