Merge pull request #3160 from MicrosoftDocs/main639196458531753896sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

docs/admin/git-integration-admin-settings.md

@@ -4,7 +4,7 @@ description: Learn about what the feature switches affecting Git integration do
 author: billmath
 ms.author: billmath
 ms.topic: how-to
-ms.date: 07/02/2024
+ms.date: 07/14/2026
 ---
 
 # Git integration tenant settings

docs/admin/media/git-integration-admin-settings/workspace-settings.png

@@ -1,44 +1,95 @@
 ---
 title: Introduction to CI/CD in Microsoft Fabric
-description: An overview of the CI/CD continuous integration, continuous deployment as part of the Application lifecycle management (ALM) cycle process in Microsoft Fabric.
+description: An overview of continuous integration and continuous delivery (CI/CD) in Microsoft Fabric, including Git integration, deployment pipelines, the Variable library, the Fabric REST APIs, the Fabric CLI, and infrastructure as code.
 ms.reviewer: NimrodShalit
 ms.topic: concept-article
-ms.date: 12/15/2025
+ms.date: 07/14/2026
+ai-usage: ai-assisted
 #customer intent: As a developer, I want to understand the CI/CD process in Microsoft Fabric so that I can efficiently manage the lifecycle of my applications.
 ---
 
-# What is application lifecycle management in Microsoft Fabric?
+# What is CI/CD in Microsoft Fabric?
 
-Microsoft Fabric's application lifecycle management tools provide a standardized system for communication and collaboration between all members of the development team throughout the life of the product. Lifecycle management facilitates an effective process for releasing products quickly by continuously delivering updated content into production and ensuring an ongoing flow of new features and bug fixes using the most efficient delivery method. There are three main components of lifecycle management in Fabric:
+Continuous integration and continuous delivery (CI/CD) in Microsoft Fabric give development teams a standardized way to build, review, and release content with speed and reliability. Instead of manual updates, teams integrate changes frequently through source control and deliver them through automated pipelines, so new features and bug fixes reach production quickly and safely.
 
-## Git integration
+The Fabric CI/CD platform is built on the Fabric REST APIs and brings source control, delivery, configuration, and developer tooling together into a single, integrated experience. The rest of this article walks through the platform layer by layer.
 
-:::image type="content" source="./media/cicd-overview/git-flow.png" alt-text="Flowchart showing the connection between the remote Git branch and the live workspace.":::
+## The Fabric CI/CD platform at a glance
+
+The Fabric CI/CD platform spans several core capabilities, all built on the Fabric REST API foundation:
+
+* **Git integration** - Sync a workspace with a Git repository in Azure DevOps or GitHub, with service principal support.
+* **Deployment pipelines** - Promote content across Dev, Test, and Prod stages with configuration rules and content comparison.
+* **Fabric REST APIs** - The foundation layer for item CRUD, item definitions, capacity, workspace, access, and job operations.
+* **Variable library** - Configuration as code, with per-stage value sets for CI/CD, managed through the API or the UI.
+* **Fabric CLI** - An open-source, scriptable, filesystem-like command-line tool that's ready for GitHub Actions and Azure DevOps.
+* **Terraform and fabric-cicd** - Infrastructure as code for environments, where fabric-cicd is the most widely adopted deployment tool.
+
+:::image type="content" source="./media/cicd-overview/fabric-cicd-platform.png" alt-text="Diagram of the Fabric CI/CD platform components: Git integration, deployment pipelines, Fabric REST APIs, Variable library, Fabric CLI, and Terraform with fabric-cicd." lightbox="./media/cicd-overview/fabric-cicd-platform.png":::
+
+## Reference architecture
+
+The following enterprise reference architecture shows how these layers fit together. Developer tools build on the Fabric REST API foundation layer. Content flows through the Fabric integration and delivery layer with the Variable library, Git integration, and deployment pipelines. Source control and CI automation run in GitHub or Azure DevOps with a CI/CD runner. The supporting Azure and Fabric tenant resources include Dev, Test, and Prod capacities, Azure Key Vault, a private network, tenant settings, connections, domains, and the parent and branch workspaces created through branch-out.
 
