updates

Author: JulianePadrao

learn-pr/wwl-data-ai/implement-compliance-controls-sensitive-data/7-explore-azure-sql-database-ledger.yml

@@ -1,11 +1,11 @@
 ### YamlMime:ModuleUnit
 uid: learn.wwl.implement-compliance-controls-for-sensitive-data.explore-azure-sql-database-ledger
-title: Explore Azure SQL Database Ledger
+title: Explore Ledger
 metadata:
   adobe-target: true
   prefetch-feature-rollout: true
-  title: Explore Azure SQL Database Ledger
-  description: "Explore Azure SQL Database Ledger"
+  title: Explore Ledger
+  description: "Explore Ledger"
   ms.date: 02/26/2025
   author: JulianePadrao
   ms.author: jupadrao

learn-pr/wwl-data-ai/implement-compliance-controls-sensitive-data/includes/1-introduction.md

@@ -8,5 +8,5 @@ After taking this module, you'll understand:
 - Why server and database audit are important
 - How to implement row level security and dynamic data masking
 - Understand the usage of Microsoft Defender for SQL
-- How Azure SQL Database Ledger works
+- How Ledger works
 - Explore Azure Purview supported capabilities 

learn-pr/wwl-data-ai/implement-compliance-controls-sensitive-data/includes/11-summary.md

@@ -6,5 +6,5 @@ Now that you've reviewed this module, you should be able to:
 - Why server and database audit are important
 - How to implement row level security and dynamic data masking
 - Understand the usage of Microsoft Defender for SQL
-- How Azure SQL Database Ledger works
+- How Ledger works
 - Explore Azure Purview supported capabilities 

learn-pr/wwl-data-ai/implement-compliance-controls-sensitive-data/includes/3-explore-server-and-database-audit.md

@@ -1,4 +1,4 @@
-Azure SQL auditing tracks database events and writes them to an audit log in your Azure Storage account, Log Analytics workspace, or Event Hubs. It helps maintain regulatory compliance, analyze activity patterns, and identify deviations that may indicate security violations.
+[Azure SQL auditing](/azure/azure-sql/database/auditing-overview) tracks database events and writes them to an audit log in your Azure Storage account, Log Analytics workspace, or Event Hubs. It helps maintain regulatory compliance, analyze activity patterns, and identify deviations that may indicate security violations.
 
 You can define server-level and database-level policies. Server policies automatically cover new and existing databases in Azure.
 

learn-pr/wwl-data-ai/implement-compliance-controls-sensitive-data/includes/4-implement-dynamic-data-masking.md

@@ -1,4 +1,4 @@
-Dynamic Data Masking works by obfuscating data in order to limit its exposure. Users who don't need to see sensitive data can view the column that contains the data, but not the actual data itself. Dynamic Data Masking works at the presentation layer, and that unmasked data is always visible by high privileged users.
+[Dynamic Data Masking](/azure/azure-sql/database/dynamic-data-masking-overview) works by obfuscating data in order to limit its exposure. Users who don't need to see sensitive data can view the column that contains the data, but not the actual data itself. Dynamic Data Masking works at the presentation layer, and that unmasked data is always visible by high privileged users.
 
 Dynamic Data Masking has the advantage that it doesn't require many modifications to the application or database. You can configure it through the Azure portal, or using T-SQL as follows.
 

learn-pr/wwl-data-ai/implement-compliance-controls-sensitive-data/includes/5-implement-row-level-security.md

@@ -1,4 +1,4 @@
-Row-level security (RLS) doesn't use encryption and operates at the database level to restrict access to a table by using a security policy based on group membership or authorization context. This functionally is equivalent to a `WHERE` clause.
+[Row-level security (RLS)](/sql/relational-databases/security/row-level-security) doesn't use encryption and operates at the database level to restrict access to a table by using a security policy based on group membership or authorization context. This functionally is equivalent to a `WHERE` clause.
 
 The security policy invokes an inline table-valued function to protect access to the rows in a table.
 
@@ -159,7 +159,7 @@ Row-level security is ideal for many scenarios, including:
 - When you need to restrict customers' data access to only the data relevant to their company.
 - When you need to restrict access for compliance purposes.
 
