Audit User and Group Permissions Across Apps in Microsoft Dynamics 365 Business Central v28

With Business Central 2026 release wave 1 (v28), Microsoft introduces a powerful new capability — the Permissions Overview page, providing a centralized view of permissions across all apps and extensions.

This feature significantly improves how administrators analyze, audit, and troubleshoot security configurations in complex environments.

In earlier versions, analyzing permissions was fragmented and time-consuming:

  • Permissions spread across multiple apps and extensions
  • No single view to understand who has access to what
  • Difficult to trace Which permission set grants access and Which users or groups are assigned.

What’s New in BC28?

The Permissions Overview page provides a unified and centralized view of all permission sets across:

  • Base application
  • Installed extensions
  • Custom apps

1. Unified View Across All Apps

The Permissions Overview page provides a centralized view of permissions across all apps and extensions, eliminating the need to navigate multiple sources to understand access configurations.


2. Advanced Filtering

Administrators can efficiently filter permissions by object type, scope, extension, or permission set, enabling quick and precise identification of relevant access rights.


3. Trace Access to Specific Objects

The system allows you to easily determine which permission sets grant access to a specific object, providing clear visibility into how permissions are assigned.


4. FactBoxes for User and Group Assignment

Built-in Fact Boxes display the users and security groups associated with each permission set, offering complete transparency into access assignments.

This will help administrator for

1. Improved Security Auditing

The new Permissions Overview enables administrators to perform faster and more accurate security audits by clearly identifying excessive permissions, detecting unused or redundant permission sets, and validating compliance requirements with greater confidence.


2. Simplified Troubleshooting

When users encounter access issues, administrators can quickly search for the relevant object, identify the required permission sets, and verify user or group assignments, significantly reducing the time required to resolve issues.


3. Better Dependency Analysis

In environments with multiple extensions, where overlapping permissions are common, this feature helps identify conflicts, understand permission dependencies, and avoid duplication, leading to a more structured and maintainable security model.

4. Better Governance and Compliance

This feature supports stronger governance by enabling efficient internal audits, simplifying external compliance checks, and ensuring that role-based access is aligned with organizational policies.


5. Improved Role Design

Functional consultants can design cleaner and more effective permission sets by avoiding over-per missioning and aligning access rights closely with business roles and responsibilities.


6. Enhanced User Management

Administrators gain complete visibility into who has access, why they have access, and through which permission sets, resulting in better control and transparency over user permissions.

The Permissions Overview page in Microsoft Dynamics 365 Business Central v28 is a major step forward in security management and transparency.

It transforms permission analysis from a fragmented process into a centralized, efficient, and user-friendly experience.

Turn Off Indexes in Microsoft Dynamics 365 Business Central v28

In version 28 of Microsoft Dynamics 365 Business Central, Microsoft introduced a powerful database optimization feature that allows administrators to disable non-unique indexes with low usage.

This capability provides greater control over database performance, storage usage, and write operations, especially in environments with large datasets and high transaction volumes.

Why Index Optimization Matters

Indexes improve query performance, but every index also introduces maintenance overhead.

Whenever records are inserted, updated, or deleted, the SQL engine must also update all associated indexes.

In high-transaction systems such as inventory, warehouse, and manufacturing operations, unnecessary indexes can lead to:

  • Slower posting performance
  • Increased SQL storage consumption
  • Higher index maintenance cost
  • Longer backup and restore time

By allowing administrators to disable rarely used indexes, Business Central now provides more flexibility to tune database performance.

How to Disable an Index

To disable an index, follow these steps:

  1. Open Table Information in Business Central.
  2. Click on Table No
  3. It will open Table Data Management Card
  4. Clear the Enabled in Database checkbox.

Once disabled, the index is immediately removed from active maintenance, meaning the database engine no longer updates it during data modifications.

Article content

Index Types That Cannot Be Disabled

Article content

These indexes are essential for system functionality and consistency, so they cannot be turned off.

Activation Behavior

Index management behaves differently depending on the operation.

Article content

The delayed activation for enabling indexes prevents heavy index rebuild operations during working hours.

Technical Impact on Performance

1. Faster Write Operations

Each index must be updated when records change.Disabling unused indexes reduces the number of updates required, resulting in faster:


2. Reduced SQL Storage Consumption

Indexes can consume a significant portion of database storage. In large systems with millions of records, removing unnecessary indexes can free several gigabytes of space.


