tablePlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Table 4508 "Email - Outlook Account"

Email - Outlook REST API · System.Email

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 4 connected objects and pages

Page 4500 "Current User Email Account" (pages and codeunits on it)Current User Email AccountPage 4503 "Microsoft 365 Email Account" (pages and codeunits on it)Microsoft 365 Email AccountPage 4504 "Microsoft 365 Email Wizard" (pages and codeunits on it)Microsoft 365 Email WizardExtending Email (Learn pages)Extending Email

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.

Email - Outlook REST API · System.Email · BC29-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 4500 “Current User Email Account” (1 Learn page), Page 4503 “Microsoft 365 Email Account” (1), Page 4504 “Microsoft 365 Email Wizard” (1).

Properties

Property Value
DataClassification CustomerContent

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No. Name Type Explanation Notes
1 Id Guid Primary Key caption DataClassification SystemMetadata
2 Name Text[250] Specifies the name of the account. via Page 4503 “Microsoft 365 Email Account”
3 Email Address Text[250] Specifies the email address of the account. via Page 4503 “Microsoft 365 Email Account”
4 Outlook API Email Connector Enum “Email Connector” — enum Email Connector; DataClassification SystemMetadata

Keys

  • PK: Id
  • EmailAddress: Email Address

Pages and codeunits on this table

Ask your agent

Procedure bodies are not stored here (D10). 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: "table", object_name: "Email - Outlook Account"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources