OpenClaw, originally called ClawBot and for a short while MoltBot, probably do not require much introduction anymore.

Rumor has it that changes are about to happen when it comes to enabling OpenClaw in Teams so that the setup becomes a little more Enterprise friendly. I wanted to check for myself what might be missing before an IT department can accept OpenClaw getting installed on corporate computers, and also if Microsoft Foundy Local can be used for running the model used by OpenClaw.

The (instructions for installing OpenClaw)[https://docs.openclaw.ai/start/getting-started#quick-setup-cli] and getting it (working in Teams)[https://docs.openclaw.ai/channels/msteams] is pretty straightforward, but unfortunaltely they appear mostly targeted for developers and not suitable for IT managed installations.

With onboarding:

iwr -useb https://openclaw.ai/install.ps1 | iex

Select Yes on that you understand OpenClaw is personal-by-default.

Select Quickstart

Model/auth provider: Skip for now

Filter models by provider: select azure-openai-responses

Default model: Enter model manually : azure-openai-responses/qwen2.5-7b (the one I am running using Foundry Local)

Select channel: Microsoft Teams

Install Microsoft Teams plugin: Download from npm

Now head over to https://portal.azure.com/#create/Microsoft.AzureBot Bot handle: openclaw-teams (or whatever you like) Select Subscription and Resource Group (create new) Pricing tier: Free or Standard Type of App: Single-Tenant Creation type: Create new Microsoft App ID Next: set tags according to your organization policy (you have one, right?) Next: Create Go to Resource after deployment succeeds. Select Settings: Configuration and copy Microsoft App ID Back to OpenClaw onboarding setup: paste App ID Back to Azure Bot in Azure Portal: select Manage Password next to Microsoft App Id Create new client secret and copy its value Paste into OpenClaw onboarding setup Paste tenant ID into onboarding setup Configure MS Teams Channels access: Yes AllowList Create a new Teams Team to which we will isolate OpenClaw permissions to Add the Team and one if its channels in onboarding setup dialog (MS Teams channels allowlist (comma-separated)) Web Search: if you have API key for any, use it Configure skills: Yes Skills: blogwatcher, camsnap, clawhub, gifgrep, github, himalaya, obsidian, openai-whisper, summarize Preferred node manager for skill installs: npm All selected skills except clawhub failed to install due to Brew requirement. Set GOOGLE_PLACES_API_KEY for goplaces? No Set GEMINI_API_KEY for nano-banana-pro? No No to all API keys actually.. Enable all 4 discovered hooks Hatch in TUI

Follow this but use Foundry Local instead https://techcommunity.microsoft.com/blog/educatordeveloperblog/integrating-microsoft-foundry-with-openclaw-step-by-step-model-configuration/4495586

edit ~/.openclaw/openclaw.json and replace agents section with:

& ([scriptblock]::Create((iwr -useb https://openclaw.ai/install.ps1))) -NoOnboard

openclaw gateway restart

Better for IT without onboarding and automated setup:

& ([scriptblock]::Create((iwr -useb https://openclaw.ai/install.ps1))) -NoOnboard