PR #49126: WORKING: All Microsoft Issues and PRs

• Repository: openclaw/openclaw
• Author: BradGroux
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/49126

Description (problem / solution / changelog)

Microsoft Ecosystem Issues & PRs Tracker

Purpose: Living checklist for maintainers to track all open Microsoft-related issues and PRs (Teams, Windows, WSL, Azure, M365/SharePoint).

How to use:

• Mark items resolved by editing this PR body and changing [ ] to [x]
• Claim items by adding your GitHub handle to the Assignee column
• Priority guide: P0 = crash/blocker, P1 = significant bug/regression, P2 = minor bug/enhancement, P3 = nice-to-have/stale
• Items marked (stale) have been flagged by the stale bot due to inactivity

Last updated: 2026-03-19

Summary

1. MS Teams Channel Plugin — Issues

Bugs / Crashes

Feature Requests

2. MS Teams Channel Plugin — PRs

3. Windows Platform — Issues

Installation / Setup / Gateway

Feature Requests

4. Windows Platform — PRs

5. WSL (Windows Subsystem for Linux) — Issues

WSL — PRs

6. Azure (Provider / Infrastructure) — Issues

Azure — PRs

7. Microsoft 365 / SharePoint — Issues

Appendix: P0 Blockers (Start Here)

Appendix: Stale Items (Consider Closing)

Changed files

PR #49147: fix(onboard): keep Azure custom providers on Azure Responses API

• Repository: openclaw/openclaw
• Author: biefan
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/49147

Description (problem / solution / changelog)

Summary

• store Azure OpenAI compatible custom providers as azure-openai-responses instead of openai-completions
• preserve the existing Azure URL transformation while selecting the provider API from the original endpoint host
• add a regression assertion covering Azure custom provider onboarding output

Testing

• pnpm -C "/root/pr/openclaw" exec vitest run "src/commands/onboard-custom.test.ts"

Closes #48939

Changed files

• src/commands/onboard-custom.test.ts (modified, +5/-1)
• src/commands/onboard-custom.ts (modified, +7/-3)
• src/config/types.models.ts (modified, +1/-0)

PR #49543: fix(provider): tui/agent etc not working when azure openai endpoint is onboarded through custom provider

• Repository: openclaw/openclaw
• Author: kunalk16
• State: closed | merged: True
• Link: https://github.com/openclaw/openclaw/pull/49543

Description (problem / solution / changelog)

Summary

Describe the problem and fix in 2–5 bullets:

1. Onboard an Azure OpenAI endpoint through the custom provider with the correct details
2. Use tui or agent, it fails

When Azure OpenAI endpoint is configured using the custom provider option, it is updated in the config with api "openai-completions". This refers to the "openai-completions" of pi-ai and when LLM calls are made to the endpoint, it fails with 404 response. My changes are going to update the onboarding code such that it instead uses the "openai-responses" api which works with azure openai endpoints. We could have also used the "azure-openai-responses" option of pi-ai but that asks for more changes so going for "openai-responses"

• Problem:
• Why it matters: Azure subscribers with Azure OpenAI endpoints are unable to use openclaw and they dont understand what is the issue after successfully onboarding the endpoint through the onboarding using custom provider option.
• What changed: Only the config generated by the custom provider onboarding wizard changed, it now generates openai-responses based config for azure openai endpoints rather than openai-completions.
• What did NOT change (scope boundary): Only the config update logic changed for azure openai endpoints, not openai endpoints/

Change Type (select all)

• Bug fix
• Feature
• Refactor
• Docs
• Security hardening
• Chore/infra

Scope (select all touched areas)

• Gateway / orchestration
• Skills / tool execution
• Auth / tokens
• Memory / storage
• Integrations
• API / contracts
• UI / DX
• CI/CD / infra

Linked Issue/PR

• Closes https://github.com/openclaw/openclaw/issues/48939
• Related #

User-visible / Behavior Changes

List user-visible changes (including defaults/config).
None

Security Impact (required)

• New permissions/capabilities? No
• Secrets/tokens handling changed? No
• New/changed network calls? No
• Command/tool execution surface changed? No
• Data access scope changed? No
• If any Yes, explain risk + mitigation:

Repro + Verification

It was reproed in my ubuntu machine/container, it was not working before the fix <img width="991" height="691" alt="image" src="https://github.com/user-attachments/assets/d3d1b0ad-6698-4efc-8f7e-6a191fa5e013" />

Environment

• OS: Ubuntu 24.04
• Runtime/container: Azure VM/container both
• Model/provider: Azure OpenAI gpt-5.2-chat
• Integration/channel (if any):
• Relevant config (redacted): Old config generated