-With Fabric's [Git integration](./git-integration/intro-to-git-integration.md) process, incremental workspace updates can be made frequently and reliably by multiple developers. By applying Git advantages and best practices, developers can collaborate and ensure that content changes get to the workspace quickly and reliably. When ready, the delivery process can then deliver the content to deployment pipelines for testing and distribution.
+:::image type="content" source="./media/cicd-overview/fabric-cicd-reference-architecture.png" alt-text="Enterprise reference architecture diagram showing developer control tools over the Fabric REST API foundation layer, the Fabric integration and delivery layer with Variable library, Git integration, and deployment pipelines, source control and CI automation with GitHub, Azure DevOps, and a CI/CD runner, and the Azure and Fabric tenant resource plan with Dev, Test, and Prod capacities, Azure Key Vault, a private network, and parent and branch workspaces." lightbox="./media/cicd-overview/fabric-cicd-reference-architecture.png":::
+
+## Fabric REST APIs: the foundation
+
+All Fabric CI/CD capabilities build on the [Fabric REST APIs](/rest/api/fabric/articles/using-fabric-apis), which provide programmatic access to core operations: item create, read, update, and delete, item definitions, capacity, workspace and access management, and job scheduling. Every higher-level experience, from Git integration to deployment pipelines, uses these APIs, so anything you do in the portal you can also automate.
+
+## Fabric integration and delivery
+
+This layer moves content reliably from development to production through three complementary capabilities.
 
 > [!NOTE]