-## Best practice
+## Best practices
 
 Here are a few best practices to consider when implementing RLS:
 

learn-pr/wwl-data-ai/implement-compliance-controls-sensitive-data/includes/6-understand-microsoft-defender-for-sql.md

@@ -1,13 +1,11 @@
-Microsoft Defender for SQL offers a suite of protections for Azure SQL Database and Azure SQL Managed Instance as part of the advanced SQL security features, including SQL vulnerability assessment and Advanced Threat Protection. 
+[Microsoft Defender for SQL](/azure/azure-sql/database/azure-defender-for-sql) offers a suite of protections for Azure SQL Database and Azure SQL Managed Instance as part of the advanced SQL security features, including SQL vulnerability assessment and Advanced Threat Protection. 
 
 ## SQL vulnerability assessment
 
 SQL vulnerability assessment is a service that uses a knowledge base of security rules to flag items that don't comply when they're scanned. It checks your database for security best practices, and providing visibility into your security state, such as misconfigurations, excessive permissions, and exposure of sensitive data.
 
 To see recommendations for SQL Database and SQL Managed Instance, you must enable Microsoft Defender for SQL at the subscription level (recommended). You also need to provide a storage account. Alternatively, you can choose to receive emails with a summary of the scan results.
 
-:::image type="content" source="../media/module-33-security-final-23.png" alt-text="Screenshot of Advanced Threat Protection page in Azure portal.":::
-
 The vulnerability assessment feature can detect potential risks in your environment, and help you enhance database security. It also provides insight into your security state and actionable steps to resolve security alerts.
 
 To learn more about SQL vulnerability assessment, see [SQL vulnerability assessment helps you identify database vulnerabilities](/azure/azure-sql/database/sql-vulnerability-assessment).

learn-pr/wwl-data-ai/implement-compliance-controls-sensitive-data/includes/7-explore-azure-sql-database-ledger.md

@@ -1,8 +1,8 @@
-The ledger feature of Azure SQL Database provides tamper-evidence capabilities in your database. You can cryptographically attest to other parties, such as auditors or other business parties, that your data hasn't been tampered with.
+[Ledger](/sql/relational-databases/security/ledger/ledger-overview) provides tamper-evidence capabilities in your database. You can cryptographically attest to other parties, such as auditors or other business parties, that your data hasn't been tampered with.
 
 ## How it works
 
-Cryptography and blockchain have begun to appear in far reaching areas of technology with varying degrees of success. One place where it has proved useful and beneficial is in being used as the technology behind the Azure SQL Database Ledger feature. The Ledger feature provides tamper-evidence capabilities in your database. Using the Ledger feature of the Azure SQL Database, you can provide concrete proof to auditors, business partners or any interested parties what data has been changed or tampered with.
+Cryptography and blockchain have begun to appear in far reaching areas of technology with varying degrees of success. One place where it has proved useful and beneficial is in being used as the technology behind the Ledger. Ledger provides tamper-evidence capabilities in your database. Using this feature, you can provide concrete proof to auditors, business partners or any interested parties what data has been changed or tampered with.
 
 A traditional ledger is defined as a collection of accounts of a particular type and that's exactly what the Azure SQL Database Ledger feature provides in your environment. It provides transparent protection of your data from bad actors including but not limited to attackers or even database or cloud administrators. It provides guarantees of cryptographic data integrity while maintaining the power, flexibility, and performance of Azure SQL Database.
 
