diff --git a/Workloads-Specific/PowerBi/ConfigureCloudConnectionsGateways.md b/Workloads-Specific/PowerBi/ConfigureCloudConnectionsGateways.md
new file mode 100644
index 0000000..7833668
--- /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: 2025-04-16
+
+------------------------------------------
+
+
+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
+
+
+List of References (Click to expand)
+
+- [Microsoft Fabric features by SKU](https://learn.microsoft.com/en-us/fabric/enterprise/fabric-features)
+- [Getting Started with Microsoft Fabric](https://www.microsoft.com/en-us/microsoft-fabric/getting-started)
+- [Roles in workspaces in Microsoft Fabric](https://learn.microsoft.com/en-us/fabric/get-started/roles-workspaces)
+- [Permission model - Microsoft Fabric](https://learn.microsoft.com/en-us/fabric/security/permission-model)
+- [Query the SQL analytics endpoint of your SQL database in Fabric](https://learn.microsoft.com/en-us/fabric/database/sql/query-sql-analytics-endpoint)
+- [Use the SQL analytics endpoint to query data](https://learn.microsoft.com/en-us/fabric/database/sql/tutorial-use-analytics-endpoint)
+- [Apache Spark Runtimes in Fabric](https://learn.microsoft.com/en-us/fabric/data-engineering/runtime)
+- [Model data in the default Power BI semantic model in Microsoft Fabric](https://learn.microsoft.com/en-us/fabric/data-warehouse/default-power-bi-semantic-model)
+- [Create reports on data warehousing in Microsoft Fabric](https://learn.microsoft.com/en-us/fabric/data-warehouse/create-reports)
+- [What is the SQL analytics endpoint for a lakehouse?](https://learn.microsoft.com/en-us/fabric/data-engineering/lakehouse-sql-analytics-endpoint)
+- [What is a lakehouse in Microsoft Fabric?](https://learn.microsoft.com/en-us/fabric/data-engineering/lakehouse-overview)
+- [Default Power BI semantic models in Microsoft Fabric](https://learn.microsoft.com/en-us/fabric/data-warehouse/semantic-models)
+- [How lakehouse sharing works](https://learn.microsoft.com/en-us/fabric/data-engineering/lakehouse-sharing)
+- [Tutorial: Stream and consume events to and from Real-Time Intelligence by using an Apache Kafka endpoint in an eventstream](https://learn.microsoft.com/en-us/fabric/real-time-intelligence/event-streams/stream-consume-events-use-kafka-endpoint)
+
+
+
+
+Table of Content (Click to expand)
+
+- [Overview](#overview)
+- [Viewer Role in Fabric Workspaces](#viewer-role-in-fabric-workspaces)
+- [Granting Read and ReadData Access to the Semantic Model](#granting-read-and-readdata-access-to-the-semantic-model)
+- [SQL Analytics Endpoint in Fabric](#sql-analytics-endpoint-in-fabric)
+- [Granting App Audience in Fabric](#granting-app-audience-in-fabric)
+
+
+
+## Overview
+
+ **Create a Fabric Capacity**: Follow the prompts to configure and create the capacity.
+
+
+
+
+## Viewer Role in Fabric Workspaces
+
+> `Fabric Workspaces` in Microsoft Fabric are `collaborative environments where users can manage, analyze, and visualize data`. These workspaces integrate various data services and tools, providing a `unified platform for data professional`s to work together
+
+
+| **Capability** | **Description** |
+|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **View All Content** | - Users can view dashboards, reports, workbooks, and other content within the workspace.
- This includes content created by other users, enabling collaboration and shared insights. |
+| **Interact with Content** | - Users can interact with the content, such as filtering and highlighting data.
- They can drill down into reports and dashboards to explore data in more detail.
- However, they cannot modify the content, ensuring that the integrity of the reports and dashboards is maintained. |
+| **Read Data** | - Users can read data from various sources within the workspace.
- This includes accessing data from SQL analytics endpoints and Lakehouse data.
- They can use this data to gain insights and make data-driven decisions without altering the underlying data sources. |
+| **View Notebooks and Lakehouses** | - Users can view notebooks, lakehouses, and everything within those lakehouses.
- This includes accessing and reading data stored in lakehouses, enabling comprehensive data analysis and insights. |
+| **View Other Objects and Artifacts** | - Users can view additional objects and artifacts such as data pipelines, Spark job definitions, ML models, experiments, and eventstreams.
- This ensures users have a comprehensive view of all relevant data and processes within the workspace. |
+
+
+
+
+
+> For information about other roles, please visit [Roles in workspaces in Microsoft Fabric](https://learn.microsoft.com/en-us/fabric/get-started/roles-workspaces). For details on the Fabric security permissions model, refer to [Permission model - Microsoft Fabric](https://learn.microsoft.com/en-us/fabric/security/permission-model).
+
+| **Role** | **Description** |
+|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **Admin** | - Full control over the workspace, including managing permissions and settings.
- Can create, edit, and delete content within the workspace. |
+| **Member** | - Can view and edit content within the workspace.
- Can create new reports, dashboards, and datasets. |
+| **Contributor**| - Similar to Member, but cannot delete content created by others.
- Can contribute to existing reports and dashboards. |
+
+
+
+## Granting Read and ReadData Access to the Semantic Model
+
+> Semantic Model: Provides a logical description of an analytical domain using business-friendly terminology and metrics.
+
+Capabilities:
+ - Data Representation: Organizes data into a star schema with facts and dimensions.
+ - Business Logic: Inherits business logic from parent lakehouses or warehouses.
+ - Visualization: Supports creating Power BI reports and dashboards for visual analysis.
+
+
+
+
+| **Permission** | **Purpose**| **Capabilities**| **Restrictions**|
+|----------------|------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|
+| **Modify Dataset** | Allows recipients to modify the dataset. | - Edit and update the dataset
- Make changes to the data structure and content
- Manage dataset settings (e.g., refresh schedules, data source credentials) | - Cannot share the dataset unless granted additional sharing permissions |
+| **Share Semantic Model** | Allows recipients to share the semantic model with others. | - Grant access to the semantic model to other users or groups
- Collaborate with others using the shared model | - Cannot modify the semantic model unless granted additional modification permissions |
+| **Build Content** | Allows recipients to build content with the data associated with the semantic model. | - Create new reports, dashboards, and datasets using the semantic model data
- Perform data analysis and generate insights
- Integrate data with other tools and platforms | - Cannot modify the semantic model or dataset unless granted additional modification permissions |
+| **Send Email Notification** | Sends an email notification to the recipient about the granted access. | - Notify recipients via email about their new permissions
- Ensure recipients are aware of their access rights | - Does not grant any additional data access or modification capabilities |
+
+
+
+
+## SQL Analytics Endpoint in Fabric
+
+> Lakehouse: A data architecture platform for storing, managing, and analyzing both structured and unstructured data.
+Capabilities:
+ - Data Storage: Combines the capabilities of data lakes and data warehouses.
+ - SQL Analytics Endpoint: Provides a SQL-based experience for querying data.
+ - Automatic Table Discovery: Automatically registers and validates tables.
+
+> SQL Analytics Endpoint: Allows users to query data in the lakehouse using SQL.
+Capabilities:
+ - T-SQL Queries: Supports T-SQL language for querying Delta tables.
+ - Read-Only Mode: Operates in read-only mode, allowing data analysis without modifying the data.
+ - Security: Implements SQL security for access control.
+
+> Apache Endpoint: Used for real-time data streaming and processing.
+Capabilities:
+ - Event Streaming: Streams events to and from Real-Time Intelligence using Apache Kafka.
+ - Integration: Integrates with event streams to process and route real-time events.
+ - Scalability: Supports building scalable, real-time data systems.
+
+
+
+
+| **Permission** | **Purpose** | **Capabilities** | **Restrictions** |
+|----------------|------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|
+| **Read All SQL Endpoint Data** | Allows users to access data without SQL policy restrictions, enabling them to perform detailed queries and analysis. | - Access and read data from SQL analytics endpoints
- Perform detailed queries and analysis | - Cannot modify the data
- Cannot manage permissions or grant access to other users |
+| **Read All Apache Spark** | Grants access to all data using Apache Spark, providing a broader scope of data access for advanced analytics. | - Access all data using Apache Spark
- Perform advanced analytics and data processing | - Cannot modify the data
- Cannot manage permissions or grant access to other users |
+| **Build Reports on the Default Semantic Model** | Allows users to create reports using the default Power BI semantic model. | - Create new reports and dashboards using the default semantic model
- Perform data analysis and generate insights
- Integrate data with other tools and platforms | - Cannot modify the semantic model or dataset unless granted additional modification permissions |
+
+
+
+## Granting App Audience in Fabric
+
+> When you create and publish an app in Power BI within Fabric, you can define multiple audiences for the app. This allows you to control who can view specific content within the app.
+
+Granting app audience permissions enables the assigned identity to:
+
+- View the app content, including dashboards and reports.
+- Interact with the app, such as filtering and highlighting data.
+- Access different content based on the audience group they belong to.
+
+Click here for [Demostration: How to Configure Workspace App](./ConfigureWorkspaceApp.md)
+
+
+
Total Visitors
+
+
+
+ 
+
+ > Select the `large semantic model only if your model exceeds 10 GB`. If not, use the small model. The large setup is for models up to 10 GB.
+
+ 
+
+3. Create a lakehouse to store your data:
+
+ 
+
+4. Get your data, in this case a CSV file will be used
+
+ 
+
+5. After uploading the information, create the tables or upload the information to your existing tables:
+
+ 
+
+6. Create a semantic model based on your tables:
+
+ 
+
+7. Now you are able to create a report based on the semantic model created, you can ask copilot to create a draft report with the `Auto-create report` option.
+
+> [!NOTE]
+> Make sure to activate the setting under `Admin Portal -> Tenant Settings -> Copilot/Data -> Enabled`. [Click here for more details](https://github.com/brown9804/MicrosoftCloudEssentialsHub/blob/main/0_Azure/2_AzureAnalytics/0_Fabric/demos/6_PBiCopilot.md#tenant-configuration)
+
+ 
+
+ - You will see something like this:
+
+ 
+
+ 
+
+ - You can leverage copilot to modify your report:
+
+ 
+
+ - Once you are ready, save your report:
+
+ 
+
+ - At this point you will have your `lakehouse`, with your `SQL analytics endpoint`, the `semantic model` and `the report`.
+
+ 
+
+8. A paginated report, can also be created:
+
+ 
+
+ 
+
+9. Create an App, and assign the required audience:
+
+ 
+
+ 
+
+ 
+
+ 
+
+> [!IMPORTANT]
+> If you encounter these errors, it's necessary to grant the appropriate `(semantic model, sql analytics endpoint, and the app` permissions for access.
+
+ 
+
+ 
+
+ - Let's say you want only `viewer` permissions:
+
+ 1. Need to give access to the lakehouse/sql analytics endpoint:
+
+ 
+
+ > `Read All SQL Endpoint Data` permission allows users to access and read data from SQL endpoints within the Fabric environment. This permission is typically required for users who need to:
+ > - Query Data: Execute SQL `queries against the data stored in the Fabric environment`.
+ > - Access Reports: `View and interact with reports and dashboards that rely on SQL data sources`.
+ > - Data Analysis: `Perform data analysis and generate insights` using SQL-based data.
+
+
+
+ 
+
+ 2. Make sure the person already have access to the semantic model:
+
+ 
+
+> - Granting `Read, ReadData` access to the `semantic model, sql analytics endpoint`
+> - Grating `App audience` will enable the assigned identity to view it.
+
+ 
+
+
+
Total Visitors
+
+
+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](#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)
+
+
+
+
+## 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
+
+
+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
+
+