.NET: [Feature Branch] Introduce Azure OpenAI config for .NET pipeline

[Chris Gillum (cgillum)]

Motivation and Context

The Durable Task / Azure Functions integration tests are designed to use Azure OpenAI with token-based credentials. However, none of the .NET tests use this configuration! The integration tests for .NET instead assume using public OpenAI or Foundry for persistent agents, so there's no compatible configuration that can be reused for our integration tests.

Description

I'm introducing the existing AZURE_OPENAI_ENDPOINT and AZURE_OPENAI_CHAT_DEPLOYMENT_NAME environment variables into the .NET pipeline. I verified that these environment variables are already being used by several of the Python tests (with Azure CLI credentials), so I have reasonably high confidence that these configuration values will work properly in the .NET context as well.

I'm also fixing the prerequisite setup to only run when targeting Ubuntu since Windows pipelines don't support docker. Conveniently, our integration tests don't run on Windows since Windows is only used to validate net472 targets, and we aren't supporting net472.

Contribution Checklist

• The code builds clean without any errors or warnings
• The PR follows the Contribution Guidelines
• All unit tests pass, and I have added new tests where possible
• Is this a breaking change? If yes, add "[BREAKING]" prefix to the title of the PR.

[Copilot]

Pull Request Overview

This PR standardizes .NET integration tests to use Azure OpenAI configuration with token-based authentication, aligning with the pattern already established in Python tests. The changes remove legacy configuration variables (AZUREAI:ENDPOINT and AZUREAI:DEPLOYMENTNAME) in favor of AZURE_OPENAI_ENDPOINT and AZURE_OPENAI_CHAT_DEPLOYMENT_NAME.

Key changes:

• Introduces AZURE_OPENAI_ENDPOINT and AZURE_OPENAI_CHAT_DEPLOYMENT_NAME environment variables to the .NET pipeline
• Updates test helper code to use standardized Azure OpenAI configuration
• Adds OS check to only run prerequisite Docker setup on Ubuntu (where .NET Framework integration tests don't run)

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
.github/workflows/dotnet-build-and-test.yml	Adds Azure OpenAI environment variables to the integration test step and restricts Docker setup to Ubuntu
dotnet/tests/Microsoft.Agents.AI.DurableTask.IntegrationTests/TestHelper.cs	Replaces legacy config variables with standardized Azure OpenAI variables and updates API key variable name
dotnet/tests/Microsoft.Agents.AI.Hosting.AzureFunctions.IntegrationTests/SamplesValidation.cs	Replaces legacy config variables with standardized Azure OpenAI variables

[Copilot]

Pull Request Overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

dotnet/tests/Microsoft.Agents.AI.Hosting.AzureFunctions.IntegrationTests/SamplesValidation.cs:645

• The environment variable name mismatch will cause the Azure Functions samples to fail. The code reads from AZURE_OPENAI_CHAT_DEPLOYMENT_NAME (line 640), but sets AZURE_OPENAI_DEPLOYMENT on line 645. The Azure Functions samples expect AZURE_OPENAI_DEPLOYMENT as seen in their Program.cs files (e.g., samples/AzureFunctions/01_SingleAgent/Program.cs line 15).

Either change line 640 to read from AZURE_OPENAI_DEPLOYMENT instead of AZURE_OPENAI_CHAT_DEPLOYMENT_NAME, or change line 645 to set AZURE_OPENAI_CHAT_DEPLOYMENT_NAME.

        string openAiDeployment = s_configuration["AZURE_OPENAI_CHAT_DEPLOYMENT_NAME"] ??
            throw new InvalidOperationException("The required AZURE_OPENAI_CHAT_DEPLOYMENT_NAME env variable is not set.");

        // Set required environment variables for the function app (see local.settings.json for required settings)
        startInfo.EnvironmentVariables["AZURE_OPENAI_ENDPOINT"] = openAiEndpoint;
        startInfo.EnvironmentVariables["AZURE_OPENAI_DEPLOYMENT"] = openAiDeployment;