-> Some of the items for CI/CD are in preview. See the list of supported item for the [Git integration](./git-integration/intro-to-git-integration.md#supported-items) and [deployment pipeline](./deployment-pipelines/intro-to-deployment-pipelines.md#supported-items) features.
+> Some of the items for CI/CD are in preview. See the list of supported items for the [Git integration](./git-integration/intro-to-git-integration.md#supported-items) and [deployment pipeline](./deployment-pipelines/intro-to-deployment-pipelines.md#supported-items) features.
+
+### Git integration
+
+:::image type="content" source="./media/cicd-overview/git-flow.png" alt-text="Flowchart showing the connection between the remote Git branch and the live workspace.":::
+
+By using Fabric's [Git integration](./git-integration/intro-to-git-integration.md), multiple developers can frequently and reliably make incremental workspace updates. By applying Git advantages and best practices, developers collaborate and ensure that content changes get to the workspace quickly and reliably. When content is ready, the delivery process can then deliver it to deployment pipelines for testing and distribution.
 
-## Delivery through deployment pipelines
+### Deployment pipelines
 
 :::image type="content" source="./media/cicd-overview/pipeline-flow.png" alt-text="Illustration showing the flow of data in a deployment pipeline from data to app." lightbox="media/cicd-overview/pipeline-flow.png":::
 
-Fabric's [deployment pipelines](./deployment-pipelines/intro-to-deployment-pipelines.md) [automates the delivery](./deployment-pipelines/pipeline-automation.md) of modified content to environments like testing and production. It allows teams to produce updates in short cycles with high speed, frequency, and reliability. Content can be released at any time with a simple, repeatable deployment process.
+Fabric's [deployment pipelines](./deployment-pipelines/intro-to-deployment-pipelines.md) [automate the delivery](./deployment-pipelines/pipeline-automation.md) of modified content to environments like testing and production. Teams produce updates in short cycles with high speed, frequency, and reliability. You can release content at any time with a simple, repeatable deployment process.
+
+For the most efficient CI/CD experience in Fabric, connect your developer workspace to Git, and deploy from the connected workspace by using deployment pipelines.
+
+### Variable library
+
+By using [Variable libraries](./variable-library/variable-library-overview.md), you can:
+
+* Define and manage user-defined variables in a unified way for all workspace items.
+* Use the variables in different places in the product: in item definitions such as queries, as references to other items such as a lakehouse ID, and more.
+* Reuse variables across Fabric workloads and items. For example, several items in the workspace can refer to the same variable.
+* Adjust values based on the release pipeline stage for CI/CD.
 
-For the most efficient lifecycle management experience in Fabric, connect your developer workspace to Git, and deploy from the connected workspace using deployment pipelines.
+## Source control and CI automation
 
-## Variable library
+Fabric Git integration connects a workspace to a Git repository in either GitHub or Azure DevOps. Your continuous integration automation, such as validating a pull request or updating an integration workspace from Git, runs in any CI/CD runner: GitHub Actions, Azure Pipelines, or a self-hosted runner. Service principal support lets these automated flows authenticate without a signed-in user, with the Azure DevOps provider.
 
-With [Variable libraries](./variable-library/variable-library-overview.md), customers can:
+## Developer tooling and infrastructure as code
 
-* Define and manage variables (user-defined variables) in a unified way for all workspace items.
-* Use the variables in different places in the product: In item definitions (such as queries), as reference to other items (Lakehouse ID), and more.
-* Reuse variables across fabric workloads and items (for example, several items in the workspace can refer to the same variable).
-* CI/CD - Use variables to adjust values based on the release pipeline stage.
+Developers drive the platform through scriptable tools that build on the Fabric REST APIs.
+
+### Fabric CLI
+
+The [Fabric CLI](/rest/api/fabric/articles/fabric-command-line-interface) (`fab`) is an open-source, scriptable command-line tool with a filesystem-like interface over Fabric. It works well in GitHub Actions and Azure DevOps for automating Git sync, deployment, and item management.
+
+### Terraform and fabric-cicd
+
+For infrastructure as code, use the [Terraform provider for Microsoft Fabric](https://registry.terraform.io/providers/microsoft/fabric/latest/docs) to provision Fabric environments such as workspaces and capacities. Use [fabric-cicd](https://microsoft.github.io/fabric-cicd/), a Python library, to deploy item definitions from a source-controlled repository. fabric-cicd is the most widely adopted deployment tool for Fabric CI/CD.
 
 ## Related content
 
-* [End to end lifecycle management tutorial](./cicd-tutorial.md)
-* [Deployment pipelines](./deployment-pipelines/intro-to-deployment-pipelines.md)
+* [CI/CD workflow options in Fabric](./manage-deployment.md)
 * [Git integration](./git-integration/intro-to-git-integration.md)
+* [Deployment pipelines](./deployment-pipelines/intro-to-deployment-pipelines.md)
+* [Variable library](./variable-library/variable-library-overview.md)
+* [Fabric REST APIs](/rest/api/fabric/articles/using-fabric-apis)
+* [Fabric CLI](/rest/api/fabric/articles/fabric-command-line-interface)
+* [Terraform provider for Microsoft Fabric](https://registry.terraform.io/providers/microsoft/fabric/latest/docs)
+* [fabric-cicd](https://microsoft.github.io/fabric-cicd/)

docs/cicd/cicd-overview.md

@@ -1,27 +1,27 @@
 ### YamlMime:Landing
 
-title: Fabric application lifecycle management documentation
-summary: The lifecycle management tools in Fabric enable efficient product development, continuous updates, and fast releases.
+title: Microsoft Fabric CI/CD documentation
+summary: The CI/CD tools in Fabric enable efficient development, continuous updates, and fast releases.
 
 metadata:
-  title: Fabric application lifecycle management documentation
-  description: Learn about lifecycle management tools in Fabric for CI/CD, Git integration, and deployment pipelines.
+  title: Microsoft Fabric CI/CD documentation
+  description: Learn about CI/CD tools in Fabric for source control, Git integration, and deployment pipelines.
   ms.subservice: cicd
   ms.topic: landing-page # Required
   ms.collection: collection # Optional; Remove if no collection is used.
-  ms.date: 1/23/2025 #Required; mm/dd/yyyy format.
+  ms.date: 07/14/2026 #Required; mm/dd/yyyy format.
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | tutorial | overview | quickstart | reference | sample | tutorial | video | whats-new
 
 landingContent:
 # Cards and links should be based on top customer tasks or top subjects
 # Start card title with a verb
   # Card 
-  - title: About application lifecycle management
+  - title: About CI/CD in Fabric
     linkLists:
       - linkListType: overview
         links:
-          - text: What is application lifecycle management in Fabric?
+          - text: What is CI/CD in Microsoft Fabric?
             url: ./cicd-overview.md 
           - text: What is Git integration?
             url: git-integration/intro-to-git-integration.md 
@@ -51,9 +51,9 @@ landingContent:
             url: variable-library/variable-library-overview.md
       - linkListType: reference
         links:
-          - text: Frequently asked questions about the Fabric lifecycle management tools
+          - text: Frequently asked questions about the Fabric CI/CD tools
             url: faq.yml
-          - text: Troubleshoot lifecycle management issues
+          - text: Troubleshoot CI/CD issues
             url: troubleshoot-cicd.md
 
   # Card 
@@ -77,15 +77,15 @@ landingContent:
             url: git-integration/manage-branches.md
           - text: Resolve conflicts in Git
             url: git-integration/conflict-resolution.md
-          - text: Lifecycle management best practices
+          - text: CI/CD best practices
             url:  ./best-practices-cicd.md 
       - linkListType: tutorial
         links:
-          - text: Lifecycle management tutorial
+          - text: CI/CD tutorial
             url: cicd-tutorial.md
 
   # Card
-  - title: Automate application lifecycle management workflows using APIs
+  - title: Automate CI/CD workflows using APIs
     linkLists:
       - linkListType: how-to-guide
         links:

docs/cicd/index.yml

@@ -1,7 +1,7 @@
 items:
 - name: Application lifecycle management documentation
   href: index.yml
-- name: What is application lifecycle management? 
+- name: What is CI/CD in Microsoft Fabric?
   href: cicd-overview.md
 
 - name: "Tutorial: End to end application lifecycle management"

docs/cicd/media/cicd-overview/fabric-cicd-platform.png

@@ -3,7 +3,7 @@ title: Fabric AI Prompt in Dataflow Gen2
 description: Learn how to use Fabric AI Functions Prompt in Dataflow Gen2.
 ms.reviewer: miescobar
 ms.topic: concept-article
-ms.date: 03/15/2026
+ms.date: 07/14/2026
 ms.custom: dataflows
 ai-usage: ai-assisted
 ms.collection: ce-skilling-ai-copilot
@@ -27,7 +27,7 @@ In the dialog, enter your prompt and choose which columns to include as context.
 :::image type="content" source="media/dataflow-gen2-ai-functions/dialog.png" alt-text="Screenshot of AI Prompt dialog in Dataflow Gen2 (CI/CD)." lightbox="media/dataflow-gen2-ai-functions/dialog.png":::
 
 >[!TIP]
->Learn how to craft more effective prompts to get higher-quality responses by following [OpenAI's prompting tips for gpt-4.1](https://cookbook.openai.com/examples/gpt4-1_prompting_guide#2-long-context).
+>Learn how to craft more effective prompts to get higher-quality responses by following [OpenAI's GPT-5 prompting guide](https://developers.openai.com/cookbook/examples/gpt-5/gpt-5_prompting_guide).
 
 ## Considerations and limitations
 

docs/cicd/media/cicd-overview/fabric-cicd-reference-architecture.png

@@ -4,7 +4,7 @@ description: Transform and enrich data at scale with lightweight, LLM-powered co
 ms.reviewer: singhrana
 reviewer: ranadeepsingh
 ms.topic: how-to
-ms.date: 06/10/2026
+ms.date: 07/14/2026
 ms.search.form: AI Functions
 ai-usage: ai-assisted
 ---
@@ -53,7 +53,7 @@ Supported file types include JPG/JPEG, PNG, static GIF, WebP, PDF, MD, TXT, CSV,
 >
 > - AI Functions are supported in [Fabric Runtime 1.3](../../data-engineering/runtime-1-3.md) and later.
 > - Python AI Functions for pandas and PySpark now default to `gpt-5-mini` with `reasoning_effort` set to `low`. This model has a 400,000-token context window and a 128,000-token maximum output. For model limits and rates, see the [language models table](./billing.md#language-models).
-> - AI Functions in Dataflow Gen2 and warehouse will receive the same model upgrade by the end of June 2026.
+> - AI Functions in Dataflow Gen2 and DataWarehouse SQL use the same base model`gpt-5-mini` with `reasoning_effort` set to `low`.
 > - Although the underlying model can handle several languages, most AI Functions are optimized for English-language text.
 > - AI Functions don't log or store user prompts, input data, or outputs.