Fabric Trial Capacity: Move Workspaces to a Different Trial Capacity

[Jay_Geng]

Hi community,

Our team started using Fabric trial since it first became available and we have built a few things with the trial capacity that support downstream production reports (I know, bad decision 😓) assuming the organsational Power BI P5 capacity will be moved to Fabric capacity and we will get Fabric automatically after the trial ends.

However, my assumption might've been too optimistic and now the decision on whether or not to enable Fabric on a organisational level is still being debated among the admins.

While we are waiting for the decision, I was getting warning that my Fabric trial would expire and if the workspaces assigned to my trial capacity were not moved to a Fabric capacity, all non-Power BI items will be permanently deleted. 😨

Luckily, some team members in my team still had 50+ days left on their Fabric trial, so I assigned the workspaces to one of their trial capacities and thinking that would give us enough time to act even if Fabric is not getting enabled in our tenant. However, to my surprise, I started getting refresh failure messages this morinng indicating the Fabric lakehouse SQL endpoint is no longer reachable (the capacity the workspace is on still has at least 40 days until expiry).

Just wondering if anybody knows what is happening here?

P.S. I managed to extend my own Fabric trial by another 60 days. After assigning the workspace back to my trial capacity (the original capacity the workspace was on), the lakehoue views become visible again.

It seems the workspace is only recogising the first trial capacity for some reason. Would be good to understand the mechanism so we can be better prepared.

[v-cboorla-msft]

Hi @Jay_Geng 

Thanks for using Microsoft Fabric Community.

Apologies for the inconvenience about the Fabric trial expiration and the unexpected behavior you are experiencing! I am glad that you were able to extend your own Fabric trial by another 60 days, and that assigning the workspace back to your original trial capacity resolved the issue temporarily.

From your description, it seems that the Fabric trial capacity is tied to the individual user who created it, and not to the organization or the workspace itself. This might be why the workspace is only recognizing the first trial capacity and not the new one you assigned it to.

Here are a few possible explanations for the behavior you are seeing:

Trial capacity binding: When you created the workspace on your original trial capacity, it might have bound the workspace to that specific trial capacity. Even when you reassigned the workspace to another trial capacity, the binding might still be in place, causing the refresh failures. 

When you initially assign a workspace to a capacity, it might be stored in a cache or configuration, and changing the assignment might not update the cache immediately.

• Temporary Glitch: Clearing cookies and caches can sometimes resolve temporary glitches within the application that might be causing the issue.
• Corrupted Data: In rare cases, corrupted data stored in the browser's cache related to Microsoft Fabric might be causing the issue. Clearing the cache removes this potentially problematic data.
• Hard Refresh: A hard refresh bypasses the cached version of the webpage and forces the browser to download the latest version from the server. Press Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac).

Lakehouse SQL endpoint: The Fabric lakehouse SQL endpoint might be specific to the trial capacity, and when you moved the workspace to a new trial capacity, the endpoint changed. This could be why the lakehouse views became unreachable.

Authentication and authorization: There might be authentication and authorization mechanisms in place that are tied to the original trial capacity, which are not being updated when you reassign the workspace to a new trial capacity.

I hope this information helps. 

Thank you.

[Jay_Geng]

Thanks for the response.

I tested today with my colleague and can confirm:

1. The SQL endpoint stays the same after switching capacity
2. Hard refresh doesn't work
3. Doesn't seem to be an authentication issue either as it is showing the below error instead of a failed authentication. "The server was not found or was not accessible"

I can still see the lakehouse in the workspace, and I can still manage or query the lakehouse using the Fabric interface but just can't connect to it from Power BI or SSMS.

Also, just realised now, I transfered the workspace to my colleague's trial capacity when I had about 5 days left on my trial, and it was working okay until my original trial expired.

It looks like the workspace is stuck on my original trial capacity before the extension when it is under another trial capacity, but it recognises the extension once it is back on my extended trial capacity 🤔

[v-cboorla-msft]

Hi @Jay_Geng 

Apologies for the inconvenience.

Please reach out to our support team to gain deeper insights and explore potential solutions. It's highly recommended that you reach out to our support team. Their expertise will be invaluable in suggesting the most appropriate approach.

Please go ahead and raise a support ticket to reach our support team:

https://support.fabric.microsoft.com/support

After creating a Support ticket please provide the ticket number as it would help us to track for more information.

Thank you.

[v-cboorla-msft]

Hi @Jay_Geng 

We haven’t heard from you on the last response and was just checking back to see if you've had a chance to submit a support ticket. If you have, a reference to the ticket number would be greatly appreciated. This will allow us to track the progress of your request and ensure you receive the most efficient support possible.

Thank you.

[Jay_Geng]

Hi, thank you for the advice.

I have raised a support ticket: 240624003000536 and I'm in contact with the support team to get this resolved.

[v-cboorla-msft]

Hi @Jay_Geng 

Thank you for sharing the details.