Forum Discussion
Error moving Premium workspace to Fabric: VNetMigrationNotAllowedException
- 1 year ago
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.
- 1 year ago
Update for anyone in the future: Microsoft had to fix it.
They described the root cause as a "residual Virtual Network (VNet) connection that had been deleted, but the workspace still retained traces of those connections". Their product team had to remove the residual VNet references from the backend.
I don't know how any workspaces had a VNet connection, but whatever the product team did worked and I was able to move the workspace from P1 to F64. We actually later had a 2nd workspace with the same glitch and they were able to fix it pretty quickly the same way.
Thank you for the suggestion. Are there specific settings you have in mind to check for VNET? I didn't find any settings in Tenant Admin labeled Vnet or Virtual.
I have used the API to export the list of datasets and datasources and didn't find any hidden items.
We're trying to avoid recreating everything in a new workspace since there are a lot of users expecting their saved links to work. I'd also like to nail down the problem in case we encounter it again.
Hi AMD0791,
The VNetMigrationNotAllowedException error you are encountering is likely related to a VNet configuration at the capacity level rather than the Tenant Admin level. Please review the original Premium capacity settings in the Admin Portal by navigating to Admin Portal > Capacity settings > [Your Premium Capacity] > Settings. Check the Networking or Gateway connections sections for any existing VNet gateway or Private Link configurations, as these can impact migration even if they were previously set up but not actively used.
Additionally, verify whether the workspace contains any deleted Fabric items, such as dataflows or pipelines, that may still be in the Recycle Bin. These items can sometimes prevent migration. Open the workspace, go to View > Recycle Bin, and permanently remove any remaining items.
Please Accept as solution if this meets your needs and a Kudos would be appreciated.
Best Regards,
Harshitha.
- AMD07911 year ago
Advocate IV
Thank you for your very specific instructions. However, I could not find any reference to networks or gateways on the capacity settings page. It also seems that a capacity level setting would have prevented me from moving the first 50 workspaces that I've moved from our P1 to Fabric.
Likewise, I cannot find the "recycle bin" for the workspace. I can't find any reference to that even existing in Power BI. If you have screenshots showing how to get there, that would be great.
Thank you!
- lbendlin1 year ago
Super User
Dare I say "hallucinations"? Workspaces definitely do not have recycle bins accessible to users. You need to raise an extremely urgent ticket with Microsoft within 30 days of a deletion event to have them restore that in the backend. Be prepared for lots of heated discussions.
- Anonymous1 year agoNot applicable
Hi AMD0791,
I’m really sorry for the earlier confusion there’s no "Recycle Bin" for Power BI workspaces. Once a workspace is deleted, it’s permanently gone and can’t be restored unless you have a backup or saved a copy somewhere else.
about the capacity settings you're correct again. There are no network or gateway options on the capacity settings page that would stop workspaces from being moved. That’s why you were able to move the first 50 workspaces without any issue.
Please check this link and give it an upvote, as Microsoft prioritizes items based on the number of votes.
Recover deleted workspace artifacts - Microsoft Fabric CommunityThanks for your patience and understanding.
Regards,
Harshitha.