Forum Discussion
Assistance Needed with Dataset Refresh Issue
Hello Fabric Community,
I hope this message finds you well. I am currently facing an issue with a dataset that was previously managed by Moazzem Hossain ([email protected]). It appears that Moazzem’s account is no longer in our Microsoft Azure Active Directory (Azure AD), possibly due to removal by an Azure AD admin.
As a result, I am unable to refresh the dataset. I have taken over the dataset using my admin account ([email protected]) and attempted to set the scheduled refresh settings myself. However, I am encountering difficulties in completing this process.
Could anyone provide guidance or share steps to resolve this issue? Any help would be greatly appreciated.
Thank you in advance for your support.
Best regards,
Moazzem Hossain
[email protected]
hello TBBD
The dataset refresh issue you’re encountering typically occurs when ownership transfer doesn’t automatically resolve credential dependencies.
The dataset refresh failure stems from identity dependency chains in Power BI’s authentication model. When Moazzem’s Azure AD account was deleted:Power BI datasets store encrypted credentials using the original creator’s:
• Azure AD Object ID
• User Principal Name (UPN)
• Security group membershipsThe dataset’s scheduled refresh attempts to use:
• Original OAuth tokens tied to Moazzem’s identity
• Database permissions granted to Moazzem’s SQL login
• Gateway configurations authenticated via Moazzem’s credentialsAdmin ownership transfer doesn’t automatically recreate this delegation chain.
To resolve the dataset refresh failure caused by the deleted Azure AD account, first ensure full ownership transfer via the Power BI admin portal or REST API, then manually purge and reconfigure all data source credentials using your admin account’s identity, update Azure SQL permissions and gateway configurations to reflect the new ownership, replace any residual user-specific references in M queries or RLS rules, and set up service principal-based authentication for long-term stability, followed by validation through test refreshes and monitoring via Azure Monitor to confirm resolution.
If this is helpful please accept the answer
6 Replies
hello TBBD
The dataset refresh issue you’re encountering typically occurs when ownership transfer doesn’t automatically resolve credential dependencies.
The dataset refresh failure stems from identity dependency chains in Power BI’s authentication model. When Moazzem’s Azure AD account was deleted:Power BI datasets store encrypted credentials using the original creator’s:
• Azure AD Object ID
• User Principal Name (UPN)
• Security group membershipsThe dataset’s scheduled refresh attempts to use:
• Original OAuth tokens tied to Moazzem’s identity
• Database permissions granted to Moazzem’s SQL login
• Gateway configurations authenticated via Moazzem’s credentialsAdmin ownership transfer doesn’t automatically recreate this delegation chain.
To resolve the dataset refresh failure caused by the deleted Azure AD account, first ensure full ownership transfer via the Power BI admin portal or REST API, then manually purge and reconfigure all data source credentials using your admin account’s identity, update Azure SQL permissions and gateway configurations to reflect the new ownership, replace any residual user-specific references in M queries or RLS rules, and set up service principal-based authentication for long-term stability, followed by validation through test refreshes and monitoring via Azure Monitor to confirm resolution.
If this is helpful please accept the answer
Hi TBBD,
Thankyou nilendraFabric for your input on this issue.
Additionally, I have outlined some steps below that may resolve the issue.
- Ensure that the full ownership of the dataset has been successfully transferred, and confirm that your admin account has the appropriate permissions to manage the workspace and the dataset.
- Update OAuth tokens or API keys for any external data sources that depend on Moazzem’s credentials.
- If you're using a service principal for authentication, make sure it has the necessary permissions within both Power BI and the underlying data sources to facilitate seamless access and refresh.
- Confirm that the data gateway is operating correctly, ensuring it is authenticated with the proper credentials. Additionally, check for any updates or issues that might be affecting the refresh process.
If my response was helpful, consider clicking "Accept as Solution" and give us "Kudos" so that other community members can find it easily. Let me know if you need any more assistance!
Regards,
Sahasra.Hi TBBD,
We wanted to follow up since we haven't heard back from you regarding our last response. We hope your issue has been resolved.
If my answer resolved your query, please mark it as "Accept Answer" and give Kudos if it was helpful.
If you need any further assistance, feel free to reach out.
Thank you for being a valued member of the Microsoft Fabric Community Forum!
Hi TBBD,
I wanted to follow up on our previous suggestions regarding the issue. We would love to hear back from you to ensure we can assist you further.
If my response has addressed your query, please accept it as a solution and give a ‘Kudos’ so other members can easily find it. Please let us know if there’s anything else we can do to help.
Thankyou.
- Ensure that the full ownership of the dataset has been successfully transferred, and confirm that your admin account has the appropriate permissions to manage the workspace and the dataset.
Hi,
in addition to the college's answers, and if theses answers didn't resolved your issue, it would be helfpfull if you could describe your "difficulties" more precise or with a screenshot?
