Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Don't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.

Reply
teeceegee
Regular Visitor

Error when trying to use copilot

We have been experimenting with Fabric for a little while now while we examine whether it is appropriate for us to use as a data platform. We turned our paid premuim instance from an F16 to an F64 and got access to the "copilot" button in the ribbon. However, when we ask a question of copilot we get the following error messge:

An error occurred while parsing the MWC token response: b'{"Message":"F16 SKU Not Supported","Source":"ML","error_code":"PERMISSION_DENIED"}' An error occurred while generating the MWC token: An error occurred while parsing the MWC token response. Retrying in 0.1 seconds...

 

We are definitely on an F64 instance. Is anyone else experiencing this or have any suggestions as to how to fix?

1 ACCEPTED SOLUTION

OK so the Azure SKU was set to F16, you've then scaled it to F64 and still having issues.

 

Can you try the following:

  • Pause and resume the capacity while it's set to F64
  • Create another Workspace and assign the F64 capacity to it
  • Ensure that both the toggle switches are on for "Copilot and Azure OpenAI Service (preview)​" in the Admin portal
  • Create a new Notebook in the new workspace, click the Co-Pilot button and test again

View solution in original post

5 REPLIES 5
teeceegee
Regular Visitor

Yes

OK so the Azure SKU was set to F16, you've then scaled it to F64 and still having issues.

 

Can you try the following:

  • Pause and resume the capacity while it's set to F64
  • Create another Workspace and assign the F64 capacity to it
  • Ensure that both the toggle switches are on for "Copilot and Azure OpenAI Service (preview)​" in the Admin portal
  • Create a new Notebook in the new workspace, click the Co-Pilot button and test again

Hello,

 

Apologies for taking a little while to respond. Due to other commitments it was a couple of days before we could try this out.

 

Pausing and resuming the capacity appears to have resolved the issue. Thanks for the work-around and we assume that at this time this is a bug.

Hi @teeceegee 
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.
Otherwise, will respond back with the more details and we will try to help.
Thanks

AndyDDC
Super User
Super User

Hi @teeceegee are you using an Azure Fabric SKU?

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Prices go up Feb. 11th.

JanFabricDE_carousel

Fabric Monthly Update - January 2025

Explore the power of Python Notebooks in Fabric!

JanFabricDW_carousel

Fabric Monthly Update - January 2025

Unlock the latest Fabric Data Warehouse upgrades!

JanFabricDF_carousel

Fabric Monthly Update - January 2025

Take your data replication to the next level with Fabric's latest updates!