Power Embedded Docs
English
English
  • Home
    • What is Power Embedded
    • How much does Power Embedded cost?
    • How to start the 30-day free trial
    • Dedicated capacities
    • System Architecture Document
    • System architecture document
  • Schedule a meeting
    • Presentation
    • Installation
    • Technical support
  • Frequently asked questions
    • General Questions
      • How do the Power Embedded savings work?
      • How many users does Power Embedded benefit my company from?
      • Does Microsoft allow the use of Power Embedded? Is it really allowed?
      • What do I need to use Power Embedded?
      • Is it possible to test or PoC the Power Embedded?
      • Do I need to hire the Power Tuning portal? Can't I use Microsoft's?
      • How long does it take to get Power Embedded in my company?
      • Will my users be able to access the reports using mobile devices?
      • Can I cancel Power Embedded? Is there a fine?
    • Licensing
      • Can I use Power BI Pro or Premium per User to Embed?
      • Do I still need a Power BI Pro license, even with Embedded?
      • Can't I share the reports without paying for a license?
      • Isn't accessing reports without a PRO license only possible from the F64?
    • Dedicated capacities
      • Fabric? Power BI Embedded? What are these capabilities?
      • While capacity is paused, no one can access the reports?
      • What are 24x7, 14x6 and 12x5?
      • My company already has Power BI Premium. Do I need to purchase Embedded?
      • A competitor was able to get a much lower Embedded price
      • I don't have an Azure account to contract the capacity
    • Technical questions
      • How does Power Embedded work internally?
      • Power Embedded's internal security
      • Privacy controls and LGPD
      • Differences between Embedded, “Publish to Web” and “Insert Report”
      • Report publishing process
      • System updates
      • System customizations
  • Power Embedded vs Power BI
  • Main features
    • Generative AI - Power Pilot
    • AI on WhatsApp
    • Synchronize with Entra ID
    • Application
    • Dark Mode
    • Scheduling data updates
    • Updating Data
    • Audits
    • Firewall
    • Report catalog
    • Customization of the portal and login screen
    • Sharing with external users
    • Dynamic Models
    • Capacity control
    • Report subscription
    • Integration with Google Analytics
    • Integrated Microsoft, Google and user/password authentication
    • Show report on your system
  • Calculator
  • Azure Partnership
  • News and updates
  • Privacy Policy
  • Portal de Relatórios
    • Visualization portal
      • Filtering reports using query parameters in the URL
    • Report Catalog
    • Navigating Reports
    • Mobile Application (PWA)
    • Report signature
    • Most common problems
      • This report has Row-Level Security (RLS) enabled, and the user is not associated.
      • Power BI service user password has expired
      • You have reached the usage limit of a shared capacity (Pro or PPU) for embedding reports
      • A capacidade não está ligando quando um usuário acessa um relatório
      • Capacity operation failed with error code CapacityNotActive
      • Embedding a DirectLake report is not supported
      • Não foi possível abrir o relatório pois o Power Embedded não enviou as informações do modelo
      • Relatórios utilizando Live Connection com Analysis Services não carregam
      • Sua capacidade de avaliação gratuita do Fabric expirará em X dias
      • Não é possível carregar o modelo devido ao alcance dos limites de capacidade
        • Como reiniciar e alterar a capacidade pelo Power Embedded
        • Como reiniciar e alterar a capacidade pelo Azure
      • Não foi possível carregar os dados para este visual: ClientError_TokenExpired
      • Erro ao exportar relatório - Error Code 400
      • Os visuais não certificados do AppSource ou aqueles adicionados a partir de um arquivo não estão dis
  • Portal de Administração
    • Overview
    • Portal navigation
    • First Access
    • DNS configuration
      • Cloudflare
    • Artefatos
      • Data set
        • Filtragem dinâmica
      • Capacidades
        • Permissões no Azure
        • Configurar a capacidade no Power Embedded
        • Atribuir um workspace à uma capacidade
        • Otimização de custos
        • Redimensionamento automático
        • Auditoria de capacidade
      • Workspaces
      • Gateways
      • Fontes de dados
    • Application
    • Reports
      • Como configurar o workspace
      • Importar relatório
        • Com importar relatório externo
      • Editar relatório
      • Como excluir um relatório
      • Segurança (RLS)
      • Publicar relatório no Power BI
      • Dynamic models
      • Assinatura de relatórios
      • Importação automática de relatórios criados pelo portal de visualização
    • Users
      • Create/edit user
      • Tipos de funções de usuário
      • Métodos de autenticação
      • Autenticação de 2 fatores
      • Importar arquivo CSV
      • Importar do Entra ID
      • Importar com API
      • Bloqueios e senhas
      • Convidar usuário externo para acessar o portal de administração
      • Usuário do Windows AD (Analysis Services)
      • Personalização do método de autenticação por usuário ou grupo
    • Grupos
      • Criar/editar grupo
      • Métodos de autenticação
      • Importar arquivo CSV
      • Importar do Entra ID
      • Synchronize with Entra ID
      • Importar com API
    • Folders
    • Audits
      • Reports
      • Usage Metrics
      • Report Catalog
      • Sent Emails
      • Entities (Changes)
      • Access Logs
      • Capacity
      • Permissions
      • Firewall
      • Audit Tab in Power Pilot
    • Billing
      • Configuring Invoicing
      • Payment Link and Invoice
    • Power Pilot (IA)
      • Prerequisites
      • Hiring an AI
        • Azure OpenAI
        • OpenAI
      • AI Models
      • AI Assistants
      • RLS on PowerPilot
      • Audits
      • AI on WhatsApp
      • Power Pilot Questions
    • Firewall
      • Blocked Login Attempts
      • Ignoring Firewall Rules
      • Firewall Audit page
    • Companies
      • Multiple companies or organizations
    • Warnings
    • Settings
      • Organization
        • Changing the Application Password
        • Atualização de token
        • Google Analytics
        • Configuração do sub-domínio
      • Visualization portal
        • Customizing Colors
        • Personalizar imagens
      • Login screen
        • Customize colors
        • Customize images
        • Authentication methods
      • Parameters
        • General customizations
        • Edit and Creation Mode
      • Emails
    • Migration
    • Systems of support
  • Links úteis
    • Power Embedded sites
    • Price Calculator
    • News
    • Meeting Support
    • Meet Power Tuning
    • Azure Partnership
    • Videos and tutorials
  • Documentação Técnica
    • Installation
      • Fabric Trial
      • Power BI Embedded
    • Commercial Presentation Document
    • Documento de arquitetura do sistema
    • API
      • Automações com APIs
      • Show report on your system
      • Filtragem dinâmica
      • Documentação técnica
