feat: existing resources support with azd up

[Yamini-Microsoft]

Purpose

• This pull request introduces significant improvements to the deployment process by adding support for reusing existing Azure resources and simplifying the documentation for customizing deployments. The changes enhance flexibility for users who want to leverage existing Event Hub namespaces, Event Hubs, and Fabric Capacities, and provide clearer instructions for advanced configuration scenarios.

Deployment customization and resource reuse:

• Added parameters in infra/main.bicep to allow the use of existing Event Hub Namespace, Event Hub, and Fabric Capacity, enabling deployments to reuse resources instead of always creating new ones.
• Updated resource creation logic in infra/main.bicep to conditionally reference or create Event Hub Namespace and Event Hub based on provided parameters, and to conditionally create Fabric Capacity. [1] [2]
• Modified outputs in infra/main.bicep to reflect whether existing resources were used and to provide additional deployment context, such as resource group location and usage flags.

Documentation improvements:

• Refactored docs/DeploymentGuide.md to clarify advanced configuration, grouping environment variable settings by common scenarios (alert email, resource reuse), and providing detailed instructions for deploying with existing resources.
• Added collapsible sections in docs/DeploymentGuide.md for permission checks, tool verification, and deployment options, making the guide more navigable and user-friendly. [1] [2] [3] [4] [5] [6] [7] [8]
• Updated troubleshooting guidance in docs/DeploymentGuide.md to reference a dedicated troubleshooting document for common deployment issues.

Other improvements:

• Revised post-deployment instructions to direct users to a summary of deployed resources rather than a list of features, streamlining next steps.
• Added parameter and variable section headers in infra/main.bicep for better readability and maintainability. [1] [2]

These changes together make deployments more flexible, documentation clearer, and troubleshooting easier for users.

Does this introduce a breaking change?

• Yes
• No

How to Test

• Get the code

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

• Test the code

What to Check

Verify that the following are valid

• ...

Other Information

[Copilot]

Pull request overview

This pull request introduces support for reusing existing Azure resources (Event Hub Namespace, Event Hub, and Fabric Capacity) during deployment, enabling cost optimization and flexibility for users who want to leverage pre-existing infrastructure. The PR also refactors the deployment documentation to provide clearer, more organized guidance with collapsible sections and specific instructions for using existing resources.

Changes:

• Added Bicep parameters and conditional logic to support existing Event Hub Namespace, Event Hub, and Fabric Capacity resources
• Updated Python deployment script to resolve Event Hub resource group correctly when reusing existing resources
• Reorganized deployment documentation with collapsible sections and comprehensive instructions for resource reuse scenarios

Reviewed changes

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

File	Description
infra/main.bicep	Added parameters for existing resources, implemented conditional resource creation logic, and updated outputs to reflect resource usage
infra/main.parameters.json	Added parameter mappings for existing resource names from environment variables
infra/scripts/fabric/deploy_fabric_rti.py	Added Event Hub resource group resolution logic and reformatted docstring for better readability
docs/DeploymentGuide.md	Restructured documentation with collapsible sections, added detailed instructions for using existing resources, and clarified deployment requirements

---

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