Forum Discussion

JarneT's avatar
JarneT
Frequent Visitor
2 months ago
Solved

Cannot deploy environment through deployment pipeline

I am unable to deploy an environment item between staging environments, as I get the error "Backend ErrorExport failure: Unknown. Unexpected failure". I do have a custom wheel module in the environme...
workspaces
  • v-veshwara-msft's avatar
    v-veshwara-msft
    2 months ago

    Hi JarneT ,

    Glad to hear you got it working!

    This behavior aligns with how the two publish modes are designed. Quick mode is intended for rapid, session-scoped iteration - libraries published in Quick mode install at notebook session start rather than being fully baked into the environment snapshot. As a result, Quick mode libraries may not be properly packaged for deployment pipeline export, which can cause the "Export failure" error you encountered.

    For any libraries that need to travel across pipeline stages, Full publish mode is the recommended approach, as it creates a stable, portable environment snapshot.

    Reference: Manage libraries in Fabric environments - Microsoft Fabric | Microsoft Learn

     

    Hope this helps. Please reach out for further assistance.
    Thank you.

v-veshwara-msft's avatar
v-veshwara-msft
Community Support
2 months ago

Hi JarneT ,

Thanks for reaching out to the Microsoft Fabric Community.

Yes, deploying environment items (including custom libraries) through deployment pipelines is supported in Microsoft Fabric. When you deploy an environment, all its contents - public libraries, custom libraries (.whl, .jar, .tar.gz), and Spark compute settings - should be copied to the destination workspace.

The generic "Export failure: Unknown. Unexpected failure" error is not expected behavior.

Here are a few things to check:

1. Ensure the source environment is in a fully published state before deploying. If there are unpublished pending changes, the deployment may fail.
2. This error can sometimes be caused by a transient backend issue. Try redeploying after a few minutes to rule that out.
3.  As a test, try deploying other items in the pipeline without the environment to confirm the issue is isolated to the environment item specifically.

Reference: Fabric environment Git integration and deployment pipeline - Microsoft Fabric | Microsoft Learn

Hope this helps. Please let us know if you have any further questions.

Thank you.

JarneT's avatar
JarneT
Frequent Visitor
2 months ago

Thank you for the reply!

I made a new environment, uploaded the wheel (in full mode) and then published succesfully.

I then went back to my original environment, deleted the wheel in quick mode and re-uploaded it in full mode and now the deployment succeeded as well!

 

Is deploying from quick mode not supported then, or is this unintended behaviour?

 

Regards,

Jarne

  • v-veshwara-msft's avatar
    v-veshwara-msft
    Community Support
    2 months ago

    Hi JarneT ,

    Glad to hear you got it working!

    This behavior aligns with how the two publish modes are designed. Quick mode is intended for rapid, session-scoped iteration - libraries published in Quick mode install at notebook session start rather than being fully baked into the environment snapshot. As a result, Quick mode libraries may not be properly packaged for deployment pipeline export, which can cause the "Export failure" error you encountered.

    For any libraries that need to travel across pipeline stages, Full publish mode is the recommended approach, as it creates a stable, portable environment snapshot.

    Reference: Manage libraries in Fabric environments - Microsoft Fabric | Microsoft Learn

     

    Hope this helps. Please reach out for further assistance.
    Thank you.