Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article helps you understand and improve the privacy aspects of your Business Central app regardless of where it's hosted. In the following sections, you find guidance and recommended privacy best practices related what you as an AL developer need to know about privacy.
Data security vs. privacy
Both of the articles of data security and privacy are about customer data stored in the Business Central database. So what's the difference between the articles?
- Data security is about protecting data from unauthorized access.
- Privacy is about the appropriate handling of personal data.
Privacy and telemetry
It's possible to configure your extension/app to emit telemetry data to an Azure Application Insights resource owned by your organization. This data can then be collected and visualized for analyzing the application against the desired business goals, troubleshooting, and more. Learn more about how to instrument an extension/app with telemetry in App telemetry overview
The out of the box telemetry data send to your app doesn't emit any personal or customer data to Azure Application Insights, see FAQ: What about privacy laws and regulations (for telemetry)?. The Business Central server uses the data classification property set on the AL methods that emit telemetry to determine if the telemetry event is safe to send to Azure Application Insights or if it shouldn't be emitted. Learn more in Using DataClassification for privacy.
Privacy and data classification of the data model
The Business Central application has support for tenant administrators to get insights into where they keep personal data in their system, and also ability to respond to requests from data subjects. Learn more about these privacy features in Classifying data sensitivity fields.
As a developer of an extension/app, you need to provide the intended data classification of fields in your data model by setting the DataClassification property on table fields. The tenant administrator can choose to keep your data classification or override it, should they use the system in a different way than anticipated by you.
Tip
You can enable the AppSourceCop rule AS00016 (Data Classification property should be different from "ToBeClassified") to find tables and fields that haven't been classified yet. Learn more in AppSourceCop Error AS0016.
Related information
AppSourceCop Error AS0016
Classifying data sensitivity fields (for tenant admins)
Privacy FAQ
Privacy (microsoft.com)
Security for AL developers
General security overview