Azure AD Empty GUID Syndrome

[Tomcat3]

Attempting to sign in from Power BI Service to Azure SQL DB. Same tenant, same credentials, authentication to Dataflows is working fine.

I get an error related to "..tenant identifier..." which is clearly not valid (see screen shot)

My web searches show a number of similar reports, but most are a few years old and refer to Gateway errors.

Looking for a few search keywords of clues to share with our MSP.

[Anonymous · Accepted solution]

Hi @Tomcat3 ,

What is the Authentication Type used by this user account, SQL authentication or Azure Active Directory Authentication ? Does the Authentication type are same in both Power BI Desktop and Power BI Service? Does other kind of account has the same issue?

Please refer to the following document to see if it helps you.

To troubleshoot this issue, identify the error code, and then contact technical support. To identify the error code, follow these steps:

1. View the source code of the "login.microsoftonline.com" webpage that shows the error message.

   For example, in Internet Explorer, press the ALT key to display the menu bar (if it isn't already displayed), and then click Source on the View menu.

2. Search the source code for the HR=string, and then note the numeric code that follows the HR=string.

More details : "Sorry, but we're having trouble signing you in" when a user signs in to Office 365, Azure, or Intun... 

I have also found a helpful blog, please refer to it to see if it helps you.

Connecting to Azure SQL Database: Requested tenant identifier ‘00000000-0000-0000-0000-000000000000’... 

• Simply enough the Active Directory Admin wasn’t set for the Azure SQL Server.

Best Regards

Community Support Team _ Polly

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Tomcat3]

Adding context based on your comments:

1) connections to Azure SQL DB are strictly old-school User Name + Password. Obviously a bad practice, but client says they do not know how to enable Azure AD. (quite a long explanation for "lazy")

2) everything at issue is within Power BI Service Dataflows, problem has nothing to do with PBI Desktop. SQL credentials are the same but we have no problem publishing reports and datasets.

3) yesterday in an AutoML Dataflow, the auto-generated reports had Power Query transformations which were blocked. I had the option to ignore security zone settings and the problem went away. I suspect something similar is happening in my Dataflows since the error message implies I am attempting to combine data from sources with different security settings, which would allow data to "leak". We have set every known security and privacy setting to "ignore".

4) regarding sign-in prompts, in every other Service process we are indeed using Azure AD, the only problem is with some of the connections to the database. I am going to push to get Azure AD enabled, per your link on AD Admin.

5) common problem: I am a BI consultant building a no-code product for my client. I am completely sandboxed in Power BI, I have no ability to access diagnostics or admin settings. The real problem is the client believes "no-code" and thinks it also means "no-support" since the platform is touted as DIY  BI. What a life, eh?