---
id: object/table/1680
type: object
title: Table 1680 "Email Logging Setup"
summary: Table 1680 "Email Logging Setup" in EmailLogging (Microsoft.CRM.EmailLoggin). 8 fields, 6 public procedures. Introduced in BC29, still in BC30.
tier: official
language: en
tags:
  - table
  - emaillogging
versions:
  introduced: "29"
  last_changed: null
  deprecated: null
review:
  state: derived
  by: null
  at: null
  flags: []
generated:
  at: "2026-10-11T00:31:51.816Z"
  pipeline: 0.2.0
  prompts: {}
  input_hash: 639fb9c1377a4d83d79a17c683374f210bf352795a52c86dce87be3136b1fbea
evidence:
  - kind: code
    url: https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Apps/W1/EmailLogging/app/src/tables/EmailLoggingSetup.Table.al
    title: src/Apps/W1/EmailLogging/app/src/tables/EmailLoggingSetup.Table.al (releases/29.x)
    date: null
    commit: ea08af5ef2d6a9b5c5af4a029288abbe2c883220
    t: null
    quote: null
links:
  learn:
    - https://learn.microsoft.com/dynamics365/business-central/marketing-set-up-email-logging
  objects: []
  features: []
  topics:
    - topic/business-central/business-functionality/relationship-management/manage-sales-opportunities
  localizations: []
  videos: []
  posts: []
  guidelines: []
object_type: table
object_id: 1680
name: Email Logging Setup
caption: Email Logging using Graph API
namespace: Microsoft.CRM.EmailLoggin
app: EmailLogging
extends: null
first_version: "29"
last_version: "30"
present_in:
  - "29"
  - "30"
changed_in: []
source_major: "29"
obsolete: null
countries: []
ms_search_form_ids: []
counts:
  fields: 8
  procedures: 6
  events: 0
  subscribers: 0
relations:
  out: 0
  referenced_by: 0
  pages: 1
  extended_by: 0
  event_subscribers: 0
  calls: 2
  called_by: 0
  implements: 0
---

# Table 1680 "Email Logging Setup"

> Table 1680 "Email Logging Setup" in EmailLogging (Microsoft.CRM.EmailLoggin). 8 fields, 6 public procedures. Introduced in BC29, still in BC30.

EmailLogging · Microsoft.CRM.EmailLoggin · captioned "Email Logging using Graph API" · BC29-30 · [source at ea08af5e](https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Apps/W1/EmailLogging/app/src/tables/EmailLoggingSetup.Table.al) · facts from BC29

Learn documents this table through its pages: [Page 1680 "Email Logging Setup"](../page/1680.md) (1 Learn page).

## Properties

| Property | Value |
|---|---|
| Caption | Email Logging using Graph API |
| Access | Internal |
| 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 | Primary Key | Code[10] | — | DataClassification SystemMetadata |
| 2 | Email Address | Text[250] | Specifies the email address of the shared mailbox in Exchange Online that was created for email logging. The shared mailbox must be in the same tenant as Business Central. <small>via [Page 1680 "Email Logging Setup"](../page/1680.md)</small> |  |
| 3 | Email Batch Size | Integer | Specifies the number of email messages that the job queue entry for email logging will get from Exchange Online in one run. By balancing this number with how often the job queue entry runs you can fine tune the process. If a message is not logged in the current run it will be in the next one. <small>via [Page 1680 "Email Logging Setup"](../page/1680.md)</small> |  |
| 4 | Enabled | Boolean | Specifies whether email logging is enabled. <small>via [Page 1680 "Email Logging Setup"](../page/1680.md)</small> |  |
| 5 | Client Id | Text[250] | 'Specifies the ID of the Azure Active Directory application that will be used to connect to Exchange Online.', Comment = 'Exchange Online and Azure Active Directory are names of a Microsoft service and a Microsoft Azure resource and should not be translated.' <small>via [Page 1680 "Email Logging Setup"](../page/1680.md)</small> | DataClassification EndUserIdentifiableInformation |
| 6 | Client Secret Key | Guid | — | DataClassification EndUserPseudonymousIdentifiers |
| 7 | Redirect URL | Text[2048] | 'Specifies the redirect URL of the Azure Active Directory application that will be used to connect to Exchange Online.', Comment = 'Exchange Online and Azure Active Directory are names of a Microsoft service and a Microsoft Azure resource and should not be translated.' <small>via [Page 1680 "Email Logging Setup"](../page/1680.md)</small> | DataClassification EndUserIdentifiableInformation |
| 8 | Consent Given | Boolean | — |  |

## Keys

- Key1: Primary Key (clustered)

## Procedures

- `SetClientSecret(ClientSecret: SecretText)` (internal)
- `GetClientSecret(): SecretText` (internal)
- `GetRedirectUrl(): Text` (internal)
- `GetEmailBatchSize(): Integer` (internal)
- `GetDefaultRedirectUrl(): Text[2048]` (internal)
- `GetDefaultEmailBatchSize(): Integer` (internal)

## Pages and codeunits on this table

- [Page 1680 "Email Logging Setup"](../page/1680.md) (source table)

## 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 1293 "Isolated Storage Management"](../codeunit/1293.md) (3 calls: `GetClientSecret → Get`, `SetClientSecret → Delete`, `SetClientSecret → Set`)
- [Codeunit 501 "OAuth2"](../codeunit/501.md) (1 call: `GetDefaultRedirectUrl → GetDefaultRedirectURL`)

## Across versions

- Present in: BC29-30
- Changed (declaration) in: none

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: "table", object_name: "Email Logging Setup")`, then `bcatlas_get_procedure_body` or `bcatlas_get_neighbors` on the returned id.