You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/stream-analytics/power-bi-output.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,12 @@
1
1
---
2
2
title: Power BI output from Azure Stream Analytics
3
-
description: This article describes how to output data from Azure Stream Analytics to Power BI.
3
+
description: This article describes how to output data from Azure Stream Analytics to Power BI for a rich visualization experience of analysis results.
4
4
author: AliciaLiMicrosoft
5
5
ms.author: ali
6
6
ms.service: azure-stream-analytics
7
-
ms.topic: conceptual
8
-
ms.date: 07/20/2023
7
+
ms.topic: concept-article
8
+
ms.date: 01/23/2025
9
+
# Customer intent: I want to learn how to send output from a Stream Analytics job to Power BI.
9
10
---
10
11
11
12
# Power BI output from Azure Stream Analytics
@@ -44,7 +45,7 @@ Azure Stream Analytics creates a Power BI dataset and table schema for the user
44
45
Power BI uses the first-in, first-out (FIFO) retention policy. Data is collected in a table until it hits 200,000 rows.
45
46
46
47
> [!NOTE]
47
-
> We do not recommend using multiple outputs to write to the same dataset because it can cause several issues. Each output tries to create the Power BI dataset independently which can result in multiple datasets with the same name. Additionally, if the outputs don't have consistent schemas, the dataset changes the schema on each write, which leads to too many schema change requests. Even if these issues are avoided, multiple outputs will be less performant than a single merged output.
48
+
> We don't recommend using multiple outputs to write to the same dataset because it can cause several issues. Each output tries to create the Power BI dataset independently which can result in multiple datasets with the same name. Additionally, if the outputs don't have consistent schemas, the dataset changes the schema on each write, which leads to too many schema change requests. Even if these issues are avoided, multiple outputs are less performant than a single merged output.
48
49
49
50
### Convert a data type from Stream Analytics to Power BI
50
51
@@ -58,7 +59,7 @@ This table covers the data type conversions from [Stream Analytics data types](/
58
59
| nvarchar(max) | String |
59
60
| datetime | Datetime |
60
61
| float | Double |
61
-
| Record array | String type, constant value `IRecord` or `IArray`|
62
+
| Record array | String type, constant value `IRecord`, or `IArray`|
62
63
63
64
### Update the schema
64
65
@@ -83,7 +84,7 @@ You can use the following equation to compute the value to give your window in s
83
84
For example:
84
85
85
86
* You have 1,000 devices sending data at one-second intervals.
86
-
* You're using the Power BI Pro SKU that supports 1,000,000 rows per hour.
87
+
* You're using the Power BI Pro Stock Keeping Unit (SKU) that supports 1,000,000 rows per hour.
87
88
* You want to publish the amount of average data per device to Power BI.
88
89
89
90
As a result, the equation becomes:
@@ -113,7 +114,7 @@ Similarly, if a job starts after the token has expired, an error occurs and the
113
114
114
115
After the authorization has been refreshed with Power BI, a green alert appears in the authorization area to reflect that the issue has been resolved. To overcome this limitation, it's recommended to [use Managed Identity to authenticate your Azure Stream Analytics job to Power BI](powerbi-output-managed-identity.md)
115
116
116
-
## Next steps
117
+
## Related content
117
118
118
119
*[Use Managed Identity to authenticate your Azure Stream Analytics job to Power BI](powerbi-output-managed-identity.md)
119
120
*[Quickstart: Create a Stream Analytics job by using the Azure portal](stream-analytics-quick-create-portal.md)
0 commit comments