{
  "wizard": {
    "lastRunAt": "2026-03-15T06:13:42.390Z",
    "lastRunVersion": "2026.3.14",
    "lastRunCommand": "onboard",
    "lastRunMode": "local"
  },
  "models": {
    "mode": "merge",
    "providers": {
      "custom-someresourcexyz-openai-azure-com": {
        "baseUrl": "https://someresourcexyz.openai.azure.com/openai/deployments/gpt-5.2-chat",
        "apiKey": "someapikey",
        "api": "openai-completions",
        "models": [
          {
            "id": "gpt-5.2-chat",
            "name": "gpt-5.2-chat (Custom Provider)",
            "reasoning": false,
            "input": [
              "text"
            ],
            "cost": {
              "input": 0,
              "output": 0,
              "cacheRead": 0,
              "cacheWrite": 0
            },
            "contextWindow": 16000,
            "maxTokens": 4096
          }
        ]
      }
    }
  },
  "agents": {
    "defaults": {
      "model": {
        "primary": "custom-someresourcexyz-openai-azure-com/gpt-5.2-chat"
      },
      "models": {
        "custom-someresourcexyz-openai-azure-com/gpt-5.2-chat": {}
      },
      "workspace": "/root/.openclaw/workspace"
    }
  },
  "tools": {
    "profile": "coding"
  },
  "commands": {
    "native": "auto",
    "nativeSkills": "auto",
    "restart": true,
    "ownerDisplay": "raw"
  },
  "session": {
    "dmScope": "per-channel-peer"
  },
  "gateway": {
    "port": 18789,
    "mode": "local",
    "bind": "loopback",
    "auth": {
      "mode": "token",
      "token": "sometoken"
    },
    "tailscale": {
      "mode": "off",
      "resetOnExit": false
    },
    "nodes": {
      "denyCommands": [
        "camera.snap",
        "camera.clip",
        "screen.record",
        "contacts.add",
        "calendar.add",
        "reminders.add",
        "sms.send"
      ]
    }
  },
  "meta": {
    "lastTouchedVersion": "2026.3.14",
    "lastTouchedAt": "2026-03-15T06:13:42.400Z"
  }
}

Steps

1. Onboard openclaw with azure openai endpoint
2. Try out tui or agent

Expected

• Tui or agent invocation would work

Actual

• Tui and agent invocation fails before the fix <img width="991" height="691" alt="image" src="https://github.com/user-attachments/assets/d3d1b0ad-6698-4efc-8f7e-6a191fa5e013" />

Evidence

Attach at least one:

• Failing test/log before + passing after
• Trace/log snippets
• Screenshot/recording
• Perf numbers (if relevant)

Human Verification (required)

Verified the onboarding then testes tui, agent commands execution Custom provider onboarded: <img width="1169" height="708" alt="image" src="https://github.com/user-attachments/assets/a79a648e-e126-4939-8019-505b0412d3eb" />

TUI/Agent both works now after the fix: <img width="1227" height="993" alt="image" src="https://github.com/user-attachments/assets/b3001d64-cd59-4227-a7e7-0e9c14586d57" />

Config generated by the onboarding wizard:

{
  "meta": {
    "lastTouchedVersion": "2026.3.13",
    "lastTouchedAt": "2026-03-18T06:22:20.794Z"
  },
  "wizard": {
    "lastRunAt": "2026-03-18T06:22:20.786Z",
    "lastRunVersion": "2026.3.13",
    "lastRunCommand": "onboard",
    "lastRunMode": "local"
  },
  "models": {
    "mode": "merge",
    "providers": {
      "custom-myresource-openai-azure-com": {
        "baseUrl": "https://myresource.openai.azure.com/openai/v1",
        "apiKey": "hidden-api-key",
        "api": "openai-responses",
        "headers": {
          "api-key": "hidden-api-key"
        },
        "authHeader": false,
        "models": [
          {
            "id": "gpt-5.2-chat",
            "name": "gpt-5.2-chat (Custom Provider)",
            "reasoning": true,
            "input": [
              "text",
              "image"
            ],
            "cost": {
              "input": 0,
              "output": 0,
              "cacheRead": 0,
              "cacheWrite": 0
            },
            "contextWindow": 400000,
            "maxTokens": 16384,
            "compat": {
              "supportsStore": false
            }
          }
        ]
      }
    }
  },
  "agents": {
    "defaults": {
      "model": {
        "primary": "custom-myresource-openai-azure-com/gpt-5.2-chat"
      },
      "models": {
        "custom-myresource-openai-azure-com/gpt-5.2-chat": {
          "params": {
            "thinking": "medium"
          }
        }
      },
      "workspace": "/root/.openclaw/workspace"
    }
  },
  "tools": {
    "profile": "coding"
  },
  "commands": {
    "native": "auto",
    "nativeSkills": "auto",
    "restart": true,
    "ownerDisplay": "raw"
  },
  "session": {
    "dmScope": "per-channel-peer"
  },
  "gateway": {
    "port": 18789,
    "mode": "local",
    "bind": "loopback",
    "auth": {
      "mode": "token",
      "token": "7c4feae22c3dcf0a629c9f3c29aa683a5f086739111f74cf"
    },
    "tailscale": {
      "mode": "off",
      "resetOnExit": false
    },
    "nodes": {
      "denyCommands": [
        "camera.snap",
        "camera.clip",
        "screen.record",
        "contacts.add",
        "calendar.add",
        "reminders.add",
        "sms.send"
      ]
    }
  }
}

