Inc. 5000 Fastest-Growing Company in the US

inc-5000-logo
Ascent Innovations Logo
Schedule
by
Microsoft Dynamics 365 Finance & Operations – Deployment options

Microsoft Dynamics 365 Finance & Operations – Deployment options Table of Contents Microsoft Dynamics 365 Finance & Operations – Deployment options You can now deploy Microsoft Dynamics 365 for Finance and Operations in the cloud or on-premises. Cloud deployments offer a software system that is fully managed by Microsoft, while on-premises deployments as name suggests, are deployed locally within a customer’s data center.   Important: On-premises deployments of Microsoft Dynamics 365 for Finance and Operations are NOT supported on any public cloud infrastructure, including Azure.   The following table provides a comparison of the capabilities provided by the two deployment options. Why cloud? Cloud deployments provide a cloud service that is easy to scale up or down as needed, as well as data centers that are fully managed by Microsoft. The time spent implementing Finance and Operations can be significantly shortened, fewer customizations may be required, and the costs of IT hardware and infrastructure are lower.   Cloud deployments include high availability, disaster recovery, sandbox environments, and application lifecycle management combined with cloud-based systems of intelligence, infrastructure, compute, and database services in a single offering. When needed, data failover in the cloud, automated deployment and continuous updates, and elastic compute capacity are available. A cloud deployment also provides data aggregation, financial reporting, and intelligence.   The cloud service provides customers with the greatest value, the broadest range of functionality, the best application lifecycle experience, the easiest and broadest integration with Microsoft Azure services, the best option for business insights and intelligence, and the most value for customers’ technology investments. Why on-premises? With an on-premises deployment, existing data center investments can be leveraged. Customers can also configure their enterprise preferences to meet their needs. The regulatory and compliance requirements of their business, Comply with data sovereignty rules in regions where there are no Azure Data Centers, or Ensure business continuity in areas with limited public infrastructure. A customer’s business data and processes are disconnected from the cloud and are stored and run locally in the customer’s or their partner’s data center. Some connectivity is required for system management and updates which are enabled through Microsoft Dynamics Lifecycle Services (LCS), a cloud-based application lifecycle management service. Customer data that is related to the configuration and application customization may be stored in the cloud.   For customers who choose to run Finance and Operations in their own data center, the on-premises deployment option will have a similar user-interface and application functionality as other deployment options. However, customers must take on the following responsibilities: Stand up their own infrastructure. Configure their own high-availability and disaster recovery solutions. Stand up sandbox environments. Manage their infrastructure, including scheduling operating system updates. The additional costs to deploy and manage these capabilities might lead to higher deployment costs and a greater Total Cost of Ownership (TCO). Tools for deploying the Finance and Operations software and updates will be available to partners and customers via Lifecycle Services. Unlike the cloud deployment option, Advanced Analytics and Azure Machine Learning services are not included in the on-premises deployment option. Talk to us regarding TCO comparison depending on your current and future state of your infrastructure. Features not implemented in on-premises deployments There are some features that have not yet been implemented and planned to be part of future releases. However, there are few features that are not intended for on-premise deployments. Features not yet implemented The following features have not yet been implemented in on-premises deployments. These features have not been deprecated. If these features are critical to your on-premises deployment, please let Microsoft know to help in prioritizing on the Dynamics 365 Application Ideas site.   Features not planned for on-premises deployments The following features are not intended for use in on-premises deployments. There are no plans to implement these features in on-premises deployments.   Author: Abdul Hafiz Enterprise Solution Architect Icon-linkedin Latest Posts You might also like:

by
All-in-one-Deployable Package (ADP)

