Page 9061 "Plan Configuration List"
System Application · System.Azure.Identity
Across versions
- BC23-30present
Neighbourhood 7 connected objects and pages
System Application · System.Azure.Identity · captioned “License Configuration” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | License Configuration |
| Extensible | true |
| SourceTable | Plan Configuration |
| PageType | List |
| UsageCategory | Administration |
| ApplicationArea | All |
| Permissions | tabledata “Plan Configuration” = rimd |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Group | License | Plan Name | Specifies the name of the license. |
| Permissions Customized | Customized | Specifies if the permissions are customized. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Creation | Add License Configuration | Add a configuration for a license. | |
| Processing | Configure | Customize license permissions. | Page 9069 “Plan Configuration Card” |
| Navigation | BCAdminCenter | Manage security groups and license-related features for each environment. | |
| M365AdminCenter | Assign licenses to existing users or create new users. |
Trigger event subscribers
- OnOpenPageEvent: Codeunit 9822 “Plan Configuration Impl.” LogFeatureTelemetryPlanConfigurationList
Triggers
OnOpenPage, OnInit
Relations
- source table Table 9017 “Plan Configuration”
Extended by
Calls
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Codeunit 457 “Environment Information” (1 call:
OnInit → IsSaaS) - Codeunit 9822 “Plan Configuration Impl.” (1 call:
OnOpenPage → ShowDefaultConfigurationNotification)
Documented on Microsoft Learn
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "page", object_name: "Plan Configuration List"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.