3. Better Performance During High Transactions

Environments with high transaction volumes, such as:

  • Manufacturing
  • Retail
  • E-commerce integrations
  • Warehouse management

can benefit from reduced index overhead during posting.

For example:

When posting thousands of item journal lines, fewer indexes mean less SQL maintenance work.


4. Improved SQL Maintenance Operations

Large numbers of indexes increase the workload for:

  • SQL statistics updates
  • Index rebuilds
  • Database maintenance jobs

By disabling unused indexes, administrators can reduce maintenance windows and resource consumption.

The ability to turn off non-unique indexes per company in Microsoft Dynamics 365 Business Central v28 is a valuable addition for system administrators and technical consultants.

It provides greater flexibility in optimizing database performance, storage usage, and transaction throughput, especially in large Business Central environments.

When used carefully with proper analysis, this feature can significantly improve system efficiency and operational performance.

Approval Workflows for Item Journals in Microsoft Dynamics 365 Business Central

With the latest updates in Microsoft Dynamics 365 Business Central, Item Journals now support approval workflows, bringing the same level of control that previously existed only for General Journal batches.

This feature introduces stronger governance and internal control for inventory transactions, ensuring that critical stock movements are reviewed before being posted.


Why This Feature Matters

Inventory transactions such as adjustments, consumption, or production output directly impact stock valuation and financial reporting.

Without an approval process, users could accidentally or intentionally post incorrect entries.

The new approval workflow capability for Item Journals helps organizations:

  • Enforce inventory control policies
  • Prevent unauthorized postings
  • Improve audit compliance
  • Reduce operational errors

Journals That Support Approval Workflows

Approval workflows can now be applied to the following journals:

Article content
Article content

How the Approval Process Works

When a user submits a journal batch for approval, the system creates an approval entry.

During the approval process:

  • The journal cannot be edited
  • The journal cannot be deleted
  • The journal cannot be posted

These restrictions remain until the approval request is approved or canceled.

This prevents any changes that could bypass the approval process.

Article content

Example Scenario

Consider a manufacturing company using the Consumption Journal to record raw material usage.

Without approval:

A user could mistakenly consume 100 units instead of 10, impacting inventory valuation.

With approval workflows:

  1. The journal batch is submitted for approval
  2. A manager reviews the entries
  3. The manager approves or rejects the request

This ensures inventory accuracy and financial integrity.

Key Benefits

The introduction of approval workflows for Item Journals provides several advantages:

✔ Stronger internal control over inventory transactions

✔ Reduced risk of incorrect stock postings

✔ Better compliance with audit and governance requirements

✔ Consistent approval processes across financial and inventory journals

The ability to apply approval workflows to Item Journals in Microsoft Dynamics 365 Business Central is a valuable enhancement for organizations managing inventory and manufacturing operations.

By ensuring that sensitive inventory transactions are reviewed before posting, businesses can maintain accurate stock records and stronger operational control.

Add Pictures to Item Variants in Microsoft Dynamics 365 Business Central

In the latest updates of Microsoft Dynamics 365 Business Central, you can now store pictures for Item Variants, making it easier to visually differentiate product options such as color, size, or style.

This enhancement improves usability for sales teams, warehouse staff, and product managers by allowing quick identification of product variations directly from the system.

Why This Feature is Useful

Many companies manage products with multiple variants, for example:

  • T-shirts with different colors
  • Jewelry with different metal types
  • Shoes with different sizes

Previously, variants were identified mainly through codes or descriptions. Now you can attach variant-specific images, making it easier to visually confirm the correct option.

Example:

ItemVariantImage
RingGoldGold ring image
RingSilverSilver ring image

This helps reduce order errors and improves product clarity.

How to Add a Picture to an Item Variant

Follow these steps to attach an image to a variant.

1. Open the Item Card

Navigate to the Item Card of the product.

2. Open Variants

Choose the Variants action to view the list of item variants.

3. Select a Variant

Select the variant you want to update and open the Item Variant Card.

4. Add or Manage the Image

On the Picture FactBox, choose one of the following actions:

Article content

Where This Feature Helps Most

This feature is particularly valuable in industries with visually distinct variants:

  • Retail
  • Fashion
  • Jewelry
  • Manufacturing
  • E-commerce integrations

Warehouse staff can quickly verify the correct variant during picking and packing, reducing mistakes.