All-in-one-Deployable Package (ADP) Table of Contents All-in-one-Deployable Package (ADP) Introduction Microsoft has recently released a feature called All-in-one-Deployable Package (ADP).   This is designed to eliminate deployment errors that many programmers deal with and improve deployment efficiency and reliability.   We analyzed how it will impact our projects and how this concept plays a vital role in deployment process. This blog series is as result of our analysis . We have taken a business scenario to explain how package movement should be carried out before ADP and after ADP. Scenario: Current model architecture On an enhancement in Human resource management solution, we have created two new models: Time and Attendance and PTO Management models Time and Attendance Let’s consider Time and attendance model containing elements with respect to employee’s working hours, clock-in, clock-out and time taken on breaks. Table -ASCTimeAndAttendanceTable Form – ASCTimeAndAttendanceForm Class – ASCTimeAndAttendanceClass PTO Management Let’s consider PTO (Personal Time Off) Management or Leave Management model with elements handling the employee’s time-off requests, approvals and the utilization. Table – ASCLeaveRequestTable Form – ASCLeaveRequestForm Class – ASCLeaveRequestClass Let us see how package deployment is done currently and how package deployment should be done after introduction to All in one deployable package (ADP). To make this blog series clear, we have split up this blog content into two-part series: Part-1: Current deployment scenarios (Before ADP) Part-2: Deployment approach with ADP Part-1. Current deployment scenarios (Before ADP) How model movement is done currently (Before ADP) In order to deploy our code and customizations to a runtime environment (demo, sandbox, production), we must create a deployable package. Currently deployments are carried out in two ways: Package generation from Visual Studio Package generation from DevOps Package generation from Visual Studio In order to deploy our code and customizations to a runtime environment (demo, sandbox, production), we have created a deployable package of our models through Visual Studio Dev tools (Dynamics 365 Menu > Create Deployable package) and then we would upload to the Asset library in LCS. Package generation from DevOps Azure DevOps provides pipelines that can be used to automate builds. There are two types of pipelines: YML and Classic. We have followed the classic pipeline which is Team Foundation Version Control (TFVC).   We have installed the NuGet package, built solution/projects, then the new deployable package would be created. We can then publish the deployable package artifact as build output. If you are following package generation from DevOps, there is no impact of ADP as that packages the entire models at all times. How it works? Initial deployment to Production For the initial deployment process, we have selected all the models i.e. Time and Attendance and Leave Management. So, our deployable package contains both the models. Going further to add the below changes which we have explained deployment-wise. Deployment -1: Changes in single model We have created a new inquiry form to list down employee’s clock-in and clock-out information.   For this, we have created a new form ASCTimeAndAttendanceInquiryForm with existing table ASCTimeAndAttendanceTable as data source.   Our deployable package contains only Time and Attendance model now. Deployment -2: Change in multiple models Change Request – 1A request came in to add a new feature for Work From Home maintenance. In order to accommodate this, we have created a new form ASCTimeAndAttendanceWFHForm with new table ASCTimeAndAttendanceWFHTable.   Change Request – 2A new validation “Employee cannot take more than 2 days of Optional leave in a year” should be added when an employee creates new leave request.   For this, we have added validation in the ValidateWrite of the ASCLeaveRequestTable.   Both these models would be a part of deployable package.  Now, in Part-2, let us see how the same scenario can be handled with ADP approach. Part-2: All in one deployable package What is ADP? In this concept, we create a deployable package with all the customized models instead of the specific model(s) with our customizations.   We follow same set of procedures here, but we would be selecting all our customized models every time we create a new deployable package regardless of changes being done in the model elements or not.   So, an ADP All-in-one Deployable Package is a software deployable package that contains all the models and binaries that you currently have in an environment. How it works? Let’s consider the same set of scenarios we explained in Part-1and try to implement them with respect to ADP (All in one data packages) Initial deployment /Existing deployment For the initial deployment process, we have selected all the models i.e. Time and Attendanceand Leave Management. So, our deployment package contains both the models. Deployment – 1: Changes in single model For the initial deployment process, we have selected all the models i.e. Time and Attendanceand Leave Management. So, our deployment package contains both the models. Deployment – 2: Change in multiple models Change – 1   Employee’s work from home details listed in a new form ASCTimeAndAttendanceWFH with new table ASCTimeAndAttendanceWFHTable.   Change – 2 A new validation “Employee cannot avail more than 2 days of Optional leave in a year” should be added when an employee creates new leave request.   For this, we have added validation in the ValidateWrite of the ASCLeaveRequestTable.   As part of deployable package creation, both these models would be a part of it. Benefits of following the ADP model deployment approach This approach helps the multi-member development teams, this process becomes even more important when dealing with multiple sprints, releasing features in parallel as well in Support mode.   This concept helps developers tremendously by drastically reducing the risk of deployment errors and helps with the overall project efficiency.   Some of the common issues multi-member development teams face: Consider we already moved our deployable package containing Time and Attendance and Leave Management to Test environment. We have modified an object ASCLeaveRequestTable in the model Leave Management, based on a Change Request. If we create deployable package with only Leave management model. When this package gets applied to the Test … Read more

