Forum Discussion

YashikaAgrawal's avatar
YashikaAgrawal
Post Patron
1 year ago
Solved

Power BI Capacity delete options

Hi,

 

We are doing a Power BI migration from tenant Infy to TATA.

Once we copy the workspace for a particular capacity

In Power BI, apart from permanently deleting a capacity, are there any options to pause, stop, or temporarily deactivate a capacity without deleting it?

 

Thanks,

  • v-hashadapu's avatar
    v-hashadapu
    1 year ago

    Hi YashikaAgrawal , Thank you for reaching out to the Microsoft Community Forum.

     

    If you delete a Power BI P SKU capacity, it cannot be restored, not even within 180 days. Deletion is permanent and Microsoft doesn’t retain any way to recover that capacity or its metadata. You'll need to recreate it if needed and reassign any workspaces.

     

    You also cannot downgrade a P1 capacity to an A SKU. They are two different capacity models, P SKUs are tied to Microsoft 365 and are subscription-based, while A SKUs are Azure-based, pay as you go and support pausing. There's no supported path to convert or resize a P SKU into an A SKU. If you want to reduce cost, you'd need to delete the P1, and then create a new A SKU in Azure, which behaves more flexibly but may not support all enterprise features of P SKUs.

     

    Licenses like P1 capacities are tenant-scoped and cannot be transferred between tenants. So, Infy’s P1 capacity cannot be moved to the TATA tenant. TATA will need to purchase a new capacity license in its own tenant. Microsoft does not allow license migration across tenants, though they can support you in workspace migration or user mapping during the transition.

     

    What is Power BI Premium? - Microsoft Fabric | Microsoft Learn

    Tenant-to-tenant migrations - Power Platform | Microsoft Learn

    Automate your migration to Microsoft Fabric capacities | Microsoft Fabric Blog

3 Replies

  • Hi YashikaAgrawal ,

    If you have a "A" sku, then you can pause and resume it in the Azure Portal.

    A "P" sku cannot be stopped or paused.  You can only delete or upgrade a "P" sku.

    • YashikaAgrawal's avatar
      YashikaAgrawal
      Post Patron

      Thank you for the reply. 3 doubts, please reply

      a. Once we delete is there any way, we can bring it back i.,e before 180 days.

      b. Can we reduce the capacity size(P1 to A SKU) to reduce cost., right not we are using in Tenant Infy for the capacity C1 i.,e P1 SKU(64 base capacity units) 

      c. Can we transfer the license from Infy tenant to another tenant TATA, do we need help of Microsoft.

       

      Thanks,

      • v-hashadapu's avatar
        v-hashadapu
        Community Support

        Hi YashikaAgrawal , Thank you for reaching out to the Microsoft Community Forum.

         

        If you delete a Power BI P SKU capacity, it cannot be restored, not even within 180 days. Deletion is permanent and Microsoft doesn’t retain any way to recover that capacity or its metadata. You'll need to recreate it if needed and reassign any workspaces.

         

        You also cannot downgrade a P1 capacity to an A SKU. They are two different capacity models, P SKUs are tied to Microsoft 365 and are subscription-based, while A SKUs are Azure-based, pay as you go and support pausing. There's no supported path to convert or resize a P SKU into an A SKU. If you want to reduce cost, you'd need to delete the P1, and then create a new A SKU in Azure, which behaves more flexibly but may not support all enterprise features of P SKUs.

         

        Licenses like P1 capacities are tenant-scoped and cannot be transferred between tenants. So, Infy’s P1 capacity cannot be moved to the TATA tenant. TATA will need to purchase a new capacity license in its own tenant. Microsoft does not allow license migration across tenants, though they can support you in workspace migration or user mapping during the transition.

         

        What is Power BI Premium? - Microsoft Fabric | Microsoft Learn

        Tenant-to-tenant migrations - Power Platform | Microsoft Learn

        Automate your migration to Microsoft Fabric capacities | Microsoft Fabric Blog