Forum Discussion
Resolver ISwitching PowerBI service data model connection in excel
Hi Rigensis,
After trying the every trouble shooting steps if still faces the same issue then please consider raising a support ticket for further assistance.
To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
If this post helps, please give us Kudos and consider marking it Accept as solution to assist other members in finding it more easily.
Thank you for being a part of Microsoft Fabric Community Forum!The solution for our company was that not only we were changing the tenant for PBI, but for the whole Microsoft ecosystem as well. And once a person's laptop was reprogrammed from company IT admins to work on the new tenant active directory by default, then the excel files also started working fine.
On one hand it makes sense, switching completely to the new tenant everywhere has solved the issue, but on the other hand a bit weird that by explicitly logging into excel with the new tenant did not entirely connect it to the PBI data from the new tenant. At the end of the day a full laptop user reboot and refactor to prompt login with the new tenant when starting up the machine was what solved the issue.
Community SupportHi Rigensis,
Thanks for using Microsoft Fabric Community Forum.
You are correct in suspecting that the issue is related to the account through which the data is connecting to Power BI. Here are the workarounds which might assist you in resloving the issue:
Please log in with the new tenant's account in Excel and navigate to Get Data From Power Platform > From Power BI. Attempt to reconnect to the new dataset and insert the table.
Open Windows Credential Manager (Control Panel > User Accounts > Credential Manager) and remove any entries related to Power BI.
If the data models in the new tenant differ in structure from the old tenant, this may cause connection issues. Ensure the data models are compatible.
Excel may cache credentials and connection details. Clear any existing data connections or cached credentials in Excel to reset the connection process.
If this solution worked for you, kindly mark it as Accept as Solution and feel free to give a Kudos, it would be much appreciated!
Thank you.
Resolver IHi,
I cleared any powerBI related credentials from Windows Credential Manager.
Then opened up the excel file in question (which has connection to the old Tenant data model), switched the user with which I'm logged into excel to the one related to the new tenant.
Then went into excel settings and deleted cache data.
Unfortunately still the old connections are able to refresh, and the new ones cannot be established.
- v-sgandrathi
Hi Rigensis,
After trying the every trouble shooting steps if still faces the same issue then please consider raising a support ticket for further assistance.
To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
If this post helps, please give us Kudos and consider marking it Accept as solution to assist other members in finding it more easily.
Thank you for being a part of Microsoft Fabric Community Forum!- v-sgandrathi
Hi Rigensis,
Could you please confirm if the issue has been resolved after raising a support case? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.
Thank you for your understanding and assistance.
Thank you.
- Rigensis
The solution for our company was that not only we were changing the tenant for PBI, but for the whole Microsoft ecosystem as well. And once a person's laptop was reprogrammed from company IT admins to work on the new tenant active directory by default, then the excel files also started working fine.
On one hand it makes sense, switching completely to the new tenant everywhere has solved the issue, but on the other hand a bit weird that by explicitly logging into excel with the new tenant did not entirely connect it to the PBI data from the new tenant. At the end of the day a full laptop user reboot and refactor to prompt login with the new tenant when starting up the machine was what solved the issue.