Summary Designed a two-page Power BI Income Pipeline Report for a Texas-based Cybersecurity & AI Business Solutions firm using Microsoft Dynamics 365 Project Operations. Unified visibility across Opportunity, Unbilled Income, Billed Income, and Paid Income in a single view. Introduced Average Turnaround to forecast realistic cash collection timelines based on actual payment behavior. Integrated Dynamics 365 Project Operations with QuickBooks to connect sales, delivery, invoicing, and cash collection. Enabled a 17-week rolling revenue forecast with week-by-week cash visibility. Provided dual invoice status for contractual vs realistic payment tracking. Table of Contents 1. Introduction 2. The Business Problem 3. Report Structure Overview 4. The Income Pipeline 5. Project Revenue Forecast 6. Design Principles 7. Business Impact 8. FAQs 9. Conclusion 1. Introduction Managing revenue across a professional services firm is rarely straightforward. When your business spans cybersecurity assessments, AI-driven solutions, and long-term managed services engagements, the gap between work being delivered and cash actually landing in the bank can be wide — and costly if left unmonitored. This is precisely the challenge we set out to solve for a U.S.-based Cybersecurity and AI Business Solutions firm running their operations on Microsoft Dynamics 365 Project Operations. The result was a two-page Power BI report — the Income Pipeline Report — that gives leadership a real-time, end-to-end view of every dollar moving through the business: from early-stage opportunity, through unbilled and billed income, all the way to cash collected. This post walks through how the report was built, how each data layer was modelled, and why the design decisions were made the way they were. 2. The Business Problem The firm needed clarity across four distinct but connected stages of their revenue lifecycle: Sales opportunities and pipeline value Delivered but unbilled work Outstanding invoices and expected payments Actual vs expected payment behavior This would answer as well as resolve the following questions – Where are active sales opportunities sitting, and how much pipeline value do they represent? Which project work has been delivered but not yet invoiced? Which invoices have been raised and sent to clients, and when are they realistically going to be paid? And finally, how does actual payment behaviour compare against what was expected? Each of these questions existed in isolation before. Project managers had partial visibility into their own contracts, and needed a comprehensive bird’s eye view of all of these together. Finance had QuickBooks data but lacked the context of the delivery pipeline. Leadership had no consolidated view. The Income Pipeline Report brought all of this together in a single, navigable Power BI experience. 3. Report Structure Overview The report consists of two pages: Income Pipeline Report — a high-level pipeline view across four stages: Opportunity, Unbilled Income, Billed Income, and Paid Income, each with summary cards and interactive donut charts. Project Revenue Forecast — a time-distributed breakdown of expected cash collection across a rolling 17-week horizon, organised by customer and contract. 4. The Income Pipeline The Four-Stage Pipeline Banner Across the top of the report, four chevron-style stage indicators guide the revenue journey: Opportunity → Unbilled Income → Billed Income → Paid Income Each stage includes a summary card showing record count and total value Provides immediate visibility into where revenue is sitting Highlights potential bottlenecks across the pipeline Stage 1 — Opportunity Data sourced from Dynamics 365 Sales using Business Process Flow (BPF) Uses active BPF stage (Develop, Propose, Close) instead of static fields Ensures accurate reflection of real sales progression Estimated revenue pulled directly from opportunity records Donut chart shows distribution across Develop, Propose, and Close stages Stage 2 — Unbilled Income Represents contracted or delivered work not yet invoiced Sourced from project contract lines in Dynamics 365 Project Operations Includes: Fixed Fee milestones (explicit values) Time & Material (T&M) estimates based on resource allocations T&M calculated as allocated hours × billing rate Clearly marked as estimated until billing run is executed Grouped into payment expectation buckets (30, 60, 90, 120, 180+ days) Uses Average Turnaround to forecast realistic payment timing Stage 3 — Billed Income (Confirmed Invoices) Combines Dynamics 365 Project Operations and QuickBooks data Tracks invoices that are confirmed and sent to clients Introduces Average Turnaround: Average days from invoice creation to payment Based on historical payment behaviour Each invoice has two statuses: Contractual (due date) Estimated (based on Average Turnaround) Provides realistic vs contractual payment visibility Includes: Due-date based categorisation Estimated overdue analysis Prevents misleading insights from strict payment terms alone Stage 4 — Paid Income Tracks fully collected invoices Uses QuickBooks for actual payment dates Groups payments by time bands (under 30, 60, 90 days, etc.) Enables comparison between actual vs estimated payment behaviour Continuously improves accuracy of Average Turnaround Tooltip Drill-Down Hover shows: Payment band Record count Total value Drill-through available for detailed record-level analysis 5. Project Revenue Forecast Overview Distributes expected cash collection across a rolling 17-week window Shifts view from pipeline stage to time-based forecasting Hierarchy and Structure Customer → Contract → Revenue Type Revenue types include: T&M run schedules Fixed Fee milestones Confirmed invoices Each row shows: Customer Contract Billing type Average Turnaround Value mapped to expected payment week Weeks range from Week 0 to Week 16 Top row aggregates total expected cash per week Colour Coding Amber — Unbilled income Green — Invoice within terms Red — Overdue (based on estimated payment date) Drill-Through to Detail Click any row to view detailed breakdown Includes: Billed invoices with due and estimated dates Unbilled milestones and run schedules Connects high-level forecast to transactional detail 6. Design Principles Average Turnaround over payment terms Reflects actual customer behaviour instead of contractual assumptions. Dual invoice status Provides both contractual and realistic payment visibility. Consistent time buckets Ensures comparability across Opportunity, Unbilled, Billed, and Paid stages. Weekly forecasting instead of monthly Supports short-term cash flow planning aligned with operational rhythm. 7. Business Impact Improved cash flow predictability Earlier visibility of at-risk invoices Unified cross-team visibility Improved T&M billing discipline Increased accountability 8. FAQs What is Average Turnaround and why does it … Continue reading How we designed & deployed an Income Pipeline Report for a Texas, U.S. based Cybersecurity & AI Business Solutions Firm, via MS D365 Project Operations and Power BI. →

