Skip to content

Bad request when using Kimi K2.5 on Azure Foundry #12879

Closed as not planned
Closed as not planned

Description

@NimaAra

Description

Using Kimi K2.5 on Azure Foundry results in the following error.

Unprocessable Entity: {"error":{"code":"Invalid input","status":422,"message":"invalid input error","details":[{"type":"enum","loc":["body","messages",0,"role"],"msg":"Input should be 'system', 'user', 'assistant' or 'tool'","input":"developer","ctx":{"expected":"'system', 'user', 'assistant' or 'tool'"}}]}}Please check this guide to understand why this error code might have been returned
https://docs.microsoft.com/en-us/azure/machine-learning/how-to-troubleshoot-online-endpoints#http-status-codes

Other models on Azure Foundry works as expected.

Plugins

No response

OpenCode version

1.1.53

Steps to reproduce

  1. Deployed Kimi K2.5 on Azure Foundry
  2. Use it in OpenCode

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Activity

  1. github-actions commented on Feb 9, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    Feel free to ignore if none of these address your specific case.

  2. JairajSustained commented on Feb 10, 2026

    @JairajSustained

    Okay
    @rekram1-node
    Would you require any help in this issue?
    I encountered it while compacting.

  3. npagare commented on Feb 20, 2026

    @npagare

    Hi, I am facing the similar issue. After successful authentication via opencode auth login -> Select provider (Azure) -> entered key. Then I got message done. But when switching to that model, I get the error - "AI_LoadSettingError: Azure OpenAI resource name setting is missing. Pass it using the 'resourceName' parameter or the AZURE_RESOURCE_NAME environment variable."

  4. smlp-UaroundAI commented on Mar 10, 2026

    @smlp-UaroundAI

    i am facing same here.

  5. removed
    bugSomething isn't working
    on May 3, 2026
  6. github-actions commented on Jul 3, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions