Is there anyway to auto create and deploy the fabric resources and deployment into Fabric

[pavannarani]

Hi Community,


I have a requirement to auto create and deploy the fabric resources like data pipeline, notebooks, lakehouse and warehouse which ever is supported with git. Is there any way we can automate the process of creating the fabric items from scratch via any scripts or CICD pipelines generally how azure devops does for cloud resources.

If any one finds solution for this please let us know here. I know Fabric deployment pipelines is available but even there in DEV workspace if we assume, all items must be created manually only am looking how to automate this.

[V-yubandi-msft]

Hi @pavannarani ,

we wanted to check in as we haven't heard back from you. Did our solution work for you? If you need any more help, please don't hesitate to ask. Your feedback is very important to us. We hope to hear from you soon.

Thank You.

[V-yubandi-msft]

Hi @pavannarani ,

We noticed we haven't received a response from you yet, so we wanted to follow up and ensure the solution we provided addressed your issue. If you require any further assistance or have additional questions, please let us know.

Your feedback is valuable to us, and we look forward to hearing from you soon.

Thank You.

[V-yubandi-msft]

Hi @pavannarani ,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution we provided for your issue worked for you  or let us know if you need any further assistance?

Your feedback is important to us, Looking forward to your response. 

Thank You.

[V-yubandi-msft]

Hi @pavannarani ,

Thank you for reaching out to the Microsoft Fabric Community with your query. @nilendraFabric , has provided a good solution to your query about automating the creation and deployment of Fabric resources through CI/CD pipelines. The steps shared cover some essential prerequisites, tools, and implementation details.  We appreciate @nilendraFabric , valuable inputs in this discussion.

For further smooth implementation, consider the following points.

• Use error handling in bash-based scripts. Configure logging to debug problems effectively while creating a workspace or pipeline.
• Define reusable ARM templates or Git templates for different environments instead of defining configurations from scratch.
• Sensitive credentials such as Fabric Token should be stored securely in Azure Key Vault or DevOps secure files rather than.env files.
• Set role-based access control (RBAC) for Azure DevOps pipelines and Fabric workspaces to prevent unauthorized access.
• If managing multiple projects or workspaces, introduce parameterization into your scripts or templates. This will allow dynamic adjustments based on project needs without duplicating effort.

If my answer addressed your query, please mark it as the Accepted Solution so that others can easily find the solution. I would also appreciate a 'Kudos' if you found my response helpful.

[nilendraFabric · Accepted solution]

Hello @pavannarani 

great question. 

have a look at this Bootstrap Scripts:

A bash-based script automates workspace creation, deployment pipelines, lakehouses, notebooks, and data pipelines. Example steps:
• Deploys Fabric workspaces (Dev, Test, Prod) via ARM templates.
• Creates a lakehouse (`lh_main`), notebooks (e.g., `nb-city-safety`), and data pipelines (e.g., `pl-covid-data`).
• Connects workspaces to Git repositories and triggers hydration (data loading) via notebooks/pipelines

https://github.com/Azure-Samples/modern-data-warehouse-dataops/blob/main/single_tech_samples/fabric/...

ps : I haven't tried it yet

if this is helpful please accept the solution.

[pavannarani]

@nilendraFabric Thank you so much for response,

It seems there is a lot of content is there in that documentation. So by following those articles we can set up the CICD deployment process for fabric interesting. Can I directly use that code to do a testing or any prerequisites needed to implement it.

[nilendraFabric]

Hello @pavannarani 

Pre-requisites

• Always ensure the latest Fabric Token is added to the .env file (see instructions for generating the token).
• Azure CLI and jq are installed.
• Ensure that correct Azure account is being used.
• Access to Azure DevOps organization and project.
• An Azure Repo. Currently, only Git in Azure Repos with the same tenant as the Fabric tenant is supported

Please accept the answer if this helpful and give kudos