fix: Update AVM & Bicep modules and resource versions

[Akhileswara-Microsoft]

Purpose

This pull request updates the infrastructure as code for the solution accelerator, focusing on modernizing resource definitions, upgrading AVM module versions, and improving compatibility with current Azure best practices. The main changes include updating module versions, resource API versions, and aligning parameters with the latest standards.

These updates collectively ensure the solution remains compatible with the latest Azure platform features and best practices, while improving maintainability and future-proofing the deployment scripts.

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.

[Copilot]

Pull request overview

This PR modernizes the solution’s IaC by upgrading AVM Bicep module versions and Azure resource API versions, aiming to align deployments with newer Azure/AVM schemas and best practices.

Changes:

• Bump multiple AVM modules (networking, storage, Cosmos DB, Container Apps, Bastion, identity, monitoring) to newer versions.
• Update several ARM resource API versions (e.g., Log Analytics workspace, Cognitive Services resources, tags).
• Adjust parameter/property names to match updated module contracts (e.g., availabilityZones, availabilityZone, Cosmos failover/role definition properties, Container Apps logging config).

Reviewed changes

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

Show a summary per file

File	Description
infra/modules/virtualNetwork.bicep	Updates AVM module versions for NSG and VNet.
infra/modules/storageAccount.bicep	Updates AVM common types + storage account module version.
infra/modules/role.bicep	Updates Cognitive Services API version for existing account reference.
infra/modules/cosmosDb.bicep	Updates AVM common types, Cosmos role definition API version, and Cosmos AVM module version.
infra/modules/ai-services-deployments.bicep	Updates AVM common types and Cognitive Services API versions (account + deployments).
infra/modules/ai-project.bicep	Updates Cognitive Services API versions for projects.
infra/main_custom.bicep	Upgrades AVM modules and updates several schema-aligned parameters in the “custom” main template.
infra/main.bicep	Upgrades AVM modules and updates several schema-aligned parameters in the primary main template.

---

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

[Akhileswara-Microsoft]

@copilot resolve the merge conflicts in this pull request

[Copilot]

@copilot resolve the merge conflicts in this pull request

Merge conflicts have been resolved in commit 8dd27f6.

The conflicts were in infra/main.bicep, infra/main_custom.bicep, and infra/main.json. Here's how each was resolved:

infra/main.bicep (3 conflicts):

• Added the new processControlCosmosContainerName variable from dev, while keeping the updated Cosmos DB module version 0.19.0 from this branch
• Moved processorContainerAppName variable declaration before containerAppBackend (as introduced in dev), while keeping the newer container app module version 0.22.0
• Removed the duplicate processorContainerAppName declaration near containerAppProcessor (since it's now declared earlier), keeping version 0.22.0

infra/main_custom.bicep (2 conflicts): Same pattern — moved the processorContainerAppName variable and removed its duplicate, keeping module version 0.22.0.

infra/main.json: Kept our branch's compiled ARM template (which reflects the updated AVM module versions).

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• aka.ms
  • Triggering command: /usr/local/bin/bicep bicep build infra/main.bicep --outfile infra/main.json (dns block)
• centralus.data.mcr.microsoft.com
  • Triggering command: /usr/local/bin/bicep bicep build infra/main.bicep --outfile infra/main.json (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)