AAS Migration Tool

Question

Can someone explain the AAS to fabric migration tool, specifically the Power BI Service reports impact. If my existing reports published online used AAS as a connection type, when I migrate my AAS model to Fabric, and then turn on the server direction, why do these published reports not connect through the old \azureaz link through to the new model in fabric, when the local desktop client drivers can do this? What is different about the service connector

Answer 1

hi Peter McInnes(Unifeye), thx for sharing urs issue here at Q&A portal,

Yep, this is a common confusion in the AAS migration tool.

Server redirection and Power BI report rebind are not the same thing.

Server redirection is mainly for XMLA/client tools, like SSMS, Tabular Editor, Excel, automation, or desktop clients using the AAS server name. That’s why ur local desktop driver can follow the old asazure://... endpoint to the new Fabric/Power BI model. Power BI Service reports don’t rely on that same client-side driver behavior. Reports published in the service have their dataset/report binding stored in the Power BI service metadata. They need to be rebound to the new semantic model after migration.

Server redirection redirects XMLA endpoint client tools, while rebind redirects live-connect reports in Power BI Service to the new Power BI model https://learn.microsoft.com/en-us/fabric/enterprise/powerbi/aas-pbi-migration-overview

So turn on server redirection for tools/clients, but use Rebind reports for published Power BI Service reports. Different path, different connector behavior. Annoying, but intentional.

rgds,

Alex

&

If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal