{"id":22304,"date":"2022-11-30T11:22:00","date_gmt":"2022-11-30T19:22:00","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-apps\/protecting-data-with-dataverse\/"},"modified":"2025-06-11T07:47:22","modified_gmt":"2025-06-11T14:47:22","slug":"protecting-data-with-dataverse","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-apps\/protecting-data-with-dataverse\/","title":{"rendered":"Protecting data with Dataverse"},"content":{"rendered":"\n
In this blog series, we will be covering how to protect data in Dataverse from external and internal threats (both from internal users and Microsoft). In today\u2019s post, we will focus on protecting data from external threats.<\/p>\n\n\n
Dataverse handles authentication with Azure Active Directory (Azure AD) to allow for conditional access and multi-factor authentication. Dataverse also uses Azure AD identity and access management mechanisms to help ensure that only authorized users can access the environment, data, and reports. Conditional access and location awareness can help control access to environments by only allowing trusted devices, locations, and other conditions which can be evaluated for authentication. Essentially, conditional access helps to secure where users can sign into Dataverse environments and what devices they can use. Also, because Dataverse is built on Azure, it benefits from the Azure platform’s powerful security technologies. Encryption of data, both at rest and in transit, also preserves confidentiality.<\/p>\n\n\n
Dataverse auditing provides ways for system admins to quickly set up audit tracking for their environment. The platform provides the ability to track and log activities that include CRUD operations, opening and viewing records, sharing records, and more. The logs can be easily accessed directly by the client without the need for additional reporting or the export of audit activity. It is important to note that read auditing is configured separately from Create, Update, or Delete as this audit trail may produce a lot of data. Please note, not all environments require read auditing.\u00a0<\/p>\n\n\n
We recommend the following preventative steps:<\/p>\n\n\n
Take these steps to identify and locate possible issues:<\/p>\n\n\n
Follow these steps to execute an effective response:<\/p>\n\n\n