Skip to content

Commit a496cef

Browse files
rvanmaanenrvanmaanen
committed
RSS processing changes:
New/changed content: - collections/_news/2026-03-20-Introducing-Bulk-Export-and-Import-APIs-for-CICD-in-Microsoft-Fabric-Preview.md - collections/_news/2026-03-20-Introducing-new-Git-developer-experiences-in-Microsoft-Fabric-Preview.md Removed content:
1 parent 757444b commit a496cef

8 files changed

Lines changed: 288 additions & 42 deletions

‎collections/_news/2026-03-20-Introducing-Bulk-Export-and-Import-APIs-for-CICD-in-Microsoft-Fabric-Preview.md‎

Lines changed: 119 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,119 @@
1+
---
2+
primary_section: ml
3+
author: Microsoft Fabric Blog
4+
section_names:
5+
- devops
6+
- ml
7+
feed_name: Microsoft Fabric Blog
8+
title: Introducing Bulk Export and Import APIs for CI/CD in Microsoft Fabric (Preview)
9+
date: 2026-03-20 16:30:00 +00:00
10+
tags:
11+
- Asynchronous Operations
12+
- Automation
13+
- Bulk Export API
14+
- Bulk Import API
15+
- CI/CD
16+
- Definitions as Code
17+
- Deployment Best Practices
18+
- Dev Test Prod
19+
- DevOps
20+
- Disaster Recovery
21+
- Environment Promotion
22+
- Fabric REST API
23+
- Git Integration
24+
- IaC
25+
- Item Definitions
26+
- Managed Identity
27+
- Microsoft Fabric
28+
- ML
29+
- News
30+
- Pull Requests
31+
- Release Pipelines
32+
- Service Principal
33+
- Version Control
34+
external_url: https://blog.fabric.microsoft.com/en-US/blog/introducing-bulk-export-and-import-apis-for-ci-cd-in-microsoft-fabric-preview/
35+
---
36+
37+
Microsoft Fabric Blog announces preview Bulk Export and Import Item Definition APIs that let teams treat Fabric items as code, store them in Git, validate via pull requests, and automate promotion across Dev/Test/Prod with repeatable CI/CD pipelines.<!--excerpt_end-->
38+
39+
# Introducing Bulk Export and Import APIs for CI/CD in Microsoft Fabric (Preview)
40+
41+
> If you haven’t already, check out Arun Ulag’s hero blog “FabCon and SQLCon 2026: Unifying databases and Fabric on a single, complete platform” for a complete look at all of our FabCon and SQLCon announcements across both Fabric and our database offerings.
42+
43+
Enterprise DevOps teams typically want automation, repeatability, and full control over release pipelines. While Microsoft Fabric includes built-in Git integration and deployment experiences, some organizations need CI/CD capabilities that integrate directly into existing DevOps tooling.
44+
45+
To address this, Microsoft Fabric is introducing **Bulk Export and Import Item Definition APIs** (REST APIs) in **Preview**.
46+
47+
## CI/CD with Fabric item definitions as code
48+
49+
In Microsoft Fabric, items like **notebooks**, **pipelines**, **reports**, and **semantic models** are backed by a **structured item definition** that describes configuration and content.
50+
51+
The Bulk Export and Import APIs are intended to treat these item definitions as **source code**, enabling:
52+
53+
- Programmatic export from a workspace
54+
- Storage and versioning in Git
55+
- Validation through pull request workflows
56+
- Automated promotion across environments using deployment pipelines
57+
58+
This supports a separation of concerns between:
59+
60+
- **Authoring**
61+
- **Review**
62+
- **Deployment**
63+
64+
## Git-based deployment using a build environment
65+
66+
A recommended model is to drive deployments from a **central Git repository**, promoting Fabric item definitions through a structured release flow.
67+
68+
A typical approach:
69+
70+
- Use a main branch aligned across environments (**Dev**, **Test**, **Prod**)
71+
- Deploy each stage independently via dedicated build and release pipelines
72+
73+
Pipelines usually start by exporting item definitions from a development workspace using:
74+
75+
- **Fabric Git Integration**, or
76+
- The **Bulk Export API**
77+
78+
Then, validate definitions in a build environment using:
79+
80+
- Automated checks
81+
- Pull request reviews
82+
- Policy enforcement
83+
84+
For deployment, invoke the **Bulk Import API** to promote approved definitions into the target workspace. The API supports:
85+
86+
- Creating new items
87+
- Updating existing items in place
88+
89+
It also relies on Fabric’s built-in dependency handling to deploy items in the correct order, with the aim of making test/prod deployments consistent and repeatable without manual steps.
90+
91+
![Figure 1- Suggested build and release pipelines using bulk export/import API](//dataplatformblogwebfd-d3h9cbawf0h8ecgf.b01.azurefd.net/wp-content/uploads/2026/03/figure-1-suggested-build-and-release-pipelines-us.png)
92+
93+
*Figure 1: Suggested build and release pipelines using bulk export/import API*
94+
95+
## Built for scale and enterprise automation
96+
97+
The Bulk Export and Import APIs are positioned as optimized for:
98+
99+
- Batch operations across large workspaces
100+
- Long-running, asynchronous execution
101+
- Authentication using **service principals** and **managed identities**
102+
- Repeatable, auditable deployments across environments
103+
104+
The post also calls out scenarios such as:
105+
106+
- Enterprise CI/CD pipelines
107+
- Disaster recovery workflows
108+
- Large-scale environment promotion
109+
110+
## Get started
111+
112+
- The APIs are part of the Microsoft Fabric REST API surface in **Preview**.
113+
- Documentation: the detailed Fabric API guide: https://aka.ms/AAzye0t
114+
- Walkthrough: complete CI/CD tutorial using the Bulk Export and Import APIs: https://aka.ms/AAzye19
115+
116+
The post invites feedback in comments as the platform evolves.
117+
118+
[Read the entire article](https://blog.fabric.microsoft.com/en-US/blog/introducing-bulk-export-and-import-apis-for-ci-cd-in-microsoft-fabric-preview/)
119+

‎collections/_news/2026-03-20-Introducing-new-Git-developer-experiences-in-Microsoft-Fabric-Preview.md‎

Lines changed: 129 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,129 @@
1+
---
2+
primary_section: ml
3+
author: Microsoft Fabric Blog
4+
section_names:
5+
- devops
6+
- ml
7+
feed_name: Microsoft Fabric Blog
8+
title: Introducing new Git developer experiences in Microsoft Fabric (Preview)
9+
date: 2026-03-20 16:30:00 +00:00
10+
tags:
11+
- Branched Workspaces
12+
- Change Review
13+
- CI/CD
14+
- Conflict Resolution
15+
- Deployment Pipelines
16+
- Developer Experience
17+
- DevOps
18+
- Diff
19+
- Feature Branches
20+
- Git Integration
21+
- Merge
22+
- Microsoft Fabric
23+
- ML
24+
- News
25+
- Preview Features
26+
- Pull Request
27+
- Selective Branching
28+
- Source Control
29+
- Workspaces
30+
external_url: https://blog.fabric.microsoft.com/en-US/blog/introducing-new-git-developer-experiences-in-microsoft-fabric-preview/
31+
---
32+
33+
Microsoft Fabric Blog announces three preview Git developer experience improvements in Microsoft Fabric—Branched Workspaces, Selective Branching, and Compare Code Changes—aimed at making CI/CD workflows in Fabric work more like familiar Git-based feature-branch development.<!--excerpt_end-->
34+
35+
## Overview
36+
37+
Development teams use Git to collaborate and ship reliably. In **Microsoft Fabric**, Git integration is a core part of CI/CD, but workflows like feature branches, isolated development, and change review inside Fabric have historically required extra coordination or tooling.
38+
39+
This announcement introduces **three new Git integration capabilities (Preview)**:
40+
41+
- **Branched Workspaces**
42+
- **Selective Branching**
43+
- **Compare Code Changes**
44+
45+
Together, they’re intended to make it easier to work in isolation, focus only on the items you care about, and review changes confidently—without leaving the Fabric experience.
46+
47+
## The challenge: Git workflows meet shared workspaces
48+
49+
A Fabric workspace is a **shared runtime environment** connected to a single Git branch. That model supports collaboration, but can create friction when developers need to:
50+
51+
- Work on a feature without affecting others
52+
- Avoid copying entire workspaces just to change one or two items
53+
- Understand exactly what will change before committing or pulling updates
54+
- Resolve conflicts with better context
55+
56+
These new experiences are described as early steps toward addressing those challenges end-to-end.
57+
58+
## Branched Workspaces: Clear relationships for feature development
59+
60+
**Branched Workspaces** create a formal relationship between a **source workspace** and the **target workspace** created during a branch-out operation.
61+
62+
When a developer branches out within Fabric:
63+
64+
- A **relationship** is created between the source and target workspace
65+
- The relationship is visible in the Fabric UI (workspace navigation and source control)
66+
- Developers get clearer context about where a workspace came from and how it fits into the overall flow
67+
68+
The post notes this relationship also lays groundwork for future enhancements.
69+
70+
## Selective Branching: Focus exclusively on relevant tasks
71+
72+
With **Selective Branching**, developers can branch out with **only the items they need** instead of copying the full workspace.
73+
74+
During branch-out, you can:
75+
76+
- Select items individually (instead of the default “all items”)
77+
- Choose a subset of items for the feature workspace
78+
- Automatically include required related items to maintain consistency
79+
80+
Expected outcomes:
81+
82+
- Faster branch-out operations
83+
- Smaller, purpose-built workspaces
84+
- Reduced risk of unintended changes
85+
- Faster time-to-code
86+
87+
This is positioned as especially useful for large workspaces where full copies are slow and unnecessary.
88+
89+
## Compare Code Changes: Review before committing or syncing
90+
91+
**Compare Code Changes** adds a diff-style experience directly into Fabric’s Git integration so developers can:
92+
93+
- Review **workspace changes before committing** to Git
94+
- Review **incoming Git updates before updating** the workspace
95+
- Inspect **conflicts side-by-side** before resolving
96+
97+
The post emphasizes the compare experience is meant to feel familiar to developers used to other Git tools and also aligns with Fabric deployment pipeline experiences.
98+
99+
## How the features fit together
100+
101+
A suggested end-to-end workflow:
102+
103+
1. Start in a shared development workspace connected to Git
104+
2. Branch out using **Selective Branching** to create a focused feature workspace
105+
3. Work in isolation within a **Branched Workspace**
106+
4. Use **Compare Code Changes** to review changes before committing
107+
5. Merge via pull request with your Git provider
108+
6. Review incoming updates with **Compare Code Changes** before syncing back
109+
110+
![Figure 1 - The enhanced developer experience with the new releases](//dataplatformblogwebfd-d3h9cbawf0h8ecgf.b01.azurefd.net/wp-content/uploads/2026/03/figure-1-the-enhanced-developer-experience-with.png)
111+
112+
*Figure 1: The enhanced developer experience with the new releases.*
113+
114+
## Preview availability
115+
116+
- [Selective Branching](https://aka.ms/AAz2i48) (Preview)
117+
- [Compare Code Changes](https://aka.ms/AAzydxy) (Preview)
118+
- Branched Workspaces (Preview), expected to be available by the end of March 2026
119+
120+
These capabilities are part of **Fabric Git Integration** and work with supported Git providers.
121+
122+
## Related announcement
123+
124+
The post also points readers to Arun Ulag’s blog for broader FabCon and SQLCon 2026 announcements across Fabric and Microsoft’s database offerings:
125+
126+
- [FabCon and SQLCon 2026: Unifying databases and Fabric on a single, complete platform](https://aka.ms/FabCon-SQLCon-2026-news)
127+
128+
[Read the entire article](https://blog.fabric.microsoft.com/en-US/blog/introducing-new-git-developer-experiences-in-microsoft-fabric-preview/)
129+

‎scripts/data/processed-entries.json‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29296,5 +29296,17 @@
2929629296
"timestamp": "2026-03-20 21:11:52 +00:00",
2929729297
"canonical_url": "https://blog.fabric.microsoft.com/en-US/blog/instantly-run-and-preview-functions-in-microsoft-fabric-eventhouse-no-code-required/",
2929829298
"collection": "news"
29299+
},
29300+
{
29301+
"reason": "Succesfully added: No generic exclusion rules apply (English, technical content, not job/business-only, not community-short, not a sales pitch). Assigned DevOps because the article is centered on CI/CD automation, Git versioning, pull request workflows, and build/release pipelines (DevOps rules 5, 8, 11). Assigned ML because it is Microsoft Fabric platform content; Fabric is explicitly included under ML for data/analytics platform services (ML rule 1), and the APIs are about deploying Fabric artifacts like notebooks, pipelines, reports, and semantic models. Did not assign Azure/.NET/AI/Security/GitHub Copilot because the post does not focus on Azure services, .NET development, AI services, security implementation, or GitHub Copilot.",
29302+
"timestamp": "2026-03-21 00:28:27 +00:00",
29303+
"canonical_url": "https://blog.fabric.microsoft.com/en-US/blog/introducing-bulk-export-and-import-apis-for-ci-cd-in-microsoft-fabric-preview/",
29304+
"collection": "news"
29305+
},
29306+
{
29307+
"reason": "Succesfully added: No generic exclusion rules apply: the content is English, technical, and not job/career-focused, not question-only, and not primarily promotional. \n\nIncluded DevOps because the article is centered on Git-based developer workflows in Fabric: Git integration, feature branching, diff/compare, conflict inspection, and a CI workflow including pull requests (DevOps inclusion rules 5, 8, and 11).\n\nIncluded ML because Microsoft Fabric is a data/analytics platform and the post is specifically about developer/engineering experiences inside Fabric workspaces and CI/CD for Fabric artifacts (ML inclusion rule 1: Microsoft Fabric). \n\nExcluded Azure: while the image is hosted on an Azure-fronted domain, the substantive content is about Microsoft Fabric Git features rather than Azure services or Azure architecture.\n\nExcluded AI, GitHub Copilot, .NET, and Security because the post does not discuss Microsoft AI services/frameworks, Copilot, .NET languages/frameworks, or security/identity controls.",
29308+
"timestamp": "2026-03-21 00:28:56 +00:00",
29309+
"canonical_url": "https://blog.fabric.microsoft.com/en-US/blog/introducing-new-git-developer-experiences-in-microsoft-fabric-preview/",
29310+
"collection": "news"
2929929311
}
2930029312
]

‎scripts/data/rss-cache/_blogs/Randy_Pagels_s_Blog/httpswwwcooknwithcopilotcomblogask-better-questions-get-better-codehtml.json‎

Lines changed: 0 additions & 14 deletions
This file was deleted.

‎scripts/data/rss-cache/_news/Microsoft_Fabric_Blog/httpsblogfabricmicrosoftcomen-USblogintroducing-bulk-export-and-import-apis-for-ci-cd-in-microsoft-f.json‎

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
{
2+
"FeedLevelAuthor": "Microsoft Fabric Blog",
3+
"Description": "If you haven’t already, check out Arun Ulag’s hero blog “FabCon and SQLCon 2026: Unifying databases and Fabric on a single, complete platform” for a complete look at all of our FabCon and SQLCon announcements across both Fabric and our database offerings. Enterprise DevOps teams expect automation, repeatability, and full control over their release pipelines. …\n\n[Continue reading “Introducing Bulk Export and Import APIs for CI/CD in Microsoft Fabric (Preview)”](https://blog.fabric.microsoft.com/en-us/blog/introducing-bulk-export-and-import-apis-for-ci-cd-in-microsoft-fabric-preview/)",
4+
"ProcessedDate": "2026-03-21 00:26:39",
5+
"Link": "https://blog.fabric.microsoft.com/en-US/blog/introducing-bulk-export-and-import-apis-for-ci-cd-in-microsoft-fabric-preview/",
6+
"Tags": [],
7+
"FeedName": "Microsoft Fabric Blog",
8+
"Author": "Microsoft Fabric Blog",
9+
"Title": "Introducing Bulk Export and Import APIs for CI/CD in Microsoft Fabric (Preview)",
10+
"FeedUrl": "https://blog.fabric.microsoft.com/en-us/blog/feed/",
11+
"OutputDir": "_news",
12+
"EnhancedContent": "*If you haven’t already, check out Arun Ulag’s hero blog “*[*FabCon and SQLCon 2026: Unifying databases and Fabric on a single, complete platform*](https://aka.ms/FabCon-SQLCon-2026-news)*” for a complete look at all of our FabCon and SQLCon announcements across both Fabric and our database offerings.*\n\nEnterprise DevOps teams expect automation, repeatability, and full control over their release pipelines. While Microsoft Fabric provides built‑in Git Integration and deployment experiences, many organizations also require additional **CI/CD capabilities** that integrate directly into their DevOps tooling and release processes.\n\nTo support these, we’re introducing the **Bulk Export and Import Item Definition APIs**—a new set of REST APIs in Preview.\n\n## CI/CD with Fabric item definitions as code\n\nEvery item in Microsoft Fabric—such as notebooks, pipelines, reports, and semantic models—are backed by a **structured item definition** that fully describes its configuration and content. The Bulk Export and Import APIs allow these definitions to be treated as **source code**:\n\n- Exported programmatically from a workspace\n- Stored and versioned in Git\n- Validated through pull request workflows\n- Promoted across environments using automated pipelines\n\nThis enables a clean separation between **authoring**, **review**, and **deployment**, aligning Fabric with established enterprise DevOps practices.\n\nGit‑based deployment using a build environment\n\nIn this CI/CD model, deployments across Microsoft Fabric workspaces are driven from a **central Git repository**, where Fabric item definitions are treated as code and promoted through a structured release flow. All environments—Dev, Test, and Prod—are aligned to the same main branch, while each stage is deployed independently using dedicated build and release pipelines.\n\nPipelines typically begin by exporting Fabric item definitions from a development workspace using **Fabric Git Integration** or the **Bulk Export API**. These definitions can then be validated in a build environment through automated checks, pull request reviews, and policy enforcement before promotion.\n\nDuring deployment, the pipeline invokes the **Bulk Import API** to promote approved item definitions into the target workspace. The API supports both creating new items and updating existing ones in place, while relying on Fabric’s built‑in dependency handling to ensure items are deployed in the correct order. This enables consistent, repeatable deployments into test and production environments without manual intervention.\n\n![Figure 1- Suggested build and release pipelines using bulk export/import API ](//dataplatformblogwebfd-d3h9cbawf0h8ecgf.b01.azurefd.net/wp-content/uploads/2026/03/figure-1-suggested-build-and-release-pipelines-us.png)*Figure 1: Suggested build and release pipelines using bulk export/import API*\n\nBuilt for scale and enterprise automation\n\nThe Bulk Export and Import APIs are optimized for:\n\n- Batch operations across large workspaces.\n- Long‑running, asynchronous execution.\n- Service principal and managed identity authentication.\n- Repeatable, auditable deployments across environments.\n\nThese capabilities make them especially well‑suited for enterprise CI/CD pipelines, disaster recovery workflows, and large‑scale environment promotion scenarios.\n\n## Get started\n\nThe Bulk Export and Import APIs are available as part of the Microsoft Fabric REST API surface in Preview. To learn more about supported item types, authentication, and best practices, see [the detailed Fabric API guide](https://aka.ms/AAzye0t).\n\nCheck out the [complete CI/CD tutorial using the Bulk Export and Import APIs](https://aka.ms/AAzye19) for a step‑by‑step example of this deployment model in action.\n\nAs always, we look forward to seeing how your teams use these APIs to build robust, automated CI/CD pipelines in Fabric—and we welcome your feedback in the comments as we continue to evolve the platform.",
13+
"PubDate": "2026-03-20T16:30:00+00:00"
14+
}

0 commit comments

Comments
 (0)