by
Microsoft Dynamics 365 for Finance and Operations begin One Version era

Microsoft Dynamics 365 for Finance and Operations begin One Version era Table of Contents Microsoft Dynamics 365 for Finance and Operations begin One Version era Microsoft Dynamics 365 for Finance and Operations has entered the so-called One Version era, in which customers will say goodbye to traditional ERP upgrades and apply an ongoing and mandatory series of smaller updates to their systems on a monthly to quarterly basis.  Microsoft has made the case for the transition, hoping to convince current Finance and Operations (D365FO) customers that the new approach will benefit them in the long-run, and that Dynamics AX customers that upgrade will never have to endure another upgrade project in the future. This is in line with Microsoft Office 365 Upgrade philosophy.   The transition comes at a time when D365FO is growing and adapted at a far higher pace than ever before in the ERP product family.   Customer mix 30% Enterprise and 70% midsize. 77% are New Implementations vs. 23 percent Upgrades.   Functional usage in D365FO production environments Finance: 98 percent Supply chain management: 82 percent SCM Human capital management: 81 percent Warehouse Management: 63 percent Project Accounting: 16 percent   Another reason is due to improved upgrade and migration tools and the approaching end of life of various versions of AX.   The current model calls for customers to apply at least one update every three months, meaning a customer can skip two monthly updates but then must deploy the next one. For each update the customer can specify the week, day (Saturday or Sunday for most, but some industries like retail are opting for mid-week), and the time.   Another validation step for new updates will be the Release Validation Program, which brings customer-specific projects into an environment where they can be validated ahead of a release. Test results are checked by Microsoft and any defects are shared with the customer. This program requires sharing code and data with a team at Microsoft. Customer responsibilities and response The users historically have been unwilling to make frequent updates when they knew a system was working well, but One Version forces them to do just that. In theory, that risk from more frequent updates should be mitigated by two factors. First, early adopters will be getting these updates ahead of the majority of customers, and those teams should detect and report problems a month or more in advance of more conservative customers. Second, partners will be seeing the same update across all customers, meaning they should be able to predict the most common issues in any given month or quarter across all their D365FO clients.   The users did not raise significant concerns or questions in response to his guidance, which helped Microsoft propel in this direction at a faster pace. The business leaders have adopted to this model of SaaS and see the value in the long run.   Microsoft is also actively investigating customer needs and have engaged an independent consulting firm to report back to Microsoft on what customers say they need in various scenarios and industries (for example, FDA-regulated manufacturers, public sector regulations, ITAR compliance). Microsoft has already heard feedback from the community, which initially raised concerns, and is now in the process of adapting these principles. Author: Abdul Hafiz Enterprise Solution Architect Icon-linkedin Latest Posts You might also like:

by
Getting D365 Right the First Time: Why Fundamentals Matter

