The procedure for dealing with modifications in the authentication parameters of data sources in pre-existing Power BI reports is less straightforward. Changes both in the Power BI and the data source must be considered to achieve effective connectivity.
1. Update Authentication in the Data Source
Where the data source authentication has changed for one reason or another (for instance,) SQL Server Authentication-based scenarios have become Azure Active Directory scenarios or have included AWS IAM codes), the first step would be to apply the new authentication settings at the source wreck. This includes adding new authentication method permission, editing roles or users, or ensuring that the said database or platform (SQL server, Snowflake, AWS, etc.) is ready to accept the incoming new authentication. Outside software such as SQL Server Management Studio (SSMS) or Snowflake’s interface can also be used to check the operational changes that have already been made.
2. Change Power BI Connection Information From within the Power BI Desktop application:
Load the report, then go to File > Options and Settings > Data Source Settings.
Find the required data source and select Edit Permissions. Change the authentication type to a new one (for example, change it to OAuth or a corporate account with new credentials).
Check the connection to make sure it is working.
As for the Power BI Service:
Access the dataset under Settings within the workspace.
Under ‘Data Source Credentials,’ alter the method of authentication or credentials. Again, where a data source is configured to route through a gateway, changes to the Authentication Configuration must be reflected in the Gateway settings, too.
3. Inspect the Configuration of the Gateway
In cases where the report depends on an on-premises data gateway, change the configuration of the data gateway to allow the new method of authentication:
Proceed to the On-Premises Data Gateway Configuration Manager.
Find the source of data, change the authentication type, and carry out a connection verification.
Make sure the gateway version is the latest one. Older versions do not support modern authentication methods such as Azure AD and IAM roles.
4. Ensure Queries are Correct and Modify Where Necessary
If queries and transformations in Power Query Editor are broken after the authentication has been updated, the reason could include the fact that Snowflake, AWS S3, or other complicated sources require encodings to be passed in correctly. If this type of authentication is used, connection strings or parameters may need to be altered.
5. Test Reports and Refresh
Update the Power BI Desktop report to check if the data loads properly. After that, republish the report in the Power BI Service and perform a manual refresh to check connectivity at the service level. In the case of a scheduled refresh, make sure it completes successfully.
6. Communicate Changes
Record and inform stakeholders about the changes. This is especially important when informing them of the adjustments that end users will have to make, such as needing to sign in with new credentials after an authentication update.
Since handling the data source and setting up Power BI are involved here, changing the authentication method will go smoothly.
