Microsoft pitched bots as apps that lived inside chat

The conversation

On 30 March 2016, at Microsoft's Build conference, chief executive Satya Nadella and Windows executive Terry Myerson described what the company's own contemporaneous press release called the new frontier that pairs natural human language with advanced machine intelligence. Nadella named the idea Conversations as a Platform. Alongside a preview of Microsoft Cognitive Services, the release introduced the Microsoft Bot Framework, a tool developers in any language could use to build bots that let customers chat using natural language across platforms including text and SMS, Office 365, Skype, Slack and the web. A separate Skype Bot Platform shipped the same day.

What the documents show

The 2016 release establishes only what Microsoft said at launch: a framework, a named set of chat surfaces, and a positioning of bots as a new application type reached through existing messaging apps rather than downloaded separately. It does not describe how the framework routes a message between a bot and each surface; for that, the operating documentation is the relevant source. Microsoft's current Azure Bot Service documentation, retrieved 16 September 2026, describes a channel as a connection between a communication application and a bot, and states that the Bot Framework lets a developer build a bot in a channel-agnostic way by normalizing the messages it sends to a channel. When a channel cannot represent part of that message, the documentation says the connecting service tries to convert it into a format the channel supports, giving the example of a card with buttons becoming an image with linked actions inside an email channel.

The system boundary

The boundary the framework draws is between a bot's own logic, written once by a developer, and a per-channel adapter layer Microsoft maintains so that logic need not be rewritten for each surface. A developer's code reasons in one schema; the platform, not the bot, translates that schema into and out of each channel's native format. That design descends directly from the 2016 pitch, though the channel list has not stood still: the current hub documentation now centers a successor called Agents SDK rather than the original Bot Builder SDK, and the channels page notes that Skype, one of the two platforms named at launch, no longer supports new bot development.

Where it fails

The clearest limitation for anyone citing this launch today is that the Bot Framework no longer points at one static thing: the SDK generation, the supported channel list and even the underlying schema-transformation version have all changed since March 2016, and Microsoft's own documentation versions these changes rather than treating them as invisible.

• Which SDK generation, and which schema-transformation version, does a given bot or tutorial actually target?
• What happens to a message the target channel cannot fully represent, and has that behavior been tested on the specific channel in use?
• Which of the originally announced channels are still supported for new development, rather than only legacy deployments?

None of this contradicts the 2016 announcement; it is a reminder that a platform pitched as channel-agnostic still depends on channel-specific adapters that keep changing underneath it.