A customer wants to check their latest sales figures, but the dashboard link asks them to sign in with a Microsoft account. They don’t have one, and creating an account just to view a report adds another step. The reporting team now has to manage access before the customer can see their data.
Power BI offers another way to deliver dashboards without requiring customers to use Microsoft accounts. Businesses can embed reports inside their own applications or provide access through secure client portals. Customers sign in with the business-provided credentials and access the latest reporting data.
This article explains how to give clients secure access to live Power BI dashboards without Microsoft accounts, including setup, data security, and ongoing access management.
1. Choose How Clients Will Access Power BI Dashboards
Power BI supports several ways to share dashboards, but not all of them work without Microsoft accounts. For private client reporting, the most practical options use Power BI Embedded and a customer-facing application.
Power BI Embedded in an Existing Application
Power BI Embedded lets businesses display interactive dashboards on their own websites or in their applications. Under the app-owns-data model, customers sign in to the business’s application, not Power BI. The application then uses its own Microsoft identity to request access to the assigned reports.
For example, a SaaS company can add a reporting page to its customer dashboard. Customers continue using their existing login details and can interact with Power BI reports without opening the Power BI service.
Ready-Made Power BI Client Portals
Not every business has developers available to build and maintain an embedded reporting application. A Power BI client portal provides a ready-made interface for sharing dashboards with customers. These platforms manage authentication, report permissions, and branding while using Power BI Embedded to deliver reports.
Some portals also support different login methods, including email-based accounts and third-party identity providers. Businesses can assign reports to customer groups and manage access through an administrative interface instead of developing these features themselves.
Why Guest Access and Public Links Are Different
Microsoft Entra B2B guest access allows external users to open reports through Microsoft’s authentication system. However, this still involves Microsoft-managed sign-in and doesn’t provide the same experience as a customer portal. It may suit businesses working with a small number of partners who already use Microsoft services.
Power BI’s Publish to web feature removes authentication entirely, but it makes the report publicly accessible. Anyone on the internet can potentially view the published content. That makes it unsuitable for private customer dashboards containing business information.
2. Set Up Power BI External Report Sharing Without Microsoft Accounts
Setting up Power BI external report sharing through an embedded application allows customers to use a separate login system. Power BI still renders the report, while the application manages customer identity and access.
The setup involves the following steps:
- Prepare the Power BI reports: Publish the customer-facing reports and their semantic models to a suitable Power BI workspace.
- Choose embedded capacity: Use supported Power BI Embedded or Fabric capacity for production customer reporting.
- Register an application identity: Configure a Microsoft Entra service principal with access to the required Power BI content.
- Set up customer authentication: Connect the application to its existing login system or another supported identity provider.
- Assign customer reports: Map each customer account to the reports and dashboards they can access.
- Generate embed tokens: The application’s backend creates tokens for authorized reports using the customer’s assigned permissions.
- Display the dashboards: The application loads the permitted Power BI content inside the customer-facing interface.
Once configured, customers can open dashboards through the business’s website or application. Under the app-owns-data model, they don’t need individual Power BI viewer licenses, but the business still pays for the required reporting capacity.
3. Keep Each Client’s Dashboard Data Separate
Giving customers access to the same Power BI report can create security problems when the underlying model contains data from several organizations. Businesses need a way to restrict the records each customer can retrieve, even when they use the same dashboard.
Use Customer IDs in the Data Model
Consider a software company serving 40 customers through one reporting application. Its database stores usage records from every organization, with each record linked to a unique customer ID. The Power BI semantic model can use that ID to identify which records belong to each customer.
This approach lets the company maintain shared reports instead of creating a new dashboard for every customer. It also supports consistent calculations across the customer base.
Apply Row-Level Security
Power BI row-level security (RLS) restricts the records users can retrieve from a semantic model. Businesses can configure dynamic RLS rules that use the supplied customer identity to filter data. A customer viewing monthly sales would then receive results based on their assigned records.
For embedded reporting, the application must pass the correct effective identity and RLS roles when generating an embed token. A dashboard filter alone cannot provide this protection because users may be able to change or remove filters.
Separate Workspaces for Customers With Different Requirements
Some businesses prefer separate Power BI workspaces for individual customers. This approach makes sense when customers use different data sources or need stronger separation between their reporting environments. Each workspace can contain the reports and semantic models assigned to that organization.
For instance, a financial reporting provider may maintain separate workspaces for customers with strict data handling requirements. The application then connects each customer to the appropriate workspace instead of relying entirely on shared models.
4. Keep Customer Dashboards Updated With Fresh Data
A live dashboard should reflect recent business activity, but Power BI doesn’t update every report in real time. The available data depends on how the report connects to its source and how often the semantic model refreshes. A report using Import mode displays data from its latest completed refresh. Customers can interact with the report at any time, but that interaction doesn’t automatically retrieve new records from the original system.
DirectQuery reports can request data from the source when users interact with visuals. Supported DirectQuery reports can also use automatic page refresh to check for changes at configured intervals. However, frequent queries can add load to the source database. Available refresh settings also depend on the Power BI capacity and the data connection used.
For customer-facing reporting, the refresh schedule should match how often customers need new information. A logistics customer tracking deliveries may need frequent updates, while a consulting client reviewing monthly revenue may only need daily refreshes. Businesses can display the last refresh time inside dashboards so customers know how current the figures are. Failed refreshes should also trigger alerts before customers spend time reviewing outdated results.
Suggested Read: Logistics Routing Software
5. Make Dashboards Easy for Clients to Use
Removing Microsoft account requirements solves the login problem, but customers still need a reporting interface they can understand. A client portal should organize dashboards around the customer’s work rather than the structure of internal Power BI workspaces.
Give Customers a Simple Login Experience
A customer may already use a company’s website to manage orders or review invoices. Adding Power BI dashboards to that same application allows customers to use their existing accounts. They can move from their normal work to reporting without signing in to another service.
For standalone reporting portals, businesses can use email-based authentication or an identity provider that customers already recognize. Customer permissions stay tied to their accounts, letting administrators remove access when needed.
Organize Reports Around Customer Needs
An agency may provide each customer with separate dashboards for advertising campaigns and sales results. Showing every report in one long list makes it harder for customers to find what matters. A simple menu with clear report names gives users a more direct route to their data.
The dashboard itself should also match the audience. An executive may prefer a short performance summary, while an operations manager may need detailed tables and filters. Separate report pages can serve these different needs without creating a new reporting application.
Support Different Devices and Report Formats
Not every customer opens a dashboard from a desktop computer. Some check results on a phone between meetings, while others review reports on larger office screens. Power BI supports mobile layouts that report authors can create for smaller displays.
Customers may also need to export figures for presentations or internal reviews. Depending on the reporting setup, businesses can provide PDF exports or scheduled report delivery. Interactive dashboards remain the main source of current data, while exported files preserve a snapshot from a particular point in time.
6. Check Security Before Giving Clients Access
External reporting introduces risks that internal Power BI users may never encounter. A customer-facing application must verify user identity and apply the correct data permissions before loading any report.
The following checks help identify problems before customers receive access:
- Test different customer accounts: Confirm that each customer sees only their assigned dashboards and records.
- Check embed token permissions: Verify that tokens include the correct report access and RLS identity.
- Protect application credentials: Store service principal secrets and other sensitive credentials outside client-side code.
- Review export permissions: Confirm that customers cannot download data they aren’t authorized to access.
- Disable public report links: Avoid Publish to web for dashboards containing private customer information.
- Test removed accounts: Confirm that former customers lose access after their accounts are disabled.
- Record customer activity: Track report access and permission changes through available application logs.
A report administrator may have access to every customer dataset, so testing with an administrator account alone isn’t sufficient. Customer-level testing can reveal permission problems that development can hide.
7. Manage Different Client Dashboards as Your Business Grows
Customer reporting becomes harder to manage when businesses add more clients with different reporting needs. An agency may deliver different dashboards for marketing, risk management, or customer support. Some clients may need only one monthly report, while others expect access to several interactive dashboards. Without a clear reporting structure, adding new customers can lead to repeated manual work.
A reporting platform should allow administrators to assign existing dashboards to new customers without rebuilding them. Shared semantic models can reduce maintenance when customers use similar calculations, while separate models may be needed for specialized reporting. Businesses also need to plan reporting capacity as more customers access dashboards at the same time. Power BI Embedded uses capacity-based pricing, so concurrent users and report complexity affect the resources required.
Client onboarding and account removal also become regular administrative tasks. When a new customer joins, they need the right reports and data permissions before they can access them. When a contract ends, the reporting team must remove access without affecting other customers. A central customer management system makes these changes easier as the number of reports grows.
Conclusion
Clients can access live Power BI dashboards without Microsoft accounts through Power BI Embedded and secure customer-facing applications. The business handles authentication, while Power BI provides the interactive reporting experience.
The setup still requires suitable capacity and clear customer data permissions. Refresh schedules also determine how current the figures will be when customers open their dashboards.
For businesses serving multiple clients, a well-managed reporting portal can reduce account administration and give customers a consistent way to access their reports.
