Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Support keyless authentication with Azure OpenAI

Open
#16 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, csharp
Domain
ai, backend, cloud

Research direction

Start by locating the demo's Azure OpenAI configuration and any existing Aspire or AZD infrastructure setup. Compare that setup with the Azure.Identity DefaultAzureCredential example in the issue; the work is complete when the demo uses keyless authentication and its configuration guidance remains usable.

Written by the indexing model from the issue text.

Description

Best practice guidance is to use keyless authentication with Azure resources, and we'll soon publish this guidance in our AI docs as well. We should update the demo to use a recommended pattern for this. For example, here's the default approach, using the Azure.Identity library, that is included in the upcoming doc:

Kernel kernel = Kernel
.CreateBuilder()
    .AddAzureOpenAITextGeneration(
        "your-model",
        "your-endpoint",
        new DefaultAzureCredential())
    .Build();

This does increase some complexity in configuring the application, which for other samples we include in the infra code that's published with AZD. Perhaps there's a good practice for this with Aspire already, I just haven't dived in there yet - Filing the issue for now so I don't forget.

Dominant language
JavaScript
Stars
658
Forks
189
PR merge metrics
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/eShopSupport

All issues in dotnet/eShopSupport

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.