Summary: In industrial manufacturing, especially in sectors like piping systems, fittings, and castings, the sales process is not a simple transaction, it is a structured, multi-stage bid lifecycle. This blog explains how organizations can manage the entire journey from lead generation to project completion using Dynamics 365 Sales. It also highlights how organizations can: Industrial sales in manufacturing industries such as pipes, fittings, and castings involve long sales cycles, multiple stakeholders, and highly detailed technical and commercial evaluations. Unlike standard product sales, these deals often begin with tenders or RFQs and require coordination across sales, engineering, finance, and production teams. Without a structured system, it becomes difficult to track bid progress, maintain version control, and ensure timely responses. This is where Dynamics 365 Sales plays a crucial role. It provides a centralized platform to manage every stage of the industrial bid process, ensuring visibility, accountability, and efficiency. From capturing initial leads to closing deals and delivering projects, it helps organizations streamline operations and improve win rates. The Challenge Section The Problem with Disconnected Data Organizations often manage sales and bid-related data across multiple systems such as ConstructConnect, Excel sheets, and offline trackers. This creates several operational challenges: As a result, the bidding process becomes reactive instead of proactive, slowing down execution and reducing win probability. Manufacturing companies dealing with industrial products face several challenges during the bid process: These challenges can result in missed opportunities, delayed submissions, and reduced customer confidence. The Solution Section Building a Structured Lead-to-Project Pipeline A key improvement is bringing all activities into a centralized system like Dynamics 365 Sales. Some practical steps include: Projects can then follow a clearly defined lifecycle: This structured pipeline ensures: Enforcing Pipeline Discipline and Accountability One key insight from mature implementations is the importance of pipeline governance. This includes: For example: This brings accountability and keeps the pipeline active and realistic. Improving Quote Tracking and Automation Quote management becomes significantly more efficient with automation. Key capabilities include: This ensures: Enhancing Visibility for Decision Making With all data centralized, leadership gains meaningful insights into the sales pipeline. Examples include: This enables: Business Impact / Results Section Adopting a unified system like Dynamics 365 Sales leads to tangible improvements: Result:A centralized platform replaces fragmented tools, enabling organizations to manage bids more effectively and improve overall project outcomes. With automation across lead capture, pipeline tracking, quote management, and follow-ups, up to 80% of the bid-to-project lifecycle can be automated, significantly reducing manual effort and operational delays. Technical Deep-Dive For organizations requiring deeper customization: FAQ Section Q1. Why is a single system important for managing industrial bids?A single system eliminates data silos, reduces manual work, and ensures all teams work with the same, up-to-date information. This improves coordination and increases the chances of winning bids. Q2. How does Dynamics 365 Sales support the industrial bidding process?It provides a structured pipeline, tracks projects from lead to completion, enables collaboration across teams, and automates key activities such as quote management and follow-ups. Q3. Can we customize the sales stages to match our business process?Yes, stages like Opportunity can be renamed to “Project,” and custom stages such as Pre-Qualified, Submittal, Negotiation, and Commitment can be configured to reflect the actual industrial bidding lifecycle. Q4. How does the system help in identifying projects at risk?Projects with no recent activity or delays in stage movement can be automatically flagged, allowing teams to take timely action and prevent potential losses. Q5. What improvements can be expected after implementation?Organizations typically see better data accuracy, faster bid processing, improved team accountability, and enhanced visibility into the sales pipeline. Q6. Can Dynamics 365 integrate with tools like ConstructConnect?Yes, it can integrate with external platforms to automatically import leads and project data, reducing manual entry and ensuring consistency. Q7. How much of the bid process can be automated using Dynamics 365 Sales?A significant portion of the process can be automated, including lead capture, stage tracking, quote handling, reminders, and reporting. In well-structured implementations, up to 80% of the bid-to-project lifecycle can be automated, allowing teams to focus on strategic and high-value activities. Conclusion Managing industrial bids across disconnected tools creates inefficiencies that directly impact business performance. By transitioning to a unified system like Dynamics 365 Sales, organizations can standardize their processes, automate critical tasks, and gain complete visibility into their pipeline. From capturing leads to delivering completed projects, a structured and integrated approach ensures better control, faster execution, and improved success rates. If your organization is still managing bids through spreadsheets and multiple systems, it may be time to move towards a more structured, scalable solution with Dynamics 365 Sales. Connect with CloudFronts to get started at transform@cloudfonts.com Author Bio The author specializes in implementing Dynamics 365 solutions for manufacturing and industrial sectors. With experience in optimizing sales processes, bid management, and system integrations, they focus on helping organizations streamline operations and improve efficiency through digital transformation.

