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

Microsoft is giving away 50,000 FREE Microsoft Certification exam vouchers. Get Fabric certified for FREE! Learn more

Reply
plott722
New Member

environments and deployment

Two part message...
1. I'm creating a new Fabric environment.  My thought is to have dev/test/prod - each on a separate subscription and different capacity (at least prod).  Does this seem reasonable and are there any deployment issues I need to consider?

2. Where can I find good documentation on using Azure DevOps on my fabric artifacts - notebooks, pipelines, etc.  Not sure how I create new branches in Fabric.

1 ACCEPTED SOLUTION
suparnababu8
Super User
Super User

Hello @plott722 

  • Your approch to create a sepearte subscriptionas and capacities for dev/test/prod is good. But, setting up different resource limiits or abilities for each environment, like prod, helps use resourcees wisely and keeps thiings running smoothly and also having different subscriptions makes it eaasier to keep an eye on expences and plan budgets for each setup or environament more effectively.
  • Pls go thorugh below documenatation to understand about Azure DevOps and fabric.

Overview of Fabric deployment pipelines - Microsoft Fabric | Microsoft Learn

Overview of Fabric Git integration - Microsoft Fabric | Microsoft Learn

Notebook source control and deployment - Microsoft Fabric | Microsoft Learn

Prepare Azure DevOps for Microsoft Fabric Git integration - Kevin Chant

 

Thank you!!!

 

Did I answer your question? Mark my post as a solution!

Proud to be a Super User!

View solution in original post

3 REPLIES 3
plott722
New Member

Thank you, suparnababu8!
Appreciate the response.

Quick follow up, if you don't mind.

Would you recommend using VS or VSCode with Fabric, or is that overkill?

Thank you!

Hi @plott722 

 

Appologies for late reply. 

 

Using VS Code with Fabric is a smart choice and not exceessive. It's a lightweight, flexible tool with strong support for Fabric. VS offers more advanceed features, which can be helpful for largerr projects or when you require sophisticated debugging and profiling tools. But, for most tasks relateed to Fabric, Visual Studio Code is easier to use and should meet your needs effecitively. 

 

If you need more info pls go thorugh below documentation URLs it might helps you.

Develop, execute, and debug notebook in VS Code - Microsoft Fabric | Microsoft Learn

Microsoft Fabric - Visual Studio Marketplace

VS Code extension overview - Microsoft Fabric | Microsoft Learn

 

Thanks!!!

 

Did I answer your question? Mark my post as a solution!

Proud to be a Super User!

suparnababu8
Super User
Super User

Hello @plott722 

  • Your approch to create a sepearte subscriptionas and capacities for dev/test/prod is good. But, setting up different resource limiits or abilities for each environment, like prod, helps use resourcees wisely and keeps thiings running smoothly and also having different subscriptions makes it eaasier to keep an eye on expences and plan budgets for each setup or environament more effectively.
  • Pls go thorugh below documenatation to understand about Azure DevOps and fabric.

Overview of Fabric deployment pipelines - Microsoft Fabric | Microsoft Learn

Overview of Fabric Git integration - Microsoft Fabric | Microsoft Learn

Notebook source control and deployment - Microsoft Fabric | Microsoft Learn

Prepare Azure DevOps for Microsoft Fabric Git integration - Kevin Chant

 

Thank you!!!

 

Did I answer your question? Mark my post as a solution!

Proud to be a Super User!

Helpful resources

Announcements
MarchFBCvideo - carousel

Fabric Monthly Update - March 2025

Check out the March 2025 Fabric update to learn about new features.

March2025 Carousel

Fabric Community Update - March 2025

Find out what's new and trending in the Fabric community.