From dcd463d5c810c20e4349c466676172e38650ab5f Mon Sep 17 00:00:00 2001 From: Timna Brown <24630902+brown9804@users.noreply.github.com> Date: Wed, 16 Jul 2025 20:39:13 -0600 Subject: [PATCH 01/17] removed not valid ref --- .../integration-with-purview.md | 1 - 1 file changed, 1 deletion(-) diff --git a/nosql/azure-managed-instance-for-apache-cassandra/integration-with-purview.md b/nosql/azure-managed-instance-for-apache-cassandra/integration-with-purview.md index 3de8f45..c76b67c 100644 --- a/nosql/azure-managed-instance-for-apache-cassandra/integration-with-purview.md +++ b/nosql/azure-managed-instance-for-apache-cassandra/integration-with-purview.md @@ -27,7 +27,6 @@ Last updated: 2025-07-17 - [Metadata Extraction](#metadata-extraction) - [Data Classification](#data-classification) - [DLP and Governance](#dlp-and-governance) - - [Example DLP Policies](#example-dlp-policies) - [Cost Monitoring](#cost-monitoring) - [Best Practices](#best-practices) - [Unity Catalog Use Case](#unity-catalog-use-case) From 994d7980e26579fd6fed3b9caa47b6ec997cb764 Mon Sep 17 00:00:00 2001 From: Timna Brown <24630902+brown9804@users.noreply.github.com> Date: Wed, 16 Jul 2025 20:39:55 -0600 Subject: [PATCH 02/17] section was removed + more examples --- nosql/mongo-db-atlas-on-azure/integration-with-purview.md | 1 - 1 file changed, 1 deletion(-) diff --git a/nosql/mongo-db-atlas-on-azure/integration-with-purview.md b/nosql/mongo-db-atlas-on-azure/integration-with-purview.md index 4682d66..c177b21 100644 --- a/nosql/mongo-db-atlas-on-azure/integration-with-purview.md +++ b/nosql/mongo-db-atlas-on-azure/integration-with-purview.md @@ -26,7 +26,6 @@ Last updated: 2025-07-17 - [Metadata and Lineage Scanning](#metadata-and-lineage-scanning) - [Classification and Labeling](#classification-and-labeling) - [Governance and DLP Controls](#governance-and-dlp-controls) - - [Examples of DLP Policies](#examples-of-dlp-policies) - [Cost Insights](#cost-insights) - [Governance Best Practices](#governance-best-practices) - [Unity Catalog Integration](#unity-catalog-integration) From feffb107e8a5072e1450f1809c451d7a0df03737 Mon Sep 17 00:00:00 2001 From: Timna Brown <24630902+brown9804@users.noreply.github.com> Date: Wed, 16 Jul 2025 20:40:47 -0600 Subject: [PATCH 03/17] change counter --- sql/azure-database-for-mysql/README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/sql/azure-database-for-mysql/README.md b/sql/azure-database-for-mysql/README.md index b18562d..2f13efa 100644 --- a/sql/azure-database-for-mysql/README.md +++ b/sql/azure-database-for-mysql/README.md @@ -138,7 +138,9 @@ connection.close() - **Pre-Migration Assessment**: Use tools like **Azure Migrate** or **MySQL Workbench** to assess compatibility and performance implications. +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-16

+ From 55a4f2f0711b8cdedfe0cda0f8b91ace172f0881 Mon Sep 17 00:00:00 2001 From: Timna Brown <24630902+brown9804@users.noreply.github.com> Date: Wed, 16 Jul 2025 20:41:09 -0600 Subject: [PATCH 04/17] change counter --- sql/azure-database-for-mysql/integration-with-purview.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/sql/azure-database-for-mysql/integration-with-purview.md b/sql/azure-database-for-mysql/integration-with-purview.md index aee6845..ea2c6d1 100644 --- a/sql/azure-database-for-mysql/integration-with-purview.md +++ b/sql/azure-database-for-mysql/integration-with-purview.md @@ -171,7 +171,9 @@ Last updated: 2025-06-19 - Centralized management of data assets. +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-16

+ From c6e59e7572a6d4fe73547cf4f23574fd45c84de3 Mon Sep 17 00:00:00 2001 From: Timna Brown <24630902+brown9804@users.noreply.github.com> Date: Wed, 16 Jul 2025 20:41:32 -0600 Subject: [PATCH 05/17] change badge format --- sql/azure-database-for-postgresql/README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/sql/azure-database-for-postgresql/README.md b/sql/azure-database-for-postgresql/README.md index 3b46b38..37c5204 100644 --- a/sql/azure-database-for-postgresql/README.md +++ b/sql/azure-database-for-postgresql/README.md @@ -98,7 +98,9 @@ conn.close() - **Storage and I/O Optimization**: Utilize **Premium SSD v2** storage to provision throughput and IOPS independently of disk size. - **Built-in Query Insights**: Azure’s Query Performance Insight tool offers visuals and recommendations for tuning workloads based on real-time performance metrics. +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-16

+ From a04be093e0567ba97990d7308b20e9ae8aa0d13d Mon Sep 17 00:00:00 2001 From: Timna Brown <24630902+brown9804@users.noreply.github.com> Date: Wed, 16 Jul 2025 20:41:47 -0600 Subject: [PATCH 06/17] chnage counter --- .../integration-with-purview.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/sql/azure-database-for-postgresql/integration-with-purview.md b/sql/azure-database-for-postgresql/integration-with-purview.md index ba697cc..b289725 100644 --- a/sql/azure-database-for-postgresql/integration-with-purview.md +++ b/sql/azure-database-for-postgresql/integration-with-purview.md @@ -150,7 +150,9 @@ Last updated: 2025-06-19 - Lower compliance risk through automated audits and DLP enforcement. - Empowered data consumers with governed, cataloged, and discoverable datasets. +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-16

+ From 7a8f5773caf7795e01ed608fef61940ac0463407 Mon Sep 17 00:00:00 2001 From: Timna Brown <24630902+brown9804@users.noreply.github.com> Date: Wed, 16 Jul 2025 20:42:31 -0600 Subject: [PATCH 07/17] change badge format --- sql/oracle-database-on-azure/integration-with-purview.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/sql/oracle-database-on-azure/integration-with-purview.md b/sql/oracle-database-on-azure/integration-with-purview.md index 39052cb..51a3166 100644 --- a/sql/oracle-database-on-azure/integration-with-purview.md +++ b/sql/oracle-database-on-azure/integration-with-purview.md @@ -31,7 +31,6 @@ Last updated: 2025-06-19 - [Managing DLP Data Loss Prevention Projects](#managing-dlp-data-loss-prevention-projects) - [Cost Management and Budgeting](#cost-management-and-budgeting) - [Cost Components](#cost-components) - - [Example Monthly Budget](#example-monthly-budget) - [Best Practices](#best-practices) - [Integration with Purview for Unity Catalog](#integration-with-purview-for-unity-catalog) - [Steps to Integrate](#steps-to-integrate) @@ -158,7 +157,9 @@ Last updated: 2025-06-19 - Improved compliance and governance. - Centralized management of data assets. +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-16

+ From 1ff986bf15e0245820bb573179c117f07316a9ea Mon Sep 17 00:00:00 2001 From: Timna Brown <24630902+brown9804@users.noreply.github.com> Date: Wed, 16 Jul 2025 20:42:47 -0600 Subject: [PATCH 08/17] change badge format --- sql/oracle-database-on-azure/README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/sql/oracle-database-on-azure/README.md b/sql/oracle-database-on-azure/README.md index cdf050e..9443a84 100644 --- a/sql/oracle-database-on-azure/README.md +++ b/sql/oracle-database-on-azure/README.md @@ -98,7 +98,9 @@ CREATE TABLE employees ( - **Fetch Size Tuning**: In hybrid or multicloud setups (e.g., Oracle DB in OCI, app in Azure), **increase fetch size** to reduce network round trips and latency. - **Networking**: Use **Accelerated Networking** and **Proximity Placement Groups** to reduce latency between app and DB tiers. +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-16

+ From e7d0fbcf8337aa9834e3f8327de8e7d444b5f04e Mon Sep 17 00:00:00 2001 From: Timna Brown <24630902+brown9804@users.noreply.github.com> Date: Wed, 16 Jul 2025 20:43:15 -0600 Subject: [PATCH 09/17] chnage counter --- sql/azure-sql-database/README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/sql/azure-sql-database/README.md b/sql/azure-sql-database/README.md index 58d849b..bc15d7e 100644 --- a/sql/azure-sql-database/README.md +++ b/sql/azure-sql-database/README.md @@ -95,7 +95,9 @@ class Program +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-16

+ From 2c1a554cf57289688fd62145dcebf003ddcad2c9 Mon Sep 17 00:00:00 2001 From: Timna Brown <24630902+brown9804@users.noreply.github.com> Date: Wed, 16 Jul 2025 20:43:40 -0600 Subject: [PATCH 10/17] chnage counter --- sql/azure-sql-database/integration-with-purview.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/sql/azure-sql-database/integration-with-purview.md b/sql/azure-sql-database/integration-with-purview.md index 1083538..ba7b559 100644 --- a/sql/azure-sql-database/integration-with-purview.md +++ b/sql/azure-sql-database/integration-with-purview.md @@ -156,7 +156,9 @@ Last updated: 2025-06-19 - Improved compliance and governance. - Centralized management of data assets. +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-16

+ From 98e9dc6f8a5f4e788025961bfb6d753d251065fa Mon Sep 17 00:00:00 2001 From: Timna Brown <24630902+brown9804@users.noreply.github.com> Date: Wed, 16 Jul 2025 20:44:24 -0600 Subject: [PATCH 11/17] change badge format --- .github/workflows/use-visitor-counter.yml | 94 +++++++++++++++++++++++ 1 file changed, 94 insertions(+) create mode 100644 .github/workflows/use-visitor-counter.yml diff --git a/.github/workflows/use-visitor-counter.yml b/.github/workflows/use-visitor-counter.yml new file mode 100644 index 0000000..4aa2c96 --- /dev/null +++ b/.github/workflows/use-visitor-counter.yml @@ -0,0 +1,94 @@ +name: Use Visitor Counter Logic + +on: + pull_request: + branches: + - main + schedule: + - cron: '0 0 * * *' # Runs daily at midnight + workflow_dispatch: # Allows manual triggering + +permissions: + contents: write + pull-requests: write + +jobs: + update-visitor-count: + runs-on: ubuntu-latest + + steps: + - name: Checkout current repository + uses: actions/checkout@v4 + with: + fetch-depth: 0 + + - name: Shallow clone visitor counter logic + run: git clone --depth=1 https://github.com/brown9804/github-visitor-counter.git + + - name: Set up Node.js + uses: actions/setup-node@v4 + with: + node-version: '20' + + - name: Install dependencies for github-visitor-counter + run: | + cd github-visitor-counter + npm ci + + - name: Run visitor counter logic (updates markdown badges and metrics.json) + run: node github-visitor-counter/update_repo_views_counter.js + env: + TRAFFIC_TOKEN: ${{ secrets.TRAFFIC_TOKEN }} + REPO: ${{ github.repository }} + + - name: Move generated metrics.json to root + run: mv github-visitor-counter/metrics.json . + + - name: List files for debugging + run: | + ls -l + ls -l github-visitor-counter + + - name: Clean up visitor counter logic + run: rm -rf github-visitor-counter + + - name: Configure Git author + run: | + git config --global user.name "github-actions[bot]" + git config --global user.email "github-actions[bot]@users.noreply.github.com" + + - name: Commit and push changes (PR) + if: github.event_name == 'pull_request' + env: + TOKEN: ${{ secrets.GITHUB_TOKEN }} + run: | + git fetch origin + git checkout -b ${{ github.event.pull_request.head.ref }} origin/${{ github.event.pull_request.head.ref }} + git add "*.md" metrics.json + git commit -m "Update visitor count" || echo "No changes to commit" + git remote set-url origin https://x-access-token:${TOKEN}@github.com/${{ github.repository }} + git pull --rebase origin ${{ github.event.pull_request.head.ref }} || echo "No rebase needed" + git push origin HEAD:${{ github.event.pull_request.head.ref }} + + - name: Commit and push changes (non-PR) + if: github.event_name != 'pull_request' + env: + TOKEN: ${{ secrets.GITHUB_TOKEN }} + run: | + git fetch origin + git checkout ${{ github.event.pull_request.head.ref }} || git checkout -b ${{ github.event.pull_request.head.ref }} origin/${{ github.event.pull_request.head.ref }} + git add "*.md" metrics.json + git commit -m "Update visitor count" || echo "No changes to commit" + git remote set-url origin https://x-access-token:${TOKEN}@github.com/${{ github.repository }} + git pull --rebase origin ${{ github.event.pull_request.head.ref }} || echo "No rebase needed" + git push origin HEAD:${{ github.event.pull_request.head.ref }} + + - name: Create Pull Request (non-PR) + if: github.event_name != 'pull_request' + uses: peter-evans/create-pull-request@v6 + with: + token: ${{ secrets.GITHUB_TOKEN }} + branch: update-visitor-count + title: "Update visitor count" + body: "Automated update of visitor count" + base: main From 3951f8cdf6dc00a042e2ec54abfe32aef8b50c7e Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Thu, 17 Jul 2025 02:44:54 +0000 Subject: [PATCH 12/17] Update last modified date in Markdown files --- sql/azure-database-for-mysql/README.md | 2 +- sql/azure-database-for-mysql/integration-with-purview.md | 2 +- sql/azure-database-for-postgresql/README.md | 2 +- sql/azure-database-for-postgresql/integration-with-purview.md | 2 +- sql/azure-sql-database/README.md | 2 +- sql/azure-sql-database/integration-with-purview.md | 2 +- sql/oracle-database-on-azure/README.md | 2 +- sql/oracle-database-on-azure/integration-with-purview.md | 2 +- 8 files changed, 8 insertions(+), 8 deletions(-) diff --git a/sql/azure-database-for-mysql/README.md b/sql/azure-database-for-mysql/README.md index 2f13efa..c066930 100644 --- a/sql/azure-database-for-mysql/README.md +++ b/sql/azure-database-for-mysql/README.md @@ -6,7 +6,7 @@ Costa Rica [![GitHub](https://img.shields.io/badge/--181717?logo=github&logoColor=ffffff)](https://github.com/) [brown9804](https://github.com/brown9804) -Last updated: 2025-06-03 +Last updated: 2025-07-17 ---------- diff --git a/sql/azure-database-for-mysql/integration-with-purview.md b/sql/azure-database-for-mysql/integration-with-purview.md index ea2c6d1..df8b144 100644 --- a/sql/azure-database-for-mysql/integration-with-purview.md +++ b/sql/azure-database-for-mysql/integration-with-purview.md @@ -4,7 +4,7 @@ Costa Rica [![Microsoft Purview](https://img.shields.io/badge/Microsoft-Purview-blue)](https://learn.microsoft.com/en-us/azure/purview/) [![Azure Database for MySQL](https://img.shields.io/badge/Azure-MySQL-blue)](https://learn.microsoft.com/en-us/azure/mysql/) -Last updated: 2025-06-19 +Last updated: 2025-07-17 --- diff --git a/sql/azure-database-for-postgresql/README.md b/sql/azure-database-for-postgresql/README.md index 37c5204..e5d9253 100644 --- a/sql/azure-database-for-postgresql/README.md +++ b/sql/azure-database-for-postgresql/README.md @@ -6,7 +6,7 @@ Costa Rica [![GitHub](https://img.shields.io/badge/--181717?logo=github&logoColor=ffffff)](https://github.com/) [brown9804](https://github.com/brown9804) -Last updated: 2025-06-03 +Last updated: 2025-07-17 ---------- diff --git a/sql/azure-database-for-postgresql/integration-with-purview.md b/sql/azure-database-for-postgresql/integration-with-purview.md index b289725..99bd51b 100644 --- a/sql/azure-database-for-postgresql/integration-with-purview.md +++ b/sql/azure-database-for-postgresql/integration-with-purview.md @@ -4,7 +4,7 @@ Costa Rica [![Microsoft Purview](https://img.shields.io/badge/Microsoft-Purview-blue)](https://learn.microsoft.com/en-us/azure/purview/) [![Azure PostgreSQL](https://img.shields.io/badge/Azure-PostgreSQL-blue)](https://learn.microsoft.com/en-us/azure/postgresql/) -Last updated: 2025-06-19 +Last updated: 2025-07-17 --- diff --git a/sql/azure-sql-database/README.md b/sql/azure-sql-database/README.md index bc15d7e..6fee223 100644 --- a/sql/azure-sql-database/README.md +++ b/sql/azure-sql-database/README.md @@ -6,7 +6,7 @@ Costa Rica [![GitHub](https://img.shields.io/badge/--181717?logo=github&logoColor=ffffff)](https://github.com/) [brown9804](https://github.com/brown9804) -Last updated: 2025-06-03 +Last updated: 2025-07-17 ---------- diff --git a/sql/azure-sql-database/integration-with-purview.md b/sql/azure-sql-database/integration-with-purview.md index ba7b559..8878022 100644 --- a/sql/azure-sql-database/integration-with-purview.md +++ b/sql/azure-sql-database/integration-with-purview.md @@ -5,7 +5,7 @@ Costa Rica [![Microsoft Purview](https://img.shields.io/badge/Microsoft-Purview-blue)](https://learn.microsoft.com/en-us/azure/purview/) [![Azure SQL Database](https://img.shields.io/badge/Azure-SQL-blue)](https://learn.microsoft.com/en-us/azure/sql-database/) -Last updated: 2025-06-19 +Last updated: 2025-07-17 --- diff --git a/sql/oracle-database-on-azure/README.md b/sql/oracle-database-on-azure/README.md index 9443a84..e036b8d 100644 --- a/sql/oracle-database-on-azure/README.md +++ b/sql/oracle-database-on-azure/README.md @@ -6,7 +6,7 @@ Costa Rica [![GitHub](https://img.shields.io/badge/--181717?logo=github&logoColor=ffffff)](https://github.com/) [brown9804](https://github.com/brown9804) -Last updated: 2025-06-03 +Last updated: 2025-07-17 ---------- diff --git a/sql/oracle-database-on-azure/integration-with-purview.md b/sql/oracle-database-on-azure/integration-with-purview.md index 51a3166..1017359 100644 --- a/sql/oracle-database-on-azure/integration-with-purview.md +++ b/sql/oracle-database-on-azure/integration-with-purview.md @@ -5,7 +5,7 @@ Costa Rica [![Microsoft Purview](https://img.shields.io/badge/Microsoft-Purview-blue)](https://learn.microsoft.com/en-us/azure/purview/) [![Oracle Database on Azure](https://img.shields.io/badge/Azure-Oracle-blue)](https://learn.microsoft.com/en-us/azure/oracle/) -Last updated: 2025-06-19 +Last updated: 2025-07-17 --- From 20e3c7d010920d7d208a84390ac25a91c292feb7 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Thu, 17 Jul 2025 02:45:01 +0000 Subject: [PATCH 13/17] Fix Markdown syntax issues --- Purview/Cost-Estimation.md | 27 ++++++++------ Purview/DLP-implementation.md | 10 ++---- Purview/Free-and-Enterprise.md | 13 ++++--- README.md | 36 +++++++++---------- _news/az-mysql.md | 20 +++++------ _news/az-sql-mi.md | 16 ++++----- nosql/azure-cache-for-redis/README.md | 1 - .../integration-with-purview.md | 13 ++++--- .../integration-with-purview.md | 5 +++ .../integration-with-purview.md | 13 ++++--- .../integration-with-purview.md | 6 +++- .../integration-with-purview.md | 4 +++ sql/azure-database-for-mysql/README.md | 7 +--- .../integration-with-purview.md | 17 +++++---- sql/azure-database-for-postgresql/README.md | 3 +- .../integration-with-purview.md | 5 +++ sql/azure-sql-database/README.md | 4 ++- .../integration-with-purview.md | 15 +++++--- sql/azure-sql-managed-instance/README.md | 7 +--- .../integration-with-purview.md | 15 +++++--- sql/oracle-database-on-azure/README.md | 2 ++ .../integration-with-purview.md | 17 +++++---- sql/sql-server-2022/README.md | 12 +++---- .../integration-with-purview.md | 16 +++++---- sql/sql-server-on-azure-vm/README.md | 3 +- .../integration-with-purview.md | 15 +++++--- tool/README.md | 4 ++- 27 files changed, 175 insertions(+), 131 deletions(-) diff --git a/Purview/Cost-Estimation.md b/Purview/Cost-Estimation.md index e2e70f1..b4a7a4a 100644 --- a/Purview/Cost-Estimation.md +++ b/Purview/Cost-Estimation.md @@ -30,6 +30,7 @@ Last updated: 2025-07-17 > [!IMPORTANT] > The general formula to keep in mind for estimating the cost of Microsoft Purview is:
+> > - **Cost of Data Map**: Calculated based on the number of capacity units and the price per capacity unit per hour.
> - **Cost of Scanning**: Calculated based on the total duration (in minutes) of all scans in a month, divided by 60 minutes per hour, multiplied by the number of vCores per scan, and the price per vCore per hour.
> - **Cost of Resource Set**: Calculated based on the total duration (in hours) of processing resource set data assets in a month, multiplied by the price per vCore per hour. @@ -38,26 +39,29 @@ Last updated: 2025-07-17 $$ 1. Data Map (Always on): - - Number of Capacity Units: Typically 1 - - Total Hours in a Month: 730 hours - - Price per Capacity Unit per Hour: \$0.411 + +- Number of Capacity Units: Typically 1 +- Total Hours in a Month: 730 hours +- Price per Capacity Unit per Hour: \$0.411 $$ \text{Total Cost for Data Map} = \text{Number of Capacity Units} \times \text{Total Hours in a Month} \times \text{Price per Capacity Unit per Hour} $$ 2. Scanning (Pay as you go): - - Total Minutes of Scanning in a Month: [M] minutes - - Number of vCores per Scan: 32 - - Price per vCore per Hour: \$0.63 + +- Total Minutes of Scanning in a Month: [M] minutes +- Number of vCores per Scan: 32 +- Price per vCore per Hour: \$0.63 $$ \text{Total Cost for Scanning} = \left( \frac{\text{Total Minutes of Scanning in a Month}}{60} \right) \times \text{Number of vCores per Scan} \times \text{Price per vCore per Hour} $$ 3. Resource Set: - - Total Hours of Processing in a Month: [H] hours - - Price per vCore per Hour: \$0.21 + +- Total Hours of Processing in a Month: [H] hours +- Price per vCore per Hour: \$0.21 $$ \text{Total Cost for Resource Set} = \text{Total Hours of Processing in a Month} \times \text{Price per vCore per Hour} @@ -117,10 +121,11 @@ $$ ## Cost Estimation for Different Metadata Volumes > [!IMPORTANT] -> Microsoft Purview `scans metadata to classify, label, and protect data assets`. It does `not scan the actual data content but rather the information about the data`.
-> `The size of the data itself does not directly` impact the cost of `metadata scanning unless it affects the amount of metadata generated`. The `number of metadata assets and their complexity` are the primary factors influencing costs. +> Microsoft Purview `scans metadata to classify, label, and protect data assets`. It does `not scan the actual data content but rather the information about the data`.
+> `The size of the data itself does not directly` impact the cost of `metadata scanning unless it affects the amount of metadata generated`. The `number of metadata assets and their complexity` are the primary factors influencing costs. Assumptions: + - The number of metadata assets is assumed based on the data volume, with an average size of 1 MB per metadata asset. - The average size of each metadata asset is assumed to be 1 MB. - These estimates are based on the assumption that the governed assets and data management costs are applied for 100 hours per month. Actual costs may vary based on specific agreements with Microsoft, usage patterns, etc. @@ -145,7 +150,7 @@ Assumptions: - Include **Managed Virtual Network** and **data transfer** costs if applicable. - Get a **real-time, region-specific estimate** (e.g., for Costa Rica or any other region). - https://github.com/user-attachments/assets/05521c11-6666-4fc8-9046-14d6958798ef + ## Additional Considerations diff --git a/Purview/DLP-implementation.md b/Purview/DLP-implementation.md index 5a55aeb..272042f 100644 --- a/Purview/DLP-implementation.md +++ b/Purview/DLP-implementation.md @@ -31,7 +31,6 @@ Last updated: 2025-07-17 image - - Select `Policies` > `Create policy`: image @@ -40,7 +39,6 @@ Last updated: 2025-07-17 image - ## Define Policy Scope - Select the locations where the policy will apply (e.g., Exchange email, SharePoint sites, OneDrive accounts, Teams chat). @@ -56,9 +54,7 @@ Last updated: 2025-07-17 image - - https://github.com/user-attachments/assets/a9165b97-f197-4f37-877e-9776015a3297 - + ## Set Up Alerts and Notifications @@ -71,7 +67,7 @@ Last updated: 2025-07-17 ## Customize access and override settings -https://github.com/user-attachments/assets/eb3d57d3-5bef-43f2-b069-1d25c3ef047b + ## Test and Deploy the Policy @@ -81,7 +77,7 @@ https://github.com/user-attachments/assets/eb3d57d3-5bef-43f2-b069-1d25c3ef047b image - https://github.com/user-attachments/assets/0a38b331-33e8-4e15-96be-3edbe79119f6 + ## Monitor and Manage Policies diff --git a/Purview/Free-and-Enterprise.md b/Purview/Free-and-Enterprise.md index 6032f2b..14c15e2 100644 --- a/Purview/Free-and-Enterprise.md +++ b/Purview/Free-and-Enterprise.md @@ -31,12 +31,12 @@ Last updated: 2025-07-17 - [Free vs Enterprise](#free-vs-enterprise) - [Overview](#overview) - [Microsoft Purview Pricing Model](#microsoft-purview-pricing-model) - - [Key Differences](#key-differences) + - [Key Differences](#key-differences) - [How Microsoft Purview can be used](#how-microsoft-purview-can-be-used) - - [Scenario 1: Data Governance for a Financial Institution](#scenario-1-data-governance-for-a-financial-institution) - - [Scenario 2: Data Protection for a Healthcare Provider](#scenario-2-data-protection-for-a-healthcare-provider) - - [Scenario 3: Data Analytics for an E-commerce Company](#scenario-3-data-analytics-for-an-e-commerce-company) - - [Scenario 4: Compliance Management for a Global Enterprise](#scenario-4-compliance-management-for-a-global-enterprise) + - [Scenario 1: Data Governance for a Financial Institution](#scenario-1-data-governance-for-a-financial-institution) + - [Scenario 2: Data Protection for a Healthcare Provider](#scenario-2-data-protection-for-a-healthcare-provider) + - [Scenario 3: Data Analytics for an E-commerce Company](#scenario-3-data-analytics-for-an-e-commerce-company) + - [Scenario 4: Compliance Management for a Global Enterprise](#scenario-4-compliance-management-for-a-global-enterprise) - [Examples of use cases](#examples-of-use-cases) - [Collect metadata information from Apache Airflow](#collect-metadata-information-from-apache-airflow) @@ -72,6 +72,7 @@ Last updated: 2025-07-17 ## Overview > Keypoints of Microsoft Purview:
+> > 1. `Integration with Microsoft Ecosystem`: Purview offers deep integration with Azure, Power BI, and Microsoft 365, providing a seamless experience for organizations already using these tools.
> 2. `Advanced Governance and Compliance`: Purview provides robust governance and compliance features, ensuring your data management practices meet regulatory standards.
> 3. `AI-Powered Search and Discovery`: With AI-driven capabilities, Purview enhances data discovery and classification, making it easier to find and manage data assets.
@@ -521,11 +522,13 @@ Find below different scenarios to manage data governance, protection, and compli > This capability is currently in public preview and is achieved through integration with **OpenLineage**, an open framework for data lineage collection and analysis. How it works: + 1. **Enable OpenLineage in Airflow**: By enabling OpenLineage in your Airflow instance, metadata and lineage information about jobs and datasets are automatically tracked as Directed Acyclic Graphs (DAGs) execute. 2. **Azure Event Hubs**: The tracked metadata and lineage information are sent to an Azure Event Hubs instance that you configure. 3. **Microsoft Purview**: Purview subscribes to the events from Azure Event Hubs, parses them, and ingests the metadata and lineage into the data map. This integration supports capturing metadata such as: + - Airflow workspace - Airflow DAG - Airflow task diff --git a/README.md b/README.md index e4ed121..1a0a8d1 100644 --- a/README.md +++ b/README.md @@ -18,7 +18,6 @@ Last updated: 2025-07-17 - > [!IMPORTANT] > The [Azure Databases Advisor Tool](https://microsoftcloudessentials-learninghub.github.io/Azure-Databases-Purview-Advisor/) is designed to help users select the most suitable Azure database service based on their specific use case. It provides recommendations by analyzing user inputs such as data type, scalability needs, latency requirements, and more. > The information provided and any document (such as scripts, sample codes, etc.) is provided `AS-IS` and `WITH ALL FAULTS`. Pricing estimates are for `demonstration purposes only and do not reflect final pricing`. `Microsoft assumes no liability` for your use of this information and makes no guarantees or warranties, expressed or implied, regarding its accuracy or completeness, including any pricing details. `Please note that these demos are intended as a guide and are based on personal experiences. For official guidance, support, or more detailed information, please refer to Microsoft's official documentation or contact Microsoft directly`: [Microsoft Sales and Support](https://support.microsoft.com/contactus?ContactUsExperienceEntryPointAssetId=S.HP.SMC-HOME) @@ -33,30 +32,29 @@ Last updated: 2025-07-17 Details (Click to expand) > - **Formats**
-> - Structured: Stored in predefined formats like rows and columns with consistent schema enforcement.
-> - Unstructured: Exists in diverse formats like free text, images, audio, video, and documents that lack a formal structure.
+> - Structured: Stored in predefined formats like rows and columns with consistent schema enforcement.
+> - Unstructured: Exists in diverse formats like free text, images, audio, video, and documents that lack a formal structure.
> - **Storage Model**
-> - Structured: Uses rigid, predefined schemas in relational databases ensuring integrity and data validation.
-> - Unstructured: Stored in flexible formats such as object storage, document stores, or blob storage without a fixed schema.
+> - Structured: Uses rigid, predefined schemas in relational databases ensuring integrity and data validation.
+> - Unstructured: Stored in flexible formats such as object storage, document stores, or blob storage without a fixed schema.
> - **Databases**
-> - Structured: Managed through SQL-based systems like Azure SQL, MySQL, and PostgreSQL.
-> - Unstructured: Supported by NoSQL systems like Cosmos DB, MongoDB, and cloud-native data lakes.
+> - Structured: Managed through SQL-based systems like Azure SQL, MySQL, and PostgreSQL.
+> - Unstructured: Supported by NoSQL systems like Cosmos DB, MongoDB, and cloud-native data lakes.
> - **Ease of Search**
-> - Structured: Easily queried using SQL, indexing, and standardized query languages.
-> - Unstructured: Requires more advanced approaches like keyword extraction, OCR, or AI-assisted search tools.
+> - Structured: Easily queried using SQL, indexing, and standardized query languages.
+> - Unstructured: Requires more advanced approaches like keyword extraction, OCR, or AI-assisted search tools.
> - **Analysis Methods**
-> - Structured: Suited for quantitative techniques, including statistical modeling, trend analysis, and aggregation.
-> - Unstructured: Often analyzed with qualitative approaches like NLP, sentiment analysis, topic modeling, or deep learning.
+> - Structured: Suited for quantitative techniques, including statistical modeling, trend analysis, and aggregation.
+> - Unstructured: Often analyzed with qualitative approaches like NLP, sentiment analysis, topic modeling, or deep learning.
> - **Tools and Technologies**
-> - Structured: RDBMS (SQL Server, Oracle), OLTP systems, CRM platforms, and OLAP tools for analytics.
-> - Unstructured: NoSQL DBMS, data mining frameworks, ML pipelines, AI services, and visualization platforms like Power BI.
+> - Structured: RDBMS (SQL Server, Oracle), OLTP systems, CRM platforms, and OLAP tools for analytics.
+> - Unstructured: NoSQL DBMS, data mining frameworks, ML pipelines, AI services, and visualization platforms like Power BI.
> - **Specialists**
-> - Structured: Typically handled by business analysts, software engineers, solution architects, and DBAs.
-> - Unstructured: Requires data scientists, AI/ML specialists, information architects, and advanced data engineers.
+> - Structured: Typically handled by business analysts, software engineers, solution architects, and DBAs.
+> - Unstructured: Requires data scientists, AI/ML specialists, information architects, and advanced data engineers.
- ## Products/Services ```mermaid @@ -127,7 +125,7 @@ Click here to read more about a [quick guide on SQL Server on Azure Virtual Mach
Azure Database for PostgreSQL (PaaS) - Click to expand -> Enterprise-ready community PostgreSQL database service, fully managed by Microsoft. +> Enterprise-ready community PostgreSQL database service, fully managed by Microsoft. > - **Benefits:** High availability with up to 99.99% SLA, built-in security, and scalability.
> - **Differentiators:** Supports PostgreSQL extensions and advanced indexing options.
@@ -169,7 +167,7 @@ Click here to read more about a [quick guide on Oracle Database on Azure](./sql/
SQL Server 2022 (IaaS) - Click to expand -> Latest release of SQL Server with built-in hybrid and cloud-connected capabilities. +> Latest release of SQL Server with built-in hybrid and cloud-connected capabilities. > - **Benefits:** Brings innovations like ledger tables, Synapse Link, and built-in security enhancements.
> - **Differentiators:** Full hybrid flexibility for modern apps with backward compatibility.
@@ -197,7 +195,7 @@ Click here to read more about a [quick guide on Azure Cosmos DB](./nosql/azure-c
Azure Managed Instance for Apache Cassandra (PaaS) - Click to expand -> Managed Cassandra database service designed for massive scale and availability. +> Managed Cassandra database service designed for massive scale and availability. > - **Benefits:** Built-in automation, scalability, and hybrid deployment options.
> - **Differentiators:** Supports native Cassandra drivers and schemas with Azure-managed benefits.
diff --git a/_news/az-mysql.md b/_news/az-mysql.md index 71e91ce..441b6be 100644 --- a/_news/az-mysql.md +++ b/_news/az-mysql.md @@ -15,7 +15,6 @@ Last updated: 2025-07-17 > [!TIP] > For technical deep dives and product team insights, visit the [Azure Database Blog](https://techcommunity.microsoft.com/category/azuredatabases/blog/azuredatablog). -
List of References (Click to expand) @@ -31,19 +30,18 @@ Last updated: 2025-07-17 Table of Content (Click to expand) - [Latest Announcements](#latest-announcements) - - [Microsoft Build 2025](#microsoft-build-2025) - - [May 2025 Release](#may-2025-release) - - [Microsoft Ignite 2024](#microsoft-ignite-2024) - - [Microsoft Build 2024](#microsoft-build-2024) + - [Microsoft Build 2025](#microsoft-build-2025) + - [May 2025 Release](#may-2025-release) + - [Microsoft Ignite 2024](#microsoft-ignite-2024) + - [Microsoft Build 2024](#microsoft-build-2024) - [Feature Highlights](#feature-highlights) - - [High Availability & Disaster Recovery](#high-availability--disaster-recovery) - - [Security & Compliance](#security--compliance) - - [Developer Productivity](#developer-productivity) + - [High Availability & Disaster Recovery](#high-availability--disaster-recovery) + - [Security & Compliance](#security--compliance) + - [Developer Productivity](#developer-productivity) - [Best Practices](#best-practices)
- ## Latest Announcements ### Microsoft Build 2025 @@ -77,21 +75,23 @@ Last updated: 2025-07-17 ## Feature Highlights ### High Availability & Disaster Recovery + - Zone-redundant HA with 99.99% SLA. - Point-in-time restore and geo-redundant backups. - Accelerated Logs for mission-critical throughput. ### Security & Compliance + - Azure AD authentication and role-based access control. - Encryption at rest with customer-managed keys. - Private Link and VNet integration for network isolation. ### Developer Productivity + - Native support for Django, Laravel, Spring Boot, and more. - Deep Azure Monitor integration with custom metrics and alerts. - Serverless compute tier (preview) for bursty or unpredictable workloads. - ## Best Practices - **Enable Zone-Redundant HA** for production workloads. diff --git a/_news/az-sql-mi.md b/_news/az-sql-mi.md index 1dcc09a..d29302b 100644 --- a/_news/az-sql-mi.md +++ b/_news/az-sql-mi.md @@ -29,14 +29,14 @@ Last updated: 2025-07-17 Table of Content (Click to expand) - [Latest Announcements](#latest-announcements) - - [Microsoft Build 2025](#microsoft-build-2025) - - [May 2025 Release](#may-2025-release) - - [Microsoft Ignite 2024](#microsoft-ignite-2024) - - [Microsoft Build 2024](#microsoft-build-2024) + - [Microsoft Build 2025](#microsoft-build-2025) + - [May 2025 Release](#may-2025-release) + - [Microsoft Ignite 2024](#microsoft-ignite-2024) + - [Microsoft Build 2024](#microsoft-build-2024) - [Feature Highlights](#feature-highlights) - - [High Availability & Disaster Recovery](#high-availability--disaster-recovery) - - [Security & Compliance](#security--compliance) - - [Developer Productivity](#developer-productivity) + - [High Availability & Disaster Recovery](#high-availability--disaster-recovery) + - [Security & Compliance](#security--compliance) + - [Developer Productivity](#developer-productivity) - [Best Practices](#best-practices)
@@ -64,7 +64,6 @@ Last updated: 2025-07-17 - **Managed Instance Link Enhancements**: Improved bidirectional replication between SQL Server 2022 and SQL MI for hybrid DR and migration scenarios. - **SDK-Style SQL Projects**: Support for cross-platform CI/CD pipelines using Microsoft.Build.Sql in Azure Data Studio and VS Code. - ## Feature Highlights ### High Availability & Disaster Recovery @@ -85,7 +84,6 @@ Last updated: 2025-07-17 - SDK-style SQL projects for DevOps pipelines. - Database Watcher for deep performance insights. - ## Best Practices - **Choose the right update policy**: Use “Always-up-to-date” for innovation, or “SQL Server 2022” for compatibility. diff --git a/nosql/azure-cache-for-redis/README.md b/nosql/azure-cache-for-redis/README.md index 78d56f3..c61acbd 100644 --- a/nosql/azure-cache-for-redis/README.md +++ b/nosql/azure-cache-for-redis/README.md @@ -12,7 +12,6 @@ Last updated: 2025-07-17 > Azure Cache for Redis provides a fully managed, in-memory data store that enables high-performance and scalable caching solutions. -
Table of Content diff --git a/nosql/azure-cache-for-redis/integration-with-purview.md b/nosql/azure-cache-for-redis/integration-with-purview.md index 92c2481..57b1cc4 100644 --- a/nosql/azure-cache-for-redis/integration-with-purview.md +++ b/nosql/azure-cache-for-redis/integration-with-purview.md @@ -23,15 +23,15 @@ Last updated: 2025-07-17 Table of Content - [How to Integrate Azure Cache for Redis with Purview](#how-to-integrate-azure-cache-for-redis-with-purview) - - [Registering the Redis Cache in Purview](#registering-the-redis-cache-in-purview) - - [Enabling Unity Data Governance](#enabling-unity-data-governance) - - [Data Classification and Labeling](#data-classification-and-labeling) + - [Registering the Redis Cache in Purview](#registering-the-redis-cache-in-purview) + - [Enabling Unity Data Governance](#enabling-unity-data-governance) + - [Data Classification and Labeling](#data-classification-and-labeling) - [Managing DLP Data Loss Prevention Projects](#managing-dlp-data-loss-prevention-projects) - [Cost Management and Budgeting](#cost-management-and-budgeting) - [Best Practices](#best-practices) - [Integration with Purview for Unity Catalog](#integration-with-purview-for-unity-catalog) - - [Steps to Integrate](#steps-to-integrate) - - [Benefits](#benefits) + - [Steps to Integrate](#steps-to-integrate) + - [Benefits](#benefits)
@@ -66,6 +66,7 @@ Last updated: 2025-07-17 > Safeguard user session data stored in Redis. **Steps:** + 1. **Create a DLP Policy:** Apply to `session_data`, `user_tokens`, and `cache_keys`. 2. **Define Detection Rules:** Use classifiers for sensitive tokens, user identifiers, and session metadata. 3. **Set Actions:** @@ -78,12 +79,14 @@ Last updated: 2025-07-17 ## Cost Management and Budgeting > [!NOTE] +> > - Costs may vary based on region, scan frequency, and data volume. > - Use [Azure Pricing Calculator](https://azure.microsoft.com/en-us/pricing/calculator/) for precise estimates. > - Set up budgets and alerts in [Azure Cost Management](https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/) to avoid overruns. > **Microsoft Purview Account:**: Billed per vCore-hour and per GB of data processed during scans. > The pricing structure is based on: +> > - **Data Map** (capacity units, always-on) > - **Scanning** (pay-as-you-go, based on vCore usage and scan duration) > - **Managed Virtual Network** and **API/Data Transfer** costs for cross-cloud governance diff --git a/nosql/azure-cosmos-db-for-mongodb/integration-with-purview.md b/nosql/azure-cosmos-db-for-mongodb/integration-with-purview.md index f3eefac..4fd0274 100644 --- a/nosql/azure-cosmos-db-for-mongodb/integration-with-purview.md +++ b/nosql/azure-cosmos-db-for-mongodb/integration-with-purview.md @@ -64,6 +64,7 @@ Last updated: 2025-07-17 > Protect customer and employee profile data stored in `user_data`, `accounts`, `profiles` collections. **Steps:** + 1. **Define a DLP Policy:** Target collections with sensitive document schemas. 2. **Set Detection Parameters:** Trigger on PII, credentials, and contact information fields. 3. **Policy Actions:** @@ -79,6 +80,7 @@ Last updated: 2025-07-17 > Safeguard financial data in `payments`, `invoices`, `billing_records`. **Steps:** + 1. **Define Policy Scope:** Look for fields like `credit_card`, `billing_address`, and `transaction_id`. 2. **Detection:** Use built-in financial data classifiers. 3. **Policy Actions:** @@ -94,6 +96,7 @@ Last updated: 2025-07-17 > Protect personal health information (PHI) within `patients`, `treatment_history`, and `medications`. **Steps:** + 1. **Policy Creation:** Include diagnosis codes and treatment plans. 2. **PHI Detection:** Use custom tags like `diagnosis`, `symptoms`, `prescription_id`. 3. **Actions:** @@ -109,6 +112,7 @@ Last updated: 2025-07-17 > Secure data in `hr`, `payroll`, and `performance_reviews` collections. **Steps:** + 1. **Scope:** Apply to fields like `salary`, `review_score`, `benefit_plan`. 2. **Detection:** Match on numerical ranges and string pattern validation (e.g., ID formats). 3. **Actions:** @@ -124,6 +128,7 @@ Last updated: 2025-07-17 > Protect sensitive legal content in `case_files`, `legal_memos`, and `contracts`. **Steps:** + 1. **Classifier Setup:** Identify documents referencing legal codes, client names, settlement terms. 2. **Actions:** - Encrypt entire documents upon detection. diff --git a/nosql/azure-cosmos-db/integration-with-purview.md b/nosql/azure-cosmos-db/integration-with-purview.md index 6ad2d14..07a1747 100644 --- a/nosql/azure-cosmos-db/integration-with-purview.md +++ b/nosql/azure-cosmos-db/integration-with-purview.md @@ -23,15 +23,15 @@ Last updated: 2025-07-17 Table of Content - [How to Integrate Azure Cosmos DB with Purview](#how-to-integrate-azure-cosmos-db-with-purview) - - [Registering the Cosmos DB in Purview](#registering-the-cosmos-db-in-purview) - - [Enabling Unity Data Governance](#enabling-unity-data-governance) - - [Data Classification and Labeling](#data-classification-and-labeling) + - [Registering the Cosmos DB in Purview](#registering-the-cosmos-db-in-purview) + - [Enabling Unity Data Governance](#enabling-unity-data-governance) + - [Data Classification and Labeling](#data-classification-and-labeling) - [Managing DLP Data Loss Prevention Projects](#managing-dlp-data-loss-prevention-projects) - [Cost Management and Budgeting](#cost-management-and-budgeting) - [Best Practices](#best-practices) - [Integration with Purview for Unity Catalog](#integration-with-purview-for-unity-catalog) - - [Steps to Integrate](#steps-to-integrate) - - [Benefits](#benefits) + - [Steps to Integrate](#steps-to-integrate) + - [Benefits](#benefits)
@@ -66,6 +66,7 @@ Last updated: 2025-07-17 > Safeguard user profile data stored in Cosmos DB. **Steps:** + 1. **Create a DLP Policy:** Apply to `user_profiles`, `preferences`, and `activity_logs`. 2. **Define Detection Rules:** Use classifiers for sensitive tokens, user identifiers, and session metadata. 3. **Set Actions:** @@ -78,12 +79,14 @@ Last updated: 2025-07-17 ## Cost Management and Budgeting > [!NOTE] +> > - Costs may vary based on region, scan frequency, and data volume. > - Use [Azure Pricing Calculator](https://azure.microsoft.com/en-us/pricing/calculator/) for precise estimates. > - Set up budgets and alerts in [Azure Cost Management](https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/) to avoid overruns. > **Microsoft Purview Account:**: Billed per vCore-hour and per GB of data processed during scans. > The pricing structure is based on: +> > - **Data Map** (capacity units, always-on) > - **Scanning** (pay-as-you-go, based on vCore usage and scan duration) > - **Managed Virtual Network** and **API/Data Transfer** costs for cross-cloud governance diff --git a/nosql/azure-managed-instance-for-apache-cassandra/integration-with-purview.md b/nosql/azure-managed-instance-for-apache-cassandra/integration-with-purview.md index c76b67c..736b34c 100644 --- a/nosql/azure-managed-instance-for-apache-cassandra/integration-with-purview.md +++ b/nosql/azure-managed-instance-for-apache-cassandra/integration-with-purview.md @@ -64,6 +64,7 @@ Last updated: 2025-07-17 > Secure login and session data in tables like `auth_tokens`, `user_sessions`. **Steps:** + 1. **Target Keyspaces/Tables:** Apply to authentication-related datasets. 2. **Detection Rules:** Look for session IDs, refresh tokens, IP addresses. 3. **Policy Actions:** @@ -79,6 +80,7 @@ Last updated: 2025-07-17 > Protect sensitive e-commerce data in `orders`, `cart_items`, `billing`. **Steps:** + 1. **Scope:** Focus on fields such as `customer_id`, `product_price`, `shipping_address`. 2. **Detection:** Classify based on customer profile info and transaction markers. 3. **Actions:** @@ -94,6 +96,7 @@ Last updated: 2025-07-17 > Restrict telemetry data in `sensor_logs`, `device_metrics`, `edge_state`. **Steps:** + 1. **Identify:** Detect geo-coordinates, MAC addresses, and voltage spikes. 2. **Policy Application:** Tag location data as confidential in production. 3. **Actions:** @@ -109,6 +112,7 @@ Last updated: 2025-07-17 > Safeguard university data stored in `grades`, `student_profiles`, `transcripts`. **Steps:** + 1. **Target Fields:** `student_id`, `gpa`, `disciplinary_notes`. 2. **Actions:** - Mask grades from public query interfaces. @@ -140,7 +144,7 @@ Last updated: 2025-07-17 > Use Microsoft Purview to extend Cassandra data observability across pipelines. -### Steps: +### Steps 1. Register Cassandra instance in **Purview** and enable **Unity Catalog Sync**. 2. Set up **Lineage Connectors** to link ingestion and downstream datasets (e.g., Synapse, Power BI). diff --git a/nosql/mongo-db-atlas-on-azure/integration-with-purview.md b/nosql/mongo-db-atlas-on-azure/integration-with-purview.md index c177b21..91e164a 100644 --- a/nosql/mongo-db-atlas-on-azure/integration-with-purview.md +++ b/nosql/mongo-db-atlas-on-azure/integration-with-purview.md @@ -63,6 +63,7 @@ Last updated: 2025-07-17 > Apply governance to `customers`, `leads`, `interactions`. **Steps:** + 1. **Classify Fields:** `customer_name`, `contact_info`, `lead_source`. 2. **Set Policy Triggers:** Block JSON exports exceeding 100 records/hour. 3. **Apply Actions:** @@ -78,6 +79,7 @@ Last updated: 2025-07-17 > Secure forecasting models stored in `budgets`, `models`, `assumptions`. **Steps:** + 1. **Scope:** Forecasted revenue, cost-of-sales fields. 2. **Detection Rules:** Numeric limits, field tags (e.g., `model_id`, `confidence_score`). 3. **Actions:** @@ -93,6 +95,7 @@ Last updated: 2025-07-17 > Protect legal content in `contracts`, `legal_reviews`, `negotiations`. **Steps:** + 1. **Tag Fields:** `contract_number`, `counterparty`, `signature_date`. 2. **Policy Actions:** - Restrict full-text searches by non-legal roles. @@ -107,6 +110,7 @@ Last updated: 2025-07-17 > Manage telemetry in `events`, `device_stats`, `system_logs`. **Steps:** + 1. **Classify Columns:** Device IDs, geographic coordinates. 2. **Policies:** - Mask PII from telemetry streams ingested via Event Hubs. diff --git a/sql/azure-database-for-mysql/README.md b/sql/azure-database-for-mysql/README.md index c066930..bfb1211 100644 --- a/sql/azure-database-for-mysql/README.md +++ b/sql/azure-database-for-mysql/README.md @@ -81,18 +81,17 @@ cursor.close() connection.close() ``` - ## Using Azure Database for MySQL in a Microservices Architecture > In a microservices architecture, each service typically owns its own data store. Azure Database for MySQL fits well into this model due to its **flexibility, scalability, and managed nature**. **Implications:** + - **Database-per-Service Pattern**: Azure allows each microservice to have its own isolated MySQL instance or schema, promoting loose coupling and independent scaling. - **Polyglot Persistence**: You can mix MySQL with other Azure-managed databases (like PostgreSQL or Cosmos DB) across services, depending on the workload. - **Operational Overhead Reduction**: Azure handles patching, backups, and high availability, letting teams focus on service logic rather than infrastructure. - **Integration with Azure Kubernetes Service (AKS)**: Ideal for containerized microservices, enabling secure and performant connectivity via VNET integration and private endpoints. - ## Performance Tuning Options in Azure Database for MySQL > Azure Database for MySQL, especially in **Flexible Server**, offers a rich set of tuning capabilities: @@ -113,8 +112,6 @@ connection.close() - **Advanced Threat Protection**: Detects anomalous activities and potential vulnerabilities. - **Compliance Certifications**: Includes ISO 27001, HIPAA, PCI DSS, SOC 1/2/3, FedRAMP High, and more. - - ## Comparing Azure Database for MySQL with Other Azure Managed Databases > Azure Database for MySQL is ideal for developers who want **open-source compatibility** with the benefits of a managed platform. @@ -127,7 +124,6 @@ connection.close() | **Data Model** | Relational (MySQL) | Relational (T-SQL) | NoSQL (document, key-value, graph) | | **Open Source** | Yes | No | No | - ## Strategies for Migrating MySQL Databases to Azure > Azure supports several migration paths depending on your source environment and downtime tolerance, for large databases (hundreds of GBs to TBs), parallel dump/restore tools and staging VMs in Azure can significantly reduce migration time. @@ -137,7 +133,6 @@ connection.close() - **Replication-Based Migration**: Set up replication from source to Azure MySQL for near-zero downtime cutovers. - **Pre-Migration Assessment**: Use tools like **Azure Migrate** or **MySQL Workbench** to assess compatibility and performance implications. -
Total views diff --git a/sql/azure-database-for-mysql/integration-with-purview.md b/sql/azure-database-for-mysql/integration-with-purview.md index df8b144..036b0bd 100644 --- a/sql/azure-database-for-mysql/integration-with-purview.md +++ b/sql/azure-database-for-mysql/integration-with-purview.md @@ -24,15 +24,15 @@ Last updated: 2025-07-17 Table of Content - [How to Integrate Azure Database for MySQL with Purview](#how-to-integrate-azure-database-for-mysql-with-purview) - - [Registering the MySQL Database in Purview](#registering-the-mysql-database-in-purview) - - [Enabling Unity Data Governance](#enabling-unity-data-governance) - - [Data Classification and Labeling](#data-classification-and-labeling) + - [Registering the MySQL Database in Purview](#registering-the-mysql-database-in-purview) + - [Enabling Unity Data Governance](#enabling-unity-data-governance) + - [Data Classification and Labeling](#data-classification-and-labeling) - [Managing DLP Data Loss Prevention Projects](#managing-dlp-data-loss-prevention-projects) - [Cost Management and Budgeting](#cost-management-and-budgeting) - [Best Practices](#best-practices) - [Integration with Purview for Unity Catalog](#integration-with-purview-for-unity-catalog) - - [Steps to Integrate](#steps-to-integrate) - - [Benefits](#benefits) + - [Steps to Integrate](#steps-to-integrate) + - [Benefits](#benefits)
@@ -67,6 +67,7 @@ Last updated: 2025-07-17 > Safeguard user payment preferences and account activity in SaaS platforms hosted on MySQL. **Steps:** + 1. **Create a DLP Policy:** Apply to `subscriptions`, `payment_settings`, and `invoices`. 2. **Define Detection Rules:** Use classifiers for credit card tokens, billing addresses, and transaction amounts. 3. **Set Actions:** @@ -82,6 +83,7 @@ Last updated: 2025-07-17 > Limit access to buyer preferences, addresses, and purchase patterns. **Steps:** + 1. **Create a DLP Policy:** Focus on tables like `orders`, `shipping_info`, and `order_notes`. 2. **Define Detection Rules:** Detect fields such as customer name, address, product SKUs, and delivery comments. 3. **Set Actions:** @@ -97,6 +99,7 @@ Last updated: 2025-07-17 > Prevent accidental leaks of sensitive environment metadata logged to MySQL by dev tools. **Steps:** + 1. **Create a DLP Policy:** Apply to `debug_logs`, `system_diagnostics`, or `error_trace`. 2. **Define Detection Rules:** Detect tokens, API keys, internal IPs, or exception traces. 3. **Set Actions:** @@ -112,6 +115,7 @@ Last updated: 2025-07-17 > Enforce localization by limiting access to user data based on country or regulatory region. **Steps:** + 1. **Create a DLP Policy:** Target tables like `user_profile`, `preferences`, `order_location` with `region_code` or `country_id`. 2. **Define Detection Rules:** Apply filters by jurisdiction (e.g., only users in LATAM). 3. **Set Actions:** @@ -124,12 +128,14 @@ Last updated: 2025-07-17 ## Cost Management and Budgeting > [!NOTE] +> > - Costs may vary based on region, scan frequency, and data volume. > - Use [Azure Pricing Calculator](https://azure.microsoft.com/en-us/pricing/calculator/) for precise estimates. > - Set up budgets and alerts in [Azure Cost Management](https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/) to avoid overruns. > **Microsoft Purview Account:**: Billed per vCore-hour and per GB of data processed during scans. > The pricing structure is based on: +> > - **Data Map** (capacity units, always-on) > - **Scanning** (pay-as-you-go, based on vCore usage and scan duration) > - **Managed Virtual Network** and **API/Data Transfer** costs for cross-cloud governance @@ -170,7 +176,6 @@ Last updated: 2025-07-17 - Improved compliance and governance. - Centralized management of data assets. -
Total views diff --git a/sql/azure-database-for-postgresql/README.md b/sql/azure-database-for-postgresql/README.md index e5d9253..4dd41be 100644 --- a/sql/azure-database-for-postgresql/README.md +++ b/sql/azure-database-for-postgresql/README.md @@ -24,14 +24,15 @@ Last updated: 2025-07-17 - ## Features + - **High Availability**: Offers up to 99.99% SLA with built-in high availability. - **Automated Backups**: Daily backups with point-in-time restore capabilities. - **Scaling**: Easily scale compute and storage resources without downtime. - **Security**: Advanced security features including encryption, firewall rules, and virtual network service endpoints. ## Use Cases + - Cloud-native applications using PostgreSQL frameworks like Django or Flask. - Applications requiring high availability and disaster recovery. - Development and testing environments that need quick provisioning. diff --git a/sql/azure-database-for-postgresql/integration-with-purview.md b/sql/azure-database-for-postgresql/integration-with-purview.md index 99bd51b..2854827 100644 --- a/sql/azure-database-for-postgresql/integration-with-purview.md +++ b/sql/azure-database-for-postgresql/integration-with-purview.md @@ -68,6 +68,7 @@ Last updated: 2025-07-17 > Fulfill data subject requests and enforce retention policies on customer records. **Steps:** + 1. **Create a DLP Policy:** Apply to tables like `customers`, `login_sessions`, `preferences`. 2. **Define Detection Rules:** Use classifiers for names, emails, phone numbers, and IP addresses. 3. **Set Actions:** @@ -83,6 +84,7 @@ Last updated: 2025-07-17 > Protect payment records in compliance with PCI DSS or local finance laws. **Steps:** + 1. **Create a DLP Policy:** Focus on tables like `transactions`, `billing_statements`, `refunds`. 2. **Define Detection Rules:** Detect patterns like credit card numbers, bank routing codes, or IBANs. 3. **Set Actions:** @@ -98,6 +100,7 @@ Last updated: 2025-07-17 > Enforce HIPAA-equivalent practices for healthcare-related apps built on PostgreSQL. **Steps:** + 1. **Create a DLP Policy:** Scan tables like `medical_visits`, `patient_conditions`, `insurance_claims`. 2. **Define Detection Rules:** Detect MRNs, ICD-10 codes, medication fields. 3. **Set Actions:** @@ -112,12 +115,14 @@ Last updated: 2025-07-17 > Integrating with Purview introduces additional costs for scanning, classification, and governance. Below is a breakdown and example budget. > [!NOTE] +> > - Costs may vary based on region, scan frequency, and data volume. > - Use [Azure Pricing Calculator](https://azure.microsoft.com/en-us/pricing/calculator/) for precise estimates. > - Set up budgets and alerts in [Azure Cost Management](https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/) to avoid overruns. > **Microsoft Purview Account:**: Billed per vCore-hour and per GB of data processed during scans. > The pricing structure is based on: +> > - **Data Map** (capacity units, always-on) > - **Scanning** (pay-as-you-go, based on vCore usage and scan duration) > - **Managed Virtual Network** and **API/Data Transfer** costs for cross-cloud governance diff --git a/sql/azure-sql-database/README.md b/sql/azure-sql-database/README.md index 6fee223..37732c2 100644 --- a/sql/azure-sql-database/README.md +++ b/sql/azure-sql-database/README.md @@ -22,17 +22,20 @@ Last updated: 2025-07-17 ## Features + - **Managed Service**: Automates database management tasks such as backups, patching, and scaling. - **High Availability**: Built-in high availability with a 99.99% SLA. - **Scalability**: Easily scale up or down based on application needs. - **Security**: Advanced security features including threat detection and encryption. ## Use Cases + - Web applications requiring a robust database backend. - Mobile applications needing a scalable and reliable data store. - Enterprise applications that require high availability and disaster recovery. ## Sample Code Snippet + ```csharp using System; using System.Data.SqlClient; @@ -94,7 +97,6 @@ class Program -
Total views diff --git a/sql/azure-sql-database/integration-with-purview.md b/sql/azure-sql-database/integration-with-purview.md index 8878022..0f28122 100644 --- a/sql/azure-sql-database/integration-with-purview.md +++ b/sql/azure-sql-database/integration-with-purview.md @@ -25,15 +25,15 @@ Last updated: 2025-07-17 Table of Content - [How to Integrate Azure SQL Database with Purview](#how-to-integrate-azure-sql-database-with-purview) - - [Registering the SQL Database in Purview](#registering-the-sql-database-in-purview) - - [Enabling Unity Data Governance](#enabling-unity-data-governance) - - [Data Classification and Labeling](#data-classification-and-labeling) + - [Registering the SQL Database in Purview](#registering-the-sql-database-in-purview) + - [Enabling Unity Data Governance](#enabling-unity-data-governance) + - [Data Classification and Labeling](#data-classification-and-labeling) - [Managing DLP Data Loss Prevention Projects](#managing-dlp-data-loss-prevention-projects) - [Cost Management and Budgeting](#cost-management-and-budgeting) - [Best Practices](#best-practices) - [Integration with Purview for Unity Catalog](#integration-with-purview-for-unity-catalog) - - [Steps to Integrate](#steps-to-integrate) - - [Benefits](#benefits) + - [Steps to Integrate](#steps-to-integrate) + - [Benefits](#benefits) @@ -68,6 +68,7 @@ Last updated: 2025-07-17 > Secure sensitive information submitted during user registration flows. **Steps:** + 1. **Create a DLP Policy:** Apply to tables like `UserAccounts`, `RegistrationForms`, or `NewCustomers`. 2. **Define Detection Rules:** Detect fields like name, email, contact number, and national IDs. 3. **Set Actions:** @@ -83,6 +84,7 @@ Last updated: 2025-07-17 > Restrict access to localized customer data based on geographic region (e.g., Costa Rica customers). **Steps:** + 1. **Create a DLP Policy:** Filter tables like `Orders`, `SupportRequests`, or `UserPreferences` with `country_code = 'CR'`. 2. **Define Detection Rules:** Use country-based tagging and IP-based access logging. 3. **Set Actions:** @@ -98,6 +100,7 @@ Last updated: 2025-07-17 > Safeguard subjective customer inputs that may contain unstructured PII. **Steps:** + 1. **Create a DLP Policy:** Apply to columns like `feedback_text`, `support_notes`, or `survey_responses`. 2. **Define Detection Rules:** Use natural language classifiers to identify PII embedded in comments. 3. **Set Actions:** @@ -111,6 +114,7 @@ Last updated: 2025-07-17 > **Microsoft Purview Account:**: Billed per vCore-hour and per GB of data processed during scans. > The pricing structure is based on: +> > - **Data Map** (capacity units, always-on) > - **Scanning** (pay-as-you-go, based on vCore usage and scan duration) > - **Managed Virtual Network** and **API/Data Transfer** costs for cross-cloud governance @@ -120,6 +124,7 @@ Last updated: 2025-07-17 > Click here to understand more about [Azure Purview Cost Estimation](../../Purview/Cost-Estimation.md) > [!NOTE] +> > - Costs may vary based on region, scan frequency, and data volume. > - Use [Azure Pricing Calculator](https://azure.microsoft.com/en-us/pricing/calculator/) for precise estimates. > - Set up budgets and alerts in [Azure Cost Management](https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/) to avoid overruns. diff --git a/sql/azure-sql-managed-instance/README.md b/sql/azure-sql-managed-instance/README.md index bf29d27..ac5ed6c 100644 --- a/sql/azure-sql-managed-instance/README.md +++ b/sql/azure-sql-managed-instance/README.md @@ -12,7 +12,6 @@ Last updated: 2025-06-03 > Azure SQL Managed Instance is a fully managed SQL Server instance that provides near-complete compatibility with on-premises SQL Server. It is designed to simplify the migration of existing applications to the cloud without requiring code changes. -
List of References @@ -43,6 +42,7 @@ Last updated: 2025-06-03 - **Compatibility**: Supports SQL Server Agent, linked servers, and cross-database transactions, making it suitable for enterprise applications. ## Use Cases + - Ideal for enterprise app migrations from legacy environments. - Suitable for applications that require SQL Server features not available in Azure SQL Database. @@ -80,7 +80,6 @@ VALUES (1, 'John', 'Doe', '2023-01-15'); | Use Cases | Cloud-native apps | Lift-and-shift of legacy SQL workloads | | Linked Servers | Unsupported | Supported | - ## Implications of Using SQL Server Agent in a Managed Instance > This support is particularly useful when trying to preserve automation behavior after migration from on-premises environments. @@ -106,10 +105,6 @@ VALUES (1, 'John', 'Doe', '2023-01-15'); - Use **backup/restore to Azure Blob Storage** for full database fidelity. - Or use **Azure DMS with continuous sync** for minimal downtime transitions. - - - -

Total Visitors

Visitor Count diff --git a/sql/azure-sql-managed-instance/integration-with-purview.md b/sql/azure-sql-managed-instance/integration-with-purview.md index b4c2a98..3c1d419 100644 --- a/sql/azure-sql-managed-instance/integration-with-purview.md +++ b/sql/azure-sql-managed-instance/integration-with-purview.md @@ -25,15 +25,15 @@ Last updated: 2025-06-19 Table of Content - [How to Integrate Azure SQL Managed Instance with Purview](#how-to-integrate-azure-sql-managed-instance-with-purview) - - [Registering the SQL Managed Instance in Purview](#registering-the-sql-managed-instance-in-purview) - - [Enabling Unity Data Governance](#enabling-unity-data-governance) - - [Data Classification and Labeling](#data-classification-and-labeling) + - [Registering the SQL Managed Instance in Purview](#registering-the-sql-managed-instance-in-purview) + - [Enabling Unity Data Governance](#enabling-unity-data-governance) + - [Data Classification and Labeling](#data-classification-and-labeling) - [Managing DLP Data Loss Prevention Projects](#managing-dlp-data-loss-prevention-projects) - [Cost Management and Budgeting](#cost-management-and-budgeting) - [Best Practices](#best-practices) - [Integration with Purview for Unity Catalog](#integration-with-purview-for-unity-catalog) - - [Steps to Integrate](#steps-to-integrate) - - [Benefits](#benefits) + - [Steps to Integrate](#steps-to-integrate) + - [Benefits](#benefits)
@@ -68,6 +68,7 @@ Last updated: 2025-06-19 > Secure access to supplier agreements and B2B NDAs hosted in SQL Managed Instance. **Steps:** + 1. **Create a DLP Policy:** Focus on tables like `LegalDocuments`, `VendorContracts`, or `PartnerNDAs`. 2. **Define Detection Rules:** Use keyword-based classifiers for contract terms, clause types, and party identifiers. 3. **Set Actions:** @@ -83,6 +84,7 @@ Last updated: 2025-06-19 > Prevent leakage of tenant data in multi-customer environments running on a shared SQL Managed Instance. **Steps:** + 1. **Create a DLP Policy:** Classify tenant identifiers in tables like `CustomerData`, `BillingRecords`, or `AppUsage`. 2. **Define Detection Rules:** Match against `tenant_id`, `org_id`, and region-specific markers. 3. **Set Actions:** @@ -98,6 +100,7 @@ Last updated: 2025-06-19 > Protect internal disaster recovery plans and business impact assessments stored in SQL MI. **Steps:** + 1. **Create a DLP Policy:** Tag documentation tables like `DR_Playbooks`, `RecoveryPlans`, and `BCP_RiskAssessment`. 2. **Define Detection Rules:** Detect sensitive recovery identifiers, backup architecture, and RTO/RPO values. 3. **Set Actions:** @@ -111,6 +114,7 @@ Last updated: 2025-06-19 > **Microsoft Purview Account:**: Billed per vCore-hour and per GB of data processed during scans. > The pricing structure is based on: +> > - **Data Map** (capacity units, always-on) > - **Scanning** (pay-as-you-go, based on vCore usage and scan duration) > - **Managed Virtual Network** and **API/Data Transfer** costs for cross-cloud governance @@ -120,6 +124,7 @@ Last updated: 2025-06-19 > Click here to understand more about [Azure Purview Cost Estimation](../../Purview/Cost-Estimation.md) > [!NOTE] +> > - Costs may vary based on region, scan frequency, and data volume. > - Use [Azure Pricing Calculator](https://azure.microsoft.com/en-us/pricing/calculator/) for precise estimates. > - Set up budgets and alerts in [Azure Cost Management](https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/) to avoid overruns. diff --git a/sql/oracle-database-on-azure/README.md b/sql/oracle-database-on-azure/README.md index e036b8d..23155a6 100644 --- a/sql/oracle-database-on-azure/README.md +++ b/sql/oracle-database-on-azure/README.md @@ -38,11 +38,13 @@ Last updated: 2025-07-17 ## Benefits + - **Flexibility**: Offers full control over the database environment, allowing for customization based on specific application needs. - **High Availability**: Ensures that Oracle applications remain available with built-in redundancy and failover capabilities. - **Cost Efficiency**: Allows organizations to utilize existing Oracle licenses, reducing overall costs. ## Use Cases + - Running core enterprise Oracle applications that require high availability and performance. - Migrating legacy Oracle applications to the cloud for improved scalability and management. diff --git a/sql/oracle-database-on-azure/integration-with-purview.md b/sql/oracle-database-on-azure/integration-with-purview.md index 1017359..2f520ed 100644 --- a/sql/oracle-database-on-azure/integration-with-purview.md +++ b/sql/oracle-database-on-azure/integration-with-purview.md @@ -25,20 +25,19 @@ Last updated: 2025-07-17 Table of Content - [How to Integrate Oracle Database on Azure with Purview](#how-to-integrate-oracle-database-on-azure-with-purview) - - [Registering the Oracle Database in Purview](#registering-the-oracle-database-in-purview) - - [Enabling Unity Data Governance](#enabling-unity-data-governance) - - [Data Classification and Labeling](#data-classification-and-labeling) + - [Registering the Oracle Database in Purview](#registering-the-oracle-database-in-purview) + - [Enabling Unity Data Governance](#enabling-unity-data-governance) + - [Data Classification and Labeling](#data-classification-and-labeling) - [Managing DLP Data Loss Prevention Projects](#managing-dlp-data-loss-prevention-projects) - [Cost Management and Budgeting](#cost-management-and-budgeting) - - [Cost Components](#cost-components) + - [Cost Components](#cost-components) - [Best Practices](#best-practices) - [Integration with Purview for Unity Catalog](#integration-with-purview-for-unity-catalog) - - [Steps to Integrate](#steps-to-integrate) - - [Benefits](#benefits) + - [Steps to Integrate](#steps-to-integrate) + - [Benefits](#benefits) - ## How to Integrate Oracle Database on Azure with Purview ### Registering the Oracle Database in Purview @@ -70,6 +69,7 @@ Last updated: 2025-07-17 > Enforce data erasure requests across customer-related tables in Oracle. **Steps:** + 1. **Create a DLP Policy:** Monitor and respond to deletion requests for tables like `CUSTOMERS`, `CONTACT_LOGS`, and `ACCOUNT_HISTORY`. 2. **Define Detection Rules:** Use Purview’s data subject tagging to flag all relevant personal data fields. 3. **Set Actions:** @@ -85,6 +85,7 @@ Last updated: 2025-07-17 > Protect sensitive reconciliation and journal entry data from internal leaks. **Steps:** + 1. **Create a DLP Policy:** Focus on Oracle ERP data, such as `GL_JOURNALS`, `RECON_TABLES`, or `LEDGER_ENTRIES`. 2. **Define Detection Rules:** Apply financial data classifiers or tag custom ERP schema elements. 3. **Set Actions:** @@ -100,6 +101,7 @@ Last updated: 2025-07-17 > Secure trial participant data, dosage logs, and test results hosted in Oracle schemas. **Steps:** + 1. **Create a DLP Policy:** Target schemas like `TRIAL_RESULTS`, `PATIENT_TRACKING`, or `MEDICATION_LOGS`. 2. **Define Detection Rules:** Detect patient IDs, consent forms, and controlled substance indicators. 3. **Set Actions:** @@ -117,6 +119,7 @@ Last updated: 2025-07-17 > **Microsoft Purview Account:**: Billed per vCore-hour and per GB of data processed during scans. > The pricing structure is based on: +> > - **Data Map** (capacity units, always-on) > - **Scanning** (pay-as-you-go, based on vCore usage and scan duration) > - **Managed Virtual Network** and **API/Data Transfer** costs for cross-cloud governance diff --git a/sql/sql-server-2022/README.md b/sql/sql-server-2022/README.md index 9cb8464..3af5785 100644 --- a/sql/sql-server-2022/README.md +++ b/sql/sql-server-2022/README.md @@ -33,16 +33,17 @@ Last updated: 2025-06-03 - [Integrating SQL Server 2022 with Azure Synapse Analytics for Real-Time Insights](#integrating-sql-server-2022-with-azure-synapse-analytics-for-real-time-insights) - [Security Enhancements in SQL Server 2022 and Their Compliance Impact](#security-enhancements-in-sql-server-2022-and-their-compliance-impact) - ## Features + - **Hybrid Capabilities**: Seamless integration with Azure services for hybrid cloud scenarios. - **Ledger Tables**: Built-in support for ledger tables to enhance data integrity and security. - **Synapse Link**: Directly connect to Azure Synapse Analytics for real-time analytics. - **Security Enhancements**: Advanced security features to protect sensitive data. ## Use Cases + - Enterprise applications requiring up-to-date SQL features and strong cloud connectivity. - Applications that benefit from hybrid deployments, allowing for flexibility in data management. @@ -69,25 +70,24 @@ WITH (SYSTEM_VERSIONING = ON (HISTORY_TABLE = dbo.LedgerTableHistory)); > This makes them a powerful tool for **financial, healthcare, and legal systems** where data integrity is non-negotiable. **Implications:** + - **Immutable History**: Ledger tables maintain a full, cryptographically verifiable history of changes, ensuring that no data can be altered without detection. - **Regulatory Compliance**: Helps meet standards like SOX, PCI DSS, and GDPR by providing nonrepudiation and traceability. - **Streamlined Audits**: Auditors can verify data integrity without relying solely on logs or manual processes. - **Minimal App Changes**: Ledger tables integrate with existing SQL Server tooling and syntax, reducing the need for external blockchain solutions. - ## Integrating SQL Server 2022 with Azure Synapse Analytics for Real-Time Insights > SQL Server 2022 introduces **Azure Synapse Link**, enabling near real-time replication of operational data into Synapse Analytics > without complex ETL pipelines. This integration empowers organizations to **analyze operational data in near real time**, unlocking faster decision-making and predictive analytics. **Benefits:** + - **Hybrid Analytics**: Combine on-prem SQL Server data with cloud-scale analytics in Synapse for unified insights. - **Change Feed Replication**: Automatically syncs changes from SQL Server to Synapse, enabling up-to-date dashboards and reports. - **No ETL Overhead**: Reduces latency and complexity by eliminating traditional extract-transform-load processes. - **Data Lake Integration**: Data lands in Azure Data Lake Storage Gen2, making it accessible for machine learning, Power BI, and more. - - ## Security Enhancements in SQL Server 2022 and Their Compliance Impact > Together, these features help organizations **meet regulatory standards** while modernizing their data infrastructure. SQL Server 2022 introduces several security upgrades that strengthen compliance posture and reduce risk: @@ -98,10 +98,6 @@ WITH (SYSTEM_VERSIONING = ON (HISTORY_TABLE = dbo.LedgerTableHistory)); - **Hypervisor-Based Security**: Isolates processes from the OS using virtualization-based security (VBS), mitigating kernel-level attacks. - **SMB over QUIC & AES-256 Encryption**: Enhances secure data transport, especially for hybrid and remote scenarios. - - - -

Total Visitors

Visitor Count diff --git a/sql/sql-server-2022/integration-with-purview.md b/sql/sql-server-2022/integration-with-purview.md index 6692bd4..16e9b72 100644 --- a/sql/sql-server-2022/integration-with-purview.md +++ b/sql/sql-server-2022/integration-with-purview.md @@ -21,20 +21,19 @@ Last updated: 2025-06-19 -
Table of Content - [How to Integrate SQL Server 2022 with Purview](#how-to-integrate-sql-server-2022-with-purview) - - [Registering the SQL Server Database in Purview](#registering-the-sql-server-database-in-purview) - - [Enabling Unity Data Governance](#enabling-unity-data-governance) - - [Data Classification and Labeling](#data-classification-and-labeling) + - [Registering the SQL Server Database in Purview](#registering-the-sql-server-database-in-purview) + - [Enabling Unity Data Governance](#enabling-unity-data-governance) + - [Data Classification and Labeling](#data-classification-and-labeling) - [Managing DLP Data Loss Prevention Projects](#managing-dlp-data-loss-prevention-projects) - [Cost Management and Budgeting](#cost-management-and-budgeting) - [Best Practices](#best-practices) - [Integration with Purview for Unity Catalog](#integration-with-purview-for-unity-catalog) - - [Steps to Integrate](#steps-to-integrate) - - [Benefits](#benefits) + - [Steps to Integrate](#steps-to-integrate) + - [Benefits](#benefits)
@@ -69,6 +68,7 @@ Last updated: 2025-06-19 > Prevent unauthorized export of customer personally identifiable information (PII). **Steps:** + 1. **Create a DLP Policy:** In Purview, define a policy targeting tables/columns with PII (e.g., email, SSN). 2. **Define Detection Rules:** Use built-in or custom classifiers to identify PII fields. 3. **Set Actions:** @@ -84,6 +84,7 @@ Last updated: 2025-06-19 > Prevent unauthorized access or leak of payroll, tax records, and bank account data. **Steps:** + 1. **Create a DLP Policy:** Target tables like `Payroll`, `Invoices`, or `TaxDocuments`. 2. **Define Detection Rules:** Use financial classifiers to detect fields like `account_number`, `routing_number`, `salary`, etc. 3. **Set Actions:** @@ -99,6 +100,7 @@ Last updated: 2025-06-19 > Protect proprietary formulas, product designs, or source code stored in SQL Server. **Steps:** + 1. **Create a DLP Policy:** Focus on R&D tables like `ProductDesign`, `AlgorithmSpecs`, or `Blueprints`. 2. **Define Detection Rules:** Customize classifiers using keywords or phrases tied to internal IP. 3. **Set Actions:** @@ -114,6 +116,7 @@ Last updated: 2025-06-19 > Comply with healthcare regulations by securing patient records and medical history. **Steps:** + 1. **Create a DLP Policy:** Target tables containing `diagnosis_codes`, `treatment_notes`, or `insurance_info`. 2. **Define Detection Rules:** Enable built-in classifiers for HIPAA-related entities such as `Patient ID`, `Diagnosis`, `Prescriptions`. 3. **Set Actions:** @@ -127,6 +130,7 @@ Last updated: 2025-06-19 > **Microsoft Purview Account:**: Billed per vCore-hour and per GB of data processed during scans. > The pricing structure is based on: +> > - **Data Map** (capacity units, always-on) > - **Scanning** (pay-as-you-go, based on vCore usage and scan duration) > - **Managed Virtual Network** and **API/Data Transfer** costs for cross-cloud governance diff --git a/sql/sql-server-on-azure-vm/README.md b/sql/sql-server-on-azure-vm/README.md index a4b770c..010e176 100644 --- a/sql/sql-server-on-azure-vm/README.md +++ b/sql/sql-server-on-azure-vm/README.md @@ -45,6 +45,7 @@ Last updated: 2025-06-03 - **Custom Applications**: Suitable for applications requiring specific SQL Server features not available in PaaS offerings. ## Sample Code Snippet + ```bash # Create a new SQL Server VM in Azure az vm create \ @@ -61,6 +62,7 @@ az vm create \ > Running SQL Server on Azure VMs (IaaS) gives you **full control** over the OS, SQL Server instance, and configuration—ideal for lift-and-shift scenarios or legacy workloads. In contrast, **PaaS solutions** like Azure SQL Database or Managed Instance abstract away infrastructure management, offering built-in high availability, automated backups, and scalability. **Key Implications:** + - **Management Overhead**: Azure VMs require patching, backup configuration, and manual HA setup. PaaS handles these automatically. - **Feature Compatibility**: SQL Server on VMs supports full SQL Server features (e.g., cross-database queries, CLR, SQL Agent), while PaaS may have limitations. - **Cost and Licensing**: VMs offer BYOL flexibility and predictable costs for long-running workloads. PaaS may be more cost-effective for variable or bursty workloads. @@ -80,7 +82,6 @@ az vm create \ - For hybrid scenarios, combine **SQL Server Failover Cluster Instances (FCIs)** with ASR or backup-based DR. - **Monitoring & Alerts**: Integrate with **Azure Monitor** and **Log Analytics** to track backup success, job failures, and RPO/RTO compliance. - ## Performance Tuning Techniques for SQL Server in a Virtualized Environment > Running SQL Server in a VM introduces unique performance considerations. Here’s how to optimize: diff --git a/sql/sql-server-on-azure-vm/integration-with-purview.md b/sql/sql-server-on-azure-vm/integration-with-purview.md index 82764b3..338b6d3 100644 --- a/sql/sql-server-on-azure-vm/integration-with-purview.md +++ b/sql/sql-server-on-azure-vm/integration-with-purview.md @@ -25,15 +25,15 @@ Last updated: 2025-06-19 Table of Content - [How to Integrate SQL Server on Azure VM with Purview](#how-to-integrate-sql-server-on-azure-vm-with-purview) - - [Registering the SQL Server on Azure VM in Purview](#registering-the-sql-server-on-azure-vm-in-purview) - - [Enabling Unity Data Governance](#enabling-unity-data-governance) - - [Data Classification and Labeling](#data-classification-and-labeling) + - [Registering the SQL Server on Azure VM in Purview](#registering-the-sql-server-on-azure-vm-in-purview) + - [Enabling Unity Data Governance](#enabling-unity-data-governance) + - [Data Classification and Labeling](#data-classification-and-labeling) - [Managing DLP Data Loss Prevention Projects](#managing-dlp-data-loss-prevention-projects) - [Cost Management and Budgeting](#cost-management-and-budgeting) - [Best Practices](#best-practices) - [Integration with Purview for Unity Catalog](#integration-with-purview-for-unity-catalog) - - [Steps to Integrate](#steps-to-integrate) - - [Benefits](#benefits) + - [Steps to Integrate](#steps-to-integrate) + - [Benefits](#benefits) @@ -68,6 +68,7 @@ Last updated: 2025-06-19 > Control export of sensitive data from Azure-hosted SQL Server in Costa Rica to other regions. **Steps:** + 1. **Create a DLP Policy:** Target columns with geo-sensitive data (e.g., address, tax ID) in tables like `CustomerProfiles` or `LocalTaxRecords`. 2. **Define Detection Rules:** Use built-in geography classifiers or custom location filters. 3. **Set Actions:** @@ -83,6 +84,7 @@ Last updated: 2025-06-19 > Detect suspicious DLP policy changes or overrides made via elevated SQL Server roles. **Steps:** + 1. **Create a DLP Policy:** Monitor admin actions on high-risk tables or rows marked as classified. 2. **Define Detection Rules:** Audit DDL/DML operations through SQL logs with extended audit policies. 3. **Set Actions:** @@ -98,6 +100,7 @@ Last updated: 2025-06-19 > Identify and block unauthorized data movement to unmanaged apps or storage targets. **Steps:** + 1. **Create a DLP Policy:** Focus on exports to unknown endpoints (e.g., personal OneDrive, rogue FTP servers). 2. **Define Detection Rules:** Use endpoint traffic patterns and Purview integration with Microsoft Defender. @@ -113,12 +116,14 @@ Last updated: 2025-06-19 > Integrating with Purview introduces additional costs for scanning, classification, and governance. Below is a breakdown and example budget. > [!NOTE] +> > - Costs may vary based on region, scan frequency, and data volume. > - Use [Azure Pricing Calculator](https://azure.microsoft.com/en-us/pricing/calculator/) for precise estimates. > - Set up budgets and alerts in [Azure Cost Management](https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/) to avoid overruns. > **Microsoft Purview Account:**: Billed per vCore-hour and per GB of data processed during scans. > The pricing structure is based on: +> > - **Data Map** (capacity units, always-on) > - **Scanning** (pay-as-you-go, based on vCore usage and scan duration) > - **Managed Virtual Network** and **API/Data Transfer** costs for cross-cloud governance diff --git a/tool/README.md b/tool/README.md index 1878d59..16f1f94 100644 --- a/tool/README.md +++ b/tool/README.md @@ -27,10 +27,10 @@ Last updated: 2025-07-17 - > The [Azure Databases Advisor Tool](https://microsoftcloudessentials-learninghub.github.io/Azure-Databases-Purview-Advisor/) is designed to help users select the most suitable Azure database service based on their specific use case. It provides recommendations by analyzing user inputs such as data type, scalability needs, latency requirements, and more. This tool consists of: + - **Static Frontend**: A web-based interface for users to input their requirements and view recommendations. The frontend operates independently and uses hardcoded logic for recommendations. - **Optional Backend**: A Flask API that processes user inputs and provides dynamic recommendations. The backend must be deployed separately to enable advanced functionality. @@ -77,11 +77,13 @@ tool/ Deployment Instructions (Click here to expand) > **Backend Deployment**: + 1. Use Azure App Service or Azure Functions to deploy the Flask API (`app.py`). 2. Ensure the API endpoint is accessible to the frontend. 3. Use Azure Monitor for logging and diagnostics. > **Frontend Deployment**: + 1. Deploy the static web app (`index.html`, `script.js`, `styles.css`) to Azure Static Web Apps. 2. Update the backend URL in `script.js` to point to the deployed API (if using the backend). From b6b73902fa400ab4061e19d1b2583e111cc9b328 Mon Sep 17 00:00:00 2001 From: Timna Brown <24630902+brown9804@users.noreply.github.com> Date: Wed, 16 Jul 2025 20:46:01 -0600 Subject: [PATCH 14/17] pull -> push --- .github/workflows/use-visitor-counter.yml | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/.github/workflows/use-visitor-counter.yml b/.github/workflows/use-visitor-counter.yml index 4aa2c96..d5c9ec1 100644 --- a/.github/workflows/use-visitor-counter.yml +++ b/.github/workflows/use-visitor-counter.yml @@ -57,31 +57,33 @@ jobs: git config --global user.name "github-actions[bot]" git config --global user.email "github-actions[bot]@users.noreply.github.com" + # Commit and push logic for PR events - name: Commit and push changes (PR) if: github.event_name == 'pull_request' env: TOKEN: ${{ secrets.GITHUB_TOKEN }} run: | git fetch origin - git checkout -b ${{ github.event.pull_request.head.ref }} origin/${{ github.event.pull_request.head.ref }} + git checkout ${{ github.head_ref }} git add "*.md" metrics.json git commit -m "Update visitor count" || echo "No changes to commit" git remote set-url origin https://x-access-token:${TOKEN}@github.com/${{ github.repository }} - git pull --rebase origin ${{ github.event.pull_request.head.ref }} || echo "No rebase needed" - git push origin HEAD:${{ github.event.pull_request.head.ref }} + git pull --rebase origin ${{ github.head_ref }} || echo "No rebase needed" + git push origin HEAD:${{ github.head_ref }} + # Commit and push logic for non-PR events (schedule, workflow_dispatch) - name: Commit and push changes (non-PR) if: github.event_name != 'pull_request' env: TOKEN: ${{ secrets.GITHUB_TOKEN }} run: | git fetch origin - git checkout ${{ github.event.pull_request.head.ref }} || git checkout -b ${{ github.event.pull_request.head.ref }} origin/${{ github.event.pull_request.head.ref }} + git checkout ${{ github.ref_name }} || git checkout -b ${{ github.ref_name }} origin/${{ github.ref_name }} git add "*.md" metrics.json git commit -m "Update visitor count" || echo "No changes to commit" git remote set-url origin https://x-access-token:${TOKEN}@github.com/${{ github.repository }} - git pull --rebase origin ${{ github.event.pull_request.head.ref }} || echo "No rebase needed" - git push origin HEAD:${{ github.event.pull_request.head.ref }} + git pull --rebase origin ${{ github.ref_name }} || echo "No rebase needed" + git push origin HEAD:${{ github.ref_name }} - name: Create Pull Request (non-PR) if: github.event_name != 'pull_request' From 419b4db81b35fbf310f64a586112b6759d953e4e Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Thu, 17 Jul 2025 02:46:13 +0000 Subject: [PATCH 15/17] Update visitor count --- Purview/Cost-Estimation.md | 4 +- Purview/DLP-Overview.md | 4 +- Purview/DLP-implementation.md | 4 +- Purview/Free-and-Enterprise.md | 4 +- README.md | 4 +- _news/az-mysql.md | 4 +- _news/az-sql-mi.md | 4 +- metrics.json | 37 +++++++++++++++++++ nosql/azure-cache-for-redis/README.md | 4 +- .../integration-with-purview.md | 4 +- nosql/azure-cosmos-db-for-mongodb/README.md | 4 +- .../integration-with-purview.md | 4 +- nosql/azure-cosmos-db/README.md | 4 +- .../integration-with-purview.md | 4 +- .../README.md | 4 +- .../integration-with-purview.md | 4 +- nosql/mongo-db-atlas-on-azure/README.md | 4 +- .../integration-with-purview.md | 4 +- sql/azure-database-for-mysql/README.md | 4 +- .../integration-with-purview.md | 4 +- sql/azure-database-for-postgresql/README.md | 4 +- .../integration-with-purview.md | 4 +- sql/azure-sql-database/README.md | 4 +- .../integration-with-purview.md | 4 +- sql/oracle-database-on-azure/README.md | 4 +- .../integration-with-purview.md | 4 +- tool/README.md | 4 +- 27 files changed, 89 insertions(+), 52 deletions(-) create mode 100644 metrics.json diff --git a/Purview/Cost-Estimation.md b/Purview/Cost-Estimation.md index b4a7a4a..37f1226 100644 --- a/Purview/Cost-Estimation.md +++ b/Purview/Cost-Estimation.md @@ -166,7 +166,7 @@ Assumptions:
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/Purview/DLP-Overview.md b/Purview/DLP-Overview.md index 7a27aaf..b0e8b03 100644 --- a/Purview/DLP-Overview.md +++ b/Purview/DLP-Overview.md @@ -79,7 +79,7 @@ Last updated: 2025-07-17
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/Purview/DLP-implementation.md b/Purview/DLP-implementation.md index 272042f..d46ff24 100644 --- a/Purview/DLP-implementation.md +++ b/Purview/DLP-implementation.md @@ -91,7 +91,7 @@ Last updated: 2025-07-17
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/Purview/Free-and-Enterprise.md b/Purview/Free-and-Enterprise.md index 14c15e2..59bbb66 100644 --- a/Purview/Free-and-Enterprise.md +++ b/Purview/Free-and-Enterprise.md @@ -535,7 +535,7 @@ This integration supports capturing metadata such as:
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/README.md b/README.md index 1a0a8d1..4bc2454 100644 --- a/README.md +++ b/README.md @@ -250,7 +250,7 @@ Click here to read more about a [quick guide on Azure Cache for Redis](./nosql/a
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/_news/az-mysql.md b/_news/az-mysql.md index 441b6be..5eddc1b 100644 --- a/_news/az-mysql.md +++ b/_news/az-mysql.md @@ -103,7 +103,7 @@ Last updated: 2025-07-17
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/_news/az-sql-mi.md b/_news/az-sql-mi.md index d29302b..ac78c55 100644 --- a/_news/az-sql-mi.md +++ b/_news/az-sql-mi.md @@ -95,7 +95,7 @@ Last updated: 2025-07-17
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/metrics.json b/metrics.json new file mode 100644 index 0000000..8665541 --- /dev/null +++ b/metrics.json @@ -0,0 +1,37 @@ +[ + { + "date": "2025-07-07", + "count": 330, + "uniques": 20 + }, + { + "date": "2025-07-08", + "count": 159, + "uniques": 6 + }, + { + "date": "2025-07-10", + "count": 482, + "uniques": 1 + }, + { + "date": "2025-07-11", + "count": 170, + "uniques": 4 + }, + { + "date": "2025-07-12", + "count": 7, + "uniques": 1 + }, + { + "date": "2025-07-14", + "count": 130, + "uniques": 2 + }, + { + "date": "2025-07-15", + "count": 2, + "uniques": 1 + } +] \ No newline at end of file diff --git a/nosql/azure-cache-for-redis/README.md b/nosql/azure-cache-for-redis/README.md index c61acbd..4635a35 100644 --- a/nosql/azure-cache-for-redis/README.md +++ b/nosql/azure-cache-for-redis/README.md @@ -76,7 +76,7 @@ print(value)
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/nosql/azure-cache-for-redis/integration-with-purview.md b/nosql/azure-cache-for-redis/integration-with-purview.md index 57b1cc4..bf5daf0 100644 --- a/nosql/azure-cache-for-redis/integration-with-purview.md +++ b/nosql/azure-cache-for-redis/integration-with-purview.md @@ -126,7 +126,7 @@ Last updated: 2025-07-17
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/nosql/azure-cosmos-db-for-mongodb/README.md b/nosql/azure-cosmos-db-for-mongodb/README.md index 881e59e..c0e5950 100644 --- a/nosql/azure-cosmos-db-for-mongodb/README.md +++ b/nosql/azure-cosmos-db-for-mongodb/README.md @@ -72,7 +72,7 @@ for doc in collection.find():
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/nosql/azure-cosmos-db-for-mongodb/integration-with-purview.md b/nosql/azure-cosmos-db-for-mongodb/integration-with-purview.md index 4fd0274..1593d31 100644 --- a/nosql/azure-cosmos-db-for-mongodb/integration-with-purview.md +++ b/nosql/azure-cosmos-db-for-mongodb/integration-with-purview.md @@ -175,7 +175,7 @@ Last updated: 2025-07-17
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/nosql/azure-cosmos-db/README.md b/nosql/azure-cosmos-db/README.md index 2680953..d4d0e68 100644 --- a/nosql/azure-cosmos-db/README.md +++ b/nosql/azure-cosmos-db/README.md @@ -92,7 +92,7 @@ for item in items:
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/nosql/azure-cosmos-db/integration-with-purview.md b/nosql/azure-cosmos-db/integration-with-purview.md index 07a1747..6158c22 100644 --- a/nosql/azure-cosmos-db/integration-with-purview.md +++ b/nosql/azure-cosmos-db/integration-with-purview.md @@ -126,7 +126,7 @@ Last updated: 2025-07-17
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/nosql/azure-managed-instance-for-apache-cassandra/README.md b/nosql/azure-managed-instance-for-apache-cassandra/README.md index e18f84c..0a83194 100644 --- a/nosql/azure-managed-instance-for-apache-cassandra/README.md +++ b/nosql/azure-managed-instance-for-apache-cassandra/README.md @@ -95,7 +95,7 @@ for row in rows:
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/nosql/azure-managed-instance-for-apache-cassandra/integration-with-purview.md b/nosql/azure-managed-instance-for-apache-cassandra/integration-with-purview.md index 736b34c..d358769 100644 --- a/nosql/azure-managed-instance-for-apache-cassandra/integration-with-purview.md +++ b/nosql/azure-managed-instance-for-apache-cassandra/integration-with-purview.md @@ -159,7 +159,7 @@ Last updated: 2025-07-17
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/nosql/mongo-db-atlas-on-azure/README.md b/nosql/mongo-db-atlas-on-azure/README.md index 2150e6e..5cac38c 100644 --- a/nosql/mongo-db-atlas-on-azure/README.md +++ b/nosql/mongo-db-atlas-on-azure/README.md @@ -72,7 +72,7 @@ for doc in collection.find():
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/nosql/mongo-db-atlas-on-azure/integration-with-purview.md b/nosql/mongo-db-atlas-on-azure/integration-with-purview.md index 91e164a..14b2559 100644 --- a/nosql/mongo-db-atlas-on-azure/integration-with-purview.md +++ b/nosql/mongo-db-atlas-on-azure/integration-with-purview.md @@ -156,7 +156,7 @@ Last updated: 2025-07-17
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/sql/azure-database-for-mysql/README.md b/sql/azure-database-for-mysql/README.md index bfb1211..1766a0e 100644 --- a/sql/azure-database-for-mysql/README.md +++ b/sql/azure-database-for-mysql/README.md @@ -135,7 +135,7 @@ connection.close()
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/sql/azure-database-for-mysql/integration-with-purview.md b/sql/azure-database-for-mysql/integration-with-purview.md index 036b0bd..04e5e2f 100644 --- a/sql/azure-database-for-mysql/integration-with-purview.md +++ b/sql/azure-database-for-mysql/integration-with-purview.md @@ -178,7 +178,7 @@ Last updated: 2025-07-17
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/sql/azure-database-for-postgresql/README.md b/sql/azure-database-for-postgresql/README.md index 4dd41be..3234820 100644 --- a/sql/azure-database-for-postgresql/README.md +++ b/sql/azure-database-for-postgresql/README.md @@ -101,7 +101,7 @@ conn.close()
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/sql/azure-database-for-postgresql/integration-with-purview.md b/sql/azure-database-for-postgresql/integration-with-purview.md index 2854827..49152aa 100644 --- a/sql/azure-database-for-postgresql/integration-with-purview.md +++ b/sql/azure-database-for-postgresql/integration-with-purview.md @@ -157,7 +157,7 @@ Last updated: 2025-07-17
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/sql/azure-sql-database/README.md b/sql/azure-sql-database/README.md index 37732c2..caf5fc5 100644 --- a/sql/azure-sql-database/README.md +++ b/sql/azure-sql-database/README.md @@ -99,7 +99,7 @@ class Program
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/sql/azure-sql-database/integration-with-purview.md b/sql/azure-sql-database/integration-with-purview.md index 0f28122..359b187 100644 --- a/sql/azure-sql-database/integration-with-purview.md +++ b/sql/azure-sql-database/integration-with-purview.md @@ -163,7 +163,7 @@ Last updated: 2025-07-17
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/sql/oracle-database-on-azure/README.md b/sql/oracle-database-on-azure/README.md index 23155a6..2ad8fc0 100644 --- a/sql/oracle-database-on-azure/README.md +++ b/sql/oracle-database-on-azure/README.md @@ -102,7 +102,7 @@ CREATE TABLE employees (
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/sql/oracle-database-on-azure/integration-with-purview.md b/sql/oracle-database-on-azure/integration-with-purview.md index 2f520ed..c66209b 100644 --- a/sql/oracle-database-on-azure/integration-with-purview.md +++ b/sql/oracle-database-on-azure/integration-with-purview.md @@ -162,7 +162,7 @@ Last updated: 2025-07-17
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

diff --git a/tool/README.md b/tool/README.md index 16f1f94..397ead6 100644 --- a/tool/README.md +++ b/tool/README.md @@ -129,7 +129,7 @@ tool/
- Total views -

Refresh Date: 2025-07-16

+ Total views +

Refresh Date: 2025-07-17

From deade329d7b892261b2c973971a807cc853e2054 Mon Sep 17 00:00:00 2001 From: Timna Brown <24630902+brown9804@users.noreply.github.com> Date: Wed, 16 Jul 2025 20:47:02 -0600 Subject: [PATCH 16/17] adding badge --- sql/azure-sql-managed-instance/README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/sql/azure-sql-managed-instance/README.md b/sql/azure-sql-managed-instance/README.md index ac5ed6c..b4ab2f9 100644 --- a/sql/azure-sql-managed-instance/README.md +++ b/sql/azure-sql-managed-instance/README.md @@ -105,7 +105,9 @@ VALUES (1, 'John', 'Doe', '2023-01-15'); - Use **backup/restore to Azure Blob Storage** for full database fidelity. - Or use **Azure DMS with continuous sync** for minimal downtime transitions. +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-16

+ From 4d480609afc013e8a0f1fe496c3104a0d377efb9 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Thu, 17 Jul 2025 02:47:12 +0000 Subject: [PATCH 17/17] Update last modified date in Markdown files --- sql/azure-sql-managed-instance/README.md | 2 +- sql/azure-sql-managed-instance/integration-with-purview.md | 2 +- sql/sql-server-2022/README.md | 2 +- sql/sql-server-2022/integration-with-purview.md | 2 +- sql/sql-server-on-azure-vm/README.md | 2 +- sql/sql-server-on-azure-vm/integration-with-purview.md | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/sql/azure-sql-managed-instance/README.md b/sql/azure-sql-managed-instance/README.md index b4ab2f9..ec57ce5 100644 --- a/sql/azure-sql-managed-instance/README.md +++ b/sql/azure-sql-managed-instance/README.md @@ -6,7 +6,7 @@ Costa Rica [![GitHub](https://img.shields.io/badge/--181717?logo=github&logoColor=ffffff)](https://github.com/) [brown9804](https://github.com/brown9804) -Last updated: 2025-06-03 +Last updated: 2025-07-17 ---------- diff --git a/sql/azure-sql-managed-instance/integration-with-purview.md b/sql/azure-sql-managed-instance/integration-with-purview.md index 3c1d419..8b67813 100644 --- a/sql/azure-sql-managed-instance/integration-with-purview.md +++ b/sql/azure-sql-managed-instance/integration-with-purview.md @@ -5,7 +5,7 @@ Costa Rica [![Microsoft Purview](https://img.shields.io/badge/Microsoft-Purview-blue)](https://learn.microsoft.com/en-us/azure/purview/) [![Azure SQL Managed Instance](https://img.shields.io/badge/Azure-SQLMI-blue)](https://learn.microsoft.com/en-us/azure/sql-managed-instance/) -Last updated: 2025-06-19 +Last updated: 2025-07-17 --- diff --git a/sql/sql-server-2022/README.md b/sql/sql-server-2022/README.md index 3af5785..c0f66f6 100644 --- a/sql/sql-server-2022/README.md +++ b/sql/sql-server-2022/README.md @@ -6,7 +6,7 @@ Costa Rica [![GitHub](https://img.shields.io/badge/--181717?logo=github&logoColor=ffffff)](https://github.com/) [brown9804](https://github.com/brown9804) -Last updated: 2025-06-03 +Last updated: 2025-07-17 ---------- diff --git a/sql/sql-server-2022/integration-with-purview.md b/sql/sql-server-2022/integration-with-purview.md index 16e9b72..80d1891 100644 --- a/sql/sql-server-2022/integration-with-purview.md +++ b/sql/sql-server-2022/integration-with-purview.md @@ -5,7 +5,7 @@ Costa Rica [![Microsoft Purview](https://img.shields.io/badge/Microsoft-Purview-blue)](https://learn.microsoft.com/en-us/azure/purview/) [![SQL Server 2022](https://img.shields.io/badge/SQL%20Server%202022-blue)](https://learn.microsoft.com/en-us/sql/sql-server/?view=sql-server-ver15) -Last updated: 2025-06-19 +Last updated: 2025-07-17 --- diff --git a/sql/sql-server-on-azure-vm/README.md b/sql/sql-server-on-azure-vm/README.md index 010e176..d281748 100644 --- a/sql/sql-server-on-azure-vm/README.md +++ b/sql/sql-server-on-azure-vm/README.md @@ -6,7 +6,7 @@ Costa Rica [![GitHub](https://img.shields.io/badge/--181717?logo=github&logoColor=ffffff)](https://github.com/) [brown9804](https://github.com/brown9804) -Last updated: 2025-06-03 +Last updated: 2025-07-17 ---------- diff --git a/sql/sql-server-on-azure-vm/integration-with-purview.md b/sql/sql-server-on-azure-vm/integration-with-purview.md index 338b6d3..d4ac89a 100644 --- a/sql/sql-server-on-azure-vm/integration-with-purview.md +++ b/sql/sql-server-on-azure-vm/integration-with-purview.md @@ -5,7 +5,7 @@ Costa Rica [![Microsoft Purview](https://img.shields.io/badge/Microsoft-Purview-blue)](https://learn.microsoft.com/en-us/azure/purview/) [![SQL Server on Azure VM](https://img.shields.io/badge/Azure-SQLServer-blue)](https://learn.microsoft.com/en-us/sql/sql-server/sql-server-on-azure-vm) -Last updated: 2025-06-19 +Last updated: 2025-07-17 ---