AI in ERP

GitHub Copilot is an AI peer programming tool that helps you write code faster and smarter. It can suggest code completions,, generate code snippets, and even write entire functions for you. GitHub Copilot works with a variety of languages and frameworks, and it can learn from your own code and preferences. By installing GitHub Copilot in VS Code or Visual Studio, you can leverage the power of AI to enhance your coding experience and productivity. Prerequisites Before you can install GitHub Copilot in Visual Studio, you need to have the following: A GitHub account. (sign up for free at github.com ) An active GitHub Copilot subscription (Individual, Business, or Enterprise). VS Code installed or Visual Studio 2022 17.6 or later installed. Installation To install GitHub Copilot, open VS Code and go to the Extensions tab. Search for GitHub Copilot. When you install Copilot in Visual Studio Code, you get two extensions: GitHub Copilot - Provides inline coding suggestions as you type. ...

AI tools and agents are no longer optional. They’ve become embedded in how employees and developers work every day. The question is no longer if your teams will use them- it’s how safely they’ll do it. [Image reference: AI Tools: Navigating the New Professional Landscape by Vicki Reyzelman] The Risk of "Free" AI Tools Organizations must recognize the inherent dangers of allowing employees to rely on publicly available AI platforms such as ChatGPT or Google Gemini. Under the pressure of deadlines and workload, employees may inadvertently copy and paste confidential information into these tools. Proprietary strategies, source code, and intellectual property can be transmitted outside the organization’s secure environment. These disclosures occur silently, without alerts or oversight, leaving leadership unaware until the damage is irreversible. The risk of loss of control is Permanent. Once confidential information enters a public AI model, it cannot be retrieved or contained. C...

The MSSQL Extension for Visual Studio Code is designed to empower developers by providing a seamless and modern database development experience. The goal is to make SQL development more productive and intuitive by integrating essential features such as schema management, query execution, and AI-powered assistance. Agents Inside VS Code One of the most underrated strengths of the MSSQL Extension is how it leverages agents directly within Visual Studio Code. This isn’t just about running queries—it’s about having intelligent helpers embedded in your workflow. Write Queries Faster: Agents can scaffold queries from natural language, explain stored procedures, and even suggest optimizations. Instead of memorizing syntax, you focus on intent, and the agent translates it into SQL. Spot Performance Bottlenecks: Agents don’t just execute queries—they help you understand them. With execution plan insights and AI-driven recommendations, you can identify bottlenecks like slow joins or missing ind...

Licensing in Dynamics 365 Finance & Supply Chain Management  (D365 FSCM) has evolved from a static, menu-item-based model to a dynamic, priority-driven framework. Refer to my previous blog  License Mapping on Menu Items  to understand the new multi-license mapping structure on menu items Each license type in D365 FSCM is now assigned a priority score, which determines how licensing is applied when users access multiple securable objects. The higher the priority score, the more comprehensive (and costly) the license. The system evaluates the highest-priority license required based on the user’s role and access level. This means licensing is no longer just about what a user touches—it’s about how their role is structured and which license tier their role access escalates to.  What happens if a user has multiple security roles? The highest license requirement applies. In case security roles span multiple workloads, this user requires more than one full user license....

Licensing in enterprise systems has long been a game of mapping menu items to license types, ticking boxes, and hoping your role design didn’t trigger unexpected costs. But with the 2025 updates to Dynamics 365 Finance and Operations, Microsoft has flipped the script—ushering in a smarter, more flexible model that reflects how users actually work. Let’s break it down. In the legacy model, each menu item was tied to a single license type. For instance, if a user accessed MenuItemA that had a Finance license type on it, they needed a Finance license. If they accessed MenuItemB with SCM assigned on it, they needed SCM. Simple? Yes. But also rigid, prone to over-licensing, and blind to real-world role overlap. Example:  This model treated licensing like a static blueprint—ignoring the nuance of blended roles, attach licenses, and shared responsibilities across departments. Fast forward to 2025. Microsoft’s new licensing logic is object-level, dynamic, and context-aware. Now, a single m...

I recently came across the Electronic Signatures feature in Microsoft Dynamics 365 Finance and Operations (D365FO) that enables secure authorization of critical changes or actions within the system. Traditionally, security roles are used to manage access and control edits, but electronic signatures provide an alternative layer of control—especially for regulated industries or audit-sensitive environments. What is an electronic signature? An electronic signature confirms the identity of a person who is about to start or approve a computing process. In some industries, an electronic signature is as legally binding as a handwritten signature. You can use electronic signatures for critical business processes. Some processes have built-in electronic signature capabilities. You can also create custom signature requirements for any database table and field. Electronic signatures have built-in digital signature functionality. Every user who signs documents must obtain a valid cryptographic cer...

Getting started with Microsoft 365 Copilot agents can transform how your organization leverages AI to streamline workflows, enhance productivity, and empower employees to build intelligent solutions. This blog outlines a phased approach—starting with forming a champion team, training employees, and scaling deployment—to help your organization confidently adopt Copilot Studio’s Agent Builder.  To start empowering employees to create and manage Microsoft 365 Copilot agents securely at scale, it is recommended that a three-phase approach is taken:  Form an "agent adoption champion" team within IT and try out Agent Builder. Train employees to build agents with Agent Builder. Provide selected employees with access to Agent Builder and set up pay-go meters.  Phase I – Form a team Step 1: Create an "agent adoption champion" team  Select a group of early adopters (your "champion team”) to explore building agents using Microsoft Copilot Studio Agent Builder in Microsoft...