🎉 What’s new

As a data engineer or admin, you’ll want this new setup flow for dbt connections because you can now select your preferred cloud storage and authentication method—ensuring a smoother, more secure integration that fits your company’s needs.

This is a major enhancement: now, when you connect dbt Core in Atlan, you can choose between S3, GCS, or ADLS and specify credentials using IAM roles, user keys, or service accounts—right from the config tab. Previously, setting up secure dbt access was one-size-fits-all and required more back-and-forth with support. Now, setup is flexible, transparent, and built for your cloud provider and security requirements.

✨ Let’s dig deeper

• You can choose your storage provider (S3, GCS, or ADLS) and authentication method directly during dbt connector setup
• For S3: enter IAM User credentials (AWS key, secret, region) or IAM Role (Role ARN, region)
• For GCS: enter your project ID and service account JSON (coming soon for all users)
• For ADLS: provide Azure tenant ID, client ID, client secret, storage account, and container names
• Your credential details are never shown in the UI after entry—for security
• When updating existing connections, fields will be empty by default; you’ll need to re-enter credentials for security, but connections will keep running as is until you do

👏 Give it a shot

• Go to your dbt connector’s profile and open the config tab
• Click the new credential tile to select your storage provider and input credentials
• Follow the prompts for your chosen method (S3, GCS, or ADLS)
• You’ll need admin access to update or set up credentials
• For more help, read the full setup guide.

Now you can connect dbt your way—securely, flexibly, and with total control.

🎉 What's new

Introducing a refined bulk glossary upload process for real time visibility, increased stability and more actionable insights into what changes your team is making.

👏 Give it a shot

Start curating your glossary via spreadsheets.

🎉 What’s new

Atlan now supports a new tag propagation mode - lineage only 

✨ Let’s dig deeper

You can now propagate tags:

• Hierarchy & lineage allows tag propagation to child and downstream assets.
• Hierarchy only (no lineage) allows tag propagation to child assets only.
• [new] Lineage only (no hierarchy) allows tag propagation to downstream assets only.
• No propagation disables any tag propagation.

👏 Give it a shot

Ready to use propagation? Get started today:

• Tag propagation

As you explore the improvement, please feel free to share your feedback!

🎉 What’s New
Atlan is excited to announce the General Availability of a long-awaited capability in the Power BI Connector:
Cataloging of Power BI Apps as First-Class Assets

• Business Users can now easily discover, trust, and navigate the official version of business content distributed through Apps.
• Data Engineers gain visibility into downstream consumption patterns from certified datasets into apps and ensure clean governance boundaries.
• BI Developers can now tag and manage apps alongside reports and dashboards, helping align packaging strategies to governance policies.

• Search and filter by Power BI Apps
• View Apps as related assets to Reports/Dashboards and vice-versa
• Understand which official version of content is being shared and used

📘 Learn More

• Power BI Apps in Atlan

⚡ Ready to track, trust, and govern your Power BI Apps? Let’s go!

🚀 WHAT’S NEW

You can now see full asset names in the lineage graph! Previously, long names were trimmed with "...", but we’ve improved this for better visibility. Browsing graphs is now easier, but also, exporting a graph & sharing it for collaboration would be possible after this release.

🚀 What’s New

We’ve made it easier to see if an asset has upstream or downstream dependencies at a glance. In the Lineage tab on Atlan’s sidebar, assets with long dependency lists now show two options: "Load Upstream" and "Load Downstream". Selecting one retrieves more dependencies and updates the relevant tabs with the latest information.

Note: The number of displayed dependencies is based on a paginated request. To view all dependencies, keep clicking "Load More".

🎉 What’s new

Atlan automatically retrieves and enriches Airflow DAGs with descriptions, source owners, and tags—if included in the OpenLineage event. This ensures your metadata stays up to date with source DAGs, helping you better govern, utilize, and understand your data estate.

Learn more:

• What Atlan Crawls from Apache Airflow
• Troubleshooting Airflow Connectivity

🎉 What’s new

Product lineage just got a 10x upgrade! Product lineage will now be generated even if the data products belong to different domains or have been modified after they are created or even archived. This release includes other improvements as well, making the depiction of dependencies between your data products automated and powerful.

✨ Let’s dig deeper

First, let's briefly revisit how product lineage works. If asset A is an output port in a data product A and a regular asset (not marked as an output port) is in data product B, then product lineage will be generated between data products A and B.

Data product lineage is now updated in the following conditions:

• Data products belong to the same or different domains.
• The asset selection in a data product is modified forming new links via output ports.
• Assets are marked as output ports OR previous output ports are unmarked.
• Data products are archived, thus removing them from product lineage.
• A data products asset list is updated when new assets satisfy the filter conditions (this is for data products created using filter rules).

Product lineage is now generated in an async manner. This means there is a time gap from the last action that can update lineage (like marking an asset as an output port) to the changes being reflected in the lineage. This time gap is around 30 minutes to an hour. Most importantly, product lineage will not be generated when any participating product has more than 30,000 assets.

Any past product lineage links that were not present due to products being in different domains will now fully reflect the updated lineage, and without requiring any action from you.

👏 Give it a shot

Visit your favorite data product today and explore a more powerful product lineage experience! Create new data products to build out and experience the new product lineage. If you do not have data products enabled, you can head over to Labs (as an admin user) and turn on the products module!

Learn more: What is business lineage?

And while you try it out, let us know what you think!

🎉 What’s new

Atlan now supports efficient handling of sharded tables in BigQuery, improving crawler performance and simplifying metadata and lineage views.

✨ Let’s dig deeper

You can now manage BigQuery sharded tables with ease:

• 🚀 Faster workflows – Avoid ingesting thousands of shard tables.
• 🧠 Clearer lineage – View one table instead of many.
• 🔍 Easier filtering – Use the new “Is Sharded” filter to find consolidated tables.

👏 Give it a shot

Start exploring sharded table consolidation today and let us know your feedback!
Refer to the documentation for more details.