Telemetry - stopping a session is logged to telemetry


This content is archived and is not being updated. For the latest documentation, go to What's new and planned for Dynamics 365 Business Central. For the latest release plans, go to Dynamics 365 and Microsoft Power Platform release plans.

Enabled for Public preview General availability
Users, automatically Apr 1, 2022 Apr 1, 2022

Business value

Partners can get insights into session errors and help the customer get unblocked.

Feature details

A session can be forcibly stopped, for example, from code by calling the Session.StopSession method or from the Business Central admin center by using the cancel session action. If a session is forcibly stopped, the Business Central server will log the occurrence to partner telemetry.

Using telemetry, partners can get insights into when sessions get stopped for users, either by an administrator or by the Business Central server.

Partners or tenant administrators can also set up alerts in Azure Monitor to get notified if many sessions get stopped.

See also

Analyzing Stopped Session Telemetry (docs)