feat: Changes for reuse of resource group and log analytics while deployment

[NirajC-Microsoft]

##Purpose

• Made changes in bicep files to reuse Resource group and Log Analytics workspace while deployment, removed existing code resource group creation and added condition in Monitor.bicep to check if existing Log Analytics workspace is provided or not.

Does this introduce a breaking change?

• Yes
• No

How to Test

• Run command - azd auth login
• To use existing log analytics run this command otherwise you can skip if you wanted to create new resource - azd env set AZURE_ENV_LOG_ANALYTICS_WORKSPACE_ID "/subscriptions//resourcegroups//providers/microsoft.operationalinsights/workspaces/"
• Run command - azd up
• I will not create log analytics resource it will use log analytics which you want to reuse

• ---

• To verify Resource Group changes run command - azd up
• enter/select all details.
• After selecting region it will ask user to select existing resource group or create new resource group

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

• Test the code

What to Check

Verify that the following are valid

• ...

Other Information

[Copilot]

Pull Request Overview

This PR enables reusing an existing Resource Group and Log Analytics workspace during deployments by introducing a parameter for the workspace ID and converting all modules to target the current resource group rather than creating a new one.

• Added existingLogAnalyticsResourceId parameter in main.bicepparam and main.bicep
• Switched targetScope to resourceGroup, removed explicit Resource Group creation, and updated module scopes
• Enhanced the monitoring module to conditionally create a new Log Analytics workspace or use an existing one

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
infra/main.bicepparam	Added existingLogAnalyticsResourceId parameter
infra/main.bicep	Changed targetScope, removed RG creation, updated module scopes, added existingLogAnalyticsResourceId
infra/core/monitor/monitoring.bicep	Conditional loganalytics module, variables for existing workspace
azure.yaml	Added infra provider configuration for Bicep path

Comments suppressed due to low confidence (1)

infra/core/monitor/monitoring.bicep:13

• New conditional logic for creating or reusing Log Analytics workspace should be covered by tests (e.g., ensure both branches produce the expected outputs).

module logAnalytics 'loganalytics.bicep' = if (!useExistingLogAnalytics) {

[Copilot]

Since targetScope is set to resourceGroup, these explicit scope declarations are redundant and could be removed to simplify the module declarations.

Suggested change

	scope: resourceGroup(resourceGroup().name)
	// scope declaration removed as it is redundant

[Prajwal-Microsoft]

Move this to monitoring.bicep to keep the main.bicep clean

[NirajC-Microsoft]

This logic is already present in monitoring.bicep