What happens when a global manufacturing giant needs to modernize its operations without grinding critical business processes to a halt? The answer is not a rip-and-replace approach – it is a carefully engineered integration strategy that lets modern and legacy systems co-exist, communicate, and complement each other. Are you planning an ERP upgrade but worried about what happens to the legacy systems your operations depend on? If so, this is for you. One of North America’s leading commercial vehicle manufacturers faced exactly this dilemma. With decades of investment in legacy financial and warehouse management systems, a hard cutover to a new ERP was not an option. Yet the need for a modern, scalable platform was undeniable. Their solution? Introduce Microsoft Dynamics 365 Finance & Operations (D365 F&O) as the new operational backbone – while keeping their legacy systems in play for financial control – and build robust, bi-directional integrations to bridge both worlds. At CloudFronts, we had the privilege of architecting and implementing those integrations. This blog walks you through three core data flows: Spot Purchase Orders, Advance Shipment Notices (ASN), and Goods Receipt Notes (GRN) – and what it really takes to make a modern ERP talk to a legacy system without missing a beat. Why Replace When You Can Integrate? Legacy systems in large manufacturers are not just old software. They carry years of financial logic, vendor relationships, and compliance configurations that are too risky to discard overnight. Replacing them introduces enormous operational and compliance risk. Doing nothing, however, is not an option either. The approach our client took – and one we increasingly recommend for manufacturers, distributors, and large enterprises – is a co-existence model: This means the business gets the agility of a modern ERP on day one, without putting financial operations at risk. The three integrations do the heavy lifting. Architecture at a Glance Before diving into each integration, it helps to understand the overall data flow pattern and the Azure services involved: Component Role D365 F&O System of record for purchasing and receiving operations Legacy System Retains financial control, inventory management authority Azure Logic Apps Parent-child middleware: orchestrates, transforms, and routes data Azure Blob Storage Checkpoint management for reliable incremental processing Azure Table Storage Full execution logs for traceability, audit, and failure replay The three integrations work in concert: Integration 1: Spot Purchase Orders — D365 F&O to Legacy Business Problem A Spot Purchase Order is an ad-hoc purchase order raised outside of long-term contracts — often for urgent material procurement. Spot POs are created and managed in D365 F&O by procurement teams. However, the legacy system is the system of financial record, meaning every Spot PO created in D365 must be reflected in the legacy system for financial commitment tracking and vendor payment processing. Without integration, this would require manual re-entry – a process prone to error, delay, and duplication. How the Integration Works Parent Logic App – Spot PO Orchestrator The primary Logic App runs on a scheduled recurrence and uses a checkpoint mechanism stored in Azure Blob Storage to fetch only incremental changes – purchase orders created or modified since the last successful run. This ensures efficiency and prevents reprocessing of already-handled records. The workflow determines the operation type required for each PO: For each scenario, the Logic App fetches enriched data from multiple D365 F&O OData entities and constructs a structured JSON payload tailored for the legacy system’s API. ⚙ Tech Note: OData Entities Used PurchaseOrderHeaders, PurchaseOrderLinesV2, PurchaseLineDataEntities, WHSPurchLines, StatusCustomDatas Child Logic App – SendRequest (Reusable) Rather than embedding API communication logic directly in the orchestrator, we separated it into a reusable child Logic App. This child app receives the constructed payload, retrieves an OAuth 2.0 Bearer token, and executes the HTTP POST call to the legacy system’s API endpoint. This modular design pays dividends during maintenance: any change to authentication logic or API communication is made once in the child app and automatically applies to all parent integrations. Failed Record Handler Every enterprise integration needs robust failure recovery. When an API call fails: Sample Payload – Spot PO Create Sample JSON Payload: {   “userId”: “JSMITH”,   “order”: “456789”,   // Last 6 digits of D365 PO number   “vendor”: “VEND001”,   “receiptLoc”: “SITE01”,   “vendorOvrdCd”: “14”,   “lineItems”: [{     “orderLine”: “001”,     “item”: “ITEM001”,     “openQty”: 10,     “deliveryDate”: “061526”,  // MMddyy format for legacy compatibility     “comment”: “MPSSYS order – JSMITH” }] } } ✓ Business Impact: Zero manual re-entry of purchase orders between systems. Every Spot PO created or changed in D365 F&O is automatically reflected in the legacy system within minutes. Integration 2: Advance Shipment Notices — Legacy to D365 F&O Business Problem An Advance Shipment Notice (ASN) is a notification sent by the legacy WMS to the receiving system, informing it of an incoming shipment before it physically arrives. D365 F&O needs to receive ASNs to create Inbound Load Headers and Load Lines – enabling warehouse teams to prepare for receiving. Without this integration, receiving teams in D365 would be blind to incoming shipments until trucks arrived at the dock – eliminating any opportunity for advance dock scheduling, labor planning, or inventory pre-positioning. The Hybrid Integration Approach This integration presented an interesting technical challenge: the standard D365 F&O Inbound ASN V5 API supports a well-defined XML format, but the business required additional fields beyond what the standard API supports. The solution was a two-step Hybrid ASN Integration approach: ⚙ Tech Note: API Endpoint Pattern Insert:  POST {{BASE_URL}}/api/connector/enqueue/{{ACTIVITY_ID}}?entity=Inbound ASN V5 Enrich:  PATCH on InboundLoadHeaders and WHSASNWorkData Smart Insert vs. Update Determination To handle scenarios where an ASN might be re-sent for corrections or resynchronization, the integration includes a check before processing: This idempotent design prevents duplicate inbound loads from being created when the legacy system re-sends an ASN. One nuance worth noting: in D365’s standard ASN structure, the LoadId, ShipmentId, and LicensePlateNumber must carry the same value. The legacy system’s outbound ASN payload is configured to honour this requirement – ensuring clean data entry … Continue reading How a Top North American Commercial Vehicle Manufacturer Connected D365 F&O with Legacy Systems Without Disrupting Operations →

Summary In global food distribution, timing is everything. A delay in decision-making can lead to stock shortages, food wastage, or supply chain disruptions. Are you struggling to get real-time visibility into your distribution network? With increasing data from warehouses, suppliers, and logistics, making quick and accurate decisions becomes challenging. In this blog, I’ll share how we used Microsoft Power BI to accelerate decision-making in a global food distribution scenario. Core Content Why Decision-Making is Critical in Food Distribution Global food distribution involves: Without proper insights: Organizations need a system that provides real-time visibility and actionable insights. Challenges Faced In our implementation, we observed: This made decision-making slow and reactive rather than proactive. Solution Using Power BI We built a centralized reporting solution using Power BI that: Key Features of the Dashboard Real-Time Inventory Tracking Regional Demand Analysis Shipment Monitoring Performance Metrics Step-by-Step Approach Step 1: Data Integration Step 2: Data Modeling Step 3: Dashboard Development Step 4: Performance Optimization Step 5: Deployment & Sharing Real-World Impact After implementing the solution: ✔ Decision-making time reduced significantly✔ Improved visibility across global operations✔ Faster identification of supply-demand gaps✔ Reduced food wastage✔ Increased operational efficiency Managers could now make decisions in minutes instead of hours. Best Practices ✔ Centralize data sources✔ Use interactive dashboards for quick insights✔ Focus on business KPIs✔ Optimize data models for performance✔ Ensure data accuracy and consistency Conclusion In global food distribution, speed and accuracy in decision-making are crucial. By leveraging Power BI, organizations can transform scattered data into meaningful insights and act faster. A well-designed dashboard not only improves visibility but also empowers teams to make proactive decisions, reducing risks and improving efficiency. Call to Action If your organization is struggling with slow decision-making in supply chain operations, start by building a centralized reporting solution in Power BI. Identify your key metrics, integrate your data, and create dashboards that drive real-time insights. The right data at the right time can make all the difference. Connect with CloudFronts to get started at transform@cloudfonts.com

Summary : In this blog, you will learn: Field sales teams generate some of the most valuable business insights during distributor visits, site meetings, and customer discussions. These interactions often include pricing feedback, upcoming opportunities, and competitor information. But in many manufacturing organizations, this information is never formally captured. It stays in personal notes or memory and is lost when teams change or time passes. The result? Leadership lacks visibility into what is actually happening in the field. This blog explains how organizations can solve this by using Microsoft Dynamics 365 Sales to turn everyday field interactions into structured, measurable data. The Challenge The Field Sales Visibility Problem Field sales in manufacturing is highly relationship-driven. While this builds strong customer connections, it also creates a major gap in tracking and visibility. Key challenges include: This leads to a situation where the CRM reflects only partial activity, missing the interactions that actually drive business. The Solution Building a Structured Field Activity System The goal is not to increase administrative work, but to make activity tracking quick, simple, and useful. 1. Introduce a “Branch Visit” Activity FrameworkCreate a structured way to capture key field interactions such as: Each visit can include: This ensures every interaction is recorded in a consistent and useful format. 2. Enable Quick Mobile UpdatesUsing the mobile capabilities of Microsoft Dynamics 365 Sales, sales teams can log visits immediately after meetings. The process is simple and takes less than a minute, making it easy to adopt without disrupting their workflow. 3. Connect Activities to Customers and OpportunitiesAll recorded visits are linked to customer accounts and ongoing deals. This allows: 4. Turn Data into InsightsOnce activities are consistently captured, organizations can generate reports such as: With Microsoft Power BI, this data can be visualized into dashboards that clearly show trends and performance. Business Impact / Results When field sales activities are properly tracked, the impact is immediate and measurable: Managers can now: Most importantly, field sales productivity becomes visible, measurable, and manageable. Technical Deep-Dive (Simplified) For implementation within Microsoft Dynamics 365 Sales: These configurations ensure the system is scalable while remaining easy for sales teams to use. FAQ Section a. What is a Branch Visit activity?It is a structured way to record field interactions like distributor visits and customer meetings, ensuring all key details are captured in the CRM. b. How does this improve productivity?It connects daily activities with actual sales outcomes, helping managers track performance and identify gaps. c. Can this data be visualized?Yes, using Microsoft Power BI, organizations can create dashboards to monitor performance across regions and teams. d. How do you ensure sales teams actually use the system?By keeping the process fast, simple, and beneficial so it saves time rather than adding extra workz To conclude, Field sales will always be driven by relationships but managing those relationships should not rely on memory or manual tracking. By using Microsoft Dynamics 365 Sales to capture and structure field activities, organizations can transform how they measure productivity. a. What was once invisible becomes clear.b. What was once assumed becomes measurable. This shift allows leadership to make better decisions, improve sales performance, and strengthen customer relationships. If you’re looking to bring visibility and structure to your field sales operations, now is the time to adopt a smarter, data-driven approach. The author is a D365 CRM Consultant specializing in sales process optimization for manufacturing organizations. She focuses on helping businesses implement practical, user-friendly solutions using Microsoft Dynamics 365 Sales to improve visibility, efficiency, and performance. Connect with CloudFronts to get started at transform@cloudfonts.com

Summary Organizations typically use Dynamics 365 CRM/Sales Business Process Flow (BPF) to manage the sales cycle and win deals. It is commonly treated as an out-of-the-box (OOB) capability designed strictly for sales processes. In this blog, we explore how a door and window manufacturer in New York successfully repurposed Dynamics 365 Business Process Flow to track ‘Shop Floor Stages’-extending its use beyond sales into operations. The Idea Behind Using Business Process Flow This company manufactures one of the most diverse ranges of steel windows and doors in the USA. While managing their sales cycle, they also needed better visibility into order progress. The idea was to reuse the standard BPF structure instead of building a new system from scratch. The standard BPF follows:Lead → Opportunity → Quote → Order The approach was to repurpose this flow into a custom process aligned with their operational needs. Extending into Order Fulfilment The Order entity was enhanced and renamed as Order Fulfilment, where the BPF continued beyond sales. Shop floor coordinators could quickly identify issues and physically inspect problem areas, improving operational efficiency. Additionally: Over time, the system evolved organically-retaining only what added value. Readiness for AI With clean, structured, and unified data across the entire lifecycle, the system became AI-ready. Key use cases included: What Did We Achieve? Key insights from the solution architects: To conclude, by reimagining the use of Dynamics 365 Business Process Flow, this organization successfully bridged the gap between sales and operations. What began as a sales tracking tool evolved into a comprehensive system managing the entire lifecycle-from lead generation to shop floor execution. Today, this approach continues to power their operations end-to-end, proving that thoughtful reuse of existing capabilities can drive efficiency, reduce costs, and create a strong foundation for future innovations, including AI. Connect with CloudFronts to get started at transform@cloudfonts.com

Summary: In today’s Agentic AI conversations, existing suite of business applications by Microsoft Dynamics 365 like CE applications, Business Central or Finance and Operations still make sense – but too early for your needs? Well, here’s where Power Apps proves to be the most apt choice in terms of license spend, use case for smaller but growing business till you need to move to full-fledged applications.   Why Power Apps Premium?  If you are a smaller team of about 5-10 and currently operating with 1-2 systems or file repositories which are smaller but disparate, here’s how this approach works best –   One of the recent examples is helping an American ISV’s build a Power Apps version of a job costing module coming from Dynamics GP which will sunset in a few years. This paves way for existing customers move to a relatively smaller license footprint while the application remains focused on a specific purpose only.   With Power Apps Premium, this is a huge deal for organizations who want to do Job Costing but don’t really need the full Field Service or Project Management applications. This lowers the barrier to entry in Dynamics 365 cloud and also enables them to spend on Power Apps Premium as well as Business Central to handle the accounting for Job Costing.  What to take care about?  While choosing Power Apps may seem like the right choice for smaller use cases that don’t need full-scale Dynamics 365 Applications, here are some of the aspects you must take care of –   To conclude, if you are a small business and looking to get started on Power Platform / Power Apps for specific needs, it makes more sense to build small using Canvas or Model Driven Apps instead of going for a full-fledged business system like Dynamics 365 CE Apps, Business Central or Finance and Operations.  This gives you the right cover for specific needs till you really get to the scale where your growth actually demands for full-scale applications.  This helps keep the cost low, applications focused to serve designated purposes and deploy and connect to existing data sources quicker.  Connect with CloudFronts to get started at transform@cloudfonts.com

Summary Microsoft Dynamics 365 Business Central keeps your business future‑ready with regular updates that improve speed, security, and usability. For customers, this means smoother workflows, fewer disruptions, and access to the latest features without extra effort. Updates are scheduled with flexibility, tested in sandboxes, and designed to fit around your operations so you stay focused on running your business while Business Central takes care of the rest. Steps to Achieve Goal Access the Admin Center Review Available Updates Schedule the Update Coordinate with Production Scheduling Test in Sandbox To conclude, updating Microsoft Dynamics 365 Business Central isn’t just a technical task it’s a way to keep your business secure, efficient, and ready for growth. Every update is designed with customers in mind: fewer disruptions, stronger protection, and smarter features that make daily work easier. By preparing ahead and using sandbox testing, you can ensure updates fit seamlessly into your operations. With Business Central, staying current means staying confident your system evolves so your business can keep moving forward without missing a step. Connect with CloudFronts to get started at transform@cloudfonts.com

Marketing teams have always produced a steady stream of content, blogs, case studies, and articles. While this content captures valuable insights, it often tells only part of the story. Most blogs focus on technical implementations and how the work was executed, rather than clearly articulating the business problem, transformation process, and measurable outcomes. As a result, the overall impact created often remains in the background. Marketing team at CloudFronts started noticing a few consistent patterns: The issue was not a lack of knowledge or expertise. Our teams had deep experience. The real challenge was that customer insights were spread across different team members, and marketing did not always have a structured way to capture the full journey. That is when we started rethinking how we can capture the customer Journeys. The Challenge with Traditional Customer Content In every customer project, valuable knowledge exists across multiple roles. However, marketing rarely has direct access to all these perspectives at the same time. Without a structured process to capture insights across teams, much of the content tends to focus on technical implementation, since delivery teams are best positioned to describe how the solution was designed and implemented. While these blogs are useful, they often miss the broader story: For decision makers evaluating partners, this business context is often more valuable than the technical details alone. Recognizing this gap pushed us to rethink our content process. Our Shift: Turning Customer Insights into Strategic Content Instead of relying on ad-hoc blog contributions, we introduced a structured customer Journey capturing process. The process starts with something simple but powerful: a conversation with the delivery team. For every major customer engagement, marketing team schedules a dedicated discussion with the people who were directly involved in the project. This usually includes architects, consultants, project manager, and sometimes presales. During these sessions, we guide the conversation using a structured set of questions designed to uncover the full customer journey. We focus on areas such as: In many cases, the delivery team also walks us through the system they implemented. Seeing the solution in action helps marketing understand the practical value delivered to the customer. These discussions capture something that traditional documentation often misses: the real story behind the transformation. Building an AI-Powered Customer Knowledge Base Capturing the conversation is only the first step. The real transformation in our process begins when we introduce AI. We record and transcribe these discussions and combine them with existing project documentation, including: We then bring all this information into AI-powered tool called NotebookLM, creating a dedicated knowledge repository for each customer journey. Instead of navigating through multiple documents and scattered notes, marketing team now has one structured knowledge base containing the full project story. This changes how we approach content creation. Using AI to Identify the Best Blog Ideas Once the knowledge base is built, we use AI to analyze the information and help us identify the most meaningful narratives within the project. Our goal is not simply to generate blogs automatically. Instead, we use structured prompts to help AI discover the strongest story angles hidden within the customer journey. This helps us uncover ideas such as: Instead of producing just one blog from a customer project, we often identify multiple content opportunities from a single engagement. Moving Beyond Technical Blogs This new approach has significantly changed the type of content we create. Rather than publishing isolated technical blogs, we now build a structured content ecosystem around each customer story. This includes: Customer Journey Blogs A narrative that captures the full transformation from the business challenge to the final outcomes. Use Case Blogs Detailed articles explaining how specific solutions solved operational challenges. Customer Milestone Stories Updates on key project achievements such as major implementations, go-lives, and expansion phases. In essence, one customer engagement now supports multiple layers of storytelling. Why AI Matters for Modern Marketing AI is often discussed as a way to generate content faster. In our experience, its real value is different. AI helps us access knowledge that already exists within the organization but is often difficult to gather and use effectively. Every customer project generates a significant amount of insight: Without the right tools, much of this knowledge remains buried in documents, presentations, and internal meetings. AI allows us to analyze, connect, and transform this knowledge into meaningful stories. The Future of Customer Storytelling Through this process, we see marketing evolving beyond content production. Our role increasingly becomes the bridge between delivery expertise and market insight. By capturing customer journeys, organizing knowledge, and using AI to uncover meaningful narratives, we are moving from fragmented content creation toward intentional storytelling. In a market where decision makers want partners who truly understand their challenges, authentic customer stories carry far more weight than generic marketing messages. The organizations that stand out will not necessarily be the ones producing the most content. They will be the ones that capture and communicate the stories that truly matter. To conclude, in today’s market, decision-makers are not looking for generic content.They are looking for partners who understand their challenges and can prove impact. The organizations that stand out will not be the ones producing the most contentbut the ones telling the most meaningful, authentic customer stories. And with AI, we now have the ability to do exactly that at scale, with precision, and with impact.

Summary A Houston-based cybersecurity firm eliminated report failures (~65%) by replacing SSRS with an Azure Function App pipeline. Dynamics 365 bound action ensured authentication stayed internal, bypassing Defender-related token failures. Integrated Power Pages, Power Automate, Dynamics 365, and Azure Functions for real-time PDF generation. Report generation time reduced from 3–8 minutes to under 15 seconds with zero infrastructure overhead. Table of Contents 1. About the Customer 2. The Challenge 3. The Solution 4. Technical Implementation 5. Business Impact 6. FAQs 7. Conclusion 1. About the Customer The client is a technology consulting and cybersecurity services firm based in Houston, Texas. They manage multiple concurrent client engagements using Dynamics 365 Project Operations as their core platform. Project managers and clients access live project data through a customer-facing portal built on Microsoft Power Pages. 2. The Challenge The organization needed one-click downloadable Project Status Reports from their Power Pages portal covering risks, issues, logs, and timelines. Their SSRS-based solution failed frequently due to authentication breakdowns caused by Microsoft Defender for Cloud Apps across multiple service boundaries. Key pain points: Silent authentication failures with no clear errors Retry delays of 60–90 seconds per attempt Separate SSRS infrastructure dependency Slow report customization cycle Project managers avoided generating reports during live meetings due to reliability concerns. 3. The Solution At Cloudfronts, while working on this project, I replaced the SSRS pipeline entirely with a synchronous, serverless architecture that keeps the authentication context inside the Dynamics 365 service layer. Technologies Used: Dynamics 365 Project Operations Power Pages Power Automate Plugins Azure Function Apps The solution generates fully formatted PDFs in real time using structured JSON payloads. This eliminated authentication failures while significantly improving speed and reliability. 4. Technical Implementation 1] Power Pages Button triggers Flow A “Download Report” button captures the project GUID and triggers a Power Automate flow with real-time progress feedback. 2] Dynamics 365 Plugin prepares JSON payload A bound action plugin retrieves all project data and converts it into a clean JSON payload for PDF generation. 3] Azure Function generates PDF The Azure Function processes the JSON and generates a formatted PDF, returning it as a Base64 string. 4] SharePoint Integration The generated PDF is automatically stored in the associated SharePoint document location linked to the project. This ensures centralized document management, version control, and easy access for stakeholders directly within the project workspace. 5] Portal PDF Preview The Base64 PDF is rendered directly in the portal using an iframe, allowing instant preview and download. Video: End-to-end implementation of real-time PDF report generation. 5. Business Impact 100% success rate — zero failures post deployment Under 15 seconds report generation time No infrastructure — fully serverless Zero authentication failures Faster iteration for report updates Project managers can now confidently generate reports during live client meetings. 6. FAQs Why not fix the SSRS authentication issue instead of replacing SSRS entirely? The authentication failures were a structural consequence of traversing multiple service boundaries in an environment with strict Defender for Cloud Apps session policies. Fixing them would have required either relaxing those policies — which the client’s security posture did not permit — or re-architecting the data retrieval to stay inside the platform, which is exactly what the bound action approach achieves. Replacing SSRS also removed a separate infrastructure dependency and gave the client full control over report formatting in code. Can this pattern be reused for other document types in Dynamics 365? Yes. The Azure Function App’s renderer is data-driven — it consumes a JSON payload and builds tables from whatever keys are present. The Dynamics 365 plugin can be adapted to query any entity and produce an equivalent payload. CloudFronts has applied the same pattern to inspection records, summary reports, and client-facing status documents across Professional Services and Manufacturing implementations. Does this work for environments without Microsoft Defender for Cloud Apps? Yes. The architectural benefits — synchronous generation, serverless PDF rendering, no SSRS infrastructure, and in-browser preview — apply regardless of the security layer on the environment. 7. Conclusion Replacing SSRS with an Azure Function App-based PDF renderer resolved both the reliability and authentication problems in a single architectural shift, delivering instant, professional-quality Project Status Reports from a Microsoft Power Pages portal with no legacy reporting infrastructure to maintain. The key lesson from this project is that keeping authentication within the Dynamics 365 service layer — rather than bridging to external systems — eliminates an entire category of environment-specific failures that are otherwise very difficult to diagnose and fix. By keeping authentication within Dynamics 365 and leveraging serverless architecture, the solution delivers instant, high-quality reports without infrastructure overhead. This approach demonstrates how modern cloud-native patterns can eliminate entire classes of system failures while improving user experience dramatically. Ready to modernise document generation in your Dynamics 365 environment?CloudFronts builds scalable Power Platform and Dynamics 365 solutions that replace legacy reporting infrastructure and automate document workflows. Reach out at transform@cloudfronts.com. Shashank Keny Associate Consultant · CloudFronts Shashank Keny is an Associate Consultant at CloudFronts with 1.5+ years of experience in cloud, data, and business applications. He specializes in building scalable, API-driven architectures and integrating enterprise systems across the Microsoft ecosystem. He is a Certified Databricks Data Engineer with hands-on experience in Dynamics 365 Project Operations and Dynamics 365 Sales, along with delivering business intelligence solutions using Power BI. His expertise also extends to modern AI solutions, including building custom copilots and implementing intelligent applications using Azure AI Foundry. Passionate about solving real-world business challenges through data and AI, he focuses on delivering efficient, scalable, and production-ready solutions. Experience: 1.5+ years Certification: Databricks Certified Data Engineer Specialization: Dynamics 365 Project Operations, Power BI, Azure Integrations, AI Solutions View LinkedIn Profile