Skip to content

integration-with-purview.md

Latest commit

 

History

History
168 lines (118 loc) · 7.34 KB

integration-with-purview.md

File metadata and controls

168 lines (118 loc) · 7.34 KB

Integrating Oracle Database on Azure with Microsoft Purview

Costa Rica

Microsoft Purview Oracle Database on Azure

Last updated: 2025-07-17

Microsoft Purview provides a unified data governance solution that enables organizations to manage and govern their on-premises, multi-cloud, and software-as-a-service (SaaS) data. Integrating Oracle Database on Azure with Purview allows you to discover, classify, and manage sensitive data, enforce compliance, and monitor data usage across your organization.

List of References
Table of Content

How to Integrate Oracle Database on Azure with Purview

Registering the Oracle Database in Purview

  • Go to the Microsoft Purview Studio.
  • Navigate to Data Map > Register > Oracle Database on Azure.
  • Provide the required connection details (server name, authentication, etc.).
  • Set up a scan rule set to define what metadata and classifications to extract.
  • Schedule regular scans to keep metadata and classifications up to date.

Enabling Unity Data Governance

  • Use Unity Catalog within Purview to manage access policies, data lineage, and data sharing.
  • Assign roles such as Data Owner, Data Steward, and Data Consumer to control access and responsibilities.
  • Track data movement and transformations for compliance and auditing.

Data Classification and Labeling

  • Apply built-in or custom classifiers to automatically detect and label sensitive data (e.g., PII, financial data).
  • Use labels to drive downstream policies such as Data Loss Prevention (DLP) and access controls.

Managing DLP (Data Loss Prevention) Projects

DLP projects in Purview help you identify, monitor, and protect sensitive data within your Oracle databases.

E.g: DLP Policy for GDPR Right to Be Forgotten (Click to expand)

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:
    • Notify data stewards when retention period expires or deletion is requested.
    • Automatically flag noncompliant records.
  4. Monitor and Audit: Prove compliance via retention logs and erasure workflows.
E.g: DLP Policy for Financial Reconciliation Data (Click to expand)

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:
    • Require managerial approval for exports over certain thresholds.
    • Redact financial summaries for non-finance roles.
  4. Monitor and Audit: Track peak financial period access and anomalous queries.
E.g: DLP Policy for Clinical Trial Data (GxP Compliance) (Click to expand)

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:
    • Encrypt output from trials unless accessed by certified trial managers.
    • Block trial data sharing outside approved vendors.
  4. Monitor and Audit: Export access reports for regulatory inspections.

Cost Management and Budgeting

Integrating with Purview introduces additional costs for scanning, classification, and governance. Below is a breakdown and example budget.

Cost Components

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
  • Resource Set Processing (based on processing time)

Tip

Click here to understand more about Azure Purview Cost Estimation

Best Practices

  • Automate Scans: Schedule regular scans to keep metadata and classifications current.
  • Least Privilege: Assign only necessary permissions to users and service principals.
  • Monitor Usage: Regularly review Purview dashboards for unusual activity or policy violations.
  • Review Costs: Monitor Purview and Oracle Database usage to optimize resource allocation and control expenses.

Integration with Purview for Unity Catalog

Oracle Database on Azure can be integrated with Microsoft Purview to enable a Unity Catalog for data governance and management. This integration allows you to:

  • Discover and classify sensitive data.
  • Track data lineage across your Oracle databases.
  • Enable centralized data governance.

Steps to Integrate

  1. Register the Oracle Database:
    • Navigate to the Microsoft Purview portal.
    • Register your Oracle Database on Azure as a data source.
  2. Scan the Data Source:
    • Configure scanning rules to classify and catalog the data.
    • Schedule periodic scans to keep the catalog updated.
  3. Manage Data Lineage: Use Purview to visualize data lineage across your Oracle databases.
  4. Set Up Access Policies: Define access policies for data governance using Purview.

Benefits

  • Enhanced data discovery and classification.
  • Improved compliance and governance.
  • Centralized management of data assets.
Total views

Refresh Date: 2025-07-17