diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index b0c7a3cfc4..d11a40ab49 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -6415,6 +6415,11 @@ "source_path": "powerbi-docs/create-reports/filters-copilot.md", "redirect_url": "/power-bi/create-reports/service-the-report-editor-take-a-tour", "redirect_document_id": false - } + }, + { + "source_path": "powerbi-docs/developer/visuals/scanner-api.md", + "redirect_url": "/power-bi/developer", + "redirect_document_id": false + } ] } diff --git a/powerbi-docs/collaborate-share/media/power-bi-dynamic-report-subscriptions/power-bi-employee.png b/powerbi-docs/collaborate-share/media/power-bi-dynamic-report-subscriptions/power-bi-employee.png index b534c98ed7..1ba73c29b6 100644 Binary files a/powerbi-docs/collaborate-share/media/power-bi-dynamic-report-subscriptions/power-bi-employee.png and b/powerbi-docs/collaborate-share/media/power-bi-dynamic-report-subscriptions/power-bi-employee.png differ diff --git a/powerbi-docs/consumer/media/end-user-data-hub/power-bi-data-hub.png b/powerbi-docs/consumer/media/end-user-data-hub/power-bi-data-hub.png index 53a7b1b0c3..023e28d3ef 100644 Binary files a/powerbi-docs/consumer/media/end-user-data-hub/power-bi-data-hub.png and b/powerbi-docs/consumer/media/end-user-data-hub/power-bi-data-hub.png differ diff --git a/powerbi-docs/create-reports/power-bi-dark-mode.md b/powerbi-docs/create-reports/power-bi-dark-mode.md index bf0bea4c32..266b75e3f9 100644 --- a/powerbi-docs/create-reports/power-bi-dark-mode.md +++ b/powerbi-docs/create-reports/power-bi-dark-mode.md @@ -7,7 +7,7 @@ ms.reviewer: '' ms.service: powerbi ms.subservice: pbi-reports-dashboards ms.topic: how-to -ms.date: 11/29/2024 +ms.date: 01/03/2025 LocalizationGroup: Create reports --- # Dark mode in Power BI Desktop @@ -41,6 +41,10 @@ There's a mode for every window in Power BI Desktop. For example, for dark mode: :::image type="content" source="media/power-bi-dark-mode/dark-mode-report-view.png" alt-text="Screenshot of Dark mode for report view." lightbox="media/power-bi-dark-mode/dark-mode-report-view.png"::: +> [!NOTE] +> Dark mode is not applied to the Report view Canvas, including the Filter Pane and Wallpaper. + + ## Model view :::image type="content" source="media/power-bi-dark-mode/dark-mode-model-view.png" alt-text="Screenshot of Dark mode for model view." lightbox="media/power-bi-dark-mode/dark-mode-model-view.png"::: @@ -55,6 +59,11 @@ There's a mode for every window in Power BI Desktop. For example, for dark mode: Try the different modes and see which you prefer. +## Considerations and limitations + +Collapsing of the **Power Query** editor ribbon is not currently available in Dark mode or Light mode. + + ## Related content - [Create reports in Power BI Desktop with Copilot](copilot-create-desktop-report.md) diff --git a/powerbi-docs/developer/embedded/TOC.yml b/powerbi-docs/developer/embedded/TOC.yml index a7af087376..fb3f1cbc54 100644 --- a/powerbi-docs/developer/embedded/TOC.yml +++ b/powerbi-docs/developer/embedded/TOC.yml @@ -18,7 +18,7 @@ items: - name: "Create a Microsoft Entra tenant" href: create-an-azure-active-directory-tenant.md - - name: "Power BI app registration tool" + - name: "Register a Power BI app" href: register-app.md - name: "Configure credentials" href: configure-credentials.md @@ -150,8 +150,6 @@ href: dev-camp-links.md - name: "Developer center" href: https://powerbi.microsoft.com/en-us/developers/ - - name: "Embedding setup tool" - href: https://aka.ms/embedsetup - name: "Embedded analytics playground" href: https://go.microsoft.com/fwlink/?linkid=848279 - name: "Power BI embedded analytics Client APIs" diff --git a/powerbi-docs/developer/embedded/dev-camp-links.md b/powerbi-docs/developer/embedded/dev-camp-links.md index cf59835031..de6e8cb69b 100644 --- a/powerbi-docs/developer/embedded/dev-camp-links.md +++ b/powerbi-docs/developer/embedded/dev-camp-links.md @@ -6,7 +6,7 @@ ms.author: monaberdugo ms.service: powerbi ms.subservice: powerbi-developer ms.topic: reference -ms.date: 11/05/2023 +ms.date: 02/02/2025 --- # Power BI Dev Camp @@ -31,7 +31,7 @@ The Power BI Dev Camp tutorials are targeted toward developers who are intereste --- -* [Tabular-Object-Model-Tutorial](https://github.com/PowerBiDevCamp/Tabular-Object-Model-Tutorial) - A tutorial and sample code programming semantic model that use the Tabular Object Model with Power BI Desktop and the Power BI service via the XMLA endpoint. +* [Tabular-Object-Model-Tutorial](https://github.com/PowerBiDevCamp/Tabular-Object-Model-Tutorial) - A tutorial and code programming semantic model that use the Tabular Object Model with Power BI Desktop and the Power BI service via the XMLA endpoint. * [PowerBI-PowerShell-Tutorial](https://github.com/PowerBiDevCamp/PowerBI-PowerShell-Tutorial) - Student files for the Power BI PowerShell tutorial from Power BI Dev Camp. @@ -59,10 +59,6 @@ The Power BI Dev Camp examples provide additional resources for developers who a * [Tenant management application for Power BI](https://github.com/PowerBiDevCamp/TenantManagement) - A .NET 5 sample application that demonstrates how to manage service principals within a large-scale Power BI embedding environment with thousands of customer tenants. -## Videos - -To view Power BI Dev Camp videos, go to the [video page](https://www.powerbidevcamp.net/videos/). - ## Presentations To download Power BI Dev Camp presentations, go to the [Camp-Sessions](https://github.com/PowerBiDevCamp/Camp-Sessions) GitHub repository. diff --git a/powerbi-docs/developer/embedded/embed-auto-install-app.md b/powerbi-docs/developer/embedded/embed-auto-install-app.md index 3f5daaaa38..7317843db3 100644 --- a/powerbi-docs/developer/embedded/embed-auto-install-app.md +++ b/powerbi-docs/developer/embedded/embed-auto-install-app.md @@ -1,5 +1,5 @@ --- -title: Automatically install Power BI apps when embedding content for your organization +title: Automatically install Power BI apps for your organization description: Learn how to set up automatic app installation for Power BI apps when embedding content from apps for your organization. author: mberdugo ms.author: monaberdugo @@ -7,7 +7,8 @@ ms.topic: how-to ms.service: powerbi ms.subservice: powerbi-developer ms.custom: -ms.date: 06/03/2024 +ms.date: 01/07/2025 +# customer intent: As a developer, I want to learn how to set up automatic app installation for Power BI apps when embedding content from apps for my organization. --- # Automatically install Power BI apps when embedding content for your organization @@ -22,11 +23,14 @@ If you have access to an app that isn't installed, and try to embed app content, ## Embedding for Power BI users (User owns data) -To allow the automatic installation of apps for your users, add the *Create APIs* permission to your application when you're [registering your application](register-app.md#step-2---register-your-application). If you've already registered your app, add the Create APIs permission by [changing your application's permissions](/power-bi/developer/embedded/change-permissions). +To allow the automatic installation of apps for your users: -:::image type="content" source="media/embed-auto-install-app/register-app-create-content.png" alt-text="Screenshot of the Power BI embedding setup tool, which shows the selected Create APIs option."::: +1. Add the *Create APIs* permission to your application when you're [registering your application](register-app.md). If you've already registered your app, add the Create APIs permission by [changing your application's permissions](/power-bi/developer/embedded/change-permissions). -Provide the app ID in the embed URL. To provide the app ID, the app creator must install the app and then use one of the supported [Power BI REST API](/rest/api/power-bi/) calls, such as [Get Reports](/rest/api/power-bi/reports/getreports) or [Get Dashboards](/rest/api/power-bi/dashboards/getdashboards). The app creator must take the embed URL from the REST API response. The app ID appears in the URL if the content is from an app. Use the embed URL to embed content. + :::image type="content" source="media/embed-auto-install-app/register-app-create-content.png" alt-text="Screenshot of the Power BI embedding setup tool, which shows the selected Create APIs option."::: + +1. Provide the app ID in the embed URL. To provide the app ID, the app creator must install the app and then use one of the supported [Power BI REST API](/rest/api/power-bi/) calls, such as [Get Reports](/rest/api/power-bi/reports/getreports) or [Get Dashboards](/rest/api/power-bi/dashboards/getdashboards). The app creator must take the embed URL from the REST API response. The app ID appears in the URL if the content is from an app. +1. Use the embed URL to embed content. ## Secure embedding @@ -37,3 +41,8 @@ To use automatic application installation, the app creator must install the app. * You can only embed reports and dashboards in this scenario. * This feature is currently not supported for app-owns data or SharePoint embedding scenarios. + +## Related content + +* [Register a Power BI Embedded app](register-app.md) +* [Embed content for your organization](embed-sample-for-your-organization.md) diff --git a/powerbi-docs/developer/embedded/embed-paginated-reports.md b/powerbi-docs/developer/embedded/embed-paginated-reports.md index b8ff282ae9..0a71cc74ab 100644 --- a/powerbi-docs/developer/embedded/embed-paginated-reports.md +++ b/powerbi-docs/developer/embedded/embed-paginated-reports.md @@ -1,6 +1,6 @@ --- -title: Embed paginated reports in your Power BI application -description: Learn how to integrate or embed a Power BI paginated report into a Power BI embedded analytics application. +title: Embed paginated reports in your embedded analytics app +description: Learn how to integrate or embed a Power BI paginated report into an embedded analytics application, and explore its features and capabilities. author: mberdugo ms.author: monaberdugo ms.reviewer: @@ -8,8 +8,8 @@ ms.topic: how-to ms.service: powerbi ms.subservice: powerbi-developer ms.custom: '' -ms.date: 01/08/2024 -#Customer intent: As a developer, I want to embed paginated reports in my application to provide my users with interactive and integrated reports. +ms.date: 02/02/2025 +#customer intent: As a developer, I want to learn how to integrate or embed a Power BI paginated report into an embedded analytics application. --- # Embed Power BI paginated reports @@ -76,38 +76,15 @@ In Power BI service, create a workspace for your paginated report. ### [Embed for your customers](#tab/customers) -Before you import or upload a paginated report to embed, you must assign the workspace containing the report to a capacity. There are two types of capacity you can choose from: +Before you import or upload a paginated report to embed, you must assign the workspace containing the report to a capacity. -* **Power BI Premium** - To embed a paginated report, you need an *EM* or *P* SKU. For more information about this subscription, see [What is Power BI Premium?](../../enterprise/service-premium-what-is.md). -* **Azure Power BI Embedded** - You can purchase a capacity from the [Microsoft Azure portal](https://portal.azure.com). This subscription uses the *A* SKUs. For details on how to create a Power BI Embedded capacity, see [Create Power BI Embedded capacity in the Azure portal](azure-pbie-create-capacity.md). - -The following table describes the resources and limits of each SKU. To determine which capacity best fits your needs, see the [which SKU should I purchase for my scenario](./embedded-faq.yml#which-solution-should-i-choose-) table. - -| Capacity Nodes | V-cores | RAM (GB) | -| --- | --- | --- | -| EM1/A1 | 1 | 2.5 | -| EM2/A2 | 2 | 5 | -| EM3/A3 | 4 | 10 | -| P1/A4 | 8 | 25 | -| P2/A5 | 16 | 50 | -| P3/A6 | 32 | 100 | +To figure out what kind of capacity you need, see [Microsoft Fabric concepts](/fabric/enterprise/licenses#microsoft-fabric-concepts). ### [Embed for your organization](#tab/organization) -By creating a capacity, you can take advantage of having a resource for the content in your app workspace. For paginated reports, you must back your app workspace with an *EM* or a *P* capacity. You can create a capacity with [Power BI Premium](../../enterprise/service-premium-what-is.md). - -The following table lists the Power BI Premium SKUs that create a capacity for paginated reports in [Microsoft Office 365](/microsoft-365): +By creating a capacity, you can take advantage of having a resource for the content in your app workspace. For paginated reports, you must back your app workspace with an *EM*, *P*, or *F* capacity. You can create a capacity with [Power BI Premium](../../enterprise/service-premium-what-is.md). -| Capacity node | V-cores | RAM (GB) | DirectQuery/live connection limits (per sec) | -| --- | --- | --- | --- | -| EM1/A1 | 1 | | 3.75 | -| EM2/A2 | 2 | | 7.5 | -| EM3/A3 | 4 | | 15 | -| P1/A4 | 8 | 25 | 30 | -| P2/A5 | 16 | 50 | 60 | -| P3/A6 | 32 | 100 | 120 | -| P4 | 64 | 200 | 240 | -| P5 | 128 | 400 | 480 | +Learn more about capacities and SKUs at [Microsoft Fabric concepts](/fabric/enterprise/licenses#microsoft-fabric-concepts). --- @@ -191,7 +168,7 @@ For more information on embedding tokens, see [Embedded analytics access tokens] --- * Paginated reports don't support client-side events (like `loaded` or `rendered`). -* Paginated reports don't support client-side setAccessToken API (you can not update acccess token without reloading the report). +* Paginated reports don't support client-side setAccessToken API (you cannot update access token without reloading the report). * Embedding paginated reports with a real-time dataset (push dataset) is not supported. ## Related content diff --git a/powerbi-docs/developer/embedded/embedded-faq.yml b/powerbi-docs/developer/embedded/embedded-faq.yml index 8ada33c293..a5f8dbd719 100644 --- a/powerbi-docs/developer/embedded/embedded-faq.yml +++ b/powerbi-docs/developer/embedded/embedded-faq.yml @@ -365,36 +365,25 @@ sections: answer: | There's no special Azure pricing for non-profit and educational entities. - - name: Embedding setup tool + - name: Set up environment questions: - question: | What is the Embedding setup tool? answer: | - The [Embedding setup tool](https://app.powerbi.com/embedsetup) allows you to quickly get started and download a sample application to begin embedding with Power BI. + The Embedding setup tool was a tool that allowed you to quickly register and download a sample application to begin embedding with Power BI. This tool has been retired. To register an app see [Register an app](register-app.md). - question: | Which solution should I choose? answer: | - * [Embedding for your customers](embedded-analytics-power-bi.md#embed-for-your-customers) provides the ability to embed dashboards and reports to users who don't have an account for Power BI. In the [Embedding setup tool](https://app.powerbi.com/embedsetup), run the *Embed for your customers* solution. - * [Embedding for your organization](embedded-analytics-power-bi.md#embed-for-your-organization) allows you to extend the Power BI service. In the [Embedding setup tool](https://app.powerbi.com/embedsetup), run the *Embed for your organization* solution. - - - question: | - I've downloaded the sample app, which solution do I choose? - answer: | - If you're working with the **Embed for your customers** experience, save and unzip the `PowerBI-Developer-Samples.zip` file. Then open the `PowerBI-Developer-Samples-master\App Owns Data` folder and run the `PowerBIEmbedded_AppOwnsData.sln` file. - - If you're working with the **Embed for your organization** experience, save and unzip the `PowerBI-Developer-Samples.zip` file. Then open the `PowerBI-Developer-Samples-master\User Owns Data\integrate-report-web-app` folder and run the `pbi-saas-embed-report.sln` file. + * [Embedding for your customers](embedded-analytics-power-bi.md#embed-for-your-customers) provides the ability to embed dashboards and reports to users who don't have an account for Power BI. When you [register your app](./register-app.md), run the *Embed for your customers* solution. + * [Embedding for your organization](embedded-analytics-power-bi.md#embed-for-your-organization) allows you to extend the Power BI service. When you [register your app](./register-app.md), run the *Embed for your organization* solution. - question: | How can I edit my registered application? answer: | To learn how to edit Microsoft Entra registered applications, see [Quickstart: Update an application in Microsoft Entra ID](/azure/active-directory/develop/quickstart-v1-update-azure-ad-app). - - question: | - How can I edit my Power BI user profile or data? - answer: | - You can learn how to edit your Power BI data [here](../../fundamentals/service-basic-concepts.md). - + For more information, see [Troubleshooting your embedded application](embedded-troubleshoot.md). More questions? [Try the Power BI Community](https://community.powerbi.com/) diff --git a/powerbi-docs/developer/embedded/embedded-troubleshoot.md b/powerbi-docs/developer/embedded/embedded-troubleshoot.md index 7107097eb3..44dc5e52d8 100644 --- a/powerbi-docs/developer/embedded/embedded-troubleshoot.md +++ b/powerbi-docs/developer/embedded/embedded-troubleshoot.md @@ -204,7 +204,7 @@ When you *embed for your organization*, to allow Microsoft Entra guest users acc To find your tenant ID, you can use the instructions in [Find the Microsoft Entra tenant ID and primary domain name](/partner-center/find-ids-and-domain-names#find-the-microsoft-azure-ad-tenant-id-and-primary-domain-name). -For more information, see [Making your application multi-tenant](/azure/active-directory/develop/howto-convert-app-to-be-multi-tenant). +For more information, see [Making your application multitenant](/azure/active-directory/develop/howto-convert-app-to-be-multi-tenant). ## Data sources @@ -221,7 +221,7 @@ After acquiring the IError object, you should look at the appropriate common err ### Typical errors when embedding for Power BI users | Message | Detailed Message | Error Code | Possible reason(s) | -|-------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|-----------|--------------------------------------------------------| +|---------|------------------|------------|--------------------| | TokenExpired | Access token has expired, resubmit with a new access token | 403 | Expired token | | PowerBIEntityNotFound | Get report failed | 404 |
  • Wrong Report ID
  • Report doesn't exist | | Invalid parameters | powerbiToken parameter not specified | N/A |
  • No access token provided
  • No Report ID provided | @@ -233,8 +233,8 @@ After acquiring the IError object, you should look at the appropriate common err ### Typical errors when embedding for non-Power BI users (using an Embed Token) -| Message | Detailed Message | Error Code | Reason(s) | -|-------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------| +| Message | Detailed Message | Error Code | Possible reason(s) | +|---------|------------------|------------|--------------------| | TokenExpired | Access token has expired, resubmit with a new access token | 403 | Expired token | | LoadReportFailed | Get report failed | 404 |
  • Wrong Report ID
  • Report doesn't exist | | LoadReportFailed | Get report failed | 403 | Report ID doesn't match token | @@ -284,79 +284,6 @@ For security purposes, access tokens (a Microsoft Entra token or an embed token) To get the best performing embedded content, we recommend that you follow the [Power BI embedded analytics best practices](embedded-performance-best-practices.md). -## Embed setup tool - -You can go through the [Embedding setup tool](https://aka.ms/embedsetup) to quickly download a sample application. Then you can compare your application to the sample. - -### Prerequisites - -Verify that you have all the proper prerequisites before using the Embedding setup tool. You need a **Power BI Pro** account and a **Microsoft Azure** subscription. - -* If you're not signed up for **Power BI Pro**, [sign up for a free trial](https://powerbi.microsoft.com/pricing/) before you begin. -* If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin. -* You need to have your own [Microsoft Entra tenant](create-an-azure-active-directory-tenant.md) setup. -* You need [Visual Studio](https://www.visualstudio.com/) installed (version 2013 or later). - -### Common Issues - -Some common issues you might encounter while testing with the Embed setup tool are: - -#### Using the Embed for your customers sample application - -If you're working with the **Embed for your customers** experience, save and unzip the *PowerBI-Developer-Samples.zip* file. Then open the *PowerBI-Developer-Samples-master\App Owns Data* folder and run the *PowerBIEmbedded_AppOwnsData.sln* file. - -* When selecting **Grant permissions** (the Grant permissions step), you get the following error: - - ```output - AADSTS70001: Application with identifier wasn't found in the directory - ``` - - The solution is to close the popup, wait a few seconds and try again. You might need to repeat this action a few times. A time interval causes the issue from completing the application registration process to when it's available to external APIs. - -* The following error message appears when running the sample app: - - ```output - Password is empty. Please fill password of Power BI username in web.config. - ``` - - This error occurs because the only value that isn't being injected into the sample application is your user password. Open the *Web.config* file in the solution and fill the `pbiPassword` field with your user's password. - -* If you get the error: - -```output -AADSTS50079: The user is required to use multi-factor authentication. -``` - - You need to use a Microsoft Entra account that doesn't have MFA enabled. - -#### Using the Embed for your organization sample application - -If you're working with the **Embed for your organization** experience, save and unzip the *PowerBI-Developer-Samples.zip* file. Then open the *PowerBI-Developer-Samples-master\User Owns Data\integrate-report-web-app* folder and run the *pbi-saas-embed-report.sln* file. - -* When you run the **Embed for your organization** sample app, you get the following error: - - ```output - AADSTS50011: The reply URL specified in the request doesn't match the reply URLs configured for the application: - ``` - - This error is because the redirect URL specified for the web-server application is different from the sample's URL. If you want to register the sample application, use `https://localhost:13526/` as the redirect URL. - - If you want to edit the registered application, [update the Microsoft Entra registered application](/azure/active-directory/develop/quickstart-v1-update-azure-ad-app), so the application can provide access to the web APIs. - - If you want to edit your Power BI user profile or data, learn how to edit your [Power BI data](../../fundamentals/service-basic-concepts.md). - -* If you get the error: - -```output -AADSTS50079: The user is required to use multi-factor authentication. -``` - - You need to use a Microsoft Entra account that doesn't have MFA enabled. - -For more information, please see [Power BI Embedded FAQ](embedded-faq.yml). - -For further assistance, [contact support](https://powerbi.microsoft.com/support/pro/?Type=documentation&q=power+bi+embedded) or [create a support ticket via the Azure portal](https://ms.portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest) and provide the error messages you encounter. - ## Related content [Power BI Embedded Frequently Asked Questions](embedded-faq.yml) diff --git a/powerbi-docs/developer/embedded/export-paginated-report.md b/powerbi-docs/developer/embedded/export-paginated-report.md index 867bed6ae1..a582a74a5a 100644 --- a/powerbi-docs/developer/embedded/export-paginated-report.md +++ b/powerbi-docs/developer/embedded/export-paginated-report.md @@ -1,12 +1,13 @@ --- title: Export Power BI embedded analytics paginated reports API -description: Learn how to export an embedded Power BI paginated report. +description: Learn how to use the exportToFile API to export an embedded Power BI paginated report to various file formats, including PDF, PPTX, and more. author: mberdugo ms.author: monaberdugo ms.topic: how-to ms.service: powerbi ms.subservice: powerbi-developer -ms.date: 05/23/2024 +ms.date: 12/23/2024 +#customer intent: As a developer, I want to export a paginated report to a file so that I can share it with others. --- # Export paginated report to file diff --git a/powerbi-docs/developer/embedded/index.yml b/powerbi-docs/developer/embedded/index.yml index 8ef3ec350d..c542075812 100644 --- a/powerbi-docs/developer/embedded/index.yml +++ b/powerbi-docs/developer/embedded/index.yml @@ -64,8 +64,6 @@ landingContent: url: embed-service-principal.md - linkListType: reference links: - - text: "Embedding setup tool" - url: https://app.powerbi.com/embedsetup - text: "Developer samples and scripts" url: https://github.com/Microsoft/PowerBI-Developer-Samples diff --git a/powerbi-docs/developer/embedded/media/register-app/application-id.png b/powerbi-docs/developer/embedded/media/register-app/application-id.png deleted file mode 100644 index 79014f8012..0000000000 Binary files a/powerbi-docs/developer/embedded/media/register-app/application-id.png and /dev/null differ diff --git a/powerbi-docs/developer/embedded/media/register-app/choose-embedding-solution.png b/powerbi-docs/developer/embedded/media/register-app/choose-embedding-solution.png deleted file mode 100644 index 783f946fed..0000000000 Binary files a/powerbi-docs/developer/embedded/media/register-app/choose-embedding-solution.png and /dev/null differ diff --git a/powerbi-docs/developer/embedded/media/register-app/step-one-signed-in.png b/powerbi-docs/developer/embedded/media/register-app/step-one-signed-in.png deleted file mode 100644 index b63e84f3ec..0000000000 Binary files a/powerbi-docs/developer/embedded/media/register-app/step-one-signed-in.png and /dev/null differ diff --git a/powerbi-docs/developer/embedded/qanda.md b/powerbi-docs/developer/embedded/qanda.md index c869daeb1e..c3cd5e015c 100644 --- a/powerbi-docs/developer/embedded/qanda.md +++ b/powerbi-docs/developer/embedded/qanda.md @@ -7,7 +7,7 @@ ms.reviewer: '' ms.service: powerbi ms.subservice: powerbi-developer ms.topic: how-to -ms.date: 02/04/2024 +ms.date: 02/02/2025 #customer intent: As a developer, I want to learn how to incorporate Q&A into my application using Power BI embedded analytics so I can write more interactive applications. --- @@ -96,6 +96,6 @@ Create an embed token from a semantic model to start a Q&A part. For more inform ## Related content -[Try out Q&A embedding with the JavaScript embed sample](https://microsoft.github.io/PowerBI-JavaScript/demo/) +[Try out the Power BI embedded analytics playground](https://go.microsoft.com/fwlink/?linkid=848279) More questions? [Ask the Power BI Community](https://community.powerbi.com/) diff --git a/powerbi-docs/developer/embedded/register-app.md b/powerbi-docs/developer/embedded/register-app.md index c6cf7e5928..412e93cc8f 100644 --- a/powerbi-docs/developer/embedded/register-app.md +++ b/powerbi-docs/developer/embedded/register-app.md @@ -1,11 +1,10 @@ --- -title: Get started with Power BI Embedded -description: Set up Power BI Embedded using a setup tool to register a Microsoft Entra app, create a workspace, import content, grant permissions, and download a sample app. +title: Register a Power BI Embedded app +description: Set up Power BI Embedded to register a Microsoft Entra app, create a workspace, import content, grant permissions. author: mberdugo ms.author: monaberdugo -keywords: -ms.date: 01/23/2024 -ms.topic: overview +ms.date: 02/02/2025 +ms.topic: how-to ms.service: powerbi ms.subservice: powerbi-developer ms.custom: intro-overview @@ -16,9 +15,7 @@ ms.custom: intro-overview **APPLIES TO:** :::image type="icon" source="../../includes/media/yes-icon.svg" border="false"::: App owns data :::image type="icon" source="../../includes/media/yes-icon.svg" border="false"::: User owns data -If you want to start using Power BI Embedded to share your reports with others, use the [Power BI embedded analytics setup tool](https://app.powerbi.com/embedsetup) to get started. This article shows you how. - -To use Power BI embedded analytics, you need to register a Microsoft Entra application in Azure. The Microsoft Entra app establishes permissions for Power BI REST resources, and allows access to the [Power BI REST APIs](/rest/api/power-bi/). +This article shows you how to start using Power BI Embedded to share your reports with others. To use Power BI embedded analytics, you need to register a Microsoft Entra application in Azure. The Microsoft Entra app establishes permissions for Power BI REST resources, and allows access to the [Power BI REST APIs](/rest/api/power-bi/). ## Prerequisite @@ -36,7 +33,7 @@ Before you can register your app, decide which of the following solutions best s ### Embed for your customers -Use the [embed-for-your-customers](embed-sample-for-customers.md) solution, also known as *app owns data*, if you create an app that's designed for your customers. Users don't need to sign in to Power BI or have a Power BI license to use your app. Your app authenticates against Power BI by using either a **master user** account (a Power BI Pro license used for signing in to Power BI) or a [service principal](embed-service-principal.md). +Use the [embed-for-your-customers](embed-sample-for-customers.md) solution, also known as *app owns data*, if you create an app designed for your customers. Users don't need to sign in to Power BI or have a Power BI license to use your app. Your app authenticates against Power BI by using either a **master user** account (a Power BI Pro license used for signing in to Power BI) or a [service principal](embed-service-principal.md). The embed-for-your-customers solution is usually used by independent software vendors (ISVs) and developers who create applications for a third party. @@ -48,106 +45,9 @@ The embed-for-your-organization solution is usually used by enterprises and larg For more about the two solutions, see [What are the Power BI embedded analytics solutions?](embedded-analytics-power-bi.md#what-are-the-power-bi-embedded-analytics-solutions). -## Set up your environment - -After you understand the two embedding options, you can use the setup tool to create your Power BI Embedded environment. - -If you prefer to manually set up your environment, skip the steps in the following sections. Instead, follow the steps in [Manual registration](#manual-registration), later in this article. - -> [!IMPORTANT] -> If you're embedding for a GCC, follow the instructions in [Manual registration](#manual-registration). - -To use the tool to set up your environment, go to the [Power BI embedded analytics setup tool](https://app.powerbi.com/embedsetup). Select the embedding option that you want. - -:::image type="content" source="./media/register-app/choose-embedding-solution.png" alt-text="Screenshot of the Power BI embedded analytics setup tool. The options for embedding for your customers or for your organization are highlighted."::: - -## Step 1 - Sign in to Power BI - -1. Under **Step 1** in the setup tool, select **Sign in**. This step signs you in to Power BI. If you're prompted to pick an account, sign in with a user that belongs to your Power BI tenant. The Microsoft Entra app gets registered under this user. - - > [!NOTE] - > If you're already signed in, verify that you're signed in with the user you want to use to create the Microsoft Entra app. To change users, select **sign out**. After the tool restarts, sign in with the correct user. - -1. Select **Next** to go to the next step. - - :::image type="content" source="./media/register-app/step-one-signed-in.png" alt-text="Screenshot of the Power BI embedded analytics setup tool after a user has signed in to Power BI. The Next button in highlighted."::: - -## Step 2 - Register your application - -In this step, you register a Microsoft Entra application in Azure. The Microsoft Entra app establishes permissions for Power BI REST resources, and allows access to the [Power BI REST APIs](/rest/api/power-bi/). You can always change these settings at a later time. - -### [Embed for your customers](#tab/customers) - -1. To register your application for your customers, fill in the following fields: - - * **Application Name** - Give your application a name. - - * **API access** - Select the Power BI APIs (also known as scopes) that your application needs. You can select **Select all** to select all the APIs. For more information about Power BI access permissions, see [Permissions and consent in the Microsoft identity platform endpoint](/azure/active-directory/develop/v2-permissions-and-consent). - -1. Select **Register**. - -1. Your Microsoft Entra app **Application ID** is displayed in the **Summary** box. Copy this value for later use. - - :::image type="content" source="./media/register-app/application-id.png" alt-text="Screenshot of the Power BI embedded analytics setup tool, with a Summary box on the right. Information in the box includes an application ID."::: - -### [Embed for your organization](#tab/organization) - -1. To register your application for your organization, fill in the following fields: - - * **Application Name** - Give your application a name. - - * **Home Page URL** - Enter a URL for your home page. - - * **Redirect URL** - Select a redirection option. When your users sign in, they're redirected to this address while your application receives an authentication code from Azure. Choose one of these options for this URL: - - * **Use a default URL** - This option automatically creates and downloads a sample embedded analytics application. The default URL is `http://localhost:13526/`. - * **Use a custom URL** - This option is appropriate if you already have an embedded analytics application, and know what you want to use as a redirect URL. +## Register your app - * **API access** - Select the Power BI APIs (also known as scopes) that your application needs. Select **Select all** to select all the APIs. For more information about Power BI access permissions, see [Permissions and consent in the Microsoft identity platform endpoint](/azure/active-directory/develop/v2-permissions-and-consent). - -1. Select **Register**. - -1. Your Microsoft Entra app **Application ID** and **Application secret** values are displayed in the **Summary** box. Copy these values for later use. - ---- - -## Step 3 - Create a workspace (optional) - -Create a workspace in the Power BI service: - -* If you already have a Power BI workspace, select **Skip**. - -* To create a workspace, enter a name for your workspace, and then select **Create workspace**. Your workspace name and ID appear in the **Summary** box. Copy these values for later use. - - >[!TIP] - >For the **embedded analytics sample app** to work as expected, you have to use the tool to create a workspace. - -## Step 4 - Import content (optional) - -Select one of the following options: - -* If you have your own Power BI app, you can select **Skip**. - -* If you want to create a sample Power BI app by using a sample report, select **Sample Power BI report**, and then select **Import**. - -* If you want to create a sample Power BI app by using your own report, select **Upload a *.pbix* file**, browse for your file, and then select **Import**. - -## Step 5 - Grant permissions (*Embed for your customers* only) - -Select **Grant permissions** and in the dialog, select **Accept**. This step allows your Microsoft Entra app to access the APIs you selected (also known as scopes) with your signed-in user. This user is also known as the **master user**. - -## Download sample app (optional) - -If you created a Power BI workspace and uploaded content to it by using this tool, you can now select **Download sample application**. - ->[!NOTE] ->If you skipped the optional stages, you can still download a sample Power BI app. However, the code in the downloaded app lacks the properties that get filled in during registration. For example, if you don't create a workspace, the sample app doesn't include the workspace ID. - -Make sure you copy all the information in the **Summary** box. Your Power BI embedding environment is ready to use. - -## Manual registration - -If you didn't use the Power BI embedded analytics setup tool, use the procedure in this section to manually register a Microsoft Entra app. But take these steps only if you're creating one of the following solutions: +To register a Microsoft Entra app, use the following procedure in this section. Take these steps only if you're creating one of the following solutions: * An embed-for-your-organization application * An embed-for-your-customers application with a *service principal* @@ -172,6 +72,8 @@ For more information about how to register applications in Microsoft Entra ID, s 1. Select **Register**. After your app is registered, you're directed to your app's overview page, where you can obtain the **Application ID**. +Make sure you copy all the information in the **Summary** box. Your Power BI embedding environment is ready to use. + ## Related content More questions? [Try asking the Power BI Community](https://community.powerbi.com/). diff --git a/powerbi-docs/developer/visuals/TOC.yml b/powerbi-docs/developer/visuals/TOC.yml index 4ec5f37048..8046eaa11a 100644 --- a/powerbi-docs/developer/visuals/TOC.yml +++ b/powerbi-docs/developer/visuals/TOC.yml @@ -31,8 +31,6 @@ href: power-bi-custom-visuals-faq.yml - name: "Examples of Power BI visuals" href: samples.md - - name: "Get custom visual metadata" - href: scanner-api.md - name: Develop your own custom visual items: - name: "Set up your environment for developing a Power BI visual" diff --git a/powerbi-docs/developer/visuals/scanner-api.md b/powerbi-docs/developer/visuals/scanner-api.md deleted file mode 100644 index db253e4af6..0000000000 --- a/powerbi-docs/developer/visuals/scanner-api.md +++ /dev/null @@ -1,252 +0,0 @@ ---- -title: Power BI visual scanner API -description: Learn how to use the report generated by the scanner API to receive metadata about a Power BI visual. -author: mberdugo -ms.author: monaberdugo -ms.reviewer: gennadyl -ms.service: powerbi -ms.subservice: powerbi-custom-visuals -ms.topic: concept-article -ms.date: 10/10/2024 -#customer intent: As a Power BI visual developer, I want to learn how to use the scanner API to receive metadata about a Power BI visual so that I can better understand the visual and its usage. ---- - -# Scanner API - -The [Workspace information scanner API](/rest/api/power-bi/admin/workspace-info-post-workspace-info) is a REST API that provides metadata about Power BI reports, datasets, and visuals. The scanner API is useful for understanding what kind of information is contained in the report, who created it, what restrictions apply to it, etc. - -If the scanner API is invoked with URI parameter `reportObjects` set to true, the reports section in the output contains information about the visuals used in each report. - -## Scanner output example - -The following snippet is an example of the reports section of the scanner API output: - -```json - "reports": [ - { - "reportType": "PowerBIReport", - "id": "a901f1d6-0848-428a-80c0-98311dc1679b", - "name": "ContosoSales", - "datasetId": "2f9bf0f9-b840-4376-a60a-47a6ae07c775", - "createdDateTime": "2024-07-02T09:28:03.077", - "modifiedDateTime": "2024-07-02T09:32:37.63", - "modifiedBy": "adminem3@PBIEmbedTestE3.ccsctp.net", - "createdBy": "adminem3@PBIEmbedTestE3.ccsctp.net", - "modifiedById": "d1814d1d-a355-40b1-8d86-0101ae965820", - "createdById": "d1814d1d-a355-40b1-8d86-0101ae965820", - "sensitivityLabel": { - "labelId": "cebb6849-d26a-4cfa-8f15-030e9d5d9a65" - }, - "users": [ - { - "reportUserAccessRight": "Owner", - "emailAddress": "adminem3@PBIEmbedTestE3.ccsctp.net", - "displayName": "Admin EM3", - "identifier": "adminem3@PBIEmbedTestE3.ccsctp.net", - "graphId": "d1814d1d-a355-40b1-8d86-0101ae965820", - "principalType": "User", - "userType": "Member" - } - ], - "sections": [ - { - "displayName": "Page 2", - "visuals": [ - { - "visualType": "clusteredBarChart" - } - ] - }, - { - "displayName": "Page 1", - "visuals": [ - { - "visualType": "Sunburst1445472000808" - }, - { - "visualType": "WordCloud1447959067750" - } - ] - } - ] - } - ] - ``` - -As you can see, the reports section contains a `sections` list. Each section contains the section name and lists the type of each visual in that section: - -```json - "sections": [ - { - "displayName": "Page 1", - "visuals": [ - { - "visualType": "Sunburst1445472000808" - }, - { - "visualType": "WordCloud1447959067750" - } - ] - } - ] -``` - -To get information about a visual (for example, its name, whether it’s a core visual, public custom visual or private visual, certified, etc.) check the visual type against multiple data sources. Then add to the data about the visual data based on the information you find. - -## Core visuals - -The following list contains the types of [Core (built-in) visuals](./power-bi-custom-visuals.md#core-power-bi-visuals): - -```json -"actionButton" -"animatedNumber" -"areaChart" -"barChart" -"basicShape" -"shape" -"card" -"cardVisual" -"multiRowCard" -"clusteredBarChart" -"clusteredColumnChart" -"columnChart" -"donutChart" -"funnel" -"gauge" -"hundredPercentStackedBarChart" -"hundredPercentStackedColumnChart" -"image" -"lineChart" -"lineStackedColumnComboChart" -"lineClusteredColumnComboChart" -"map" -"filledMap" -"azureMap" -"ribbonChart" -"shapeMap" -"treemap" -"pieChart" -"realTimeLineChart" -"scatterChart" -"stackedAreaChart" -"table" -"matrix" -"tableEx" -"pivotTable" -"accessibleTable" -"slicer" -"advancedSlicerVisual" -"pageNavigator" -"bookmarkNavigator" -"filterSlicer" -"textbox" -"aiNarratives" -"waterfallChart" -"scriptVisual" -"pythonVisual" -"kpi" -"keyDriversVisual" -"decompositionTreeVisual" -"qnaVisual" -"scorecard" -"rdlVisual" -"dataQueryVisual" -"debugVisual" -"heatMap" -``` - -If the visual type is a core visual, there's no need to look for it in other data sources, like AppSource catalog. - -## AppSource (public) custom visuals - -AppSource visuals are public Custom Visuals available from [Microsoft AppSource](https://appsource.microsoft.com/marketplace/apps?product=power-bi-visuals). You can fetch visual information from the public [catalog endpoint](https://catalogapi.azure.com/offers?storefront=appsource&api-version=2018-08-01-beta&$filter=offertype+eq+%27PowerBIVisuals%27) that AppSource provides. - -The resulting json contains a list of items and a link to the next page, `nextPageLink`. For example: - -```json -{ - "items": [ - { -} - ], - "nextPageLink": https://catalogapi.azure.com/offers?storefront=appsource&api-version=2018-08-01-beta&$filter=offertype+eq+%27PowerBIVisuals%27&$skiptoken=W3sidG9rZW4iOiIrUklEOn4yVk53QUxkRkVIeHNhQUFBQUFCQUNBPT0jUlQ6MSNUUkM6MTg1I0lTVjoyI0lFTzo2NTU2NyNRQ0Y6OCIsInJhbmdlIjp7Im1pbiI6IjA1QzFFNzBCM0IzOTUwIiwibWF4IjoiMDVDMUU3QUIxN0U3QTYifX1d -} -``` - -Typically, a full list of visuals is about 3-4 pages long. For complete information about the visual, you must fetch the entire report. - -Each item in the items list is a custom visual and contains all the information stored about it in AppSource. This document references only relevant fields: - -```json - - -"powerBIVisualId": "visualType", - -"displayName": "Mapbox Custom Visual", - -"publisherDisplayName": "OKVIZ Corp.", - -"enrichedData": { - - "tags": [ - - "PowerBICertified" - - ], - -}, - -"categoryIds": [ - - "pbiv-other", - - "PowerBICertified" - -], - -"id": "xviz.inforiver-charts" -``` - -The following fields can be used to enhance information about a visual provided by Scanner API: - -* "powerBIVisualId": used to find correct item, which should be the same as `visualType` from Scanner output - -* "displayName": visual name - -* Tag “PowerBICertified” means that visual is Certified - -* "publisherDisplayName": publisher name - -* "id" is used to calculate PDP link page: `https://appsource.microsoft.com/ /product/PowerBIVisuals/` - -## Private Custom Visuals (from a file) - - Private visuals added to a Power BI report using the [Import a visual from a file](./import-visual.md#import-a-visual-file-from-your-local-computer-into-power-bi) option. If a visual isn't a core visual and not an AppSource visual, it’s a private visual. For private visuals, we provide only their `visualType`. - -## Organization visuals - -Both AppSource visuals and private visuals can be added to the Organization’s visuals store which exists for each organization (tenant). If a private custom visual is added to an organization’s visual store, the suffix _OrgStore is added to its `visualType`. In contrast, when an AppSource visual is added directly to an organization’s visual store, it keeps its original `visualType`. - -To determine if a public custom visual (from AppSource) is in an organization's store: - -1. Get the visual’s information using information from the [AppSource catalog](#appsource-public-custom-visuals). -1. Download the organization’s visuals list (in CSV format) from **Power BI** -> **Admin Portal** -> **Organization Visuals** -> **Export**. -1. If the visual’s `visualType` appears in the downloaded list, this visual is an organizational visual. In this case, update visual name to match the one in the CSV file. - -> [!NOTE] -> -> * There is no difference between an AppSource custom visual and its counterpart in the organization store, including its code and version. The only difference might be in the visual name. -> * If the tenant admin downloads a custom visual *.pbiviz* file from AppSource and adds it to the organization store using Add Visual -> From File, the suffix *_OrgStore* is added and when exported, it will appear as a *Private file*. A private file visual doesn't get upgraded and is treated as a private visual in the Org Store. - -Demo application to use Scanner API - -Original code: - -`https://github.com/microsoft/Fabric-metadata-scanning` - -Updated code includes visual info enrichment: -`https://github.com/gennadylaventman/Fabric-metadata-scanning/tree/dev/glaventman/enrichCV` - -## Related content - -[Power BI custom visuals](./power-bi-custom-visuals.md) diff --git a/powerbi-docs/fundamentals/desktop-change-log.md b/powerbi-docs/fundamentals/desktop-change-log.md index f3c03aea2a..10c2dff7ba 100644 --- a/powerbi-docs/fundamentals/desktop-change-log.md +++ b/powerbi-docs/fundamentals/desktop-change-log.md @@ -7,7 +7,7 @@ ms.reviewer: kfollis, davidi ms.service: powerbi ms.subservice: pbi-fundamentals ms.topic: conceptual -ms.date: 01/21/2025 +ms.date: 02/02/2025 no-loc: [Copilot] --- @@ -18,13 +18,33 @@ This change log is for Power BI Desktop and lists new items and bug fixes for ea See [What's new in Power BI](desktop-latest-update.md) for more information about new features. + +## January 2025 QFE 3 + +*Version 2.139.2054.0, Released: January 29, 2025* + +Bug fixes/improvements: + +* Fixed issue in v2 connector that create duplicate records, and some missing records, causing rows in the dataset to be repeated instead of new rows being returned + + +## January 2025 QFE 2 + +*Version 2.139.1733.0, Released: January 24, 2025* + +Bug fixes/improvements: + +* Fixed issue of users receiving an error due to pending changes at the conclusion of a model change +* Fixed SQL Server connector to operate properly with Fabric SQL + + ## January 2025 QFE 1 *Version 2.139.1678.0, Released: January 14, 2025* Bug fixes/improvements: -* Fixed issue of connecting to Fabric SQL database using SQL connector. +* Fixed issue when connecting to Fabric SQL database using SQL connector ## November 2024 QFE 3 @@ -42,7 +62,7 @@ Bug fixes/improvements: Bug fixes/improvements: * Fixed a regression issue where users in certain regions were seeing an error because they can access and use the Copilot pane, even though it shouldn't have been available to them -* Fixed an issue where incorrect column names were being returned from *AdomdDataReader* results after changing column format or aggregation, causing broken data views and visual updates.= +* Fixed an issue where incorrect column names were being returned from *AdomdDataReader* results after changing column format or aggregation, causing broken data views and visual updates ## November 2024 QFE 1 @@ -53,7 +73,7 @@ Bug fixes/improvements: * Diagnostic telemetry to capture logs related to the broken data view and visuals issue, when a user changes the column format or aggregation * Disabled *Inline Sparkline Measure* since it broke previously created reports that used calculation groups with sparklines * Fixed an issue preventing users from connecting to SAP HANA due to a *Non-null assertion failure: queryName* error -* Removed telemetry service suspend for Power BI Desktop applications, and introduced configuration for page visibility service +* Removed telemetry service suspends for Power BI Desktop applications, and introduced configuration for page visibility service * Fixed the endless retry of the V2 client-side copilot orchestrator and added a limit to the number of retries * Fixed an issue where Q&A tooling was broken due to improper error handling @@ -143,7 +163,7 @@ Bug fixes/improvements: ## April 2024 QFE 3 -*Version : 2.128.1380.0, Released: May 02 , 2024* +*Version: 2.128.1380.0, Released: May 02, 2024* Bug fixes/improvements: @@ -155,7 +175,7 @@ Bug fixes/improvements: ## April 2024 QFE 2 -*Version 2.128.1177.0: , Released: April 24 , 2024* +*Version 2.128.1177.0: , Released: April 24, 2024* Bug fixes/improvements: @@ -193,8 +213,8 @@ Bug fixes/improvements: Bug fixes/improvements: -* Fix for DataGrid copy to clipboard : Fixed issue of "Copy Table" not working in datagrid view of Power BI Desktop -* Bug fixes for the DAX inline Copilot: Fixed issue where invalid DAX query banner shows up unexpectedly in some cases. Prevents cancel button from being stuck when pressed too early. Prevents stale user input from showing when signing in again +* Fix for DataGrid copy to clipboard: Fixed issue of "Copy Table" not working in datagrid view of Power BI Desktop +* Bug fixes for the DAX inline Copilot: Fixed issue where invalid DAX query banner shows up unexpectedly in some cases. Prevents **Cancel** button from being stuck when pressed too early. Prevents stale user input from showing when signing in again ## February 2024 QFE 1 @@ -302,7 +322,7 @@ Bug fixes/improvements: Bug fixes/improvements: -* Fix to large models. Now customers would be able to see relationships lines in Model View. Template files with multiple queries now load faster. +* Fix too large models. Now customers would be able to see relationships lines in Model View. Template files with multiple queries now load faster. ## July 2023 QFE 1 @@ -476,7 +496,7 @@ Bug fixes/improvements: - Data view regression fix: now list of filters in context menu will be displayed even when menu icons aren't in focus. - EvaluateAndLog DAX function fix: now the function works as expected and won't return an error. - SAP HANA regression fixes: now power query won't show "the index is outside the bounds of the records" error message and there won't be missing values for columns when using Cube.AttributeMemberID on the query. -- Roll back change for cashing: cashing will be done the same way as in previous releases +- Roll back change for cashing: cashing is done the same way as in previous releases - Formula bar fixes for cases when **Shift+Enter** is used. - “Apply/discard changes” regression fix. @@ -498,8 +518,8 @@ Bug fixes/improvements: *Version: 2.107.841.0, Released: July 21, 2022* Bug fixes/improvements: -- Fix for SAP BW: now customers will be able to retrieve a full semantic model when querying SAP BW and using paging operations (Table.skip, Table.FirstN etc.) even if the data exceeds the page size. -- Fix for SAP HANA: now when creating new connections or refreshing data, a display name will be shown instead of a technical column name in the fields well. +- Fix for SAP BW: now customers are able to retrieve a full semantic model when querying SAP BW and using paging operations (Table.skip, Table.FirstN etc.) even if the data exceeds the page size. +- Fix for SAP HANA: now when creating new connections or refreshing data, a display name is shown instead of a technical column name in the fields well. ## June 2022 QFE 1 diff --git a/powerbi-docs/guidance/powerbi-implementation-planning-content-lifecycle-management-deploy.md b/powerbi-docs/guidance/powerbi-implementation-planning-content-lifecycle-management-deploy.md index 8824072783..492c1a18f0 100644 --- a/powerbi-docs/guidance/powerbi-implementation-planning-content-lifecycle-management-deploy.md +++ b/powerbi-docs/guidance/powerbi-implementation-planning-content-lifecycle-management-deploy.md @@ -172,7 +172,7 @@ Azure Pipelines and other code-based tools can programmatically deploy content b - **[XMLA read/write endpoints](../enterprise/service-premium-connect-tools.md)**: You can _[create](/analysis-services/tmsl/create-command-tmsl?view=asallproducts-allversions&preserve-view=true)_ or [_alter_ semantic models](/analysis-services/tmsl/alter-command-tmsl?view=asallproducts-allversions&preserve-view=true) by using XMLA endpoints together with a valid model.bim file. XMLA endpoints let you deploy changes to specific model objects instead of the entire model. Azure Pipelines can make use of third-party tools (like the Tabular Editor command line interface) to deploy semantic models by using the XMLA endpoints. > [!TIP] -> When you use the Fabric or Power BI REST APIs, you must first create an app registration in Azure ([described here for Power BI Embedded](../developer/embedded/register-app.md?tabs=customers&preserve-view=true#step-2---register-your-application)). This requires a Microsoft Entra ID tenant and an organizational user, and can be a complex process to set up the appropriate permissions. However, you can execute the Fabric REST APIs in notebooks without creating an app registration. This streamlines the setup and use of APIs in your solutions, so that you don't have to manage credentials or configure any setup prior to using the APIs. +> When you use the Fabric or Power BI REST APIs, you must first create an app registration in Azure ([described here for Power BI Embedded](../developer/embedded/register-app.md)). This requires a Microsoft Entra ID tenant and an organizational user, and can be a complex process to set up the appropriate permissions. However, you can execute the Fabric REST APIs in notebooks without creating an app registration. This streamlines the setup and use of APIs in your solutions, so that you don't have to manage credentials or configure any setup prior to using the APIs. > > To use the Fabric REST APIs without registering an app, use [semantic link](/fabric/data-science/semantic-link-overview) in a Fabric notebook with the [FabricRestClientClass](/python/api/semantic-link-sempy/sempy.fabric.fabricrestclient?view=semantic-link-python&preserve-view=true) of [sempy](/python/api/semantic-link-sempy/sempy?view=semantic-link-python&preserve-view=true) to call the API. diff --git a/powerbi-docs/report-server/compare-report-server-service.md b/powerbi-docs/report-server/compare-report-server-service.md index 315d78c89b..507072ca34 100644 --- a/powerbi-docs/report-server/compare-report-server-service.md +++ b/powerbi-docs/report-server/compare-report-server-service.md @@ -8,7 +8,7 @@ ms.topic: overview ms.service: powerbi ms.subservice: powerbi-report-server ms.custom: mvc, intro-overview -ms.date: 11/12/2024 +ms.date: 02/03/2025 #Customer intent: As a customer of Power BI, I'd like to understand how Power BI Report Server and the Power BI service are the same and are different. --- @@ -40,7 +40,7 @@ Power BI Report Server and the Power BI service have many similarities and some | Q&A | No | Yes | [Q&A in the Power BI service and Power BI Desktop](../create-reports/power-bi-tutorial-q-and-a.md) | Quick insights | No | Yes | [Automatically generate data insights with Power BI](../consumer/end-user-insights.md) | | Paginated reports | Yes | Yes | [Paginated reports](../paginated-reports/paginated-reports-report-builder-power-bi.md) | -| Personalize visuals | No | No | You can [interact with a report to see different data](../consumer/end-user-paginated-report.md#interact-with-a-paginated-report), but you can't modify the report itself. | +| Personalize visuals | No | Yes | Consumers can [customize visual type or data fields](../create-reports/power-bi-personalize-visuals.md) without modifying the report itself. | | Power BI mobile apps | Yes | Yes | [Power BI mobile apps overview](../consumer/mobile/mobile-apps-for-mobile-devices.md) | | Real-time streaming | No | Yes | [Real-time streaming in Power BI](../connect-data/service-real-time-streaming.md) | | Automatic page refresh for DirectQuery models | No | Yes | [Automatic page refresh](../create-reports/desktop-automatic-page-refresh.md) |