Govern your Snowflake data with Azure Purview
Azure Purview as a unified data governance service keeps expanding support for various data sources across on-premises, multi-cloud, and SaaS applications. It helps you generate a holistic, up-to-date map of your data landscape with automated data discovery. Now you can easily bring over metadata from Snowflake by scanning your Snowflake databases, then manage and govern your Snowflake data in Azure Purview.
Register and scan
Azure Purview data source administrators can start by registering Snowflake under the data map, and set up reoccurring or one-time scan. You can choose to scan the entire Snowflake database(s) or scope the scan to selective schemas. When scanning Snowflake, Purview extracts rich set of metadata including Snowflake server, databases, schemas, tables, views, stored procedures, functions, pipes, stages, streams, tasks, sequences, and table/view/stream columns, as well as fetches static lineage on assets relationships among tables, views, and streams. Learn more about the prerequisites and step-by-step instruction to register and scan Snowflake in Azure Purview.
Search and browse assets
Once the scan completes, you can discover assets via search or browse.
You can search for the Snowflake assets by keyword, and narrow down results by using the facet filters.
To browse, click on the “Browse assets” tile on the Purview home page, navigate to the “By source type” tab and select Snowflake. You can then see the list of Snowflake assets brought in by the scan.
View and manage metadata
Click into the asset to view more details including the properties, schema, lineage, and more. You can also add business metadata like descriptions, glossary terms, and manually classify the data assets to further manage and govern your Snowflake data in Purview.
Get started today!
- Quickly and easily create an Azure Preview account to try the features.
- Learn more about Connect to and manage Snowflake in Azure Purview.
- See the full list of Azure Purview supported sources.
Published on:
Learn moreRelated posts
Announcing the end of support for Node.js 20.x in the Azure SDK for JavaScript
After July 9, 2026, the Azure SDK for JavaScript will no longer support Node.js 20.x. Upgrade to an Active Node.js Long Term Support (LTS) ver...
MCP Apps on Azure Functions: Quickstart with TypeScript
Learn how to build and deploy MCP (Model Context Protocol) apps on Azure Functions using TypeScript. This guide covers MCP tools, resources, l...
Setting up Power BI Version Control with Azure Dev Ops
In this blog post is a way set up version control for Power BI semantic models (and reports) using the PBIP (Power BI Project) format, Azure D...
Azure Developer CLI (azd) – March 2026: Run and Debug AI Agents Locally, GitHub Copilot Integration, & Container App Jobs
Run, invoke, and monitor AI agents locally or in Microsoft Foundry with the new azd AI agent extension commands. Plus GitHub Copilot-powered p...
Writing Azure service-related unit tests with Docker using Spring Cloud Azure
This post shows how to write Azure service-related unit tests with Docker using Spring Cloud Azure. The post Writing Azure service-related uni...
Azure SDK Release (March 2026)
Azure SDK releases every month. In this post, you find this month's highlights and release notes. The post Azure SDK Release (March 2026) appe...
Specifying client ID and secret when creating an Azure ACS principal via AppRegNew.aspx will be removed
The option to specify client ID and secret when creating Azure ACS principals will be removed. Users must adopt the system-generated client ID...
Azure Developer CLI (azd): Run and test AI agents locally with azd
New azd ai agent run and invoke commands let you start and test AI agents from your terminal—locally or in the cloud. The post Azure Developer...