We are constantly working hard to create a better experience for you and our VAP users.
Your satisfaction as a customer is key to moving VAP forward and essential for us. We know VAP is a business critical system and an enabler for growing your business.
Unfortunately some times there are unforeseen issues. Those we work hard to fix as soon as possible.
Updated 13. May 2025
This post is to inform you about known issues, bugs, defects, side effects and failures in VAP:
-
Did you receive an error when uploading a paginated report (RDL) file?
Then, your service was not set up using Service Principal, a requirement for paginated reports. Please get in touch with the vap@dnv.com team. We can offer some consultancy hours to help you and agree upon a plan and the responsibilities to make it work for your service.
VAP release in November 2024 informed you that we support paginated reports. Paginated reports are ideal for presenting content with tightly controlled rendering requirements, such as certificates, audit findings, and test results. They can display all the data in a table and are print-friendly, even if they span multiple pages.
Services set up before 10 October 2024 are using another method. Microsoft Power BI does not provide automated methods, but the VAP team has done a migration experiment and found and tested ways to help you upgrade your service. -
Row Level Security (RLS) is not currently supported for Paginated report (RDL) file
If you have an RDL report with RLS, you will get this error: ‘Get Power BI file failed’ when running the report from Home.
Workaround: Upload a paginated report without RLS -
Your request is blocked in the firewall security scan. Why do I get it, and what do I do to solve it?
Why: The VAP network security policy has been upgraded to include Azure WAF (Web Application Firewall). If VAP’s firewall security policy detects sensitive information in a request, the request will be blocked, an error message will be presented, or the behaviour will not be as expected.
If you meet the case, please evaluate if there are some special characters in your input strings, such as — - ,', etc.
The Colons and Commentators is probably treated as sql injection risks and blocked by WAF. Please remove special characters from your input and try again.
If the error is not caused by the special input string from your user interface, then please create a Veracity support case and provide the support code presented it the error message. It looks like this: 20241112T072836Z-158f2r2r2jjf8*************00f70000000003bwu
Workaround and how to fix: Please clear the Browser cookie and access again -
My service is set up in US. Why do I see an error where NORTH-EUROPE is mentioned?
If your service has some issue with a Power BI report you may see a error message from Microsoft where https://WABI-NORTH-EUROPE-E-Primary is referd.
The URL https://WABI-NORTH-EUROPE-E-Primary-redirect.analysis.windows.net/ is part of Power BI’s internal routing mechanism. When you use Power BI Embedded, the service may interact with different regional endpoints for various reasons, such as load balancing, optimizing performance, or meeting data residency requirements1.
Even if your Power BI capacity is in the United States, it’s not unusual for requests to be routed through different regions. This helps ensure efficient handling of requests and can be part of the service’s design to maintain high availability and reliability1. -
I have enabled self-subscribe for a entity, but user can’t access it, why?
If your service has been set up with ‘Awaiting approval,’ all users who request access must go through the approval process.
Workaround: We advice not enable self-subscribe when ‘Awaiting approval’ is set for your service. Add the user manually into your service or use the Public Viewer option.
As design, will not be fixed -
Azure Maps are not supported in VAP. Since it is not supported in Power BI-embedded, the version used in VAP
This means that it works in Desktop but not in VAP until Microsoft fixes it. Unfortunately, we can’t do anything about it from our side.
However, there is something you can do to help.
You can vote for Microsoft to build Azure Maps support in Embedded Power BI by following this link: https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=634c89ed-c6f8-ed11-a81c-00224853a463
Please sign in with your work account and ask your colleagues to vote too. The more votes we get, the more likely they are to listen to us.
You can also spread the word through this DNV post: Viva Engage.
More details and documentation can be found here: Get started with Azure Maps Power BI visual - Microsoft Azure Maps | Microsoft Learn
Here’s the direct link to limitations, where we soon hope The Embedded line will be moved from No to Yes available
Get started with Azure Maps Power BI visual - Microsoft Azure Maps | Microsoft Learn
Workaround: Use another map type that is supported in embedded Power BI