Practical Example

Suppose you sell a Bracelet with multiple color options.

Variant CodeDescriptionImage
BR-GLDGold BraceletGold image
BR-SLVSilver BraceletSilver image
BR-BLKBlack BraceletBlack image

By attaching pictures, users can instantly confirm they are selecting the correct variant.


Summary

The Item Variant Picture feature in Microsoft Dynamics 365 Business Central enhances product management by:

  • Allowing images for each variant
  • Improving visual identification
  • Reducing selection errors
  • Enhancing user experience

This is a small but powerful improvement that helps organizations manage complex product catalogs more efficiently.

Top 10 Developer Changes in Business Central v28 (AL / VS Code)

Every major release of Microsoft Dynamics 365 Business Central introduces improvements that impact how developers design, build, and maintain extensions.

Version 28 (2026 Release Wave 1) focuses strongly on performance optimization, platform modernization, and improved developer productivity.

For developers building extensions using AL and Visual Studio Code, several changes require attention during upgrades.

In this article, I will walk through the Top 10 developer changes in Business Central v28 and what they mean for your extensions.

1. Legacy Pricing Engine Removed

One of the biggest platform changes in v28 is the complete removal of the legacy pricing engine.

Microsoft introduced the new Price List architecture in earlier versions, and now it becomes the only supported pricing model.

Developer Impact

Extensions relying on older pricing logic must migrate.

Areas to review include:

  • custom price calculations
  • discount logic
  • pricing-related code units
  • integrations referencing legacy pricing tables

The new pricing system provides a more flexible framework for managing pricing rules and discounts.

2. FlowField Calculation Optimization

Business Central v28 introduces an important optimization for FlowField calculations.

Previously, FlowFields could be calculated even if they were not visible on the page.

In v28, FlowFields are calculated only when the field is visible in the UI.

Benefits

  • fewer SQL queries
  • faster page loading
  • improved scalability for large datasets

3. Improved Search Metadata

Search and navigation are significantly improved in v28.

Developers can now provide better search metadata that improves how users discover pages, actions, and data.

Why this matters

In large Business Central environments with hundreds of pages and reports, improved search helps users locate functionality much faster.

Developers should review:

  • page captions
  • action captions
  • field descriptions

Clear naming improves search results and usability.

4. Resource Files in Extensions

Another useful improvement in v28 is the ability to include resource files within extensions.

These files can store:

  • configuration data
  • templates
  • initialization data

Benefits

Developers can package configuration data directly with the extension instead of writing complex installation code.

This simplifies deployment and improves maintainability.

5. Profile Extension Objects

Customizing user profiles previously required copying base profiles, which created upgrade issues.

Business Central v28 introduces profile extension objects, allowing developers to extend profiles without duplication.

Advantages

  • cleaner customization model
  • easier upgrades
  • better maintainability

Developers can now modify Role Centers and user experiences in a more structured way.

6. Improved Performance Profiling

Performance troubleshooting becomes easier with new profiling improvements.

Developers can capture performance data to analyze:

  • long-running AL procedures
  • page load times
  • inefficient database queries

Why this matters

In large implementations with many extensions, performance bottlenecks can be difficult to detect.

Profiling tools help developers identify inefficient code earlier.

7. SQL Telemetry Insights

Business Central v28 provides better telemetry insights for database operations.

Telemetry data includes:

  • SQL query execution time
  • table interactions
  • query performance statistics

This information integrates with Microsoft Azure Application Insights.

Developer Advantage

Developers can monitor real production workloads and optimize extensions based on actual usage patterns.

8. Sandbox Upgrade Testing Improvements

Upgrade testing is easier in v28.

Developers can now upgrade existing sandbox environments to preview versions.

Benefits

  • test extension compatibility earlier
  • simulate production upgrades
  • reduce upgrade risks

This is particularly important for partners maintaining multiple customer environments.


9. AI Agent Development Scenarios

Microsoft continues to move toward AI-assisted development workflows.

New tools and integrations enable AI agents to assist developers in tasks such as:

  • analyzing AL code
  • generating documentation
  • improving developer productivity

This aligns with Microsoft’s broader AI strategy across the Dynamics ecosystem.


10. Enhanced VS Code Development Experience

The development experience in Visual Studio Code continues to improve.

