feat: EXP environment changes for Existing Resource Group & Fabric workspace

[Yamini-Microsoft]

Purpose

• Resource Group Reuse
  *Accept the existing Resource Group name as a parameter in the Bicep templates.
  *Ensure Bicep scripts do not attempt to create the Resource Group if it already exists.
  *Validate that all resources deploy into this specified Resource Group.

• Fabric Workspace Reuse
  *Accept the existing Microsoft Fabric Workspace details (ID or name) as an input parameter.
  *Reference it in relevant components (e.g., if using Synapse, Data Factory, Power BI, etc.).
  *Avoid creating a new Fabric Workspace in the template.

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

[Copilot]

Pull Request Overview

This PR enhances deployment flexibility by allowing reuse of existing Azure Resource Groups and Microsoft Fabric workspaces, updates project dependencies to newer versions, and refines deployment scripts and documentation.

• Parameterize Bicep templates and PowerShell scripts to accept existing resource group and environment inputs.
• Add a resourcePrefix.bicep helper and update deployAzureResources.ps1 for interactive RG selection.
• Bump package versions across multiple projects from 8.x to 9.x (and related updates) and refine deployment docs.

Reviewed Changes

Copilot reviewed 13 out of 16 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
Services/src/kernel-memory/service/**/*.csproj	Updated dependency versions from 8.x to 9.x (various Microsoft.Extensions and other)
Deployment/scripts/resourcePrefix.bicep	New script to compute a consistent resource name prefix based on subscription & env
Deployment/scripts/deployAzureResources.ps1	Script now prompts for RG and environment, supports creating or reusing an RG
Deployment/bicep/main_services.bicep	Removed RG creation resource, scoped modules to resourceGroup(), added parameters
Deployment/DeployFabric.md	Clarified step for creating or reusing an existing Fabric Lakehouse
Deployment/DeployAzureResources.md	Added guidance for specifying or auto-generating an RG and environment name

Comments suppressed due to low confidence (3)

Deployment/bicep/main_services.bicep:1

• The file no longer contains the original license header; re-adding a license comment at the top helps maintain attribution and clarity on usage terms.

targetScope = 'resourceGroup'

Deployment/bicep/main_services.bicep:146

• [nitpick] Hardcoding the location limits flexibility; consider exposing the region as a parameter instead of using literal values like 'eastus'.

    location: 'eastus'

Deployment/DeployFabric.md:27

• [nitpick] Using emphasis (*) inside a Markdown header can render inconsistently; consider removing the italics markup to keep the header plain and clear.

##  Step 1: *Create or Use an Existing Fabric Lakehouse

[Copilot]

[nitpick] The message is printed when $resourceGroupName is empty; consider moving or updating this line into the else block or changing it to reflect that no RG was provided.

Suggested change

	Write-Host "Using provided resource group: $resourceGroupName"
	Write-Host "No resource group name provided. A new resource group will be generated." -ForegroundColor Yellow

[Copilot]

[nitpick] This package version (9.0.0) does not match the 9.0.3 used for other Microsoft.Extensions.* dependencies; aligning them improves consistency.

Suggested change

	<PackageReference Include="Microsoft.Extensions.Configuration.Json" Version="9.0.0" />
	<PackageReference Include="Microsoft.Extensions.Configuration.Json" Version="9.0.3" />

[Copilot]

Add a space after the period in prod).This to improve readability.

Suggested change

	+ **Environment Name** - A unique environment name (e.g., dev, test, prod).This is used to scope resource names and group deployments logically.
	+ **Environment Name** - A unique environment name (e.g., dev, test, prod). This is used to scope resource names and group deployments logically.