| title | description | services | ms.service | ms.subservice | ms.custom | ms.devlang | ms.topic | author | ms.author | ms.reviewer | manager | ms.date |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Azure portal: SQL Database dynamic data masking | Microsoft Docs |
How to get started with SQL Database dynamic data masking in the Azure portal |
sql-database |
sql-database |
security |
conceptual |
ronitr |
ronitr |
vanto |
craigg |
04/01/2018 |
This article shows you how to implement dynamic data masking with the Azure portal. You can also implement dynamic data masking using Azure SQL Database cmdlets or the REST API.
-
Launch the Azure portal at https://portal.azure.com.
-
Navigate to the settings page of the database that includes the sensitive data you want to mask.
-
Click the Dynamic Data Masking tile that launches the Dynamic Data Masking configuration page.
-
Alternatively, you can scroll down to the Operations section and click Dynamic Data Masking.
-
-
In the Dynamic Data Masking configuration page, you may see some database columns that the recommendations engine has flagged for masking. In order to accept the recommendations, just click Add Mask for one or more columns and a mask is created based on the default type for this column. You can change the masking function by clicking on the masking rule and editing the masking field format to a different format of your choice. Be sure to click Save to save your settings.
-
To add a mask for any column in your database, at the top of the Dynamic Data Masking configuration page, click Add Mask to open the Add Masking Rule configuration page.
-
Select the Schema, Table and Column to define the designated field for masking.
-
Choose a Masking Field Format from the list of sensitive data masking categories.
-
Click Save in the data masking rule page to update the set of masking rules in the dynamic data masking policy.
-
Type the SQL users or AAD identities that should be excluded from masking, and have access to the unmasked sensitive data. This should be a semicolon-separated list of users. Users with administrator privileges always have access to the original unmasked data.
[!TIP] To make it so the application layer can display sensitive data for application privileged users, add the SQL user or AAD identity the application uses to query the database. It is highly recommended that this list contain a minimal number of privileged users to minimize exposure of the sensitive data.
-
Click Save in the data masking configuration page to save the new or updated masking policy.
- For an overview of dynamic data masking, see dynamic data masking.
- You can also implement dynamic data masking using Azure SQL Database cmdlets or the REST API.