pageAL Developmentofficial - Microsoftderived - from the source, no model text

Page 6302 "Azure AD Access Dialog"

Base Application · System.Azure.Identity

Across versions

  1. BC23-24present
  2. BC251 procedures added, 1 procedures removed
  3. BC26-30unchanged

Neighbourhood 5 connected objects and pages

Codeunit 6400 "Flow Service Management" (event subscribers)Flow Service ManagementCodeunit 4030 "Client Type Management" (calls)Client Type ManagementCodeunit 6300 "Azure AD Mgt." (calls)Azure AD Mgt.Page 6300 "Azure AD App Setup Wizard" (calls)Azure AD App Setup WizardCreate users according to licenses (Learn pages)Create users according to li…

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · System.Azure.Identity · captioned “Microsoft Entra service permissions” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Microsoft Entra service permissions
PageType NavigatePage

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
Content The functionality you have selected to use requires services from Microsoft Entra to access your system. label —
Before you can begin using this functionality, you must first grant access to these services. To grant access, choose the ‘Authorize Azure Services’ link. label —
OAuthIntegration add-in OAuthIntegration —
Para2 label —
Microsoft Entra Services: label —
Para4 ResourceFriendlyName —

Events published

Procedures

  • GetAuthorizationCodeAsSecretText(Resource: Text; ResourceName: Text): SecretText + BC25

Plus 1 local procedures.

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.

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: "Azure AD Access Dialog"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 2 sources