M365.FM - Modern work, security, and productivity with Microsoft 365

Mirko Peters - Founder of m365.fm, m365.show and m365con.net

Welcome to the M365.FM — your essential podcast for everything Microsoft 365, Azure, and beyond. Join us as we explore the latest developments across Power BI, Power Platform, Microsoft Teams, Viva, Fabric, Purview, Security, and the entire Microsoft ecosystem. Each episode delivers expert insights, real-world use cases, best practices, and interviews with industry leaders to help you stay ahead in the fast-moving world of cloud, collaboration, and data innovation. Whether you're an IT professional, business leader, developer, or data enthusiast, the M365.FM brings the knowledge, trends, and strategies you need to thrive in the modern digital workplace. Tune in, level up, and make the most of everything Microsoft has to offer. M365.FM is part of the M365-Show Network. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

  1. 14h ago

    GitHub Copilot, Clean Context, Automated Testing & AI Coding Agents with Lars Gyrup Brink Nielsen [MVP]

    AI-assisted development is moving beyond autocomplete and chat. Modern AI coding agents can inspect repositories, modify files, run tests, analyze failures, create pull requests, and execute increasingly complex development tasks. In this episode of the M365 FM Podcast, Mirko Peters talks with Microsoft MVP Lars Gyrup Brink Nielsen about GitHub Copilot, AI coding agents, developer experience, automated testing, TypeScript, JavaScript, Nx, monorepos, Polygraph, GitHub Actions, Playwright, and the architectural foundations required to make agentic software engineering work at enterprise scale. FROM AI ASSISTANCE TO AI CODING AGENTS For the last few years, AI development tools have primarily helped developers generate code, autocomplete functions, answer technical questions, and accelerate individual programming tasks. Agentic engineering changes that model. AI coding agents can potentially inspect an existing repository, understand an issue, modify multiple files, run automated tests, analyze failures, make corrections, and prepare a pull request. That changes the central question from "Can AI generate code?" to "Can AI safely perform engineering work inside a real software architecture?" MEET LARS GYRUP BRINK NIELSEN Lars Gyrup Brink Nielsen is a Microsoft MVP in Developer Technologies, author, international speaker, tech writer, open-source maintainer, community organizer, and former GitHub Star. His experience spans frontend development, cloud-native systems, developer experience, automated testing, continuous delivery, deployment, and open-source software. He has also worked with GitHub Copilot since its early days and has spent more than a year experimenting with AI coding agents in open-source development. WHY DEVELOPER EXPERIENCE MATTERS Developer experience is fundamentally about removing friction from software development. That includes choosing and integrating development frameworks, testing tools, build systems, CI pipelines, documentation, reusable packages, development environments, architectural standards, and automation. Lars contrasts modern developer tooling with earlier workflows involving FTP deployments, directly editing production systems, shared ZIP files, and environments without proper source control. Modern developer experience replaces these fragile processes with repeatable, automated, and verifiable workflows. ARCHITECTURE SHOULD BE ENFORCED Documentation alone isn't enough for large software architectures. Lars explains how tooling such as Nx can attach metadata to projects and enforce architectural boundaries. Organizations can define which types of projects may depend on other projects and use linting rules to automatically detect violations. Generators can also scaffold components, services, projects, tests, and configurations according to organizational standards. This becomes particularly important with AI coding agents. Instead of expecting an agent to remember every architectural rule, organizations can make those rules automatically enforceable. MONOREPOS EXPLAINED A monorepo stores multiple projects or systems inside a shared source-control repository. Microservices and micro-frontends don't necessarily require separate repositories. They can exist within one monorepo while still being independently built and deployed. The advantage is that dependencies between projects become easier to understand and changes spanning multiple systems can be tested together. However, Lars also explains that moving hundreds or thousands of developers from established repositories into one monorepo can be extremely difficult organizationally. MONOREPO VS MULTIPLE REPOSITORIES Separate repositories don't eliminate dependencies between teams. They simply manage those dependencies differently. When two teams maintain dependent systems in different repositories, changes can require coordination, separate environments, cross-repository testing, and synchronized deployments. A monorepo can make those dependencies more visible because the relevant source code exists within the same repository. The larger challenge is often organizational rather than technical: teams still need to communicate, coordinate ownership, and manage dependencies regardless of repository strategy. WHAT IS NX? Nx is a development toolchain that helps teams manage complex codebases, project dependencies, tasks, testing, builds, linting, generators, and development workflows. Lars explains how Nx has evolved beyond its earlier JavaScript-focused roots. It can integrate development tools, automate migrations, understand project relationships, orchestrate tasks, and support multiple technologies. It can also determine which projects are actually affected by a change rather than unnecessarily rebuilding or retesting an entire large codebase. CACHING CAN DRAMATICALLY ACCELERATE DEVELOPMENT Large codebases can contain hundreds of projects and enormous test suites. Repeatedly running every build, test, linting operation, and compilation task wastes significant developer and CI time. Nx can cache task results. If the relevant source files and dependencies haven't changed, developers can reuse previous results instead of executing the same work again. Remote caching can also allow teams and CI systems to share those results. For AI agents, faster verification becomes especially valuable because an agent may repeatedly modify, test, inspect, and correct code during a single task.  POLYGRAPH AND MULTI-REPOSITORY AI AGENTS Not every enterprise can move hundreds of existing repositories into a monorepo. Lars discusses Polygraph as a newer approach for helping AI coding agents operate across multiple related repositories. Instead of an AI coding session being isolated to one repository, Polygraph can provide a harness around multiple repositories and their dependencies. This can allow an agent to work across frontend, backend, microservice, and other repositories during the same development task and potentially prepare coordinated pull requests across those systems. GITHUB ACTIONS AND CONTINUOUS INTEGRATION Automation is a major part of the development environment discussed throughout the episode. GitHub Actions can provide the CI foundation for building, testing, validating, and deploying changes. Nx can work alongside CI workflows and delegate tasks through its own cloud capabilities. During the rapid-fire round, Lars gives GitHub Actions a particularly strong endorsement, calling it the best CI system. PLAYWRIGHT FOR AUTOMATED TESTING Automated verification becomes more important as AI writes a larger percentage of software. When asked to choose between Playwright and Cypress during the rapid-fire round, Lars chooses Playwright. The broader point is significant for agentic development: organizations need reliable automated feedback loops. If an agent changes code, it needs tools capable of determining whether those changes still satisfy the expected behavior.ㅤ GITHUB COPILOT AND THE AGENTIC SHIFT Lars was an early GitHub Copilot user through his involvement with the GitHub Stars program and provided feedback during Copilot's earlier development. His development workflow has now moved significantly beyond traditional Copilot autocomplete. He explains that he rarely writes code manually anymore and instead instructs coding agents to perform much of the implementation work. The challenge increasingly becomes reviewing and ensuring the quality of the code produced by those agents. CONTEXT IS THE NEW ENGINEERING PROBLEM An AI model may understand TypeScript, JavaScript, Angular, React, .NET, testing frameworks, and popular development tools from its training. What it doesn't automatically understand is your organization. Every large software environment contains internal naming conventions, architectural decisions, team standards, project-specific rules, historical constraints, and unique development practices. Those rules need to become accessible to AI agents through mechanisms such as agent instructions, skills, automated checks, architectural boundaries, and repository-specific context. CLEAN CONTEXT FOR AI CODING AGENTS Giving an AI agent more information isn't automatically better. Large repositories can contain enormous amounts of source code, documentation, configuration, legacy decisions, and irrelevant files. The challenge is providing the agent with the information required for its current task without overwhelming its working context. Development tooling, dependency graphs, repository structures, project metadata, agent instructions, and automated validation can help narrow that context. The objective is to give agents enough information to make architecturally correct decisions rather than merely locally correct code changes. CODIFY YOUR TEAM STANDARDS FOR AI Organizations don't necessarily need to fine-tune an AI model on their complete private codebase. Lars points instead toward codifying team-specific knowledge into agent skills and instruction files such as AGENTS.md. These instructions can explain how a particular team performs common tasks, which conventions should be followed, and how the codebase should be approached. This transforms knowledge that previously existed mainly inside experienced developers' heads into context AI coding agents can use. ㅤ Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

    GitHub Copilot, Clean Context, Automated Testing & AI Coding Agents with Lars Gyrup Brink Nielsen [MVP]
  2. 15h ago

    Dynamics 365 Asset Management - Simply Explained

    A conveyor stops in the middle of a shift, a forklift won't start, or a pump suddenly begins leaking. Before anyone can repair the equipment, the business needs answers: Who is responsible? When was it last serviced? Which parts are required? What happened during the previous repair? Dynamics 365 Asset Management provides one central place for this information. In this episode of M365 FM, Mirko Peters explains how Dynamics 365 Asset Management helps organizations track physical equipment, preventive maintenance, work orders, spare parts, costs, service history, functional locations, condition-based maintenance, and connected maintenance processes. WHAT IS DYNAMICS 365 ASSET MANAGEMENT? Dynamics 365 Asset Management is part of Dynamics 365 Supply Chain Management and focuses on the physical equipment businesses rely on every day. That could include production machines, conveyor belts, motors, pumps, forklifts, trucks, generators, heating and cooling systems, and other equipment requiring regular inspection, servicing, or repair. Instead of maintenance information being distributed across spreadsheets, folders, emails, invoices, and individual employees' knowledge, Asset Management creates a shared record around the equipment and its maintenance history.  WHY PHYSICAL ASSETS BECOME A BUSINESS PROBLEM A machine doesn't only affect the maintenance department. When equipment fails, operations can lose production capacity, maintenance teams need to diagnose the fault, purchasing may need to urgently source replacement parts, and finance eventually receives the resulting costs. Emergency maintenance can become particularly expensive because organizations may need expedited shipping, urgent purchasing, overtime, or temporary workarounds. Dynamics 365 Asset Management connects these different parts of the maintenance story so teams can understand what happened and why money was spent. ㅤ THE ASSET RECORD Every piece of equipment can have its own digital asset record. The record can contain information such as the asset name, product or model number, serial number, description, technical details, and warranty information. This becomes particularly useful when several machines look almost identical but use different components, have different warranty periods, or require different maintenance procedures. Instead of relying on somebody remembering which machine is which, the asset record provides a consistent reference point. FUNCTIONAL LOCATIONS EXPLAINED Dynamics 365 Asset Management uses functional locations to describe where equipment performs its job. A functional location can represent a site, building, warehouse, workshop, production line, or another operational location. These locations can also form hierarchies. For example, an organization might have a plant containing a packing area, which contains a conveyor line, which contains individual motors, sensors, and rollers. When a motor fails, technicians therefore don't simply see a serial number. They can understand exactly where that motor operates and which wider process could be affected.  PARENT AND CHILD ASSET STRUCTURES Complex equipment frequently consists of smaller components that need their own maintenance history. Dynamics 365 can represent parent-and-child relationships between equipment and components. A conveyor can contain a motor, while the motor itself might contain another component requiring individual maintenance attention. This structure helps maintenance teams understand how individual assets relate to larger equipment and operational systems. ㅤ TRACKING EQUIPMENT AS IT MOVES Physical equipment doesn't necessarily remain in the same location forever. Forklifts can move between warehouses. Pumps can move from storage into buildings. Machines can be reassigned between production lines. Asset Management can track these movements through functional locations. This also matters financially because maintenance costs can follow the equipment to the location currently using it. Managers can therefore understand which plant, department, or operational area is responsible for the costs associated with an asset. BUILDING A COMPLETE SERVICE HISTORY The real value of an asset record grows over time. Inspections, repairs, replaced parts, technician notes, labor time, faults, downtime, and other maintenance information can become part of the equipment's history. A technician investigating a recurring problem can review previous repairs instead of starting from zero. The history might reveal that the same motor has been repaired several times, that a particular component repeatedly fails, or that an earlier technician identified something that needs additional monitoring. ASSET MANAGEMENT VS IT ASSET MANAGEMENT Dynamics 365 Asset Management focuses on physical operational equipment requiring maintenance, inspections, servicing, and repair. It isn't primarily designed for tracking office laptops, smartphones, or software licenses. Production machinery, vehicles, pumps, motors, building equipment, and similar physical assets create a different maintenance requirement because downtime, replacement parts, labor, inspections, and equipment condition all need to be managed over time. REACTIVE VS PREVENTIVE MAINTENANCE Reactive maintenance begins after something fails. The equipment stops, operations are affected, and the maintenance team needs to restore service as quickly as possible. Preventive maintenance attempts to perform appropriate maintenance before a small problem becomes an unexpected failure. Dynamics 365 Asset Management helps organizations plan recurring inspections, cleaning, lubrication, safety checks, testing, and replacement of components that wear out over time. MAINTENANCE PLANS Maintenance plans help organizations turn preventive maintenance into repeatable work. A forklift might require regular inspections of its brakes, tires, fluid levels, lights, and battery condition. A production line might require weekly sensor cleaning, monthly belt inspections, and component replacement after a particular amount of use. These tasks aren't dramatic individually, but performing them consistently can reduce the likelihood of equipment failing during critical operations. MAINTENANCE BASED ON EQUIPMENT USAGE Calendar schedules aren't always enough. Two identical machines might have very different workloads. One could operate for a single shift every day while another operates continuously. Technical readings such as running hours, distance traveled, temperature, pressure, or other measurements can provide additional information about when maintenance should occur. This allows organizations to combine scheduled maintenance with the actual usage and condition of equipment. MAINTENANCE ROUNDS Maintenance rounds provide technicians with planned routes or groups of inspections across multiple assets. Instead of treating every inspection as a separate activity, a technician can inspect related equipment during one routine visit. For example, someone could walk through a packing area checking several conveyor motors, listening for unusual sounds, inspecting fittings, and recording relevant technical readings. This creates a more consistent inspection process even when different technicians perform the work.  CONDITION-BASED MAINTENANCE Condition-based maintenance uses equipment measurements to identify when something may require attention. Imagine vibration readings from a conveyor motor gradually increasing over several weeks. The motor still operates, but the changing measurement indicates that something may be developing. When a reading crosses a threshold established by the organization, the maintenance team can investigate before the equipment necessarily fails. The objective isn't to perfectly predict every breakdown. It is to provide earlier warning and give maintenance teams more time to respond. FROM MAINTENANCE NEED TO WORK ORDER When maintenance becomes actual work, Dynamics 365 uses a work order. The work order acts as the job ticket connecting the problem, required activities, responsible workers, schedule, parts, safety instructions, labor, costs, and final outcome. Work orders can originate from scheduled maintenance, inspections, equipment breakdowns, or follow-up work identified by technicians. Regardless of the source, the work order turns a maintenance requirement into something that can be assigned, scheduled, tracked, completed, and reviewed. PLANNING THE MAINTENANCE JOB A work order can describe the job and the tasks required to complete it. For a conveyor motor showing unusual vibration, technicians might need to isolate the equipment, inspect the mounting, check bearings, complete the repair, test the machine, and return it to service. Checklists can help technicians perform required activities in the correct sequence. Safety instructions can also be associated with the work so requirements such as power isolation, protective equipment, or stopping moving equipment are visible during the job. SPARE PARTS AND INVENTORY Maintenance work frequently depends on replacement parts. A work order can identify required items such as bearings, filters, bolts, grease, or replacement motors. Because Asset Management connects with Dynamics 365 Supply Chain Management, teams can determine whether the required part is already available in inventory. If stock can't cover the requirement, purchasing can order the necessary item while keeping the reason for that purchase connected to the maintenance job. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

  3. 20h ago

    Dynamics 365 Dataverse Integration - Simply Explained

    Dynamics 365 Dataverse Integration is easier to understand once you stop thinking about Dynamics 365 and Dataverse as two completely separate systems that constantly need to synchronize customer data. For Dynamics 365 applications such as Sales and Customer Service, Dataverse provides the shared data foundation underneath the applications. Accounts, contacts, leads, opportunities, cases, activities, relationships, permissions, and business rules can all live within this structured environment. In this episode of M365 FM, Mirko Peters explains what Dataverse actually is, how Dynamics 365 uses it, and how the same business data can power Power Apps, Power Automate, Power BI, and other connected processes. WHAT IS MICROSOFT DATAVERSE?  Microsoft Dataverse is Microsoft's cloud data platform for structured business information. Instead of keeping customer and operational data across disconnected spreadsheets, lists, emails, and applications, Dataverse provides a common place where approved business applications can work with structured information. Think of Dynamics 365 as an office building. Sales, Customer Service, and other applications are the rooms where employees work. Dataverse is the filing system, structure, and rules behind those rooms. The objective is to reduce unnecessary copies of the same business information and provide applications with a shared foundation. ONE CUSTOMER INSTEAD OF MULTIPLE COPIES Consider a company where Sales stores customer information in one system, Support maintains another customer list, Finance keeps another version, and additional information lives inside shared mailboxes and spreadsheets. When the customer's address or contact information changes, those copies quickly become inconsistent. With Dataverse, approved applications can work with the same customer information. A customer used by Dynamics 365 Sales can also provide context when that customer contacts Dynamics 365 Customer Service. Instead of asking which customer list is correct, teams can work around a shared reference point. DATAVERSE TABLES EXPLAINED Dataverse organizes business information into tables. An Account table can contain companies. Contacts can contain individual people. Leads represent potential customers, Cases can represent customer support requests, and Activities can represent calls, emails, appointments, and tasks. Microsoft provides standard tables for common business concepts, while organizations can create custom tables when they need to represent information specific to their business. A training company, for example, could create tables for courses and certificates, while a property company might create tables for buildings and inspections. ROWS AND COLUMNS Each table contains rows representing individual pieces of business information. One Contact row might represent a particular person. Columns then describe the information associated with that person, such as first name, last name, email address, phone number, job title, company, owner, and status. This structured approach gives information a predictable shape. Applications know what each value represents, reports can analyze it consistently, and automation can react when specific information changes. STANDARD VS CUSTOM TABLES Organizations should generally start with standard Dataverse tables when those structures already represent the business concept they need. Creating several custom tables that all represent slightly different versions of "customer" can recreate the same data fragmentation Dataverse is intended to reduce. Custom tables become valuable when the organization genuinely has business information that doesn't fit existing standard structures. The objective is a data model people can understand and reuse across applications. RELATIONSHIPS CONNECT BUSINESS INFORMATION Tables become significantly more useful when they are connected through relationships. A Contact can belong to an Account. A Case can connect to the customer who created the support request. An Opportunity can connect to calls, emails, appointments, and tasks associated with the sales process. Instead of repeatedly copying company information into every related record, relationships maintain connections between the information. If a company's address changes, the Account can be updated while related Contacts continue pointing toward the same company. TABLES, COLUMNS AND ROWS VS OLDER TERMINOLOGY Older Dynamics 365 and Dataverse documentation may use different terminology. What Microsoft now calls a table was previously commonly called an entity. A column was called a field, and a row was commonly called a record. Understanding both sets of terminology can make older documentation and training material easier to follow. ㅤ SECURITY STARTS WITH IDENTITY Shared information doesn't mean everybody should have access to everything. Microsoft Entra ID provides the identity used to determine who is working with Dataverse. Dataverse can then apply additional security controls governing what that person is permitted to do with business information. Think of Entra ID as the reception desk verifying who entered the building, while Dataverse security determines which rooms, filing cabinets, and information that person can access after entering. ㅤ SECURITY ROLES Security roles provide permissions associated with different jobs and responsibilities. Sales representatives might receive permissions for Accounts, Contacts, Leads, and Opportunities. Customer service agents might work with Cases without receiving the same permissions over sales opportunities. Permissions can govern operations such as reading, creating, updating, and deleting information. Because these controls exist around the underlying data, security doesn't need to depend exclusively on hiding buttons inside individual applications. ㅤ ROW AND COLUMN LEVEL SECURITY Access can become more granular than simply allowing or denying access to an entire table. Row-level security can determine which individual rows a person can access. A salesperson might only work with customers they own, while a sales manager can access customers belonging to the wider team. Column-level security can protect particularly sensitive information within an otherwise accessible row. This provides organizations with more control over who can access particular business information. ㅤ Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

    Dynamics 365 Dataverse Integration - Simply Explained
  4. 23h ago

    Dynamics 365 Inventory Management - Simply Explained

    Dynamics 365 Inventory Management gives businesses one shared record for the products, materials, parts, and other stock moving through their organization. Instead of purchasing, warehouse, sales, production, and finance maintaining separate versions of inventory information, Dynamics 365 connects quantities, locations, availability, ownership, movements, and financial value. In this episode of M365 FM, Mirko Peters explains how Dynamics 365 Inventory Management works from supplier receipt to customer shipment — including inventory dimensions, reservations, transfers, costing, cycle counting, safety stock, consignment inventory, and the connection between inventory and finance. ㅤ WHAT IS DYNAMICS 365 INVENTORY MANAGEMENT? Inventory Management provides a shared stock record across the business. For every item, organizations need to answer five fundamental questions: How many do we have? Where are they? Can we use or sell them? Who owns them? And what are they worth? Dynamics 365 brings those answers together. Purchasing records incoming goods, warehouse teams record movements, sales records what leaves, production records materials consumed, and finance receives the financial value associated with those transactions. ㅤ WHY INVENTORY MANAGEMENT MATTERS Too little inventory creates stockouts, delayed customer orders, lost sales, and potentially interrupted production. Too much inventory creates a different problem: money becomes trapped on warehouse shelves. Products also carry risks while sitting in inventory. They can expire, become damaged, go out of style, or simply stop selling. Inventory management therefore isn't about maximizing stock. The objective is maintaining enough inventory to satisfy demand without unnecessarily tying up working capital. ㅤ MORE THAN FINISHED PRODUCTS Inventory doesn't only mean products waiting to be sold. A manufacturer might track raw materials such as wood, screws, fabric, or components. Materials being transformed into products can become work in progress, while completed products become finished goods. Businesses may also track spare parts, packaging, replacement components, cleaning supplies, and materials required for service operations. Dynamics 365 provides a common inventory structure for these different types of stock. ㅤ THE DIGITAL RECORD BEHIND EVERY ITEM Every inventory item needs an identity inside Dynamics 365. This normally includes an item number, description, and unit of measure. Units of measure become particularly important when organizations purchase and sell products differently. A supplier might sell something by the box while customers purchase individual packs. Dynamics needs to understand the relationship between those units so purchasing, sales, warehouse, and finance teams interpret inventory quantities consistently. ㅤ PRODUCT VARIANTS Some products have multiple variations. Clothing might differ by size and color, while manufactured products can have different styles or configurations. Dynamics 365 can distinguish between these combinations rather than treating them as one generic quantity. The organization can therefore know that it has twelve black medium shirts in one warehouse and six white large shirts somewhere else rather than simply knowing that eighteen shirts exist. ㅤ INVENTORY DIMENSIONS EXPLAINED Inventory dimensions are labels that help Dynamics distinguish where inventory is located and exactly which inventory is being tracked. Storage dimensions describe location. These can include site, warehouse, and the specific location within a warehouse. Tracking dimensions identify particular inventory through information such as batch numbers and serial numbers. Together, these dimensions transform a generic stock quantity into information people can actually use operationally. ㅤ SITES, WAREHOUSES AND LOCATIONS A site represents a broader business location such as a factory or distribution center. Within a site, organizations can operate multiple warehouses. Locations provide another level of detail by identifying where inventory physically sits inside the warehouse. Instead of telling someone that a component is somewhere inside Warehouse A, Dynamics can provide a specific aisle, rack, shelf, or bin location. This becomes increasingly important as warehouse size and inventory complexity increase. ㅤ BATCH AND SERIAL NUMBER TRACKING Batch numbers identify groups of products received or produced together. They become important when organizations need to track expiration dates, quality information, supplier history, or product recalls. Serial numbers identify individual units. A laptop, medical device, or industrial machine can therefore maintain its own identity throughout inventory processes. This can support warranty claims, servicing, returns, and precise traceability. ㅤ FROM PURCHASE ORDER TO GOODS RECEIPT Inventory can begin its operational journey with a purchase order. The purchase order records what the organization expects to receive, the quantity ordered, the supplier, and the intended destination. When the shipment arrives, employees compare the physical delivery with that expectation. Once the goods receipt is recorded, Dynamics knows the inventory has physically arrived. This creates an important distinction between inventory that has merely been ordered and inventory that is actually present. ㅤ QUARANTINE AND INVENTORY STATUS Physically receiving inventory doesn't necessarily mean it should immediately become available. Some goods require quality inspection, expiry checks, testing, or regulatory verification. Dynamics can represent inventory in quarantine or assign a status preventing it from being used prematurely. Warehouse employees can see that the inventory exists while sales and production understand that it isn't currently available for consumption or customer orders. ㅤ PUT-AWAY AND INTERNAL MOVEMENTS After receiving and inspection, goods normally need to move from the receiving area into their appropriate storage locations. Dynamics records these internal movements so the system reflects where inventory physically resides. This means the inventory history doesn't stop when a delivery enters the building. It continues as stock moves between receiving areas, storage locations, warehouses, and sites. ㅤ TRANSFER ORDERS Organizations frequently move inventory between warehouses or sites. A transfer order records this movement. When goods leave the sending warehouse but haven't yet arrived at the destination, Dynamics can represent them as inventory in transit. The stock therefore hasn't simply disappeared from the system. The sending location knows what left, the receiving location knows what to expect, and discrepancies can be investigated against a documented movement. ㅤ INVENTORY RESERVATIONS When a customer places an order, inventory can be reserved specifically for that demand. Reservation means the quantity is no longer simply available for anyone to promise. It has been allocated to a particular requirement. This reduces the risk of two salespeople promising the same limited stock to different customers and becomes especially valuable when availability is low or delivery commitments are important. ㅤ PICKING, PACKING AND SHIPPING Once inventory is committed to an order, warehouse employees can pick the goods from their storage locations, prepare them for shipment, and dispatch them to the customer. When the goods ship, Dynamics records that inventory has left the warehouse and updates the available quantity. The transaction history can therefore provide a connected chain from supplier receipt through internal storage and eventually customer delivery. ㅤ RETURNS, CORRECTIONS AND ADJUSTMENTS Real inventory processes aren't perfect. Customers return products, items become damaged, workers discover incorrect quantities, and physical stock sometimes differs from the quantity recorded in the system. Dynamics can record returns, counting differences, movement corrections, and inventory adjustments. These records provide a history showing what changed and can help organizations identify recurring problems such as inaccurate receiving, damaged stock, incorrect locations, or missing warehouse movements. ㅤ THE FINANCIAL VALUE OF INVENTORY Inventory isn't only a physical quantity. It represents money the organization has already invested. When goods arrive, warehouse teams see additional units while finance needs to understand the corresponding inventory value. When inventory leaves, finance needs to recognize the financial impact of that movement. Dynamics connects the operational inventory record with the company's financial records so quantity and value remain connected. ㅤ ITEM GROUPS AND THE GENERAL LEDGER Item groups help organize similar products and influence how inventory transactions connect with financial accounts. Organizations might create separate groups for raw materials, spare parts, and finished products. The associated financial configuration determines which general ledger accounts receive the accounting impact of purchases, sales, adjustments, production activities, and other inventory transactions. This connection helps warehouse operations and finance work from the same underlying item activity. ㅤ Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

    Dynamics 365 Inventory Management - Simply Explained
  5. 1d ago

    Dynamics 365 Financial Reporting - Simply Explained

    Dynamics 365 Financial Reporting turns the financial data already posted in Dynamics 365 Finance into structured reports that finance teams, managers, auditors, and executives can actually use. Instead of rebuilding financial statements in multiple spreadsheets every month, organizations can use the general ledger, main accounts, financial dimensions, reporting categories, and predefined report structures to create consistent income statements, balance sheets, cash flow reports, trial balances, and budget-versus-actual reports. In this episode of M365 FM, Mirko Peters explains how Dynamics 365 Financial Reporting works and how organizations can move from financial transactions to reports people can trust.ㅤ WHAT IS DYNAMICS 365 FINANCIAL REPORTING? Financial Reporting is the Dynamics 365 Finance capability used to create, maintain, generate, and view financial statements based on general ledger information.It isn't another accounting ledger. Transactions such as invoices, payments, journals, payroll entries, and inventory adjustments are posted in Dynamics 365 Finance first. Financial Reporting then reads those financial results and organizes them into meaningful statements.Think of the general ledger as the financial filing cabinet and Financial Reporting as the report room that organizes those records into something people can understand.ㅤ THE GENERAL LEDGER IS THE FOUNDATION Every useful financial report starts with correctly structured accounting data.The general ledger contains the financial impact of customer invoices, supplier bills, payroll, bank payments, inventory adjustments, and other business transactions. Each amount is assigned to a main account representing what happened financially.Cash, sales revenue, rent expense, wages, accounts receivable, accounts payable, loans, and taxes can each have their own main accounts.Financial statements don't create these numbers. They organize and summarize balances that already exist in the ledger.ㅤ MAIN ACCOUNT TYPES AND CATEGORIES Main account types provide broad accounting classifications. Profit and loss accounts represent revenue and expenses for a period, while balance sheet accounts represent assets, liabilities, and equity.Main account categories provide another reporting layer.Several individual bank accounts, petty cash accounts, and clearing accounts might all belong to a broader cash category. A financial report can therefore show one clean cash line while finance retains the detailed accounts underneath it.Correct account types and categories make financial statements significantly easier to build and maintain.ㅤ FINANCIAL DIMENSIONS ADD BUSINESS CONTEXT Main accounts explain what happened financially. Financial dimensions explain where, who, or which part of the organization was responsible.Dimensions might represent departments, cost centers, business units, regions, locations, or projects.For example, three transactions could all post to the same rent expense account while their dimensions identify Head Office, Warehouse, and Retail North.Finance can see total rent expense while individual managers can analyze the portion associated with their area of responsibility.ㅤ FINANCIAL DIMENSIONS VS FINANCIAL TAGS Not every piece of transaction information should become a financial dimension.Dimensions are most useful for reusable values organizations expect to report against repeatedly, such as department, cost center, region, or business unit.Financial tags are better suited to flexible transaction references such as invoice numbers, purchase order numbers, payment references, or external system IDs.Creating dimensions for thousands of unique transaction references can make the financial structure unnecessarily complicated.ㅤ DEFAULT FINANCIAL REPORTS Dynamics 365 Finance includes 22 default financial reports that organizations can use as starting points.These include common reports such as income statements, balance sheets, cash flow reports, detailed and summary trial balances, rolling expense reports, budget-versus-actual reports, and other financial views.Organizations don't necessarily need to design every statement from scratch. A default report can be opened, compared against actual ledger balances, and adjusted to match the company's account structure and reporting requirements.ㅤ FINANCIAL REPORTING VS POWER BI, EXCEL AND OTHER TOOLS Dynamics 365 Finance provides several reporting technologies, and each serves a different purpose.Financial Reporting is designed for structured general-ledger-based financial statements. Power BI is better suited to interactive dashboards, visual analysis, filters, trends, and management questions.Excel remains useful for additional analysis, calculations, checks, and familiar data exploration.SSRS is generally suited to fixed-format operational documents and detailed reports, while Electronic Reporting focuses on structured files such as tax submissions, bank files, XML, and CSV outputs.Using the appropriate tool reduces the need to force every reporting requirement into Excel.ㅤ HOW ROW DEFINITIONS WORK A row definition controls what appears down the left side of a financial statement.For an income statement, rows might include Revenue, Cost of Sales, Gross Margin, Operating Expenses, and Net Result.Rows can reference individual main accounts, ranges of accounts, account categories, dimension combinations, or calculated totals.Gross margin, for example, doesn't necessarily point directly to an account. It can be calculated by subtracting cost of sales from revenue.Row definitions therefore determine what the report is actually reporting.ㅤ HOW COLUMN DEFINITIONS WORK Column definitions determine how financial information is displayed across the report.Columns might show the current month, year-to-date results, previous-year results, budget, actuals, forecast figures, or variance between actual and budget.A management income statement could therefore contain Current Month, Year to Date, Budget, and Variance columns without requiring someone to export the report into Excel and manually create comparison formulas.ㅤ REPORT DEFINITIONS A report definition connects the row and column structures into a report users can generate.For example, finance might create an Income Statement Rows definition and combine it with a Monthly Actual, Budget and Variance column definition.The resulting report definition could become the Monthly Management Income Statement.This modular approach means organizations can reuse the same financial statement structure with different periods, comparisons, and reporting views rather than rebuilding reports repeatedly.ㅤ REPORTING TREES Reporting trees allow organizations to structure financial reports around different reporting units.These units might represent legal entities, regions, departments, business units, or other organizational structures.A company with subsidiaries could generate results for each individual subsidiary and then provide a combined group view. A regional organization might show North, South, and West individually while also producing a company-wide total.This allows the same reporting framework to serve both local managers and centralized finance teams.ㅤ SUMMARY, DETAIL AND DRILL-DOWN Financial reports don't need to remain static pages.Users can begin with a summary showing figures such as total revenue, costs, and net result and then move into additional detail when a number requires investigation.If operating expenses are significantly above budget, finance can drill into the amount and inspect the transactions behind it, including journal entries, dates, vouchers, and related details.This turns a financial statement into a starting point for analysis instead of simply a document distributed at month-end.ㅤ FILTERING FINANCIAL REPORTS The same report can answer different questions by changing parameters and filters.Users can change report dates, currencies, detail levels, financial dimensions, and other attributes.A finance manager might begin with a company-wide income statement and then filter the same structure to a specific business unit or another reporting period.This reduces the need to maintain separate spreadsheet versions for every department or management question.ㅤ SCHEDULING AND MULTI-ENTITY REPORTING Financial reports can be generated on recurring schedules such as daily, weekly, monthly, or annually.This can support regular management packs, budget reviews, period-close processes, and group reporting.Organizations operating several legal entities can also use Financial Reporting to create views spanning multiple companies and support reporting currency requirements while individual entities continue maintaining their own accounting records.ㅤ REPORT RETENTION AND AUDIT COPIES Generated financial reports have retention considerations. The script notes that newly generated reports receive a 90-day expiration date by default, which appropriately authorized users can modify.It also highlights an important consideration for historical reporting: when saved reports are rerun or users drill into their details, current transaction data can be used.Organizations requiring an immutable audit copy of a finalized reporting period should therefore export the finalized report to Excel or PDF and retain it according to their normal records-management process.ㅤ Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

    Dynamics 365 Financial Reporting - Simply Explained
  6. 1d ago

    Dynamics 365 General Ledger - Simply Explained

    Dynamics 365 General Ledger provides the central financial record behind Dynamics 365 Finance. Customer payments, supplier invoices, inventory movements, payroll, bank transactions, taxes, accruals, and other financial events ultimately affect the company's financial position, and the general ledger brings those accounting entries together in a structured and traceable way. In this episode of M365 FM, Mirko Peters explains the Dynamics 365 General Ledger in plain English, including the chart of accounts, financial dimensions, subledgers, posting profiles, vouchers, journals, allocations, tax, period close, and consolidation.ㅤ WHAT IS THE GENERAL LEDGER IN DYNAMICS 365? The general ledger is the company's master financial record. Instead of finance teams piecing together numbers from separate spreadsheets and systems, financial transactions come together in one consistent accounting structure.The ledger contains debit and credit entries organized into accounts such as cash, sales revenue, inventory, rent expense, and accounts payable. Every financial event has two sides, and total debits and credits must remain balanced.Dynamics 365 Finance maintains a ledger for each legal entity, allowing individual companies within a larger organization to maintain their own financial records, reporting responsibilities, currencies, and accounting periods.ㅤ CHART OF ACCOUNTS EXPLAINED The chart of accounts provides the structure used to organize financial transactions. Think of it as a financial filing cabinet where each main account represents a specific category.Cash, inventory, accounts payable, sales revenue, and rent expense are examples of main accounts. These accounts are grouped into categories used for financial statements.Assets, liabilities, and equity appear on the balance sheet, while revenue and expenses contribute to the income statement. Correct account structures therefore form the foundation for reliable financial reporting.ㅤ FINANCIAL DIMENSIONS A main account tells finance what happened, but organizations often need additional information about where or why it happened.Financial dimensions provide those additional labels. An organization might use dimensions for department, cost center, business unit, or location.A travel expense can therefore remain in one travel expense account while dimensions identify whether the cost belongs to Sales, Support, Finance, London, Berlin, or another organizational unit.This allows companies to analyze financial performance without creating hundreds of unnecessary main accounts.ㅤ ACCOUNT STRUCTURES AND FINANCIAL CONTROLS Dynamics 365 Finance can use account structures to control which combinations of main accounts and financial dimensions are permitted.For example, a travel expense might require both a department and cost center, while another account may require fewer dimensions.These rules help prevent incomplete or inconsistent financial information from reaching the ledger and improve the quality of reporting across the organization.ㅤ GENERAL LEDGER VS SUBLEDGERS The general ledger provides the overall accounting record, while subledgers maintain the detailed operational information behind specific types of transactions.Accounts Payable tracks vendor invoices and payments. Accounts Receivable tracks customer invoices and incoming payments. Inventory tracks stock movements and value, while Fixed Assets tracks long-term assets such as equipment, vehicles, and buildings.Tax and production processes can also maintain specialized details.These subledgers feed accounting entries into the general ledger, allowing operational teams to retain the detail they need while finance receives the accounting impact required for reporting.ㅤ HOW POSTING PROFILES WORK Employees processing normal business transactions shouldn't have to manually determine every debit and credit account.Dynamics 365 Finance uses posting profiles and related accounting rules to determine which main accounts should receive particular transactions.When Accounts Payable processes a vendor invoice, for example, posting rules can automatically direct the liability to the appropriate accounts payable account while the other side of the transaction is posted according to the underlying purchase or expense.This creates more consistent accounting than asking individual users to determine postings manually.ㅤ VOUCHERS AND FINANCIAL TRACEABILITY A voucher provides an important connection between source documents, subledger transactions, and the accounting entries appearing in the general ledger.If a finance manager sees an amount in an account and wants to understand where it came from, the voucher can help trace the financial posting back to the corresponding vendor invoice, product receipt, customer invoice, or other business event.This traceability works in both directions. Finance can move from the ledger toward the source document or from the original transaction toward its accounting impact.ㅤ HOW A PURCHASE REACHES THE GENERAL LEDGER The episode follows a practical example involving a company purchasing 100 office chairs.The process begins with a purchase order. When the chairs arrive, a product receipt confirms that the company has received them. If the chairs are worth $10,000, inventory can receive a $10,000 debit while purchase accrual receives the corresponding $10,000 credit.The purchase accrual acts as a temporary accounting position because the goods have arrived but the vendor invoice hasn't yet been processed.When the invoice arrives, Dynamics 365 can clear the temporary purchase accrual and record the $10,000 obligation in accounts payable.One purchase therefore creates connected operational and accounting records without repeatedly entering the same financial information.ㅤ DOUBLE-ENTRY ACCOUNTING Dynamics 365 Finance follows double-entry bookkeeping. Every financial posting needs balanced debit and credit entries.If $10,000 is debited to one side of a transaction, an equal $10,000 must be credited somewhere else.The accounts involved depend on the business event, but the fundamental principle remains the same: total debits and total credits must balance.This provides the accounting structure that keeps the company's financial records internally consistent.ㅤ JOURNAL ENTRIES Not every accounting transaction begins with a purchase order, customer invoice, or inventory movement. Finance teams sometimes need to create journal entries directly.Journals can be used for adjustments, accruals, corrections, or other financial events that originate within the finance function.For example, if electricity was consumed during March but the corresponding invoice won't arrive until April, finance can create an accrual so the expense is represented in the appropriate accounting period.ㅤ FINANCIAL ALLOCATIONS Allocations allow organizations to distribute costs across accounts, departments, cost centers, or other dimensions according to defined rules.A fixed allocation might distribute head-office rent 50% to Sales, 30% to Support, and 20% to Finance.Variable allocations can distribute costs according to changing measures. Warehouse expenses, for example, could be distributed according to how much each business unit actually used the warehouse.This helps organizations represent shared costs more accurately in management reporting.ㅤ TAX MANAGEMENT Dynamics 365 Finance uses sales tax codes to define how taxes should be calculated and posted.Tax requirements can differ between countries, regions, states, counties, and cities, so tax configuration provides structured rules instead of requiring users to manually calculate taxes for individual transactions.When tax requirements change, organizations can update the appropriate configuration rather than relying on individual employees to remember new calculations.ㅤ FISCAL CALENDARS AND ACCOUNTING PERIODS The fiscal calendar determines how an organization's financial year is divided into accounting periods.These periods are commonly months and provide the structure used for month-end, quarter-end, and year-end financial activities.Transactions need to be recorded in the correct period so finance teams can accurately understand what happened during a particular part of the financial year.ㅤ YEAR-END CLOSING At year-end, Dynamics 365 Finance supports the process of preparing financial accounts for the next fiscal year.Revenue and expense accounts represent activity during a particular year, so their completed result moves through the closing process into equity.Balance-sheet accounts behave differently. Cash, inventory, accounts payable, and similar balances carry forward because those assets and obligations continue to exist when the calendar moves into a new financial year.ㅤ CONSOLIDATION ACROSS LEGAL ENTITIES Larger organizations may operate multiple legal entities while still requiring a combined view of overall financial performance.Consolidation combines financial information from multiple companies into an organizational view while each underlying legal entity continues maintaining its own financial records.Organizations can therefore preserve separate company accounting while still producing consolidated financial information for the wider group.ㅤ Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

    Dynamics 365 General Ledger - Simply Explained
  7. 1d ago

    Dynamics 365 Autonomous Agents - Simply Explained

    Dynamics 365 Autonomous Agents move AI beyond answering questions and generating content. Instead of waiting for someone to prompt them, autonomous agents can watch for specific business events, understand the context stored in Dynamics 365, choose between permitted actions, and continue a defined process within rules established by the organization. In this episode of M365 FM, Mirko Peters explains how autonomous agents differ from Copilot and traditional automation, where Microsoft is applying them across Dynamics 365, and why permissions, guardrails, approvals, and human oversight remain essential. ㅤ WHAT ARE DYNAMICS 365 AUTONOMOUS AGENTS? An autonomous agent is a specialized AI tool designed to perform a narrow business job. It can review business information, choose from allowed next steps, and carry out work toward a defined goal. The important word is defined. An autonomous agent isn't given unrestricted control of a business process. Organizations determine its job, the information it can access, the actions it can perform, and when it must involve a person. Think of it as a digital team member with a specific job description rather than a general-purpose AI system. ㅤ COPILOT VS AUTONOMOUS AGENTS Copilot typically waits for a person to request assistance. A user asks a question, requests information, generates a draft, or asks Copilot to summarize something. An autonomous agent works differently. It can react when something happens, such as a new customer case arriving, a customer sending another message, a new sales lead entering the system, or an order requiring confirmation. A useful analogy is an office building. Copilot works at the reception desk helping people who approach it, while autonomous agents work behind the scenes performing specific operational jobs. ㅤ AUTONOMOUS AGENTS VS TRADITIONAL AUTOMATION Traditional automation is extremely useful when processes follow predictable rules: if something happens, perform a predefined action. Agents add another layer by interpreting context. They can read customer messages, examine connected records, use approved knowledge, and select between actions their configuration permits. Generative AI provides the language understanding, while autonomous behavior connects that understanding to business actions. The agent might identify an issue, find relevant knowledge, update a record, prepare a response, or escalate the situation to a person. ㅤ WHY DYNAMICS 365 DATA MATTERS Generic AI can understand a sentence such as "my delivery still hasn't arrived," but it doesn't automatically know which customer, order, shipment, previous conversation, or support case that statement relates to. Dynamics 365 provides the business context. Customer records, cases, orders, sales leads, financial records, previous conversations, and other connected information allow an agent to understand the situation within the organization's actual business process. This context is what turns general AI capabilities into practical business assistance. ㅤ CUSTOMER INTENT AGENT Customer service provides some of the clearest examples of autonomous agents. The Customer Intent Agent can analyze customer conversations and cases to identify patterns in why customers are contacting an organization. Customer questions continually change as companies launch products, modify services, change delivery partners, or introduce new billing processes. The agent can help identify emerging topics instead of requiring managers to manually analyze hundreds of customer conversations. These insights can help organizations improve self-service experiences, knowledge content, and support processes. ㅤ CASE MANAGEMENT AGENT The Case Management Agent helps with routine activities across the customer service case lifecycle. It can assist with creating cases, updating information, progressing work toward resolution, following up, and closing cases according to the organization's configured processes. The objective isn't to remove customer service representatives. Instead, the agent can reduce repetitive administrative work surrounding cases so service professionals can spend more time understanding customer situations and handling exceptions. Organizations remain responsible for defining when cases require review, approval, or direct human intervention. ㅤ CUSTOMER KNOWLEDGE MANAGEMENT AGENT Useful support knowledge frequently becomes trapped inside closed cases, agent notes, and previous conversations. The Customer Knowledge Management Agent can examine completed case information to identify potentially reusable knowledge and gaps in existing support content. However, not everything contained within an old case should automatically become official guidance. A workaround may be outdated, customer-specific, or based on an exception. The agent can surface useful material while people determine what should become trusted organizational knowledge. ㅤ SALES QUALIFICATION AGENT Sales teams can receive large numbers of inbound leads with very different levels of potential. Researching every prospect and deciding where sellers should focus can consume significant amounts of time. The Sales Qualification Agent for Dynamics 365 Sales can help research and prioritize inbound leads and develop personalized sales emails to begin conversations. Salespeople still determine which opportunities deserve attention, review communications, contribute their own customer knowledge, and build the relationships required to actually close deals. ㅤ SALES ORDER AGENT IN BUSINESS CENTRAL Order processing provides another example of repetitive business work. Customer orders can arrive through email and other channels, requiring employees to interpret the request, enter information, verify details, and prepare confirmation. The Sales Order Agent in Dynamics 365 Business Central can support the order intake process from initial entry through confirmation. This reduces manual data entry while allowing people to concentrate on exceptions, unusual requests, and customer situations requiring judgment. ㅤ FINANCIAL RECONCILIATION AGENTS Finance teams perform substantial amounts of repetitive preparation and reconciliation work, particularly around financial period closing. The Financial Reconciliation Agent can assist with preparing and cleansing datasets used during period-close activities. The Account Reconciliation Agent in Dynamics 365 Finance can help match and clear transactions between subledgers and the general ledger. Accountants remain responsible for investigating discrepancies and determining whether the organization's financial information is correct. ㅤ SUPPLIER COMMUNICATIONS AGENT Procurement teams frequently spend time contacting suppliers to confirm purchase orders and expected delivery dates. The Supplier Communications Agent for Dynamics 365 Supply Chain Management can support this communication and help identify potential delivery delays earlier. Instead of procurement specialists manually chasing every routine confirmation, the agent can support standard follow-up while people concentrate on supplier relationships and problems requiring negotiation or intervention. ㅤ SCHEDULING OPERATIONS AGENT Field Service schedules rarely remain unchanged throughout the day. Traffic, cancellations, urgent jobs, and conflicting bookings can disrupt carefully planned technician schedules. The Scheduling Operations Agent for Dynamics 365 Field Service can help dispatchers adjust schedules as circumstances change. Dispatchers remain responsible for decisions involving customer priorities, difficult commitments, and other situations where business judgment matters. ㅤ PERMISSIONS AND GUARDRAILS The critical question isn't simply whether an autonomous agent can take action. Organizations need to determine exactly which actions it is permitted to take. Can the agent read a customer record? Can it update the record? Can it prepare an email? Can it send that email without approval? Can it recommend closing a case, or can it actually close one? Clear permissions and guardrails turn a broad AI capability into a controlled business process. Agents should only have access to the information and tools necessary for their assigned job. ㅤ WHY HUMAN OVERSIGHT STILL MATTERS Autonomous doesn't mean unsupervised. Agents can misunderstand customer requests, operate on incomplete information, or produce responses that don't fit a specific situation. Processes involving customer promises, financial transactions, exceptions, privacy, or consequential business decisions require appropriate human control. Organizations should review agent activity, analyze employee and customer feedback, inspect affected records, improve instructions and knowledge sources, and adjust permissions when necessary. ㅤ HOW TO START WITH AUTONOMOUS AGENTS A sensible first autonomous-agent project is a narrow, repetitive process where mistakes can be identified and corrected. Organizations might begin with drafting follow-up messages for review, sorting incoming requests, researching leads, or completing routine case information. Teams can then measure the results, improve instructions, refine permissions, and determine whether the agent should receive additional autonomy. Starting small provides an opportunity to understand how the agent behaves before connecting it to more consequential processes. ㅤ Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

    Dynamics 365 Autonomous Agents - Simply Explained
  8. 1d ago

    Dynamics 365 Case Management - Simply Explained

    Dynamics 365 Case Management gives customer service teams one central place to manage customer issues from the first contact through resolution. Instead of information being scattered across emails, calls, chats, notes, and separate systems, each customer problem becomes a structured case containing the issue, customer context, activities, ownership, priority, service commitments, and final resolution. In this episode of M365 FM, Mirko Peters explains how Dynamics 365 Customer Service uses cases, queues, routing, SLAs, knowledge articles, Copilot, entitlements, and automation to create a more consistent support experience. ㅤ WHAT IS A CASE IN DYNAMICS 365? A case represents one customer issue that requires an answer or resolution. It could be a damaged product, billing question, login problem, technical issue, or request for help. Customers can have multiple cases simultaneously because each problem is managed separately. Cases can be connected to contacts and accounts while recording information such as the subject, product, priority, case type, description, and responsible owner. This creates a single working record for the entire support issue rather than forcing agents to reconstruct the customer story from multiple systems. ㅤ KEEPING THE COMPLETE CUSTOMER HISTORY TOGETHER Emails, calls, notes, appointments, tasks, chats, and other activities can remain connected to the same case. When ownership changes, the next agent can understand what happened without asking the customer to explain everything again. This customer context becomes particularly important for complex cases involving several agents or previous troubleshooting attempts. The case shows the immediate problem while the broader customer record provides information about previous interactions, products, and support  history. ㅤ ENTITLEMENTS AND CUSTOMER SUPPORT AGREEMENTS Not every customer receives the same level of support. Dynamics 365 can use entitlements to represent the support terms associated with a customer. An entitlement might define warranty coverage, available support hours, permitted numbers of cases, or premium service conditions. Agents can therefore understand what support applies before committing resources or making promises to customers. ㅤ KNOWLEDGE MANAGEMENT FOR FASTER RESOLUTION Customer service teams frequently solve the same problems repeatedly. Dynamics 365 Knowledge Management allows organizations to maintain approved articles containing troubleshooting instructions, explanations, screenshots, standard answers, and other reusable support information. Agents can search these articles while working on cases instead of recreating solutions from memory. This can improve consistency and make organizational knowledge more accessible to less experienced support agents. ㅤ COPILOT CASE SUMMARIES Long-running cases can contain substantial amounts of information. Copilot can help agents understand that history by generating concise case summaries from information such as the customer, subject, product, priority, description, case type, and recent activities. The summary provides a faster starting point, particularly when a case changes ownership. Agents still review the underlying information and apply their own judgment before deciding what to do next. ㅤ AUTOMATIC CASE CREATION Customers can contact support through channels such as email, phone, chat, social media, and self-service portals. Dynamics 365 can use record creation rules to turn supported incoming communications into structured cases. For example, an email sent to a shared support address can automatically create a case rather than remaining unnoticed in a mailbox. Existing conversations can remain associated with their original cases while genuinely new problems receive separate records. ㅤ QUEUES AND ROUTING Once a case exists, it needs to reach the appropriate team. Dynamics 365 queues provide shared work areas where teams can manage incoming cases. Organizations might create separate queues for billing, technical support, returns, products, languages, regions, or different levels of urgency. Routing rules can evaluate information contained within a case and automatically direct it toward the appropriate queue or agent. Cases can also be manually reassigned when human judgment determines that a particular specialist is better suited to handle the problem. ㅤ PARENT CASES, CHILD CASES AND DUPLICATES Sometimes many customers report problems caused by the same underlying issue. Dynamics 365 can use parent and child cases to connect those individual customer reports to a larger problem. This allows teams to investigate the underlying issue centrally while maintaining individual customer records and communications. Duplicate cases can also be merged so multiple agents don't unknowingly work on the same problem. ㅤ SERVICE LEVEL AGREEMENTS AND RESPONSE TIMES Getting a case to the correct person isn't enough. Customers also expect organizations to meet agreed response and resolution times. Dynamics 365 Service Level Agreements, or SLAs, can attach time-based targets to cases. First-response targets measure how quickly the organization acknowledges the customer, while resolution targets measure how long the organization has to completely address the issue. Different support agreements, priorities, and case types can have different targets. Agents can see which cases are approaching deadlines, while alerts and escalation processes can help teams respond before service commitments are missed. ㅤ BUSINESS PROCESS FLOWS FOR CONSISTENT SUPPORT Business Process Flows provide agents with structured stages for handling cases. A process might move through intake, investigation, diagnosis, and resolution while requiring important information at each stage. This helps newer agents understand what information they need while providing experienced teams with a consistent process. Managers can also identify stages where cases frequently become delayed. ㅤ RESOLVING AND REOPENING CASES Sending an email doesn't automatically mean the customer's problem has been solved. Teams should record how the issue was resolved and then formally close the case. Resolution information creates useful history for future interactions. If the original solution doesn't work, the case can be reopened so the team continues with the existing history instead of creating another disconnected record. ㅤ USING CASE DATA TO IMPROVE CUSTOMER SERVICE Individual cases also become valuable operational data. Managers can analyze time to resolution, time spent in different stages, first-contact resolution, queue workloads, reopened cases, and recurring issue categories. Patterns can reveal broader problems. Increasing case volumes around one product could indicate a product issue, while repeated questions may indicate that documentation or knowledge articles need improvement. Case management therefore supports both individual customer service and continuous improvement across the support organization. ㅤ CUSTOMER SELF-SERVICE Some customers don't need direct assistance from an agent. Self-service experiences can allow customers to create requests, check case status, provide additional information, and access approved knowledge content themselves. This can reduce routine support demand while allowing customer service agents to concentrate on problems requiring investigation, explanation, or human judgment. ㅤ MICROSOFT 365 AND POWER PLATFORM INTEGRATION Dynamics 365 Case Management can work alongside familiar Microsoft technologies. Outlook can support email communication, Teams can help employees collaborate on difficult cases, SharePoint can manage related documents, Power BI can provide reporting and dashboards, and Power Platform can extend processes with additional forms and automation. The tools surrounding the process may change, but the Dynamics 365 case remains the central record connecting the customer problem, activities, ownership, service commitments, and resolution. ㅤ THE KEY TAKEAWAY Dynamics 365 Case Management isn't simply a ticketing system. It provides a structured lifecycle for customer issues from initial contact through routing, investigation, service commitments, knowledge, collaboration, resolution, and reporting. By keeping the customer, problem, communication history, support agreement, ownership, deadlines, and final answer connected to one record, customer service teams can reduce lost context, avoid duplicated work, and provide customers with a more consistent support experience. Subscribe to M365 FM for more Microsoft Knowledge Nuggets and Simply Explained episodes covering Dynamics 365, Microsoft 365, Power Platform, Copilot, AI, Azure, security, governance, and the Microsoft ecosystem. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

    Dynamics 365 Case Management - Simply Explained

Ratings & Reviews

5
out of 5
3 Ratings

About

Welcome to the M365.FM — your essential podcast for everything Microsoft 365, Azure, and beyond. Join us as we explore the latest developments across Power BI, Power Platform, Microsoft Teams, Viva, Fabric, Purview, Security, and the entire Microsoft ecosystem. Each episode delivers expert insights, real-world use cases, best practices, and interviews with industry leaders to help you stay ahead in the fast-moving world of cloud, collaboration, and data innovation. Whether you're an IT professional, business leader, developer, or data enthusiast, the M365.FM brings the knowledge, trends, and strategies you need to thrive in the modern digital workplace. Tune in, level up, and make the most of everything Microsoft has to offer. M365.FM is part of the M365-Show Network. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

You Might Also Like