What you personally verified (not just CI), and how:

• Verified scenarios: Manually onboarded, checked the config, tui chat execution, agent execution
• Edge cases checked:
• What you did not verify:

Review Conversations

• I replied to or resolved every bot review conversation I addressed in this PR.
• I left unresolved only the conversations that still need reviewer or maintainer judgment.

If a bot review conversation is addressed by this PR, resolve that conversation yourself. Do not leave bot review conversation cleanup for maintainers.

Compatibility / Migration

• Backward compatible? Not applicable
• Config/env changes? Not applicable
• Migration needed? Not applicable
• If yes, exact upgrade steps:

Failure Recovery (if this breaks)

• How to disable/revert this change quickly: Revert the PR, use non-azure openai endpoint through custom provider, this flow never worked before so it will not be an issue
• Files/config to restore:
• Known bad symptoms reviewers should watch for:

Risks and Mitigations

List only real risks for this PR. Add/remove entries as needed. If none, write None. None

• Risk:
  • Mitigation:

Changed files

• CHANGELOG.md (modified, +1/-1)
• src/commands/onboard-custom.test.ts (modified, +192/-8)
• src/commands/onboard-custom.ts (modified, +107/-19)

PR #50851: chore(provider): use pi-ai's azure-openai-responses for azure openai endpoints

• Repository: openclaw/openclaw
• Author: kunalk16
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/50851

Description (problem / solution / changelog)

Summary

Describe the problem and fix in 2–5 bullets: This is just a small extension to this PR: https://github.com/openclaw/openclaw/pull/49543 We now use the "azure-openai-responses" implementation for azure openai custom provider endpoint. A manually configured azure openai endpoint with api "azure-openai-responses" fails as the enum MODEL_APIS in types.models.ts does not have an entry for "azure-openai-responses"

Response sanitization, etc not needed for azure-openai-responses as we have done for openai-responses, verified it manually

• Problem:
• Why it matters: pi-ai has a dedicated handler for azure-openai endpoints named "azure-openai-responses" to take care of azure-openai responses API calls, we might as well use it over "openai-responses" for azure openai endpoints as it has some specific handling over "openai-responses" which users might hit for some edge cases.
• What changed: For custom azure openai endpoints, we were earlier using "openai-responses" we now use "azure-openai-responses"
• What did NOT change (scope boundary): Scope is only the config generated for azure openai endpoints through custom provider onboarding.

Change Type (select all)

• Bug fix
• Feature
• Refactor
• Docs
• Security hardening
• Chore/infra

Scope (select all touched areas)

• Gateway / orchestration
• Skills / tool execution
• Auth / tokens
• Memory / storage
• Integrations
• API / contracts
• UI / DX
• CI/CD / infra

Linked Issue/PR

• Closes #
• Related: https://github.com/openclaw/openclaw/pull/49543 & https://github.com/openclaw/openclaw/issues/48939

User-visible / Behavior Changes

List user-visible changes (including defaults/config).
The generated config now has api "azure-openai-responses" rather than "openai-responses" for custom provider azure openai endpoints.

Security Impact (required)

• New permissions/capabilities? No
• Secrets/tokens handling changed? No
• New/changed network calls? No
• Command/tool execution surface changed? No
• Data access scope changed? No
• If any Yes, explain risk + mitigation:

Repro + Verification

Manually verified that after the change, tui and agent with tool calls work with a configured azure openai endpoint <img width="1512" height="948" alt="image" src="https://github.com/user-attachments/assets/f1c8eb42-38b1-4702-a630-1245be10bad0" />

Manually verified that after the change, the api field in focus generates "azure-openai-responses" <img width="1342" height="893" alt="image" src="https://github.com/user-attachments/assets/9356a268-c115-4c85-b4a4-dc18b3aaf266" />

Environment

