PowerBi Data Gateway Error when registering email

[TJUGGS]

Installed PowerBI datagateway and when I go to register the gateway I get this error in the log 

"EnterpriseGatewayConfigurator.exe Error: 0 : Error authenticating user: An error occurred while sending the request..
EnterpriseGatewayConfigurator.exe Error: 0 : Exception details: System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure."

and this error in the user interface "failed to sign in. Please verify your credentials and try again"

 Ive tried a lot of things I have read and nothing has worked thus far. Any ideas or help?  Thanks 

[v-tsaipranay]

Hi @TJUGGS ,

We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?

If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. please feel free to reach out for any further assitance.

Thank you.

[v-tsaipranay]

Hi @TJUGGS ,

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.

Thank you.

[v-tsaipranay]

Hi @TJUGGS 

As you've already tried all possible troubleshooting steps and the issue is still not resolved, I suggest raising a support ticket with Microsoft using the link below. Their team can look into the issue in detail and help you fix it.

How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Thank you.

[TJUGGS]

I get this error when I do the revoke

Invoke-WebRequest : The underlying connection was closed: Could not establish trust relationship for the SSL/TLS
secure channel.
At line:1 char:1
+ Invoke-WebRequest https://login.microsoftonline.com
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc
eption
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

[v-tsaipranay]

Hi @TJUGGS ,

Thank you for reaching out to the Microsoft Fabric Community Forum. And also for confirming that you're using a valid Microsoft account and have successfully accessed other gateways.

As @Greg_Deckler , this issue is likely related to a trust-related SSL/TLS configuration on your current machine. This can often be due to missing root certificates, SSL interception by security software, or disabled TLS 1.2 protocols.

Please make sure to follow the recommended steps, including:

• Importing trusted root certificates using PowerShell
• Checking the certificate at https://login.microsoftonline.com
• Verifying that your system time and TLS 1.2 are properly set up

If you've done these steps and are still having problems, you can provide:

• A screenshot of the certificate from the login URL
• The output from Invoke-WebRequest https://login.microsoftonline.com
• Information about whether this machine has stricter security policies compared to other working devices.

Hope this helps. Please reach out for further assistance.

Thank you.

[TJUGGS]

I get this error when I do the revoke

Invoke-WebRequest : The underlying connection was closed: Could not establish trust relationship for the SSL/TLS
secure channel.
At line:1 char:1
+ Invoke-WebRequest https://login.microsoftonline.com
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc
eption
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

[TJUGGS]

Thankyou for your response. I have followed the steps listed below and it still fails. 

Here is the response from the invoke. 

"Invoke-WebRequest : The underlying connection was closed: Could not establish trust relationship for the SSL/TLS
secure channel.
At line:1 char:1
+ Invoke-WebRequest https://login.microsoftonline.com
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc
eption
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand"

[TJUGGS]

@Greg_Deckler  Yes I am using a microsoft account. I have greated other gateways on other servers same environment . Just this one server is giving me issues. 

[Greg_Deckler]

 Is it a domain controller by chance? And here are some ChatGPT suggestions 

Possible Causes & Fixes

✅ 1. Missing or Outdated Root Certificates

Cause: The local Windows machine doesn’t have the correct root certificates to validate Microsoft's certificate chain.

Fix:

• Run Windows Update and ensure "Trusted Root Certificates" updates are installed.

• Alternatively, use this command:

  powershell

  CopyEdit

  certutil -generateSSTFromWU roots.sst

  Then double-click roots.sst to import it into your Trusted Root Certification Authorities store.

  ---

  ✅ 2. Corporate Network Inspection/Proxy (SSL Interception)

  Cause: A firewall, proxy, or antivirus (e.g., Zscaler, Palo Alto, Sophos, etc.) is performing HTTPS inspection and replacing Microsoft’s certificate with its own (untrusted by .NET runtime).

  Fix:

  • Check with your network/security team: Are they intercepting SSL traffic?

  • If yes, make sure the interception certificate is:

    • Installed in Local Machine > Trusted Root Certification Authorities

    • Available to the service account running the Gateway

    • Test by visiting https://login.microsoftonline.com in Internet Explorer or Edge on that machine and viewing the certi...

      ---

      ✅ 3. Incorrect System Time/Date

      Cause: SSL/TLS validation fails if the system clock is skewed.

      Fix:

      • Ensure your server has the correct time zone, time, and is syncing with a time server (NTP).

      • Run w32tm /resync if needed.

        ---

        ✅ 4. TLS Protocols Disabled or Misconfigured

        Cause: The required TLS 1.2 protocol might be disabled via registry or group policy.

        Fix:

        • Ensure TLS 1.2 is enabled. Set these registry keys:

          reg

          CopyEdit

          [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client] "Enabled"=dword:00000001 "DisabledByDefault"=dword:00000000

          • Restart the machine afterward.

            ---

            ✅ 5. Gateway Version Too Old

            Cause: You're using an outdated version of the Power BI Data Gateway.

            Fix:

            • Download and install the latest version from:
              https://powerbi.microsoft.com/en-us/gateway/

              ---

              🧪 Testing Steps

              Try this on the same machine:

              1. Open a browser and visit: https://login.microsoftonline.com

              2. View the certificate and check if it's:

                 • Valid

                 • Issued by a trusted authority

                 • Try running this PowerShell command:

                   powershell

                   CopyEdit

                   Invoke-WebRequest https://login.microsoftonline.com

                   If that also fails, it's confirmation of a trust or network-level SSL issue.

                   ---

                   ✅ Final Tip

                   If you're in a locked-down enterprise network, consider installing the gateway on a less restricted test server first, or try connecting via mobile hotspot (to bypass inspection) to confirm it’s a network issue.

@TJUGGS

[TJUGGS]

Yes I am using a microsoft account when registering it. I have created other gatesways on other systems. Just this one instance is having an issue. 

[Greg_Deckler]

@TJUGGS Are you using a Microsoft account for this when you are trying to authenticate? As in a Microsoft account that can logon to your Power BI tenant? Is the Power BI tenant already created? Otherwise, it could be a temporary service thing. Is gateway installation restricted at all within your tenant?