Powered by GitBook
On this page
  • 1. How does Power Embedded work internally?
  • 2. Power Embedded's internal security
  • 3. Privacy controls and LGPD
  • 4. Differences between Embedded, “Publish to Web” and “Insert Report”
  • Embedded
  • Insert report
  • Publish on the web
  • 5. Report publishing process
  • 6. System updates
  • 7. System customizations
  1. Frequently asked questions

Technical questions

PreviousI don't have an Azure account to contract the capacityNextHow does Power Embedded work internally?

Last updated 3 months ago

1. How does Power Embedded work internally?

The internal workings of Power Embedded for displaying reports are described below:

1) Power Embedded checks if the logged in user can access the report and sends the data to apply the RLS (if any).

2) Power Embedded authenticates to the Azure API and retrieves a token for authentication

3) Power Embedded sends the necessary metadata to the Power BI APIs (Workspace, Report and Dataset IDs)

4) Power BI API loads the data that is stored in the workspaces and the report

5) Power BI API assembles the iframe element pointing to the ready-made report and returns it to the system

6) Power Embedded displays the returned iframe to the user. NO report data is read, accessed, stored or trafficked by the system's servers

The internal workings for importing Power BI reports into Power Embedded are described below:

1) Power Embedded interacts with the Power BI API's

2) API returns the metadata required for display (Workspace, Report and Dataset IDs)

3) Power Embedded stores the returned metadata

4) Administrator manages permissions, RLS, folder structure and other report attributes

5) NO personal data is stored by Power Embedded, only the users' email and name.

6) NO report data is stored or travels over the network, or through Power Embedded's servers.

2. Power Embedded's internal security

Power Embedded's internal security is extremely robust and the system uses an entire architecture based on self-managed SaaS resources in Azure, where management is done by Microsoft, automatic backups and high availability of the application and database by availability zones with automatic failover and guaranteed availability of 99.99%.

The system is subjected to various complex pentests on a regular basis, both automatic ones carried out by pentest tools and manual validations and tests carried out by security specialists from contracted companies.

The entire cloud environment is protected by Microsoft Defender for Cloud, which provides proactive and continuous protection, analysis and recommendations.

Access to Azure resources is blocked to the internet and only accessible via VPN.

Communication between the system and the browser is encrypted using SSL certificates (HTTPS).

The Power BI access key is stored in the database encrypted using the most secure algorithm on the market (RSA-OEAP) and various protection mechanisms to ensure that even in the event of improper access to the database, this key cannot be decoded, since access to the security key for decryption (which is individual per client) is stored in an Azure KeyVault where only the application has permission and connectivity to access.

The public API key is encrypted using a HASH algorithm that does not allow recovery of the generated value, just like the secret of a KeyVault.

3. Privacy controls and LGPD

The process of embedding the reports in the system does not require loading or reading any data from our clients.

All the data is stored on the Power BI servers themselves, in a dataset published in a workspace, and the system simply uses the Power BI API to render the report (also published in the workspace) within the system.

So we don't read or collect any information, we just make an HTTP call to the Power BI API, which reads the data and displays it on the screen.

The only company data that is stored are the names and emails of the users registered in the system, to manage access.

In terms of security, all Power Embedded communication is encrypted end-to-end, using SSL and HTTPS security, as well as Azure Firewall and various Azure security mechanisms.

4. Differences between Embedded, “Publish to Web” and “Insert Report”

Although the 3 options allow you to embed reports in websites, sharepoint, e-mail, teams, etc., they are quite different.

Embedded

This is a license per capacity, which allows you to view reports securely, with permissions, RLS, OLS, access audits, IP blocks, etc., through an application, without the need for the viewer to have a Power BI license, and to control all the visuals, colors, themes, pages and components of the reports using programming language.

Insert report

This is a way of sharing reports on websites, applications, sharepoint, teams, etc. securely, while maintaining all Power BI security controls, such as permissions, RLS, OLS and access audits.

Unlike Embedded, in this sharing mode, all users who will access the report need to have a Pro or PPU license (or Premium capacity).

In addition, you can NOT control the elements of the report via programming language to dynamically create/edit visuals, change themes, create/delete pages, etc...

Publish on the web

This is a way of sharing reports for free, without the person viewing them needing to have a Power BI account or license. It works very well when you need to share reports that contain public data, i.e. there is no concern about data leakage.

Unlike Embedded, in “Publish to Web” there is no security: anyone who has access to the report link will view it, without any user-level control, such as RLS or OLS, there is no need for the viewer to be registered in any application and there is no audit to know who is viewing the report. Anyone can be viewing your company's data and you won't know who.

What's more, as has already been widely publicized on the Internet, all reports published in this way can be accessed through simple Google queries, even if the link has never been published anywhere.

Even if you try to block access by using a password to open the portal, this type of mechanism is easily broken in a few seconds using the browser's Developer Tools option and the person will have unrestricted access to the data published in the report.

5. Report publishing process

The process of importing and publishing reports in Power Embedded is practically the same as in the traditional Power BI service:Comment

  • User opens Power BI Desktop and creates the report.Comment

  • User publishes the report in the desired workspace.Comment

  • Power Embedded administrator imports the report from the Power BI workspace into the system.

  • Power Embedded administrator assigns permissions via group or individual user.

  • Power Embedded administrator defines the RLS rules for the dataset (if any).

  • User accesses the report via the Power Embedded Visualization Portal.

6. System updates

Power Embedded is a very dynamic system, and our team is always attentive to our customers' requests and needs, as well as to new features made available by Microsoft.

We have a very fast development and deployment time, which allows us to carry out 2 to 5 updates of improvements and new features per week.

Whenever a feature or improvement is implemented, we automatically apply it and make it available free of charge to all our clients.

7. System customizations

If you request a change to Power Embedded and the customization cannot be applied to other customers and will be restricted to your company only, we will schedule a meeting with your team to better understand your needs and we will send you a commercial proposal to implement this customization in the system.

If your suggestion/idea can be applied to other clients, there is no charge for development.