• OS: Ubuntu 25.10/Ubuntu 24.04
• Runtime/container: Tested in both Azure VM & Docker container
• Model/provider: Azure OpenAI gpt-5.2-chat & gpt-5.3-chat
• Integration/channel (if any):
• Relevant config (redacted):

{
  "wizard": {
    "lastRunAt": "2026-03-20T04:33:02.576Z",
    "lastRunVersion": "2026.3.14",
    "lastRunCommand": "onboard",
    "lastRunMode": "local"
  },
  "models": {
    "mode": "merge",
    "providers": {
      "custom-kkarmakar-ai-eus2-openai-azure-com": {
        "baseUrl": "https://resource.openai.azure.com/openai/v1",
        "apiKey": "key1234",
        "api": "azure-openai-responses",
        "headers": {
          "api-key": "key1234"
        },
        "authHeader": false,
        "models": [
          {
            "id": "gpt-5.3-chat",
            "name": "gpt-5.3-chat (Custom Provider)",
            "reasoning": true,
            "input": [
              "text",
              "image"
            ],
            "cost": {
              "input": 0,
              "output": 0,
              "cacheRead": 0,
              "cacheWrite": 0
            },
            "contextWindow": 400000,
            "maxTokens": 16384,
            "compat": {
              "supportsStore": false
            }
          }
        ]
      }
    }
  },
  "agents": {
    "defaults": {
      "model": {
        "primary": "custom-resource-openai-azure-com/gpt-5.3-chat"
      },
      "models": {
        "custom-resource-openai-azure-com/gpt-5.3-chat": {
          "params": {
            "thinking": "medium"
          }
        }
      },
      "workspace": "/root/.openclaw/workspace"
    }
  },
  "tools": {
    "profile": "coding"
  },
  "commands": {
    "native": "auto",
    "nativeSkills": "auto",
    "restart": true,
    "ownerDisplay": "raw"
  },
  "session": {
    "dmScope": "per-channel-peer"
  },
  "gateway": {
    "port": 18789,
    "mode": "local",
    "bind": "loopback",
    "auth": {
      "mode": "token",
      "token": "0e8dbc50a15d49e09a70c4594b0f1a0abcbce8f6e1ebc51d"
    },
    "tailscale": {
      "mode": "off",
      "resetOnExit": false
    },
    "nodes": {
      "denyCommands": [
        "camera.snap",
        "camera.clip",
        "screen.record",
        "contacts.add",
        "calendar.add",
        "reminders.add",
        "sms.send"
      ]
    }
  },
  "meta": {
    "lastTouchedVersion": "2026.3.14",
    "lastTouchedAt": "2026-03-20T04:33:02.586Z"
  }
}

Steps

1. Install openclaw
2. Onboard an azure openai endpoint using custom provider option or onboard an azure openai endpoint with api "azure-openai-responses" manually

Expected

TUI/Agent should work

Actual

Currently, without the change, onboarding wizard generates a config with "openai-responses" api fo azure openai responses which works but we dont know if any use case will break as pi-ai has a dedicated "azure-openai-responses" specifically for azure openai endpoints. A manually configured azure openai endpoint with api "azure-openai-responses" fails as the enum MODEL_APIS in types.models.ts does not have an entry for "azure-openai-responses"

Evidence

Attach at least one:

• Failing test/log before + passing after
• Trace/log snippets
• Screenshot/recording
• Perf numbers (if relevant)

Human Verification (required)

What you personally verified (not just CI), and how:

• Verified scenarios: Manually installed openclaw, did the onboarding with custom provider interactive onboarding, verified tui & agent tool calls, verified the config file generated Response sanitization, etc not needed for azure-openai-responses as we have done for openai-responses, verified it manually, if we add the sanitization, we get 400 errors for azure-openai-responses
• Edge cases checked:
• What you did not verify:

Review Conversations

• I replied to or resolved every bot review conversation I addressed in this PR.
• I left unresolved only the conversations that still need reviewer or maintainer judgment.

If a bot review conversation is addressed by this PR, resolve that conversation yourself. Do not leave bot review conversation cleanup for maintainers.

Compatibility / Migration

• Backward compatible? Not applicable
• Config/env changes? Not applicable
• Migration needed? Not applicable
• If yes, exact upgrade steps:

Failure Recovery (if this breaks)

• How to disable/revert this change quickly: Revert the PR
• Files/config to restore:
• Known bad symptoms reviewers should watch for:

Risks and Mitigations

None

List only real risks for this PR. Add/remove entries as needed. If none, write None.

• Risk:
  • Mitigation:

Changed files

• CHANGELOG.md (modified, +1/-0)
• src/commands/onboard-custom.test.ts (modified, +2/-2)
• src/commands/onboard-custom.ts (modified, +1/-1)
• src/config/types.models.ts (modified, +1/-0)