Enhancements include:

  • better debugging capabilities
  • improved symbol downloads
  • smoother Git integration
  • improved navigation in large AL projects

These improvements help developers manage complex extension projects more efficiently.


What Developers Should Prepare for in v28

Before upgrading to Business Central v28, developers should review their extensions carefully.

Key areas to validate include:

  • pricing logic compatibility
  • FlowField calculations
  • performance-sensitive code
  • search metadata
  • extension initialization processes

Testing extensions in sandbox environments before production upgrades is strongly recommended.

Business Central v28 continues Microsoft’s focus on modernizing the platform and improving developer productivity.

The most significant changes for developers include:

  • removal of legacy pricing logic
  • optimized FlowField calculations
  • improved telemetry and profiling tools
  • better development workflows in Visual Studio Code

Stay tune for more..

How to Create and Use AI Agents in Microsoft Dynamics 365 Business Central

Artificial Intelligence is rapidly expanding inside enterprise systems. With Microsoft Dynamics 365 Business Central v27.4, Microsoft now exposes a first-class agent creation capability — allowing you to define, configure, and run intelligent agents directly inside your ERP environment.

In this blog, we’ll walk through how agents work, the creation experience based on what’s available in the product today.

🚀 What Are AI Agents in Business Central?

In Business Central, AI agents are software assistants that can:

  • Understand natural language instructions
  • Execute business tasks against Business Central data
  • Follow configured rules and permissions
  • Operate autonomously or with human review

These agents sit at a higher abstraction layer than traditional workflows — they interpret intent and then coordinate actions across standard Business Central APIs, pages, and logic.

🛠 Step-by-Step: Creating an Agent in Business Central

Here’s a distilled implementation walk-through based on the video and documentation:

1. Enable Agent Capabilities

Before you can create agents, you must:

  • Enable Custom Agent capability in your Business Central environment
  • Have a sandbox tenant for experimentation
  • Ensure you have relevant permission sets such as AGENT-ADMIN and AGENT-DIAGNOSTICS applied to your user account

2. Start the Agent Wizard

Once enabled:

  1. Click the “Agent” icon in the role centre
  2. Choose Create New Agent
  3. Select a template (e.g., Sales Validation) or start from scratch
  4. Provide:

The installer guides you through setting up:

  • Purpose
  • Profile
  • Permissions

Agents are treated like users, so they must have clear permissions defining what Business Central data they can access and act on.

3. Define Agent Instructions

This is the heart of the agent. Instructions are plain-language “task definitions” that guide what the agent should do when triggered.

A basic instruction structure looks like:

  • Introductory purpose
  • Step-by-step tasks
  • Expected output or result

Example :

“You are a Business Central agent. When invoked, check all overdue receivables and create a work list of customers where the balance exceeds credit terms.”

Agents use this instruction to orchestrate actions, call APIs, or run logic — all while respecting security.

4. Configure Execution Profile

Each agent runs under a specific profile:

  • Choose standard or custom roles used in Business Central
  • Profiles determine UI access and actions available to the agent
  • Permissions are tied to the profile

Profiles limit what the agent can read or write — essential for governance.

5. Test and Activate

Once configured:

  1. Use the Agent Task Playground to simulate tasks
  2. Review output and refine instructions
  3. When ready, activate the agent
  4. The agent can run immediately or wait for a trigger

In preview today, scheduling and automated triggers are limited — most agents are started manually or via designated events.

📍 Real Business Examples

Agents being highlighted in Business Central include:

🔹 Sales Order Agent

  • Monitors a designated email inbox
  • Parses incoming customer requests
  • Locates or creates the customer record
  • Verifies item availability
  • Generates and sends quotes or orders via email
  • Keeps the human reviewer in the loop for approvals and changes

This helps sales teams minimize manual order entry by automating standard order processing tasks.


🔹 Payables & AP Agents

Similar to sales agents, agents can automate Accounts Payable workflows by:

  • Monitoring invoice email inboxes
  • Extracting invoice data using AI
  • Drafting vendor invoices inside Business Central
  • Letting users review and finalize postings

This frees AP teams from repetitive data entry and improves efficiency.

AI agents in Microsoft Dynamics 365 Business Central are more than an experiment — they’re a new paradigm for embedding intelligence inside operational ERP processes. Rather than writing bespoke automation, you define business intent, and the system interprets and operationalizes it — provided you set the rules, permissions, and expectations correctly.