on 08 Jun 2016 01:21:20
Enable SQL data source properties configuration when SQL connection is create. This way, will be possible use features like SQL Server 2016 Always Encrypted, that needs the propertie "Column Encryption Setting=enabled". If it's possible, I don't find a way the use. I try configurate in Advanced Editor, but didn't work
- Comments (10)
RE: SQL Server 2016 Always Encription features.
We are working on a project that manages sensitive data and this is a key feature that we would like to use. I hope this gets some attention from the Power BI team as this may be useful to many use cases, especially in the context of Data Privacy.
RE: SQL Server 2016 Always Encription features.
MSFT, we need this feature.
RE: SQL Server 2016 Always Encription features.
It is no good to have encrypted data if you can not decrypt and report on it. This absolutely needs to be considered by Microsoft. We are unable to deliver reporting solution at the moment, it is a mood killer for financial organisations.
RE: SQL Server 2016 Always Encription features.
This is a significant showstopper from the GDPR perspective. Right now, the workaround is to use a SSAS (not Azure AS) with DirectQuery mode, but that's a significant administration cost and a risk to manage, as well as unnecessary for companies that aim to go PaaS and SaaS.
A native connector with Always Encrypted support (including Azure Key Vault providers) would unblock a lot of things when trying to store PII data on Azure.
RE: SQL Server 2016 Always Encription features.
I thought this might work using the generic ODBC connector as that connector has parameters for talking to Azure Key Vault. Unfortuneately I got a bunch of key vault errors like the following:
OLE DB or ODBC error: [DataSource.Error] ODBC: ERROR [CE269] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Error 12038 sending request to https://cjdsqlvault.vault.azure.net:443
ERROR [CE263] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Error verifying signature of ECEK.
ERROR [CE202] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]The keystore provider AZURE_KEY_VAULT failed to decrypt the ECEK
RE: SQL Server 2016 Always Encription features.
We need this to address requirements for financial and health data.
You may use SSAS between database and power bi to decrypt data.
Not a solution because someone needs to administrate SSAS !
RE: SQL Server 2016 Always Encription features.
When dealing with any database containing PII information which people want to run reports where grouping occurs on the PII field, this is very critical. Please make this a priority.
RE: SQL Server 2016 Always Encription features.
This is a must have for HIPAA compliance in PBI.
RE: SQL Server 2016 Always Encription features.
This would also apply to Azure SQL DB, this is requested more and more from our customers and is a necessary connection type.
RE: SQL Server 2016 Always Encription features.
This is must have feature for financial and healthcare customers who wants to leverage SQL 2016 AlwaysEncrypted feature.