Power BI Error

[ericjo]

I'm working within a VPN that doesn't allow internet access. I've requested and received approval from the security team for internet access for the required IP address.

Until recently, it was working fine, but this error has been occurring for the past few months. The security team says they haven't made any security changes, but I don't know why this is happening, so I'm having trouble working on it. Thank you for your interest and assistance.

<Error Occurred>
1. Unable to access the Power BI website.
2. Unable to log in to my MS account in Power BI Desktop.
-> Error: An error occurred while connecting to the service. (The service connection was terminated prematurely). If the problem persists, please contact your IT administrator.

3. The provider 'microsoft.powerbi.oledb' is not registered. The following system error occurred: Class not registered.

[v-hjannapu]

Hi @ericjo 
Thank you  for reaching out to the Microsoft fabric community forum.

I would also take a moment to thank @Ritaf1983 , @rohit1991  for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

It looks like there are two separate problems here  one is with your VPN/network and the other is with a missing Power BI component. Power BI needs to connect to certain Microsoft sites like .powerbi.com, .analysis.windows.net, .microsoftonline.com, and login.microsoftonline.com through port 443. Even if your IT team had approved IPs earlier, Microsoft updates these regularly, so they may need to check the latest list and allow them again. Also, make sure TLS 1.2 is enabled and no SSL inspection is blocking the connection.

For the “microsoft.powerbi.oledb not registered” error, it usually means a required driver is missing or damaged. The simplest fix is to install the latest Power BI Desktop from the Microsoft Store or the official site. If it’s already installed, you can try the Repair option from Apps & Features, and if that does not help, uninstall, restart your PC, and reinstall. After installing, run Power BI once as administrator so that all files get registered. Please also check if WebView2 Edge runtime is installed, as it’s needed for sign-in. If Power BI works outside the VPN, then it confirms the VPN rules need to be updated.

Gothrough with the below document hope it may resolve your Issue
https://learn.microsoft.com/en-us/fabric/security/power-bi-allow-list-urls
https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-troubleshooting-sign-in
https://community.fabric.microsoft.com/t5/Desktop/Microsoft-PowerBI-OleDb-is-not-registered/m-p/8934...

Hope this helps if you have any queries we are  happy to assist you further.
Best Regards,
Harshitha.

[v-hjannapu]

Hi @ericjo,
I hope the information provided above assists you in resolving the issue. If you have any additional questions or concerns, please do not hesitate to contact us. We are here to support you and will be happy to help with any further assistance you may need.

Regards,
Harshitha.

[v-hjannapu]

Hi @ericjo,
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We are always here to support you.


Regards,
Harshitha.

[rohit1991]

Hi @ericjo 

From the errors, there are two separate issues here  both likely related to network restrictions and local components:

1. Unable to access Power BI service / log in via VPN

• Power BI Desktop and the service need access to certain endpoints. If your VPN blocks or restricts these, you’ll get “service connection terminated prematurely.”
• Even if your security team previously allowed an IP range, Microsoft endpoints and IPs do change over time. They may need to review and re-approve based on the latest list.
• Check that TLS inspection or SSL packet inspection is not breaking authentication.

2. OLEDB provider not registered

• This means the local Microsoft Power BI OLEDB driver is missing or corrupted.
• To fix:
  1. Install the latest version of Power BI Desktop from the Microsoft Store or official site.
  2. If already installed, run Repair from Apps & Features >> Power BI Desktop >> Modify >> Repair.
  3. If the issue persists, uninstall Power BI Desktop completely, reboot, and reinstall.

3. Combined steps to try

1. Test Power BI Desktop outside of the VPN  if it works, it’s a network rule issue.
2. Inside VPN, have IT check:
   • Latest Power BI endpoints are whitelisted (including login endpoints).
   • No outbound SSL inspection blocking auth.
3. Repair/reinstall Power BI Desktop to restore missing OLEDB provider.

[Ritaf1983 · Accepted solution]

Hi @ericjo 

Since this seems to involve a combination of connection, authentication, and missing component issues, here are steps you can take together with your IT team for troubleshooting:

1. VPN and Network Configuration
   Even with security team approval, Power BI Desktop requires access to several domains over port 443 (HTTPS):
   *.powerbi.com, *.analysis.windows.net, *.microsoftonline.com, *.msftauth.net, login.microsoftonline.com
   Make sure these are allowed both in the firewall and DNS resolution. It's not enough to approve a single IP. Tools like Fiddler or Power BI Diagnostics can help identify blocked endpoints.

2. TLS and System Requirements
   Make sure TLS 1.2 is enabled, Windows is fully updated, and you're using a supported version of Power BI Desktop. Outdated environments may block secure communication with Microsoft services.

3. OLEDB Provider Not Registered
   The error 'microsoft.powerbi.oledb' is not registered usually means the provider is missing or failed to register. Try:

• Reinstalling Power BI Desktop (preferably from the Microsoft Store)

• Running it once as administrator to allow component registration

• If needed, manually register the DLL (if you locate it) using regsvr32.

4. Authentication Issues – WebView2
   Modern authentication in Power BI Desktop relies on WebView2 (Edge runtime). Ensure it's installed.
   If not, install it from the Microsoft site. You can also try launching Power BI with --disable-webview2 to test legacy mode.

5. If VPN Restrictions Remain
   If no configuration works under VPN, consider authenticating and publishing from a non-VPN machine, then transferring the PBIX back into the VPN environment. Alternatively, use a Power BI Gateway from a machine with full access.

If none of the above resolves the issue, I recommend opening a support ticket with Microsoft, especially if you're working in a controlled or enterprise environment.

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickl