chore: Automate fabric workspace & fabric capacity creation in Workshop mode by Prajwal-Microsoft · Pull Request #343 · microsoft/agentic-applications-for-unified-data-foundation-solution-accelerator

Prajwal-Microsoft · 2026-04-20T12:40:46Z

Purpose

This pull request introduces several enhancements to the deployment process for Microsoft Fabric resources, focusing on the flexibility and automation of Fabric capacity and workspace management. It adds new parameters and logic for auto-creating or reusing Fabric capacities and workspaces, improves script robustness, and updates documentation and environment configuration to support these new features.

Fabric Capacity and Workspace Management Enhancements:

Added support for specifying an existing Fabric capacity (AZURE_FABRIC_CAPACITY_NAME) and its SKU (FABRIC_CAPACITY_SKU), as well as additional admin members (FABRIC_ADMIN_MEMBERS), allowing for more flexible and reusable deployments. [1] [2] [3] [4]
Introduced the CREATE_FABRIC_WORKSPACE flag to enable automatic creation of a Fabric workspace during the build script, with corresponding changes in environment variable handling and documentation. [1] [2] [3]

Deployment Script and Output Improvements:

Updated 00_build_solution.py to prompt for a workspace ID only if auto-creation is not enabled, persist the workspace ID to both .env and the azd environment, and dynamically adjust step labels and script parameters based on workspace creation mode. [1] [2] [3]
Ensured UTF-8 output for script logs, particularly on Windows, to avoid encoding issues with emoji or special characters. [1] [2]

Automation and Cleanup Hooks:

Added predown hooks for both Windows and POSIX systems to optionally clean up Fabric workspaces if CREATE_FABRIC_WORKSPACE is set, improving resource hygiene during teardown.
Refined post-provisioning instructions and logic in deployment hooks to better reflect the new workspace and capacity management options.

Documentation Updates:

Expanded documentation to describe the new parameters and environment variables for Fabric capacity and workspace management, making it easier for users to understand and configure these options.

These changes collectively provide a more robust, flexible, and user-friendly experience for deploying and managing Microsoft Fabric resources in both automated and interactive scenarios.

Does this introduce a breaking change?

Yes
No

Golden Path Validation

I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

...

Other Information

When isWorkshop=true and azureEnvOnly=false, Fabric Capacity is automatically provisioned via AVM Bicep module and Fabric Workspace is created via Fabric REST API in post-provision hook. Users can opt to use existing resources via env vars: - EXISTING_FABRIC_CAPACITY_NAME: use existing capacity - EXISTING_FABRIC_WORKSPACE_ID: use existing workspace - FABRIC_CAPACITY_SKU: configure capacity SKU (default: F2) Changes: - infra/main.bicep: Add Fabric Capacity AVM module (conditional) - infra/main.parameters.json: Add Fabric parameter mappings - infra/scripts/fabric/: New Fabric workspace automation scripts - azure.yaml: Add post-provision hook for workspace setup - docs: Update workshop guide and parameters documentation Resolves: ADO US #40274 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Prajwal-Microsoft · 2026-04-20T12:46:46Z