Getting D365 Right the First Time: Why Fundamentals Matter Table of Contents Getting D365 Right the First Time: Why Fundamentals Matter ERP implementations are among the hardest things a business can do. They touch every part of an organization, bringing both transformation and disruption. The difference between success and failure often comes down to one thing: getting the fundamentals right. I founded Ascent Innovations because I’ve seen firsthand what happens when an ERP project doesn’t have the right leadership, expertise, and structure behind it. The truth is, a D365 implementation is not the time for trial and error. It’s like choosing a surgeon for heart or brain surgery—you want to know the expert you trusted will be there, not handing things off while they go golfing. At Ascent, we don’t just advise from the sidelines. I personally hire, train, and work alongside our team, ensuring that every project benefits from real experience—not just certification exam course prep level knowledge. Why the Details Matter D365 should be a game-changer for your business, but only if the foundation is solid. That foundation comes down to four things: Data – If your data is wrong, everything built on top of it will be wrong. Processes – ERP should support your business, not force you into workarounds. Integration – Systems need to talk to each other, otherwise efficiency breaks down. Analytics – If you can’t trust your reporting, you can’t make informed decisions. If any of these are overlooked, rushed, or mishandled, the result is the same—delays, budget overruns, and a system that doesn’t deliver what was promised. The 5 Most Critical D365 Implementation Fundamentals 1. Data Accuracy and Migration Your ERP is only as good as the data inside it. Messy, incomplete, or inaccurate data leads to incorrect reports, broken workflows, and user frustration. What Needs to Happen Data cleansing before migration—not after problems surface. Structured mapping to ensure all critical relationships stay intact. Rigorous validation to prevent surprises post-go live. Data translations and transformation for accuracy and efficiency. 2. Business Process Alignment ERP success isn’t just about technology—it’s about how your business operates. If key workflows aren’t well-defined and integrated, the system will never fully support your team. What we focus on: End-to-end process analysis – Understanding how departments interact. Fit-gap assessments – Identifying where D365 meets your needs and where adjustments are required. Thoughtful customization – Only where it adds business value, not adding complexity. 3. System Integration An ERP does not operate in isolation. It needs to connect seamlessly with everything from CRM and eCommerce to payroll, warehouse management and other external systems. Where failures happen: Incomplete integration planning leading to manual workarounds. Weak data mapping that creates reporting discrepancies. Delayed testing that uncovers issues too late. How we solve it: Early-stage integration planning to map system dependencies. Test-driven validation to ensure real-world functionality before go-live. Scalable architecture that grows with your business. 4. Reporting and Analytics Decisions should be based on real-time, accurate data. If leadership cannot trust the numbers coming from the system, they will revert to spreadsheets—and the entire ERP investment loses its value. What matters: Finance and supply chain reports need to be accurate from day one. Role-based dashboards so each team sees relevant insights. Data governance policies to prevent long-term reporting issues. 5. User Readiness and Training Even the best system fails if people do not know how to use it. Training is not an afterthought—it is a core part of success. Our approach: Power users trained early to act as internal champions. Train the trainers – power users will become the go-to users for their respective department as first level support Practical, role-specific training instead of generic system overviews. Post-go-live support to ensure long-term adoption. Why Leadership and Experience Matter D365 implementation is not a textbook exercise. It’s a complex transformation that requires leadership, foresight, and real experience. This is why I still practice, mentor, and work alongside my team—because when problems arise, leadership should be in the room solving them, not just checking in. At Ascent Innovations, we believe ERP should be predictable, rewarding, and successful—but that only happens when the right fundamentals are in place from the start. Let’s Have a Conversation I encourage you to explore our website and see how we approach D365 projects, but there is no substitute for a real conversation. If you are considering implementation, or if your current project is not where it should be, we would welcome a conversation. Even if, for whatever reason, you do not choose us—and we hope you do—our mission is always your success. About the Author Sohena Hafiz is the Founder and CEO of Ascent Innovations, with 20 years of experience in Microsoft Dynamics and 16 years leading ERP implementations. She has been directly involved in 50+ ERP projects, including 30+ in D365, across industries like industrial equipment, steel fabrication, food manufacturing, banking, recycling, retail, and the public sector. Sohena Hafiz President Icon-linkedin Latest Posts You might also like:

by
Why Upgrade from AX to D365?

