It starts the way most work starts these days: in a chat window, where Replit Agent now lives. A sales lead flags a broken reporting workflow at 9:04 in the morning. Someone replies that the dashboard has been wrong for a week. A third person pastes a screenshot.
And then, instead of a ticket that sits in a queue for a month, someone asks the chat itself to fix it.
That is the moment Replit is aiming at. At Microsoft Ignite on November 18, the company announced that Replit Agent is now available inside Microsoft Teams, alongside two more integrations reaching general availability and an early-access route to publish apps into a company’s Azure tenant.
The pitch is simple: the place where teams talk about a problem should also be the place where the problem gets built away.
Replit Agent in Microsoft Teams is the headline, but the announcement is really a bundle. Microsoft Fabric integration, local work on the desktop, and Azure publishing all landed together, and Replit was named the 2026 Microsoft Partner of the Year for Startups on the same day.
For a company that began as a browser-based coding playground, it is a deliberate move into the enterprise stack — and straight onto the home turf of Microsoft’s own Copilot.
Replit Agent in Microsoft Teams: From Chat to Working Software
The Teams integration works the way a good colleague would. A person asks Replit a question inside a team conversation, investigates a problem, or starts a piece of work without leaving the chat. When the job outgrows the conversation, it hands off to Replit on the web, where the full workspace takes over.
Replit describes the goal plainly: shorten the path from discussing a problem to doing something about it. The Teams integration is generally available now, according to Replit’s changelog dated November 20.
It arrives at a moment when every major platform is racing to put an agent where people already work. Microsoft’s own Copilot lives in Teams. So does Salesforce’s Copilotforce, announced the same week.
Replit is walking into a crowded room — and betting that building software, not just answering questions, is the difference.
Microsoft Fabric Goes Generally Available
The second piece of the announcement may matter more to large companies. Replit’s integration with Microsoft Fabric, in public preview since June, is now generally available. It gives enterprises a direct path from describing an application in natural language to deploying it inside their own Fabric tenant.
The practical pitch is for the teams that live in data. A department can ask for an operational dashboard, a reporting interface, or a small internal tool, and have it built against the company’s governed data.
The existing per-user access controls and security policies stay in force. Nothing is copied out to a side system. The data stays where the company already governs it.
Under the hood, Replit uses Rayfin, a Microsoft open-source SDK and command-line tool, to scaffold application backends with data models, authentication, and access policies. For enterprises already invested in Fabric, the integration extends the platform from data and analytics into the applications teams actually use to run the business.
The value, as one customer put it, is not having to choose between speed and control. Cody Luth, an AI solutions architect at Leatherman, said his team appreciates how quickly it can build and iterate in Replit, but some of its data needs to stay governed and centralised in Fabric. With Rayfin, he said, the company finally has both.
Local Work on Windows, Mac and Linux
The third generally available piece is Local Work in the Replit Desktop app, now available on Windows, Mac, and Linux. The idea is the mirror image of the Fabric integration: instead of bringing the agent to the company’s cloud data, bring it to the files on your own machine.
A developer chooses which folders Replit can access, describes what they want to build or change, and reviews the results locally. The local environments are sandboxed using Microsoft Execution Containers, so the agent’s work stays contained.
And for teams worried about code leaving the machine at all, local apps can use Microsoft Foundry Local models, which run directly on-device with no cloud round-trip, alongside NVIDIA CUDA-accelerated models.
Publishing Apps to Azure, With Full BYOC Next
The announcement also opens an early-access path to publish apps to Azure. Replit is available in the Microsoft Marketplace, which lets Azure customers build with Replit and publish applications directly into their company’s Azure tenant.
Replit provisions and manages the hosting infrastructure, while administrators control the publishing destination for each workspace. For the person building, the experience stays familiar: click “Publish” and the app deploys.
Published apps can connect to private databases inside the company’s Azure environment, with access configurable through the company network or VPN. Security teams can use their existing cloud security tools to inspect deployed workloads and dependencies. Development, in this configuration, remains on Replit.
What comes next is bigger. Full bring-your-own-cloud, or BYOC, will move compute, storage, the file system, integrations, and Replit’s Agent harness into the customer’s own Azure environment. Teams will be able to build with internal systems and company data while security teams govern which resources the agent can reach and apply controls to outbound connections.
Why This Matters for Microsoft Teams
There is a reason Replit chose Ignite for this announcement, and a reason Microsoft is cheering it on. Sachin Patney, vice president of app development at Microsoft, said integrating Replit with Microsoft’s data, developer tools, and workplace experiences helps businesses put AI-powered software creation into the hands of the people closest to the work, while keeping people in control.
That framing — people closest to the work, kept in control — is the thread running through the whole announcement. Replit’s chief executive, Amjad Masad, has described a future he calls the “self-driving company”, in which people set direction, exercise judgment, and remain accountable while agents take on more of the execution.
These launches are, in Replit’s words, practical steps toward that future.
But the subtext is competitive. Teams is where Microsoft’s Copilot lives, and where Salesforce has just planted its own flag. Replit is not trying to out-assistant Copilot. It is trying to do something Copilot does not: turn a conversation into a deployed application, running on the company’s own data, inside the company’s own cloud.
What Happens Next
The three integrations are available now, with Azure publishing in early access and full BYOC still to come. The open questions are the ones that will decide whether this lands or stalls: how well the Teams agent handles real, messy enterprise conversations, and whether business users, not just developers, actually start building from a chat window.
Replit’s answer, for now, is to make the first step as small as possible. Ask a question in Teams. Investigate a problem. Start a piece of work. The agent does the rest — and when the work outgrows the chat, the web workspace is one click away.
The company that once made coding accessible from a browser tab is now trying to make building software as natural as sending a message. Whether teams adopt it will be the real test, and it starts in the place where their work already happens.
Source: Replit’s announcement at Microsoft Ignite, reported via the company’s blog — Replit.
Related reading on Wasl Tech: Claude Office Suite: Anthropic Takes on Microsoft and Google as OpenAI Fires Back, Databricks Genie Is Now an Always-On AI Coworker That Works While You Don’t, and Grok Bot 1.0 Is Here: xAI’s AI Teammates Now Join Your Meetings and Take On Work.



