chore: dev to main merge

[Saswato-Microsoft]

Purpose

This pull request introduces several improvements and clarifications to the deployment process, infrastructure configuration, and documentation for the accelerator. The main changes enhance automation for service principal handling, clarify and standardize VM credential management, update quota check instructions, and improve workflow triggers and environment variable handling for CI/CD. These updates aim to make deployments more reliable, transparent, and user-friendly.

Infrastructure and Workflow Automation:

• Service principal handling is now automated: the workflows resolve and set AZURE_PRINCIPAL_ID dynamically if not provided, and use AZURE_PRINCIPAL_TYPE with a default of 'ServicePrincipal'. This ensures correct role assignments and RBAC configuration during deployment. (.github/workflows/azure-dev.yml, infra/main.bicepparam, [1] [2] [3]
• The GitHub Actions workflows now check out submodules recursively and are triggered only on infrastructure-related changes, reducing unnecessary runs and ensuring all dependencies are present. (.github/workflows/azd-template-validation.yml, .github/workflows/azure-dev.yml, [1] [2] [3]

VM Credential Management and Documentation:

• The process for setting and retrieving Jump VM admin credentials is standardized: environment variables (VM_ADMIN_USERNAME, VM_ADMIN_PASSWORD) are now the recommended method, with clear fallbacks and defaults (testvmuser for username, a default password). Documentation is updated to reflect this across guides and troubleshooting sections. (infra/main.bicepparam, docs/ACCESSING_PRIVATE_RESOURCES.md, docs/deploymentguide.md, docs/post_deployment_steps.md, [1] [2] [3] [4] [5]

Quota Check and Model/Capacity Documentation:

• The quota check documentation is expanded to cover both AI model and Microsoft Fabric capacity requirements, with updated default values, sample output, and clear instructions for both Bash and PowerShell usage. (docs/quota_check.md, [1] [2]

Other Notable Improvements:

• The required Bicep version is now specified in azure.yaml to ensure compatibility. (azure.yaml, azure.yamlR5)
• Resource group creation is automated in the workflow if it does not exist, further reducing manual setup steps. (.github/workflows/azure-dev.yml, .github/workflows/azure-dev.ymlL27-R96)

Let me know if you want to walk through any of these changes in detail or see how they impact your development workflow!

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