Use this repo and README.md there to extend the current README with more instructions.

Alternatively, this repo contains nice solution diagram as well.

The reference architecture for this template should deploy (or conditionally deploy) key resources. This code needs to be available and linked in the azure.yaml manifest.

Use the following docs page as a reference.

Requirements:

• App Service Standard Plan
• Enabled VNet integration
• Key Vault
• App Insights (new or BYO)
• VNet (new or BYO)
• Function App v3 runtime - PowerShell
• Storage account

Update the .devcontainer configuration with a full authoring experience for Bicep.

Use this repo as a source.

Add .devcontainer configuration, so this project can be opened as a Dev Container in VS Code or as a Codespace on GitHub.

• Add PowerShell and Azure Functions extensions
• Add GitHub Pull Request & Issues and Bicep extensions

Use this repo as a reference.

Build a structure similar to this sample, so it can be used as a template for azd.

DoD for Bicep code:

• Validate, compile, and test the code.
• Extend the modules / templates with VNet integration and Private Endpoint.
• Deploy all components in the GUI and reverse engineer (import existing resources) to Bicep templates.

Add the .vscode directory with a fine-tuned configuration for this template.

Use func CLI to scaffold a test AzFunc project in the repo (e.g., a schedule-based PowerShell function) that would emulate 'batch copy job'.

Add a README file, explaining the purpose of this template repo and giving pointers to:

• PowerShell developer reference for Azure Functions
• Develop Azure Functions with VS Code
• AZD CLI template
• Working with Function Core Tools
• Development Containers