Total Visitors
From b831747e6fb15cd5044f209792b8f3622760a9d1 Mon Sep 17 00:00:00 2001
From: Timna Brown <24630902+brown9804@users.noreply.github.com>
Date: Wed, 16 Apr 2025 11:41:10 -0600
Subject: [PATCH 06/13] + ConfigureCloudConnectionsGateways.md
---
.../ConfigureCloudConnectionsGateways.md | 243 ++++++++++++++++++
1 file changed, 243 insertions(+)
create mode 100644 Workloads-Specific/PowerBi/ConfigureCloudConnectionsGateways.md
diff --git a/Workloads-Specific/PowerBi/ConfigureCloudConnectionsGateways.md b/Workloads-Specific/PowerBi/ConfigureCloudConnectionsGateways.md
new file mode 100644
index 0000000..e7ac877
--- /dev/null
+++ b/Workloads-Specific/PowerBi/ConfigureCloudConnectionsGateways.md
@@ -0,0 +1,243 @@
+# Demostration: How to Configure Power Bi Cloud Connections \& Gateways
+
+Costa Rica
+
+[](https://github.com/)
+[brown9804](https://github.com/brown9804)
+
+Last updated: 2024-11-15
+
+------------------------------------------
+
+
+List of References (Click to expand)
+
+- [Create and share cloud data sources in the Power BI service](https://learn.microsoft.com/en-us/power-bi/connect-data/service-create-share-cloud-data-sources)
+- [Connect to cloud data sources in the Power BI service](https://learn.microsoft.com/en-us/power-bi/connect-data/service-connect-cloud-data-sources)
+- [Manage users around Cloud Connections](https://learn.microsoft.com/en-us/fabric/data-factory/data-source-management#manage-users)
+- [Migrate from Azure Analysis Services to Power BI Premium](https://learn.microsoft.com/en-us/power-bi/guidance/migrate-azure-analysis-services-to-powerbi-premium)
+- [On-premises and virtual network (VNet) data gateways documentation](https://learn.microsoft.com/en-us/data-integration/gateway/)
+- [What is an on-premises data gateway?](https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-onprem)
+- [What is a virtual network (VNet) data gateway?](https://learn.microsoft.com/en-us/data-integration/vnet/overview)
+- [Set privacy levels (Power Query) details](https://support.microsoft.com/en-us/office/set-privacy-levels-power-query-cc3ede4d-359e-4b28-bc72-9bee7900b540?ui=en-us&rs=en-us&ad=us)
+- [What is the admin monitoring workspace? (Preview)](https://learn.microsoft.com/en-us/fabric/admin/monitoring-workspace)
+- [Feature usage and adoption report (preview)](https://learn.microsoft.com/en-us/fabric/admin/feature-usage-adoption)
+- [Manage security roles of an on-premises data gateway](https://learn.microsoft.com/en-us/data-integration/gateway/manage-security-roles)
+- [Virtual network (virtual network) data gateway FAQs](https://learn.microsoft.com/en-us/data-integration/vnet/data-gateway-faqs)
+
+
+
+
+Table of Contents (Click to expand)
+
+- [Power Bi: Cloud Connections & Gateways](#power-bi-cloud-connections--gateways)
+ - [Wiki](#wiki)
+ - [Content](#content)
+ - [How to Manage Cloud connections](#how-to-manage-cloud-connections)
+ - [Creating Shareable Connections](#creating-shareable-connections)
+ - [Managing Connections](#managing-connections)
+ - [Admin Monitoring Workspace](#admin-monitoring-workspace)
+ - [Identify Access per report](#identify-access-per-report)
+ - [Restrict Access from new gateway connections](#restrict-access-from-new-gateway-connections)
+ - [On-premises Data Gateways](#on-premises-data-gateways)
+ - [Virtual Network VNet Data Gateways](#virtual-network-vnet-data-gateways)
+
+
+
+
+## How to Manage Cloud connections
+
+Managing cloud connections in Power BI, below you can find differences between personal and shareable cloud connections:
+
+> [!NOTE]
+> `When you publish a .PBIX file` from Power BI Desktop that connects to a cloud data source, `Power BI automatically creates a personal cloud connection and binds it to your semantic model`. This means that the connection details and credentials you used in Power BI Desktop are carried over to the Power BI service, allowing the report to continue accessing the cloud data source without any additional configuration.
+
+> Personal Cloud Connections
+
+| **Aspect** | **Details** |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **Automatic Creation** | When you publish a .PBIX file from Power BI Desktop that connects to a cloud data source, a personal cloud connection is automatically created and bound to your semantic model. This means the connection details and credentials used in Power BI Desktop are carried over to the Power BI service, allowing the report to continue accessing the cloud data source without additional configuration. |
+| **Limitations** | Personal cloud connections are tied to the individual user who created them and cannot be shared with others. This can be limiting if multiple users need to access the same data source. |
+
+> Shareable Cloud Connections
+
+| **Aspect** | **Details** |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **Advantages** | Shareable cloud connections allow multiple connections to the same data source with different settings and can be shared with other users. This makes data management more collaborative and flexible. |
+| **Manual Creation** | Unlike personal cloud connections, shareable cloud connections need to be created manually in the Power BI service. You can create a new shareable cloud connection directly from the Semantic model settings page under Gateway and cloud connections. Select the shareable cloud connection you want to use and apply it. |
+
+### Creating Shareable Connections
+
+> You can create a new shareable cloud connection directly from the Semantic model settings page under Gateway and cloud connections. Select the shareable cloud connection you want to use and apply it.
+
+> [!IMPORTANT]
+> Security: If a data source contains `highly sensitive or confidential data`, set the privacy level to `Private`.
+
+| Privacy level | Details |
+| --- | --- |
+| Private | Contains sensitive or confidential information, and the visibility of the data source may be restricted to authorized users. It is completely isolated from other data sources. Examples include Facebook data, a text file containing stock awards, or a workbook containing an employee review. |
+| Organizational | Limits the visibility of a data source to a trusted group of people. It is isolated from all Public data sources, but is visible to other Organizational data sources. A common example is a Microsoft Word document on an intranet SharePoint site with permissions enabled for a trusted group. |
+| Public | Gives everyone visibility to the data. Only files, internet data sources, or workbook data can be marked Public. Examples include data from a Wikipedia page, or a local file containing data copied from a public web page.|
+
+Steps:
+- Go to [Power Bi](https://app.powerbi.com/)
+- Click on ⚙️, and go to `Manage connections and gateways`
+
+
+
+- Click on `+ New`, and choose the connection type, and fill required details.
+
+
+
+### Managing Connections
+
+> - `Switching to Shareable Connections`: If you want to switch from a personal cloud connection to a shareable one, you can do so in the Semantic model settings. This allows you to leverage the benefits of shareable connections, such as easier management and sharing capabilities.
+> - `Granular Access Control`: Power BI allows for granular access control at the tenant, workspace, and semantic model levels. This means you can enforce access policies to ensure that only authorized users can create or use specific connections.
+
+- To assign the connection a semantic model, click on `...` over your semantic model, and go to `Settings`
+
+
+
+- Under `Semantic models`, search for `Gateway and cloud connections`. Assign you connection to the data source in the semantic model.
+
+
+
+- Another way go to that view og assign the connection, you can click on ⚙️, and go to `Power Bi Settings`. Search for your semantic models, and the `Gateway and cloud connections`:
+
+
+
+## Admin Monitoring Workspace
+
+> Can help to identify which Power BI Premium Users are making use of the Cloud connections
+
+The admin monitoring workspace in Microsoft Fabric is designed for `administrators to monitor and manage workloads, usage, and governance within their tenant`. It provides insights into user activity, content sharing, and capacity performance. The workspace is `automatically installed the first time an admin accesses it`. It includes `few reports and semantic models for detailed analysis`, helping administrators keep track of how resources are being used and ensuring compliance with governance policies.
+
+Steps to setup admin monitoring workspace:
+
+- Go to [Power Bi](https://app.powerbi.com/)
+- Click on ⚙️, and go to `Admin portal`
+- Under `Usage metrics`, and go to `Open admin monitoring workspace`
+
+
+
+> The report can be accessed from the Admin monitoring workspace and is designed for admins to analyze various usage scenarios.
+
+| Report Name | Details |
+| --- | --- |
+| Feature Usage and Adoption Report | This report provides an in-depth analysis of how different features are utilized and adopted across your Microsoft Fabric tenant. It includes pages for activity overview, analysis, and detailed activity scenarios, helping identify which users are making use of cloud connections. |
+| Purview Hub | Offers insights into data governance and compliance. It helps administrators manage and monitor data policies, ensuring that data usage aligns with organizational standards and regulatory requirements. |
+
+
+
+Some key limitations and considerations regarding reports in the admin monitoring workspace:
+
+| **Category** | **Details** |
+|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **Non-Modifiable Reports** | - ``Fixed Reports``: Reports in the admin monitoring workspace are often pre-configured and cannot be modified. This means you cannot change the visuals, add new data fields, or customize the layout to fit specific needs.
- ``Limited Customization``: The inability to modify these reports can be restrictive if you need to tailor the data presentation to specific audiences or requirements. |
+| **Access and Permissions** | - ``Restricted Access``: Only users with appropriate permissions can view these reports. This can limit the ability of other team members to access and utilize the data.
- ``Data Sensitivity``: Since these reports often contain sensitive administrative data, access controls are crucial to ensure data security and compliance. |
+
+Benefits of sharing the semantic model:
+
+| **Category** | **Details** |
+|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **Creating Custom Reports** | - ``Flexibility``: By sharing the semantic model, users can create their own reports using the same underlying data. This allows for greater flexibility in how data is visualized and analyzed.
- ``Tailored Insights``: Users can customize reports to highlight specific metrics or insights that are most relevant to their needs. |
+| **Collaboration** | - ``Shared Understanding``: Sharing the semantic model promotes a shared understanding of the data across the organization. Different teams can collaborate more effectively by working with the same data definitions and structures.
- ``Enhanced Data Utilization``: Multiple users can leverage the semantic model to create diverse reports, enhancing the overall utilization of the data. |
+| **Consistency** | - ``Standardized Data``: Using a shared semantic model ensures that all reports are based on the same data definitions and calculations, promoting consistency and accuracy in reporting.
- ``Reduced Redundancy``: It reduces the need for multiple versions of the same data, minimizing redundancy and potential discrepancies. |
+
+> [!IMPORTANT]
+> Other ways to get insights:
+> - `Monitoring Usage`: You can monitor and manage cloud connections through the Power BI service. By navigating to the Manage connections and gateways section, you can see which users have access to and are using specific cloud connections.
+>
+> - `Premium Capacity Metrics`: For a more detailed analysis, you can use the Premium Capacity Metrics app, which provides insights into the usage and performance of your Power BI Premium capacities.
+
+## Identify Access per report
+
+- Go to your workspace
+- Click on `...`, and select `Manage permissions`
+
+
+
+- You will see something like this:
+
+
+
+## Restrict Access from new gateway connections
+
+> Facilitate secure data transfer between Power BI or Power Apps and non-cloud data sources like on-premises SQL Server databases or SharePoint sites.
+
+Gateway Roles:
+
+| Role | Permissions |
+|------------------------------|------------------------------------------------------------------------------------------------------|
+| `Admin` | - Can manage and update the gateway.
- Allowed to create connections (data sources) on the gateway.
- Can manage (add/delete) users with admin, connection creator, and connection creator with sharing roles.
- Manages access to all connections created on the gateway. |
+| `Connection Creator` | - Allowed to create connections/data sources on the gateway.
- Can test the status of the gateway cluster and its members.
- Cannot manage or update the gateway or add/remove users. |
+| `Connection Creator with Sharing` | - Allowed to create connections/data sources on the gateway and test the gateway status.
- Can share the gateway with other users as a connection creator but cannot remove users. |
+
+Connection Roles:
+
+| Role | Permissions |
+|------------------------------|------------------------------------------------------------------------------------------------------|
+| `Owner` | - Can update credentials and delete the connection.
- Can assign others to the connection with Owner, User, or User with sharing permissions. |
+| `User` | - Can use the connection in Power BI reports and dataflows.
- Cannot see or update credentials. |
+| `User with Sharing` | - Can use the connection in Power BI reports and dataflows.
- Can share the data source with others with User permission. |
+
+
+Steps to Manage Gateway and Connection Roles:
+
+- Go to [Power Bi/Fabric admin center](https://app.powerbi.com/)
+- Click on ⚙️, and go to `Manage Connections and Gateways`
+- Choose `Connections`, `On premises data gateway` or `Virtual Network data gateways`:
+
+
+
+- Click on `...`, and select `Manage users`:
+
+
+
+
+
+### On-premises Data Gateways
+
+> On-premises data gateways facilitate secure data transfer between on-premises data sources and Power BI services. They are essential for scenarios `where data cannot be moved to the cloud due to compliance or security reasons`.
+
+| **Category** | **Details** |
+|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ``Restricting Gateway Installations`` | - ``Tenant-Level Control``: Restrict who can install on-premises data gateways at the tenant level through the Power Platform admin center. This prevents unauthorized users from creating new gateway connections.
- ``Role Management``: Assign specific roles to users, such as Admin, Connection Creator, and Connection Creator with Sharing, to control who can create and manage connections on the gateway. |
+| ``Security Measures`` | - ``Network Security Groups (NSGs)``: Configure NSGs to allow outbound traffic to necessary endpoints, such as Microsoft Entra ID for authentication and Certificate Authorities for HTTPS connections.
- ``Private Links``: Use private links to secure connectivity from your network to Power BI, ensuring that data traffic does not traverse the public internet. |
+| ``Managing Data Sources`` | - ``Data Source Configuration``: Configure data sources on the gateway and manage user access to these sources. Ensure that only authorized users can create and manage connections. |
+| ``Monitoring and Auditing`` | - ``Usage Monitoring``: Regularly monitor gateway usage to detect any unauthorized access or unusual activity.
- ``Audit Logs``: Maintain audit logs to track changes and access to the gateways and data sources. |
+
+Steps to Restrict Access for On-Premises Data Gateways:
+
+> - **Tenant-Level Control**: You can `restrict who can install on-premises data gateways at the tenant level through the Power Platform admin center`. This prevents unauthorized users from creating new gateway connections.
+> - **Role Management**: Assign specific roles to users, such as Admin, Connection Creator, and Connection Creator with Sharing, `to control who can create and manage connections on the gateway`.
+
+
+1. **Access the Power Platform Admin Center**: Go to the [Power Platform Admin Center](https://admin.powerplatform.microsoft.com/ext/DataGateways).
+2. **Navigate to Data Gateways**:
+ - Click on **Data** (preview) in the left-hand menu.
+ - Select **On-premises data gateway**.
+3. **Enable Tenant Administration for Gateways**: Turn on **Tenant administration for gateways**.
+
+
+
+4. **Restrict Users from Installing Gateways**: Toggle on **Restrict users in your organization from installing gateways**.
+5. **Allow Specific Users to Override the Restriction** (if needed): Add the users who are allowed to install gateways by specifying their details.
+
+
+
+### Virtual Network (VNet) Data Gateways
+
+> Allow Power BI to connect to data services within an Azure virtual network without needing an on-premises data gateway. This setup is particularly useful for maintaining security and compliance by keeping data traffic within the Azure backbone.
+
+| **Section** | **Details** |
+|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **Licensing Requirements:**| VNet data gateways require a Power BI Premium capacity license (A4 SKU or higher or any P SKU). |
+| **Managing VNet Data Gateways:** | - **Admin Management:** You can manage VNet data gateways through the Power Platform admin center or the Manage Gateways page in Power BI.
- **Data Source Management:** Create and share data sources within the VNet data gateway as you would with standard data gateways. |
+| **Security and Connectivity:** | - **Private Endpoints:** Use private endpoints to connect securely to your data sources within Azure. This ensures that all traffic remains on the Azure backbone and is not exposed to the public internet.
- **Conditional Access Policies:** VNet data gateways support conditional access policies, allowing you to enforce security measures based on user identity and location.
- **Microsoft Entra ID SSO:** Enable single sign-on (SSO) for DirectQuery to ensure that queries execute under the user's Microsoft Entra ID identity. |
+| **Restrictions and Limitations:** | - **Cross-Tenant Scenarios:** VNet data gateways must be created in the same tenant as the Power BI tenant.
- **Region Constraints:** The virtual network data gateway is physically located in the same region as your Azure virtual network. |
+
+
+
Total Visitors
+
+
From fa1b03d778cef33efef5d2cf36dc77a2a8cc9679 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
Date: Wed, 16 Apr 2025 17:41:23 +0000
Subject: [PATCH 07/13] Update last modified date in Markdown files
---
Workloads-Specific/PowerBi/ConfigureCloudConnectionsGateways.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Workloads-Specific/PowerBi/ConfigureCloudConnectionsGateways.md b/Workloads-Specific/PowerBi/ConfigureCloudConnectionsGateways.md
index e7ac877..7833668 100644
--- a/Workloads-Specific/PowerBi/ConfigureCloudConnectionsGateways.md
+++ b/Workloads-Specific/PowerBi/ConfigureCloudConnectionsGateways.md
@@ -5,7 +5,7 @@ Costa Rica
[](https://github.com/)
[brown9804](https://github.com/brown9804)
-Last updated: 2024-11-15
+Last updated: 2025-04-16
------------------------------------------
From 1f32c52a1c650fd64c63743ab9b2408794458e12 Mon Sep 17 00:00:00 2001
From: Timna Brown <24630902+brown9804@users.noreply.github.com>
Date: Wed, 16 Apr 2025 11:43:51 -0600
Subject: [PATCH 08/13] + CopilotReports.md
---
Workloads-Specific/PowerBi/CopilotReports.md | 78 ++++++++++++++++++++
1 file changed, 78 insertions(+)
create mode 100644 Workloads-Specific/PowerBi/CopilotReports.md
diff --git a/Workloads-Specific/PowerBi/CopilotReports.md b/Workloads-Specific/PowerBi/CopilotReports.md
new file mode 100644
index 0000000..abc3799
--- /dev/null
+++ b/Workloads-Specific/PowerBi/CopilotReports.md
@@ -0,0 +1,78 @@
+# Demostration: How to use Copilot in Reporting
+
+Costa Rica
+
+[](https://github.com/)
+[brown9804](https://github.com/brown9804)
+
+Last updated: 2024-11-19
+
+----------
+
+> Prerequisites:
+> - **Admin Account**: Ensure you have admin privileges in Microsoft Fabric.
+> - **Licenses**: You need a paid Fabric capacity (F64 or higher) or Power BI Premium capacity (P1 or higher).
+
+
+
+List of References (Click to expand)
+
+- [Enable Copilot in Fabric - Microsoft Fabric](https://learn.microsoft.com/en-us/fabric/get-started/copilot-enable-fabric)
+- [Enable Fabric Copilot for Power BI - Power BI](https://learn.microsoft.com/en-us/power-bi/create-reports/copilot-enable-power-bi)
+- [How to enable Copilot in Fabric for Everyone](https://blog.fabric.microsoft.com/en-us/blog/how-to-enable-copilot-in-fabric-for-everyone-2/)
+
+
+
+
+Table of Content (Click to expand)
+
+
+
+
+
+## How to Tenant configuration
+
+1. **Sign In**: Log in to Microsoft Fabric using your admin account credentials.
+2. **Access Admin Portal**: Go to the Fabric settings and select the Admin portal from the menu.
+
+ 
+
+3. **Tenant Settings**: Navigate to the Tenant settings in the Admin portal.
+4. **Enable Copilot**: Use the search feature to locate the Copilot settings. Toggle the switch to enable Copilot in Fabric.
+
+ 
+
+5. **Geographic Boundaries**: If Azure OpenAI isn't available in your region, enable the setting to allow data to be processed outside your geographic region.
+
+ 
+
+## How to Configure Workspaces
+1. **Workspace Settings**: Ensure that your reports are located in a workspace with either Premium Power BI (P1 and above) or paid Fabric (F64 and above) capacity.
+
+ 
+
+2. **Apply Capacity**: Check your license type in the Workspace settings and apply either Premium capacity or Fabric capacity to the workspace.
+
+ 
+
+## How to Using Copilot in Power BI
+1. **Access Copilot**: Once enabled, users can access Copilot across different workloads in Fabric, including Power BI.
+2. **Generate Insights**: Use Copilot to transform and analyze data, generate insights, and create visualizations and reports.
+
+
+
+ 
+
+
+
Total Visitors
+
+
Table of Content (Click to expand)
+- [How to Tenant configuration](#how-to-tenant-configuration)
+- [How to Configure Workspaces](#how-to-configure-workspaces)
+- [How to Using Copilot in Power BI](#how-to-using-copilot-in-power-bi)
From 2f8a9de479584d318be3a76490cac67d699bb123 Mon Sep 17 00:00:00 2001
From: Timna Brown <24630902+brown9804@users.noreply.github.com>
Date: Wed, 16 Apr 2025 11:45:51 -0600
Subject: [PATCH 11/13] how to use rest api in place
---
Workloads-Specific/PowerBi/UseRestAPI.md | 145 +++++++++++++++++++++++
1 file changed, 145 insertions(+)
create mode 100644 Workloads-Specific/PowerBi/UseRestAPI.md
diff --git a/Workloads-Specific/PowerBi/UseRestAPI.md b/Workloads-Specific/PowerBi/UseRestAPI.md
new file mode 100644
index 0000000..9e297cc
--- /dev/null
+++ b/Workloads-Specific/PowerBi/UseRestAPI.md
@@ -0,0 +1,145 @@
+# Demostration: How to Use Power BI REST API
+
+Costa Rica
+
+[](https://github.com/)
+[brown9804](https://github.com/brown9804)
+
+Last updated: 2025-01-17
+
+----------
+
+> The Power BI REST API provides programmatic access to several Power BI resources, enabling automation and embedding of analytics.
+
+
+
+List of References (Click to expand)
+
+- [Using the Power BI REST APIs](https://learn.microsoft.com/en-us/rest/api/power-bi/)
+- [Reports - Get Report](https://learn.microsoft.com/en-us/rest/api/power-bi/reports/get-report)
+- [Reports Operations](https://learn.microsoft.com/en-us/rest/api/power-bi/reports)
+- [Datasets Operations](https://learn.microsoft.com/en-us/rest/api/power-bi/datasets)
+- [Get-PowerBIWorkspace](https://learn.microsoft.com/en-us/powershell/module/microsoftpowerbimgmt.workspaces/get-powerbiworkspace?view=powerbi-ps)
+- [Admin - Groups GetGroupsAsAdmin](https://learn.microsoft.com/en-us/rest/api/power-bi/admin/groups-get-groups-as-admin)
+- [Admin - WorkspaceInfo GetScanResult](https://learn.microsoft.com/en-us/rest/api/power-bi/admin/workspace-info-get-scan-result)
+- [Push semantic model limitations](https://learn.microsoft.com/en-us/power-bi/developer/embedded/push-datasets-limitations)
+- [Enhanced refresh with the Power BI REST API](https://learn.microsoft.com/en-us/power-bi/connect-data/asynchronous-refresh)
+
+
+
+
+
+Table of Contents (Click to expand)
+
+- [Overview](#overview)
+- [How to work around the rate limits](#how-to-work-around-the-rate-limits)
+ - [Batch Request](#batch-request)
+ - [Example Implementation in Python](#example-implementation-in-python)
+
+
+
+## Overview
+
+
+> [!IMPORTANT]
+> There are rate limits for Power BI REST API endpoints.
+> These limits can vary depending on the specific API you're using.
+> Make sure to check out the limits section (e.g., [Limitations Admin - WorkspaceInfo GetScanResult](https://learn.microsoft.com/en-us/rest/api/power-bi/admin/workspace-info-get-scan-result#limitations))
+
+| API Endpoint | Rate Limit | Description |
+|------------------|----------------|-----------------|
+| General API Requests | 120 requests per minute per user | Applies to most general API requests|
+| POST Rows Requests (Tables with < 250,000 rows) | 120 requests per minute per dataset | For tables with fewer than 250,000 rows |
+| POST Rows Requests (Tables with ≥ 250,000 rows) | 120 requests per hour per dataset | For tables with 250,000 or more rows|
+| Admin - GetDatasourcesAsAdmin | 50 requests per hour | Specific to the GetDatasourcesAsAdmin endpoint |
+| Specific Endpoints (e.g., Get Report Users) | 200 requests per hour | Applies to certain endpoints like retrieving report users. |
+
+## How to work around the rate limits
+
+> Few stategies below:
+
+| **Strategy** | **Description** | **Implementation** |
+|--------------------|---------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|
+| **Batch Requests** | Combine multiple operations into a single batch request. | Use the `/batch` endpoint to send multiple sub-requests in one HTTP request. |
+| **Optimize Queries** | Ensure queries are efficient and retrieve only necessary data. | Use filters and select specific fields to minimize data retrieval. |
+| **Caching** | Store frequently accessed data to reduce repeated API calls. | Implement in-memory or distributed caching systems like Redis or Memcached. |
+| **Rate Limiting** | Control the rate at which your application makes API requests. | Use libraries or frameworks that support rate limiting to manage request frequency. |
+| **Retry Logic** | Handle cases where you hit the rate limit by retrying requests after a delay. | Implement logic to check for HTTP status code 429 and use the `Retry-After` header to determine retry time.|
+| **Parallel Processing** | Distribute API requests over multiple time periods or user accounts. | Schedule requests to avoid hitting the rate limit for a single user or distribute requests across accounts.|
+
+### Batch Request
+
+> Example of this works:
+
+```mermaid
+graph TD
+ A[Client Application] -->|Batch Request| B[Power BI REST API]
+ B -->|Response| A
+ B --> C[Sub-Request 1]
+ B --> D[Sub-Request 2]
+ C -->|Response 1| B
+ D -->|Response 2| B
+```
+
+```json
+POST https://api.powerbi.com/v1.0/myorg/$batch
+Content-Type: application/json
+
+{
+ "requests": [
+ {
+ "id": "1",
+ "method": "GET",
+ "url": "/v1.0/myorg/reports/{reportId}/users"
+ },
+ {
+ "id": "2",
+ "method": "GET",
+ "url": "/v1.0/myorg/reports/{reportId}"
+ }
+ ]
+}
+```
+
+#### Example Implementation in Python
+
+```python
+import requests
+
+def batch_request(access_token, requests):
+ url = "https://api.powerbi.com/v1.0/myorg/$batch"
+ headers = {
+ "Authorization": f"Bearer {access_token}",
+ "Content-Type": "application/json"
+ }
+ body = {
+ "requests": requests
+ }
+ response = requests.post(url, headers=headers, json=body)
+ return response.json()
+
+# Example usage
+access_token = "YOUR_ACCESS_TOKEN"
+requests = [
+ {
+ "id": "1",
+ "method": "GET",
+ "url": "/v1.0/myorg/reports/{reportId}/users"
+ },
+ {
+ "id": "2",
+ "method": "GET",
+ "url": "/v1.0/myorg/reports/{reportId}"
+ }
+]
+
+response = batch_request(access_token, requests)
+print(response)
+```
+
+
+
+
+
Total Visitors
+
+