Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
We are currently using Power BI Report Server (PBIRS) installed on a Windows Server machine, and we would like to know if it's possible to modify the access URLs to include an additional context path.
Specifically, we would like to prepend a custom context (e.g., /myapp) to the default PBIRS URLs, so that instead of accessing the Report Manager and Report Server via:
...we could use:
Is there a supported way to configure PBIRS or IIS (if applicable) to achieve this behavior?
Thank you in advance for your assistance.
Solved! Go to Solution.
Hi @jcaroe,
Thank you for reaching out to the Microsoft Fabric Community Forum.
Power BI Report Server (PBIRS) does not natively support adding a custom context path (e.g: /myapp) to the default URLs (/Reports and /ReportServer) through its configuration tools, as the virtual directories are fixed. However, you can achieve the desired URL structure by using IIS as a reverse proxy with URL rewriting on the Windows Server hosting PBIRS.
Here are the official Microsoft documentation links for URL Rewrite and Application Request Routing (ARR) for IIS, as referenced in the response:
These links provide detailed guidance on configuring URL Rewrite and ARR in IIS, including setup, rule creation, and proxy settings, which are relevant to achieving the custom URL structure for Power BI Report Server.
If this information is helpful, please “Accept as solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
Thank you.
Hi @jcaroe,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
Hi @jcaroe,
May I ask if you have resolved this issue? If so, please mark it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hello, I havent tried the solution you proposed yet but it sounds like exactly what we need!
Hi @jcaroe
May I ask if you have resolved this issue? If so, please mark it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hi @jcaroe,
Thank you for reaching out to the Microsoft Fabric Community Forum.
Power BI Report Server (PBIRS) does not natively support adding a custom context path (e.g: /myapp) to the default URLs (/Reports and /ReportServer) through its configuration tools, as the virtual directories are fixed. However, you can achieve the desired URL structure by using IIS as a reverse proxy with URL rewriting on the Windows Server hosting PBIRS.
Here are the official Microsoft documentation links for URL Rewrite and Application Request Routing (ARR) for IIS, as referenced in the response:
These links provide detailed guidance on configuring URL Rewrite and ARR in IIS, including setup, rule creation, and proxy settings, which are relevant to achieving the custom URL structure for Power BI Report Server.
If this information is helpful, please “Accept as solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
Thank you.
Hi,
I did try this solution, but the problem then occurs when I access any dashboard via the web portal. I managed to rewrite Reports and ReportServer urls to omr/Reports and omr/ReportServer.
Basically when you click on any item, an HTTP call is automatically fired to the /powerbi url, which is not rewritable (this is handled by the Power BI Report Server Back-End application).
Since any call is to be sanitized by a proxy which only accepts calls under a specific context (for example, omr) this is unacceptable since it will be blocked and all calls will end up in a 404 error.
Is there really no other way?