Update direct lake guidance around calculated columns

content/features/Semantic-Model/semantic-model-types.md

@@ -2,7 +2,7 @@
 uid: semantic-model-types
 title: Power BI Semantic model Types
 author: Morten Lønskov
-updated: 2026-03-27
+updated: 2026-08-28
 applies_to:
   products:
     - product: Tabular Editor 2
@@ -32,7 +32,7 @@ Tabular Editor can work with several different model types. Below is an overview
 |Create & Edit Partitions|✔️|✔️|✔️<sup>[1](#DirectLake)</sup>|✔️<sup>[1](#DirectLake)</sup>|✔️|✔️|
 |Create & Edit Columns|✔️|✔️|✔️<sup>[1](#DirectLake)</sup>|✔️<sup>[1](#DirectLake)</sup>|✔️|✔️|
 |Create & Edit Calculated Tables|✔️|✔️|✔️<sup>[2](#DirectLakeCalculated)</sup>|✔️<sup>[4](#DirectLakeSQLCalculated)</sup>|✔️|✔️|
-|Create & Edit Calculated Columns|✔️|✔️|❌|❌|✔️|✔️|
+|Create & Edit Calculated Columns|✔️|✔️|✔️<sup>[5](#DirectLakeCalcColumn)</sup>|❌|✔️|✔️|
 |Create & Edit Calculation Groups|✔️|✔️|✔️|✔️|✔️| |
 |Create & Edit Relationships|✔️|✔️|✔️|✔️|✔️| |
 |Create & Edit Roles|✔️|✔️|✔️|✔️|✔️|✔️|
@@ -59,6 +59,7 @@ Tabular Editor can work with several different model types. Below is an overview
 
 <a name="TE3Prem">3</a> - Tabular Editor 3 features only. Operations performed through the XMLA endpoint requires a Business or Enterprise license. [More information](xref:editions).
 <a name="DirectLakeSQLCalculated">4</a> - Direct Lake on SQL only supports calculation groups, what-if parameters and field parameters, which implicitly create calculated tables. General calculated tables are not supported.
+<a name="DirectLakeCalcColumn">5</a> - Preview feature. Calculated columns on Direct Lake on OneLake evaluate in the current user's query context rather than being materialized: they respect row-level and object-level security, but cannot be used as relationship keys and do not respond to report filters or slicers. See [Direct Lake Guidance](xref:direct-lake-guidance) for details.
 
 >[!NOTE]
 > The June 2025 release of Power BI Desktop lifted all modeling limitations for third-party tools. Prior to that, various modeling operations were not supported. See [Power BI Desktop Limitations](xref:desktop-limitations).

content/tutorials/direct-lake-guidance.md

@@ -1,8 +1,8 @@
 ---
 uid: direct-lake-guidance
 title: Direct Lake Guidance
-author: Daniel Otykier
-updated: 2026-03-27
+author: Morten Lønskov
+updated: 2026-08-28
 applies_to:
   products:
     - product: Tabular Editor 2
@@ -45,7 +45,7 @@ The following table summarizes the storage modes available in Power BI semantic
 
 However, as with Direct Lake on SQL, there are still some [limitations that *do* apply](https://learn.microsoft.com/en-us/fabric/fundamentals/direct-lake-overview#considerations-and-limitations). Key limitations include:
 
-- Calculated columns are not supported in either Direct Lake mode.
+- Calculated columns on Direct Lake on OneLake tables are supported in preview, but only in *user context*: the value is evaluated at query time for the current user rather than materialized. This means a Direct Lake calculated column respects row-level and object-level security, but it cannot be used as a relationship key and does not respond to report filters or slicers. Use a measure instead when the result must react to filter context. Direct Lake on SQL still does not support calculated columns at all. See [Develop Direct Lake semantic models](https://learn.microsoft.com/en-us/fabric/fundamentals/direct-lake-develop) for details.
 - Calculated tables cannot reference columns or tables in Direct Lake storage mode. Calculation groups, what-if parameters and field parameters are supported because they create implicit calculated tables that do not reference Direct Lake columns.
 - Non-materialized SQL views are not supported as data sources for Direct Lake on OneLake tables. Use materialized views or ensure the source Delta table contains the columns you need.
 - Shortcuts in a lakehouse are not supported as data sources during the public preview of Direct Lake on OneLake.
@@ -54,7 +54,7 @@ For a full and up-to-date list of limitations, see the [Microsoft documentation
 
 ### Composite models
 
-One workaround for the calculated column limitation is to create a **composite model** by combining Direct Lake tables with Import tables. This is supported with Direct Lake on OneLake, but not with Direct Lake on SQL. In a composite model, you typically keep larger fact tables in Direct Lake mode while using Import mode for smaller dimension tables where you need calculated columns or custom groupings.
+If you need a calculated column that is materialized, usable as a relationship key, or responsive to report filters and slicers, the preview calculated column feature above is not enough. In that case, create a **composite model** by combining Direct Lake tables with Import tables. This is supported with Direct Lake on OneLake, but not with Direct Lake on SQL. In a composite model, you typically keep larger fact tables in Direct Lake mode while using Import mode for smaller dimension tables where you need full calculated columns or custom groupings.
 
 Direct Lake on OneLake also supports combining with DirectQuery tables through XMLA-based tools such as Tabular Editor. Import tables can be added through Power BI web modeling, Power BI Desktop (live editing) or through XMLA tools.