feat: Merging the naming standard changes from dev to main

[Abdul-Microsoft]

Purpose

• This pull request introduces several updates across documentation and infrastructure code to enhance clarity, improve naming conventions, and add new configurations. The most significant changes include the removal of the AZURE_AISERVICE_LOCATION parameter, the addition of new parameters for Jumpbox and Cosmos DB in the documentation, and the adoption of a consistent abbreviation-based naming convention in the infrastructure code.

Documentation Updates:

• Removed the AZURE_AISERVICE_LOCATION parameter from both docs/CustomizingAzdParameters.md and docs/DeploymentGuide.md. This parameter is no longer required for AI services. [1] [2]
• Added new parameters for Jumpbox (AZURE_ENV_JUMPBOX_ADMIN_USERNAME, AZURE_ENV_JUMPBOX_ADMIN_PASSWORD) and Cosmos DB (AZURE_ENV_COSMOS_SECONDARY_LOCATION) in the documentation to support additional configuration options. [1] [2]

Infrastructure Code Updates:

• Introduced an abbreviation-based naming convention for resources in infra/main.bicep and its modules. For example, updated resource names for managed identities, log analytics, AI services, storage accounts, and more. This change ensures consistency and reduces name length. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
• Added private endpoint configurations for various modules (e.g., Key Vault, Cosmos DB, Storage Account) to enhance security by enabling private networking. [1] [2] [3] [4]
• Modified network configurations to update naming conventions for network security groups and bastion host resources. [1] [2] [3] [4] [5] [6]

New Features:

• Added support for loading abbreviations from an external JSON file (abbreviations.json) in infra/main.bicep, enabling dynamic and centralized management of resource name prefixes.
• Configured public IP address objects for Bastion Host in infra/modules/network/bastionHost.bicep, allowing customization of public IP settings.

These changes collectively improve the maintainability, security, and configurability of the deployment templates.

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

[github-actions]

🎉 This PR is included in version 1.4.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