Forum Discussion

pmscorca's avatar
pmscorca
Icon for Post Prodigy rankPost Prodigy
6 months ago

Moving Fabric between two subscriptions

Hi,

a my customer has an Azure tenant with a subscription where a Fabric capacity was created.

My customer has decided to create a new subscription and so it is necessary to move the Fabric capacity from the previous subscription.

Is a such operation possible? Does it occur to migrate workspaces, lakehouses, warehouses, pipelines, dataflow gen2s, semantic models, reports and so on?
Is it possible to use deployment pipeline to deploy from a Fabric capacity in a dev/test subscription to another Fabric capacity in a prod subscription?

Thanks

9 Replies

  • Hi pmscorca 

     

    I don't think it's possible to move directly MSFT Fabric capacity between Azure subscriptions. Fabric capacity is boundned to subscription where it was created. But you can assign your pld workspsces to new Fabric cappcity and also once you assigne this, then you can use deployement pipelines to promote content across your environments.

     

    Few threads which will help you below mentioned. Pls read it.

    Capacity reassignment restrictions and common issues - Microsoft Fabric | Microsoft Learn

    Understand Microsoft Fabric Licenses - Microsoft Fabric | Microsoft Learn

    Moving the MS Fabric from one subscription to another - Microsoft Q&A

     

    Please let me if ti helps you!!

     

    Thank you!!

     

    Did I answer your question? Mark my post as a solution!

    Proud to be a Super User!

     

     

  • Hi pmscorca  of course is possible...  I tested my self! Create a fabric capacity in one subscription and then move to antoher subscription WITHIN THE SAME TENANT. 

     

    The steps are as follow: 

    #01. From your current fabric capactity, click on Move > Move to another subscrption as shown below 

     

     

    #02. Pick the new subscription and resource group, wait for the validation and click accept... Azure will do the rest. 

     

    And NO, you don't have to move anything, BUT, I recommend you to PLAN ACCORDINGLY, that is: 

     

    #01. Schedule when you will move the capacity and inform users to stand-by for any issues. 

    #02. Stop the capacity and then, move to another subscription 

    #03. Confirm the capacity on the new subscription and re-start 

    #04. Verify that any workspaces attached work properly after the move. 

     

    I don't think you will have any issues, but is better to be prepared for any contigencies  and give your self some time to troubleshoot  😉

     

    With regards to "Is it possible to use deployment pipeline to deploy from a Fabric capacity in a dev/test subscription to another Fabric capacity in a prod subscription?" of course is also possible! Remember, a fabric capacity from azure perspective, IS JUST ANOTHER RESOURCE,  so, to use a deployment pipeline, understending deployment pipeline means AZURE DEVOPS DEPLOYMENT PIPELINE, you just need to wrap the powershell cmdlet Move-AzResource (Az.Resources) | Microsoft Learn in your pipeline, give permission and of you go! 

     

    Hope this answer your questions! Kudos if you find this info. useful and mark as an answer if appropiate... best of lucks and ping us if any additional questions. 

     

     

     

  • v-dineshya's avatar
    v-dineshya
    Icon for Community Support rankCommunity Support

    Hi pmscorca ,

    Thank you for reaching out to the Microsoft Community Forum.

     

    Hi svenchio  and suparnababu8 ,Thank you for your prompt responses.

     

    Hi pmscorca  ,  could you please try the proposed solutions shared by  suparnababu8  and svenchio ? Let us know if you’re still facing the same issue we’ll be happy to assist you further.

     

    Regards,

    Dinesh

    • v-dineshya's avatar
      v-dineshya
      Icon for Community Support rankCommunity Support

      Hi pmscorca ,

      We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.

       

      Regards,

      Dinesh

    • pmscorca's avatar
      pmscorca
      Icon for Post Prodigy rankPost Prodigy

      Hi, thanks for your reply.

      Before advising my customer I need more reliable answers.

      Remaining in the same tenant and the same region, a new subscription is ready, called f.e. NewSubscr. Respect to NewSubscr is ready a prod capacity, ProdCap.

      The first step to do is to migrate the old Fabric capacity for dev/test purposes from OldSubscr to NewSubscr and the related workspaces, each having lakehouses, pipelines, dataflow gen2s, notebooks, semantic models and so on. Which do actions implement and in which order to accomplish a such first step?

      The second thing is to deploy the dev/test workspace, and the related items, from the migrated old capacity in NewSubscr to the new ProdCap in NewSubscr by using a Fabric deployment pipeline, not a AzureDevOps pipeline: is it possible?

      Thanks