Why Upgrade from AX to Dynamics 365 Finance & Operations? Table of Contents Why Upgrade from AX to Dynamics 365 Finance & Operations? For years, Dynamics AX has been a reliable ERP system, providing robust financial and operational capabilities for mid-sized and large enterprises. But as business landscapes evolve, so do the tools required to stay competitive. Microsoft’s Dynamics 365 Finance & Operations (D365 F&O) represents the next generation of enterprise technology—designed to enhance agility, intelligence, and scalability.   Upgrading from AX to D365 F&O is not just about moving to a newer system—it’s about enabling new business capabilities that drive revenue growth, streamline operations, and improve decision-making. While your organization must be in the right cycle for migration, this blog focuses on the advantages of making the move when the time is right. Why Upgrade? Predictive Forecasting for Demand & Materials Planning Accurate forecasting is critical to optimizing supply chains, managing costs, and meeting customer demand. In AX, forecasting is largely manual and based on historical data alone. With D365, AI-driven analytics enhance demand planning, ensuring better alignment between procurement, production, and sales. How D365 Helps: Uses AI-powered insights to improve demand forecasts based on real-time market trends Reduces last-minute production changes and raw material shortages Prevents surplus inventory, minimizing waste and improving cash flow Enables supply chain agility with rapid response to market fluctuations Optimized Financial Management & Reporting D365 Finance integrates financial management, supply chain oversight, and real-time analytics, providing a holistic view of financial health. Unlike AX, where reporting is often fragmented across different modules, D365 eliminates process gaps, enabling real-time performance tracking. How D365 Helps: Provides a unified view of financials across business functions Automates reconciliations and month-end close processes Improves cost tracking with real-time visibility into spending and profitability Enhances FP&A capabilities with AI-powered scenario modeling Cost Accounting & Product Costing Managing costs effectively is essential for profitability, and D365 Finance provides deeper insights into cost structures. Businesses can analyze COGS, SG&A, and profitability per product, allowing for better strategic decision-making. How D365 Helps: Centralizes cost accounting across ledgers, sub-ledgers, and budgets Empowers finance teams to track cost variances and make data-driven adjustments Identifies high-margin products and underperforming SKUs for optimization Improves financial planning by aligning cost analysis with operational goals Modern Customer & Partner Portals D365 provides self-service portals that allow customers and business partners to access real-time data on orders, invoices, and shipments. Unlike AX, where external access often requires custom development, D365 natively supports secure, interactive portals that improve collaboration and efficiency. How D365 Helps: Enhances customer experience with self-service access to real-time information Reduces manual workload by automating order tracking and invoice processing Improves supplier collaboration with better visibility into procurement and payments AI-Powered Cash Flow Forecasting One of the most significant advantages of D365 Finance is its predictive cash flow management. Unlike AX, which requires manual tracking and reconciliation, D365 leverages AI to automate and enhance cash flow forecasting. How D365 Helps: Provides real-time cash flow projections, reducing reliance on static reports Uses machine learning to predict receivables and payables trends Helps businesses optimize working capital for reinvestment in growth initiatives Supply Chain Resilience & Process Automation D365 Supply Chain Management introduces end-to-end visibility and automation, allowing businesses to optimize procurement, warehousing, and logistics. AX users often rely on third-party solutions for these capabilities, while D365 integrates them natively. How D365 Helps: Automates warehouse operations with real-time inventory tracking Improves production scheduling to minimize bottlenecks and reduce lead times Enhances supplier risk management with AI-driven insights Enables seamless collaboration across supply chain functions Gaining the Competitive Edge Upgrading to D365 F&O isn’t just about moving to a cloud-based system—it’s about gaining a competitive advantage through automation, AI, and real-time data. Businesses that embrace these capabilities can increase revenue per employee by allowing their teams to focus on high-value strategic planning, management, and execution. How D365 Helps Organizations Scale & Grow: AI and automation reduce manual effort, freeing teams to focus on strategy Real-time insights improve decision-making, helping companies pivot faster Streamlined operations allow businesses to scale without adding unnecessary overhead Competitive laggards will struggle to catch up as early adopters leverage these capabilities In today’s fast-moving market, those who modernize first will lead. Companies still relying on AX risk falling behind as their competitors adopt AI-driven forecasting, automated workflows, and real-time analytics to optimize their operations. The Business Impact The ROI of modernizing your business isn’t just about technology—it’s about how your people leverage it. The capabilities we’ve described don’t just streamline processes; they empower your teams to shift from reactive problem-solving to proactive decision-making that drives measurable business outcomes.   Instead of constantly firefighting operational issues, your employees can focus on high-value strategic planning, collaboration, and execution. Real-time insights ensure that risks and opportunities don’t catch you off guard—they appear on your radar as they emerge, giving you the time to respond with precision and confidence.   With D365 the ROI is in your hands. The future belongs to those who can harness their data, empower their teams, and take full control of their business outcomes. About the Author Sohena Hafiz is a D365 strategist with 20 years of experience in Microsoft ERPs. As CEO and founder of Ascent Innovations, she provides hands-on leadership, guiding delivery teams and clients while overseeing Ascent’s largest customer engagements to ensure strategic execution and business impact. Sohena Hafiz President Icon-linkedin Latest Posts You might also like: