An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
hi Saiyudh Mannan,
the error is a dead giveaway that somewhere, deep in the metadata, your synapse workspace is still linked to that original gmail identity. just changing ownership is not always enough. the sql server behind synapse can retain that old connection info.
you need to check the active directory admin setting for your synapse sql server. this is a separate step from just resource ownership. go to your synapse workspace in the portal. under the 'settings' section, find 'active directory admin'. make absolutely sure your .edu account is set as the admin here. this controls who can connect to the sql endpoint.
next, dive into the sql server itself. your synapse workspace has a dedicated sql server name that ends in 'sql.azuresynapse.net'. find that server in the azure portal. go to its 'active directory admin' blade and again, verify your .edu account is the admin. this is often the missing piece. the docs for this are here https://learn.microsoft.com/azure/azure-sql/database/authentication-aad-configure
also, check this. from power bi desktop, try clearing any cached credentials. sometimes power bi hangs on to old logins. go to 'file' -> 'options and settings' -> 'data source settings'. find the synapse connection and click 'clear permissions'. then close and reopen power bi before trying to connect again. this might help in other tools too.
now for a general tip. when you connect from power bi, use the 'microsoft account' authentication option, not the active directory one. it sounds counter intuitive, but it often works better for this specific scenario with educational accounts.
aha, and one more thing. if all else fails, you can try creating a new dedicated sql user inside the synapse database itself using your .edu account. then connect to power bi using that sql username and password instead of active directory. it is a workaround, but it gets the job done.
good luck. this permissions maze can be tricky, but you will conquer it. let me know if setting the sql server admin does the trick.
Best regards,
Alex
and "yes" if you would follow me at Q&A - personaly thx.
P.S. If my answer help to you, please Accept my answer