Connecting Power BI with an Azure SQL Server Database

[ToddChitt]

Hello. I am trying to connect the SQL Database Auditing content pack to my Azure SQL Database Audit log blob storage and am following instruction in this article: https://powerbi.microsoft.com/en-us/documentation/powerbi-content-pack-azure-audit-logs/

Should be straight forward enough except:

1. What do I put for table name? NOTE: In Azure SQL Database, Auditing & Threat Detection, it tells me that Auditing Type of Table is depricated. So I'm using Blob storage. Will this work?

2. When I click Next, I then copy andpast in the Key and hit Sign-In. I get "Failed to update data source credentials".

I defaulted my Storage Account name for Account, and "blob.core.windows.net" for the domain. Is that all correct?

Thanks in advance.

Oh, and the documentation mentioned at the start is pretty generic. It would be great to have screen shots that indicate what fields in Azure correlate to what fields in the connection setup. There is no mention of using Blob storage for the Azure SQL Audit logs so I have no idea if what I am trying to do is even possible. I just know that I have a month's worth of Audit Logs out there and the Azure Portal is useless in trying to analyze them. Power BI seemed such a natural choice.

Frustrated.

[Greg_Deckler]

Just use * to show all tables. If my understanding is correct, the table name is the name of the table in the database.

[ToddChitt]

Tried putting in * for all fields ( Table, Dates, etc) and got this:

Failed to update data source credentials.Hide details

Activity ID:
Request ID:	281dbb1c-065f-f53d-527a-a73d2a73e044
Status code:	400
Time:	Fri May 12 2017 10:18:44 GMT-0400 (Eastern Daylight Time)
Version:	13.0.1700.2027
Cluster URI:	https://wabi-us-east2-redirect.analysis.windows.net

Not sure what Status Code 400 indicates.

[Greg_Deckler]

Hmm, putting in * is what the Content Pack suggests. I suppose you should be able to connect to your Azure SQL Audit database instance via SQL Server Manager and look at the table names?

The error you are getting doesn't seem related to the * however, it looks more like failing to update credentials. Perhaps blast it and recreate it using * from the get go?

[ToddChitt]

Let's take a step back and define the WHAT and WHERE of the "AUDIT" portion of this.

I have an Azure SQL Database. I log in to the Azure Portal, click on the database name on my dashboard, then click "Audit & Threat detection". I turn on Auditing, and leave the Auditing Type as Blob (because it indicates that table auditing is depricated).

QUESTION: Is THIS what this Content Pack is supposed to connect to? If so, and if Table type auditing is depricated, why does the content pack setup ask for a TABLE Storage Account Name?

Can I use this Content Pack to connect to a BLOB storage account?