@@ -0,0 +1,80 @@
+"""


Lets add it the changes with in the 02 script, lets not have sub folder everything goes under scripts

Done — consolidated everything into scripts/02_create_fabric_items.py, deleted scripts/fabric/ subfolder.

- Inline workspace setup/cleanup into scripts/02_create_fabric_items.py - Remove scripts/fabric/ subfolder (workspace_setup.py, cleanup_workspace.py) - Remove infra/scripts/fabric/ (fabric_api.py, helpers/) - Add --cleanup flag for azd down predown hook - Update azure.yaml predown hook path - Match existing coding style (flat functions, AzureCliCredential) - Clear FABRIC_WORKSPACE_ID from .env on cleanup Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…s and fix indentation Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

… cleanup

Copilot

Pull request overview

This PR aims to automate Microsoft Fabric “workshop mode” provisioning by creating a Fabric capacity via IaC and auto-creating (or reusing) a Fabric workspace during the data/load step, plus adding a teardown hook to optionally delete the workspace on azd down.

Changes:

Add Bicep parameters/outputs and an AVM module to create or reuse a Fabric capacity in workshop mode.
Update the Fabric item creation pipeline to auto-create/reuse a Fabric workspace and add a --cleanup mode for teardown.
Update docs and azure.yaml hooks to reflect (and trigger) the new automated workflow.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 9 comments.

Show a summary per file

File	Description
workshop/docs/01-deploy/02-setup-fabric.md	Documents the new “automated Fabric setup” workflow and env vars.
scripts/02_create_fabric_items.py	Adds workspace auto-create/reuse logic, Fabric API helpers, and `--cleanup` deletion flow.
scripts/00_build_solution.py	Adjusts prompting/persistence for workspace id and improves quiet-mode subprocess output handling.
infra/main.parameters.json	Adds parameters for existing Fabric capacity name and capacity SKU.
infra/main.bicep	Adds Fabric capacity parameters, optional AVM capacity module, and outputs consumed by scripts.
documents/CustomizingAzdParameters.md	Documents new azd parameters related to Fabric capacity/workspace.
docs/Fabric_workspace_changes.md	Adds an explanatory doc describing the workspace creation/cleanup changes.
azure.yaml	Adds a `predown` cleanup hook and tweaks postprovision messaging logic.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-04-21T15:15:49Z

+!!! tip "Automated Fabric Setup (Recommended)"
+    When running in **workshop mode** (default), Fabric Capacity and Workspace are **automatically created** during `azd up`. No manual steps are needed unless you want to use existing resources.
+


The doc says Fabric Capacity and Workspace are automatically created during azd up, but in this PR only the capacity is created by Bicep; the workspace is created later by scripts/02_create_fabric_items.py when step 02 runs (or when FABRIC_WORKSPACE_ID is provided). Please update this wording so users don’t expect a workspace to exist immediately after azd up.

Fixed — updated wording to clarify that capacity is created during azd up and workspace is created later by the build script when CREATE_FABRIC_WORKSPACE is enabled.

Copilot · 2026-04-21T15:15:49Z

+      ```
+    - To use an **existing Fabric workspace**, set:
+      ```bash
+      azd env set EXISTING_FABRIC_WORKSPACE_ID "your-workspace-id"


This page instructs users to set EXISTING_FABRIC_WORKSPACE_ID, but no code/infra in this PR reads that variable (workspace reuse is driven by FABRIC_WORKSPACE_ID). Either wire EXISTING_FABRIC_WORKSPACE_ID through to FABRIC_WORKSPACE_ID (or a new infra param) or change the docs to reference the supported variable.

Suggested change

azd env set EXISTING_FABRIC_WORKSPACE_ID "your-workspace-id"

azd env set FABRIC_WORKSPACE_ID "your-workspace-id"

Fixed — docs now reference FABRIC_WORKSPACE_ID consistently.

Copilot · 2026-04-21T15:15:50Z

 | `DEPLOYING_USER_PRINCIPAL_TYPE`           | string  | `User`                   | Principal type of deployer (allowed: `User`, `ServicePrincipal`).          |
+| `EXISTING_FABRIC_CAPACITY_NAME`           | string  | ` `                      | Use an existing Fabric capacity instead of creating a new one. If empty, a new capacity is auto-created in workshop mode. |
+| `FABRIC_CAPACITY_SKU`                     | string  | `F2`                     | SKU tier for the Fabric capacity (allowed: `F2` through `F2048`).          |
+| `EXISTING_FABRIC_WORKSPACE_ID`            | string  | ` `                      | Use an existing Fabric workspace instead of creating a new one. If empty, a new workspace is auto-created in workshop mode. |


The parameter table adds EXISTING_FABRIC_WORKSPACE_ID, but it is not referenced anywhere else in the repo (scripts use FABRIC_WORKSPACE_ID, infra only supports existing capacity). Please remove/replace this entry or implement the end-to-end support so the documented parameter actually works.

Suggested change

| `EXISTING_FABRIC_WORKSPACE_ID` | string | ` ` | Use an existing Fabric workspace instead of creating a new one. If empty, a new workspace is auto-created in workshop mode. |

| `FABRIC_WORKSPACE_ID` | string | ` ` | Use an existing Fabric workspace instead of creating a new one. If empty, a new workspace is auto-created in workshop mode. |

Fixed — replaced FABRIC_WORKSPACE_ID and FABRIC_WORKSPACE_NAME with CREATE_FABRIC_WORKSPACE flag and FABRIC_ADMIN_MEMBERS parameter.

Copilot · 2026-04-21T15:15:50Z

+def make_request(method, url, **kwargs):
+    """Make request with retry logic for 429 rate limiting"""
+    max_retries = 5
+    for attempt in range(max_retries):
+        response = requests.request(method, url, headers=get_headers(), **kwargs)
+        if response.status_code == 429:
+            retry_after = int(response.headers.get("Retry-After", 30))
+            print(f"  Rate limited. Waiting {retry_after}s...")
+            time.sleep(retry_after)
+            continue
+        return response
+    return response


make_request() does not set a network timeout, so a hung TCP connection can block the entire provisioning flow indefinitely. Consider adding a default timeout (and allowing override via kwargs) so CI/automation doesn’t stall on transient network issues.

Fixed — added kwargs.setdefault("timeout", 60) as default, overridable via kwargs.

Copilot · 2026-04-21T15:15:51Z

+      run: python scripts/02_create_fabric_items.py --cleanup
+      shell: pwsh
+      continueOnError: true
+      interactive: true
+    posix:
+      run: python scripts/02_create_fabric_items.py --cleanup


The new predown hook runs workspace cleanup unconditionally and is marked interactive: true, but the cleanup script prompts for confirmation. In non-interactive runs (CI or azd down --no-prompt), this can block teardown. Consider gating the hook on AZURE_ENV_ONLY/IS_WORKSHOP, or passing a non-interactive flag to the script once supported.

Suggested change

run: python scripts/02_create_fabric_items.py --cleanup

shell: pwsh

continueOnError: true

interactive: true

posix:

run: python scripts/02_create_fabric_items.py --cleanup

run: |

$isWorkshop = $env:IS_WORKSHOP

$azureEnvOnly = $env:AZURE_ENV_ONLY

if ($isWorkshop -eq "true" -and $azureEnvOnly -ne "true") {

python scripts/02_create_fabric_items.py --cleanup

} else {

Write-Host "Skipping Fabric cleanup for non-workshop or Azure-env-only teardown."

}

shell: pwsh

continueOnError: true

interactive: true

posix:

run: |

IS_WORKSHOP_VAL="${IS_WORKSHOP:-}"

AZURE_ENV_ONLY_VAL="${AZURE_ENV_ONLY:-}"

if [ "$IS_WORKSHOP_VAL" = "true" ] && [ "$AZURE_ENV_ONLY_VAL" != "true" ]; then

python scripts/02_create_fabric_items.py --cleanup

else

echo "Skipping Fabric cleanup for non-workshop or Azure-env-only teardown."

fi

Fixed — predown hook is now gated on CREATE_FABRIC_WORKSPACE=true. Also added --yes flag for non-interactive cleanup.

Copilot · 2026-04-21T15:15:51Z

+            confirm = input(f"\n  Delete workspace '{ws_name}' ({workspace_id})? [y/N]: ").strip().lower()
+            if confirm != "y":
+                print("  Skipped workspace deletion.")
+                return


--cleanup always prompts for confirmation via input(). When invoked from azd down (or any non-interactive environment), this can hang teardown indefinitely. Suggest adding a non-interactive/auto-confirm option (e.g., --yes or env var) and/or skipping deletion when stdin isn’t a TTY.

Fixed — added --yes/-y flag that skips the confirmation prompt for non-interactive environments.

Copilot · 2026-04-21T15:15:51Z

+var fabricCapacityDefaultAdmins = deployer().?userPrincipalName == null
+  ? [deployer().objectId]
+  : [deployer().userPrincipalName]


fabricAdminMembers is documented as an array of object IDs, but fabricCapacityDefaultAdmins uses deployer().userPrincipalName when present. This mismatch can break deployments (and also makes the output AZURE_FABRIC_CAPACITY_ADMINISTRATORS ambiguous). Please either pass deployer().objectId consistently or update the parameter description/type expectations to match what the AVM module requires.

Suggested change

var fabricCapacityDefaultAdmins = deployer().?userPrincipalName == null

? [deployer().objectId]

: [deployer().userPrincipalName]

var fabricCapacityDefaultAdmins = [deployer().objectId]

Fixed — changed to [deployer().objectId] consistently as suggested.

Copilot · 2026-04-21T15:15:52Z

        $isWorkshop = $env:IS_WORKSHOP
        $deployApp = $env:AZURE_ENV_DEPLOY_APP
+        $azureEnvOnly = $env:AZURE_ENV_ONLY



$azureEnvOnly is assigned but never used in this hook script. Please remove it or use it to conditionally print Fabric/Azure-only guidance so the hook stays easy to maintain.

Copilot · 2026-04-21T15:15:52Z

      run: |
-        if [ "$IS_WORKSHOP" != "true" ] || [ "$AZURE_ENV_DEPLOY_APP" = "true" ]; then
+        IS_WORKSHOP_VAL="${IS_WORKSHOP:-}"
+        AZURE_ENV_ONLY_VAL="${AZURE_ENV_ONLY:-}"


AZURE_ENV_ONLY_VAL is set but never used in the POSIX postprovision hook. Please remove it or use it for conditional messaging to avoid dead variables.

Suggested change

AZURE_ENV_ONLY_VAL="${AZURE_ENV_ONLY:-}"

… Fabric workspace docs

Prajwal-Microsoft · 2026-04-21T16:27:25Z

 | `DEPLOYING_USER_PRINCIPAL_TYPE`           | string  | `User`                   | Principal type of deployer (allowed: `User`, `ServicePrincipal`).          |
+| `EXISTING_FABRIC_CAPACITY_NAME`           | string  | ` `                      | Use an existing Fabric capacity instead of creating a new one. If empty, a new capacity is auto-created in workshop mode. |
+| `FABRIC_CAPACITY_SKU`                     | string  | `F2`                     | SKU tier for the Fabric capacity (allowed: `F2` through `F2048`).          |
+| `FABRIC_WORKSPACE_ID`                     | string  | ` `                      | Use an existing Fabric workspace instead of creating a new one. If empty, a new workspace is auto-created in workshop mode. |


I see that these variables are not used while deployment, we can remove both Workspace id and workspace name

Done — removed both FABRIC_WORKSPACE_ID and FABRIC_WORKSPACE_NAME from the parameters table. Replaced with CREATE_FABRIC_WORKSPACE flag and FABRIC_ADMIN_MEMBERS.

Prajwal-Microsoft · 2026-04-21T16:29:06Z

+param fabricCapacitySku string = 'F2'
+
+@description('Optional. An array of user object IDs or service principal object IDs that will be assigned the Fabric Capacity Admin role.')
+param fabricAdminMembers array = []


This should be mapped tom main.paramaters.json, else users might need to manaully edit bicep file, also include that in CustominzingAzdParameters.md

Done — added fabricAdminMembers mapping to main.parameters.json as FABRIC_ADMIN_MEMBERS and documented it in CustomizingAzdParameters.md.

… flag, timeout, --yes flag, fix docs - Add CREATE_FABRIC_WORKSPACE env flag (default false) to control workspace creation - Add default timeout (60s) to make_request() to prevent hanging - Add --yes/-y flag for non-interactive cleanup in CI - Gate predown hook on CREATE_FABRIC_WORKSPACE - Fix fabricCapacityDefaultAdmins to use objectId consistently - Map fabricAdminMembers to main.parameters.json - Remove unused azureEnvOnly vars from postprovision hooks - Update docs: clarify workspace creation timing, add new params Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

- Update Fabric_workspace_changes.md to reflect CREATE_FABRIC_WORKSPACE flag - Restore AZURE_ENV_ONLY vars in postprovision hooks Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…workspace creation options

… clarity and consistency

…e clarity in main.bicep and main.parameters.json

Prajwal-Microsoft · 2026-04-27T04:43:46Z

 ### 5. Build the solution

-#### Retrieve your Fabric workspace ID
+This step runs `scripts/00_build_solution.py`, which creates (or uses) the Fabric workspace, loads the sample data, creates the Ontology and Data Agent, and publishes the MCP endpoint.


No need to mention details of the script it runs

Prajwal-Microsoft · 2026-04-27T04:44:37Z

+
+Let the build script create the workspace for you. Set this flag before running Section 5:
+
+```bash


This has to be ran before azd up

…an docs - Remove fabricWorkspaceId param from main.bicep - Add createFabricWorkspace bool param to main.bicep - Update shouldCreateFabricCapacity condition and outputs - Update main.parameters.json mapping - Recompile main.json from Bicep - Remove script implementation details from docs - Rewrite Section 1b/1c options and automation tip - Add optional env flags before azd up in Section 3 - Fix garbled box-drawing characters in customdata tree Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…wn hook Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Yamini-Microsoft and others added 2 commits April 17, 2026 23:06

Move Fabric workspace creation to scripts pipeline, auto-detect from env

ba35a0c

Prajwal-Microsoft requested review from Avijit-Microsoft, Roopan-Microsoft, Vinay-Microsoft, aniaroramsft, brittneek, malrose07, nchandhi and toherman-msft as code owners April 20, 2026 12:40

Prajwal-Microsoft had a problem deploying to production April 20, 2026 12:41 — with GitHub Actions Failure

Prajwal-Microsoft commented Apr 20, 2026

View reviewed changes

Yamini-Microsoft had a problem deploying to production April 20, 2026 19:29 — with GitHub Actions Failure

Normalize print statements: replace emoji with [OK]/[FAIL]/[WARN] tag…

7ef2925

…s and fix indentation Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Yamini-Microsoft had a problem deploying to production April 20, 2026 19:39 — with GitHub Actions Failure

Sync FABRIC_WORKSPACE_ID to azd env (.azure/<env>/.env) on create and…

42b19e0

… cleanup

Yamini-Microsoft had a problem deploying to production April 21, 2026 15:06 — with GitHub Actions Failure

Prajwal-Microsoft requested a review from Copilot April 21, 2026 15:10

Copilot started reviewing on behalf of Prajwal-Microsoft April 21, 2026 15:11 View session

Copilot AI reviewed Apr 21, 2026

View reviewed changes

Fix docs: EXISTING_FABRIC_WORKSPACE_ID -> FABRIC_WORKSPACE_ID, update…

9173430

… Fabric workspace docs

Yamini-Microsoft had a problem deploying to production April 21, 2026 15:17 — with GitHub Actions Failure

Prajwal-Microsoft commented Apr 21, 2026

View reviewed changes

Yamini-Microsoft had a problem deploying to production April 21, 2026 19:01 — with GitHub Actions Failure

Update docs and restore AZURE_ENV_ONLY_VAL in azure.yaml

a68ee94

- Update Fabric_workspace_changes.md to reflect CREATE_FABRIC_WORKSPACE flag - Restore AZURE_ENV_ONLY vars in postprovision hooks Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Yamini-Microsoft had a problem deploying to production April 21, 2026 19:49 — with GitHub Actions Failure

Merge branch 'microsoft:main' into psl-automate-fabric-workshop

a14242f

Yamini-Microsoft had a problem deploying to production April 23, 2026 16:33 — with GitHub Actions Failure

feat: Enhance Fabric setup and configuration documentation; automate …

d00121d

…workspace creation options

Yamini-Microsoft had a problem deploying to production April 24, 2026 08:13 — with GitHub Actions Failure

Yamini-Microsoft added 2 commits April 24, 2026 16:48

fix: Update documentation for Fabric setup and configuration; improve…

0a966b2

… clarity and consistency

refactor: Rename parameters for Fabric capacity and workspace; improv…

b98e90a

…e clarity in main.bicep and main.parameters.json

Yamini-Microsoft had a problem deploying to production April 24, 2026 11:20 — with GitHub Actions Failure

chore: Remove outdated Fabric workspace management documentation

362afaf

Yamini-Microsoft had a problem deploying to production April 24, 2026 11:42 — with GitHub Actions Failure

Prajwal-Microsoft changed the title ~~Psl automate fabric workshop~~ chore: Automate fabric workspace & fabric capacity creation in Workshop mode Apr 27, 2026

Prajwal-Microsoft commented Apr 27, 2026

View reviewed changes

Yamini-Microsoft and others added 5 commits April 27, 2026 11:46

revert 02-setup-fabric.md to original, add only auto-create tip

ca22a8a

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

revert unrelated postprovision changes in azure.yaml, keep only predo…

c1380fc

…wn hook Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

change default Fabric capacity SKU from F2 to F8

c3477a9

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

fix garbled emoji in commented-out ontology section

e0ac3f5

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

		!!! tip "Automated Fabric Setup (Recommended)"
		When running in workshop mode (default), Fabric Capacity and Workspace are automatically created during `azd up`. No manual steps are needed unless you want to use existing resources.

	azd env set EXISTING_FABRIC_WORKSPACE_ID "your-workspace-id"
	azd env set FABRIC_WORKSPACE_ID "your-workspace-id"

	\| `EXISTING_FABRIC_WORKSPACE_ID` \| string \| ` ` \| Use an existing Fabric workspace instead of creating a new one. If empty, a new workspace is auto-created in workshop mode. \|
	\| `FABRIC_WORKSPACE_ID` \| string \| ` ` \| Use an existing Fabric workspace instead of creating a new one. If empty, a new workspace is auto-created in workshop mode. \|


		Let the build script create the workspace for you. Set this flag before running Section 5:

		```bash

Conversation

Prajwal-Microsoft commented Apr 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Purpose

Does this introduce a breaking change?

Golden Path Validation

Deployment Validation

What to Check

Other Information

Uh oh!

Prajwal-Microsoft Apr 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Apr 21, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 21, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 21, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 21, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 21, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 21, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 21, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 21, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 21, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Prajwal-Microsoft commented Apr 20, 2026 •

edited

Loading

Prajwal-Microsoft Apr 20, 2026 •

edited

Loading