@@ -12,7 +12,7 @@ Each transaction that the database receives is cryptographically hashed (SHA-256
 
 ## Components
 
-Azure SQL Database Ledger function currently exists for tables in two forms: The Updatable Ledger Tables and the Append-only Ledger Tables.
+Ledger function currently exists for tables in two forms: The Updatable Ledger Tables and the Append-only Ledger Tables.
 
 ### Updatable ledger tables
 
@@ -24,15 +24,15 @@ Append-only ledger tables work well with insert only applications such as an acc
 
 ## Benefits
 
-The Azure SQL Database Ledger feature provides multiple benefits:
+Ledger provides multiple benefits:
 
 **Ease Audits –** Audits are frequently enacted to ensure that proper security controls are in place to reduce potential attacks, backup and restore practices are as required, and thorough disaster recovery procedures are in place. Ledger provides documented proof that your data hasn't been altered in an auditing process.
 
 **Increased trust –** Ledger also can help establish trust between multiple-party business processes without the complexity and performance implications that network consensus can introduce.
 
 **Data integrity –** Querying the data on a blockchain network without sacrificing performance can be a serious challenge. Ledger provides data integrity for off-chain storage of blockchain networks, which helps ensure complete data trust through the entire system.
 
-## Enabled ledger on a SQL database
+## Enable ledger on a SQL database
 
 You can enable the ledger capability only during the database creation process. Once the database is created, you cannot modify it.
 

learn-pr/wwl-data-ai/implement-compliance-controls-sensitive-data/includes/8-implement-azure-purview.md

@@ -169,37 +169,6 @@ To scope and run the scan, follow these steps:
 
     :::image type="content" source="../media/dp-3300-module-33-lab-63.png" alt-text="Screenshot of review scan page for Azure Purview.":::
 
-### View a scan
-
-To view a scan, follow these steps:
-
-1. Navigate to the data source in the collection, and then select **View Details** to check the status of the scan.
-
-    :::image type="content" source="../media/dp-3300-module-33-lab-64.png" alt-text="Screenshot of the view details for a Microsoft Purview scan.":::
-
-1. The scan details indicate the progress of the scan in the **Last run status** and the number of assets scanned and classified. The **Last run status** is updated to **In progress** and then **Completed** once the entire scan has run successfully.
-
-    > [!div class="mx-imgBorder"]
-    > [![Screenshot of the scan progress for a Microsoft Purview scan.](../media/dp-3300-module-33-lab-65.png)](../media/dp-3300-module-33-lab-65.png#lightbox)
-
-### Manage Scan
-
-Scans can be managed or run again on completion:
-
-1. Select your scan name to manage the scan.
-
-    :::image type="content" source="../media/dp-3300-module-33-lab-66.png" alt-text="Screenshot of the recent scans list for Microsoft Purview.":::
-
-1. From the scan history page, you can run the scan again, edit the scan, or delete the scan.
-
-    > [!div class="mx-imgBorder"]
-    > [![Screenshot of the scan history page showing how to manage scan options.](../media/dp-3300-module-33-lab-67.png)](../media/dp-3300-module-33-lab-67.png#lightbox)
-
-1. You can also run an incremental scan or a full scan again.
-
-    > [!div class="mx-imgBorder"]
-    > [![Screenshot of the full or incremental scan for a Microsoft Purview scan.](../media/dp-3300-module-33-lab-68.png)](../media/dp-3300-module-33-lab-68.png#lightbox)
-
 ## Data lineage
 
 Generally, data lineage represents the journey the data takes from its origin to where it moves across the data estate over time. Among its many uses are troubleshooting, tracing the root cause in data pipelines, and debugging.

learn-pr/wwl-data-ai/implement-compliance-controls-sensitive-data/index.yml

@@ -11,13 +11,13 @@ metadata:
   ms.topic: module
   ms.service: azure
 title: Implement compliance controls for sensitive data
-summary: Explore data classification capabilities and degrees of confidentiality. Implement security options to maintain private data safe, including Azure SQL auditing, Microsoft Defender for SQL, row-level security, Dynamic Data Masking and Azure SQL Database Ledger.
+summary: Explore data classification capabilities and degrees of confidentiality. Implement security options to maintain private data safe, including Azure SQL auditing, Microsoft Defender for SQL, row-level security, Dynamic Data Masking and Ledger.
 abstract: |
   After completing this module, you will be able to:
   - Plan and implement data classification in Azure SQL Database
   - Understand and configure row-level security and dynamic data masking
   - Understand the usage of Microsoft Defender for SQL
-  - Explore how Azure SQL Database Ledger works
+  - Explore how Ledger works
 prerequisites: |
   - Ability to write code in the SQL language, particular the Microsoft T-SQL dialect, at a basic level.
   - Experience creating and configuring resources using the Azure portal.