Codeunit 48525 "Fabric Platform Http Client"

MicrosoftFabricMirroring · Microsoft.FabricExport · BC30 · source at f18567dc · facts from BC30

Properties

Events published

• OnBeforeGetHttpClientHandler(var HttpClientHandler: Interface "Http Client Handler"; var IsHandled: Boolean) (internal): Raised before the HTTP client handler is created. Bind a subscriber to inject a mock handler in tests.

Procedures

• CreateClientWithBearer(AccessToken: SecretText): Codeunit "Rest Client" (internal)
• BuildJsonRequest(Method: Text; Url: Text; JsonBody: Text): Codeunit "Http Request Message" (internal)
• TrySend(var RestClientParam: Codeunit "Rest Client"; var HttpRequestMessage: Codeunit "Http Request Message"; var HttpResponseMessage: Codeunit "Http Response Message") (internal)

Plus 1 local procedures.

Calls

From the extracted call graph of BC30 (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 2350 “Rest Client” (1 call: TrySend → Send)
• Codeunit 2354 “Http Content” (1 call: BuildJsonRequest → Create)

Called by

• Codeunit 48526 “Fabric Platform Admin Client” (9 calls: AddServicePrincipalToWorkspace → BuildJsonRequest, AddServicePrincipalToWorkspace → CreateClientWithBearer, AddServicePrincipalToWorkspace → TrySend, …)

Recent changes

• 2026-10-01 #11314 [Project Arches] Microsoft Fabric Export Setup (main, BC30, feature, added)

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC30 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: "codeunit", object_name: "Fabric Platform Http Client"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.