georgiKocev's avatar
georgiKocev
New Member
2 years ago
Status:
Done

Issue with Fabric Trial

Hello,
 
I have created myself an onmicrosoft.com account and subscribed for a Fabric Trial. The problem is that when I try to create a Fabric item I always get the following error:

Unable to create this item

To create a Lakehouse, you need a free Microsoft Fabric trial capacity. Unfortunately, your Microsoft tenant has reached the maximum number of available free trial capacities. Go to the documentation to see your options.
 
Could you help me to fix this error, please?
 
Thank you

4 Comments

  • Hi Anonymous,

     

    I have the "Users can try Microsoft Fabric paid features" enabled, the "Users can create Fabric items" enabled, the trial started: 

     

    but I do not see any available trial capacity: 

    I am not able to create a workspace with a trial license, because selection is disabled: 

    Could you please tell me what I am doing wrong? 

     

    Thanks!

     

  • georgiKocev Anonymous 

    I had the same issue on Fabric Trial (I tried with 4 tenants and all of them failed with the same error).

    Details are in my blogpost( Sorry but all info is in Japanse. Please use web translation).

     

    Workaround which I suceeded in all  tenants.

    Same Error appeared when I used my company offical email address.

    Try Userprincipal account with "xxxxxxx.onmicrosoft.com" associated with your azure tenant.

     

    Microsoft Fabric トライアル時のバグと対処方法-世界初(多分)のリゾリューション付き » ラプラス・ディー (laplaced.net)

     

    I will look into it again if you will still have difficulties.

    But now I can access to the tiral capacity, so it would be much difficult to reproduce the same error...

    Best regards,

    Akiyama from Laplaced,inc

  • iakiyama-laplac 

    Thanks for the feedback. I initially created an account with "xxxxxxx.onmicrosoft.com" and it was not allocating a trial capacity to it.

    Now I tried to create a LakeHouse again and as you mention in your post - I got the capacity allocated .... 😄

    So it seems there was some temp issue that was resolved. 

     

    Many Thanks!