New AL objects – Entitlement, PermissionSet, and PermissionSetExtension
Some of the functionality described in this release plan has not been released. Delivery timelines may change and projected functionality may not be released (see Microsoft policy). Learn more: What's new and planned
|Enabled for||Public preview||General availability|
|Users by admins, makers, or analysts||Mar 1, 2021||Apr 2021|
The ability to manage user access to the functionality provided by a business application is a cornerstone of any successful solution or service. The Business Central application and service helps organizations across the world manage their most valuable and sensitive data.
Business Central uses two main concepts for defining access to the functionality:
Entitlements describe which objects in Business Central a customer is entitled to use according to the license that they purchased from Microsoft or the Azure Active Directory role that they have assigned in the Microsoft 365 admin center (such as Global Administrator).
Permissions describe which objects an administrator or a partner gave to the customer user.
In the previous releases of Business Central, permissions and entitlements were defined as data in the application database. Keeping such sensitive information as data comes with additional security and audit risks. Changes applied to this data should ideally be well traceable. "Treat your critical data as you treat your code" is a mantra applied to this type of sensitive data in DevOps practices. With this release of Business Central we are turning this data into code.
Three new object types are introduced in the AL language:
This change will give you all of the advantages of using the AL Language extension in Visual Studio Code and source control systems (as Visual Studio Online and GitHub) to design, get an overview, and track changes to the objects that describe user access.
Permissions and entitlements issues also fall into a category of frequently experienced issues online and on-premises. Turning this data into code has another significant advantage: the ability to apply hotfixes to the entitlements and permissions in the same way that the hotfixes are applied to the apps themselves, simply by updating an app to a new version that carries fixed code. This improves Business Central online support agility considerably, ultimately improving customer satisfaction with the service.
Finally, the new objects that we introduce in this release are envisioned to become the core building blocks in the story of monetizing the AppSource apps. It is through these new AL objects that AppSource ISVs will be able to define which capabilities of their apps should be made available to their users when the customers purchase their app licenses. With the current release, we pave the way by moving the entitlements and permission sets into AL objects for Microsoft apps, so that ISVs can follow the same approach for their apps, when the monetization story is introduced with one of the next releases of Business Central.
Usage of the Entitlement objects will be limited to Microsoft apps only in this release (enforced by the AppSource technical validation). PermissionSet and PermissionSetExtension objects will be fully available for all ISVs to use. While supplying permissions in the XML format within the app files will still be supported, we encourage all ISVs to gradually move their permissions from the XML format to the new AL objects.