Chris
904a5b843e
* Python: .NET Samples - Restructure and Improve Samples (Feature Branch) (#4091) * Moved by agent (#4094) * Fix readme links * .NET Samples - Create `04-hosting` learning path step (#4098) * Agent move * Agent reorderd * Remove A2A section from README Removed A2A section from the Getting Started README. * Agent fixed links * Fix broken sample links in durable-agents README (#4101) * Initial plan * Fix broken internal links in documentation Co-authored-by: crickman <66376200+crickman@users.noreply.github.com> * Revert template link changes; keep only durable-agents README fix Co-authored-by: crickman <66376200+crickman@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: crickman <66376200+crickman@users.noreply.github.com> * .NET Samples - Create `03-workflows` learning path step (#4102) * Fix solution project path * Python: Fix broken markdown links to repo resources (outside /docs) (#4105) * Initial plan * Fix broken markdown links to repo resources Co-authored-by: crickman <66376200+crickman@users.noreply.github.com> * Update README to rename .NET Workflows Samples section --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: crickman <66376200+crickman@users.noreply.github.com> * .NET Samples - Create `02-agents` learning path step (#4107) * .NET: Fix broken relative link in GroupChatToolApproval README (#4108) * Initial plan * Fix broken link in GroupChatToolApproval README Co-authored-by: crickman <66376200+crickman@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: crickman <66376200+crickman@users.noreply.github.com> * Update labeler configuration for workflow samples * .NET - Reorder Agents samples to start from Step01 instead of Step04 (#4110) * Fix solution * Resolve new sample paths * Move new AgentSkills and AgentWithMemory_Step04 samples * Fix link * Fix readme path * fix: update stale dotnet/samples/Durable path reference in AGENTS.md Co-authored-by: crickman <66376200+crickman@users.noreply.github.com> * Moved new sample * Update solution * Resolve merge (new sample) * Sync to new sample - FoundryAgents_Step21_BingCustomSearch * Updated README * .NET Samples - Configuration Naming Update (#4149) * .NET: Restore AzureFunctions index parity with ConsoleApps under DurableAgents samples (#4221) * Clean-up `05_host_your_agent` * Config setting consistency * Refine samples * AGENTS.md * Move new samples * Re-order samples * Move new project and fixup solution * Fixup model config * Fix up new UT project --------- Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>
2.8 KiB
Summary
These samples showcases the ability to parse a declarative Foundry Workflow file (YAML)
to build a Workflow that may be executed using the same pattern as any code-based workflow.
Configuration
These samples must be configured to create and use agents your Azure Foundry Project.
Settings
We suggest using .NET Secret Manager to avoid the risk of leaking secrets into the repository, branches and pull requests. You can also use environment variables if you prefer.
The configuraton required by the samples is:
| Setting Name | Description |
|---|---|
| AZURE_AI_PROJECT_ENDPOINT | The endpoint URL of your Azure Foundry Project. |
| AZURE_AI_MODEL_DEPLOYMENT_NAME | The name of the model deployment to use |
| AZURE_AI_BING_CONNECTION_ID | The name of the Bing Grounding connection configured in your Azure Foundry Project. |
To set your secrets with .NET Secret Manager:
-
From the root of the repository, navigate the console to the project folder:
cd dotnet/samples/03-workflows/Declarative/ExecuteWorkflow -
Examine existing secret definitions:
dotnet user-secrets list -
If needed, perform first time initialization:
dotnet user-secrets init -
Define setting that identifies your Azure Foundry Project (endpoint):
dotnet user-secrets set "AZURE_AI_PROJECT_ENDPOINT" "https://..." -
Define setting that identifies your Azure Foundry Model Deployment (endpoint):
dotnet user-secrets set "AZURE_AI_MODEL_DEPLOYMENT_NAME" "gpt-5" -
Define setting that identifies your Bing Grounding connection:
dotnet user-secrets set "AZURE_AI_BING_CONNECTION_ID" "mybinggrounding"
You may alternatively set your secrets as an environment variable (PowerShell):
$env:AZURE_AI_PROJECT_ENDPOINT="https://..."
$env:AZURE_AI_MODEL_DEPLOYMENT_NAME="gpt-5"
$env:AZURE_AI_BING_CONNECTION_ID="mybinggrounding"
Authorization
Use Azure CLI to authorize access to your Azure Foundry Project:
az login
az account get-access-token
Execution
The samples may be executed within Visual Studio or VS Code.
To run the sampes from the command line:
-
From the root of the repository, navigate the console to the project folder:
cd dotnet/samples/03-workflows/Declarative/Marketing dotnet run Marketing -
Run the demo and optionally provided input:
dotnet run "An eco-friendly stainless steel water bottle that keeps drinks cold for 24 hours." dotnet run c:/myworkflows/Marketing.yamlThe sample will allow for interactive input in the absence of an input argument.