Forum Discussion
environments and deployment
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!
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!
Super UserHi 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!