Error moving Premium workspace to Fabric: VNetMigrationNotAllowedException

[AMD0791]

We have migrated quite a few workspaces from our Premium capacity to our Fabric capacity in a different region.  We've had a few errors related to the known issues for fabric items, but the message was clearly about the fabric items, and we're working through those few use cases.

I am now trying to move one workspace and the message is not helpful:

"This workspace does not support migration to another region or capacity type".  There is nothing to give us a clue about WHY it doesn't support migration.  The fabric items were deleted and there are no large semantic models in the workspace.

When I monitor the network traffic via the F12 developer tools , I see this error on the call to move the workspace:

"PowerBICapacityFoldersMigrationVNetMigrationNotAllowedException"

VNet migration?  I can't find any any datasets connected to a VNet gateway.  Most of the datasets aren't actively connected to any gateway because they are mostly manually updated by republishing.

Any ideas on what to look at for this?

Thank you!

[v-hjannapu]

Hi @AMD0791,

Thank you  for reaching out to the Microsoft fabric community forum.
Thank you @Nasif_Azam for your reply regarding the issue.

check if the Premium capacity has any VNet settings turned on in the Admin Portal, even if you haven’t used it before. Sometimes these settings can cause issues. Next, use the Power BI REST API like GET /groups/{groupId  to see if there’s any hidden stuff in the workspace that’s causing the migration error. Also, make sure all deleted Fabric items or dataflows are completely removed, as leftover data can create problems. If you’re in a hurry, try copying the reports and datasets to a new Fabric workspace as a workaround.

If the response has addressed your query, please Accept it as a solution and give a 'Kudos' so other members can easily find it

Best Regards,
Harshitha.

[Nasif_Azam]

Hey @AMD0791 ,

Based on the error message PowerBICapacityFoldersMigrationVNetMigrationNotAllowedException, it seems the issue might not be about active VNet connections at the dataset level, but rather a VNet integration setting tied to the workspace or the capacity it's currently in. Few things to check:

1. VNet Integration at the Capacity Level: Is the source Premium capacity using VNet data gateway or VNet integration? Even if your datasets aren’t actively using it, if the workspace inherits from a capacity with VNet integration enabled, that could block migration.

2. Check for Legacy Dataflows or Linked Entities: Sometimes dataflows or linked datasets retain metadata that causes migration to fail. Even deleted items can leave traces until fully purged.

3. Use Power BI REST API to Inspect the Workspace: The Power BI Admin REST API can help check for hidden dependencies or configurations not visible in the UI.

4. Try Cloning to a New Workspace: As a workaround, if urgent, consider cloning the reports and datasets to a new Fabric-backed workspace (export/import PBIX or use deployment pipelines) to bypass the migration blocker.

For Detailed Information:

VNet data gateway in Power BI

Power BI workspace migration to Fabric

Power BI Admin REST API – Get Workspaces

Deployment Pipelines in Power BI

If you found this solution helpful, please consider accepting it and giving it a kudos (Like) it’s greatly appreciated and helps others find the solution more easily.

Best Regards,
Nasif Azam

[AMD0791]

Thank you for your extensive reply. Unforrtunately, the links are all 404 right now.  

I will look into the VNet at the capacity level, although I would expect that issue would affect a lot more workspaces.  TO my knowledge, we have never used a VNet with this capacity.

[lbendlin]

Don't waste your time. Since you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi

Let them figure it out.

[AMD0791]

I've done that as well.  We have a call in a few days.  Just want to have as much info as possible.