Simple Chat Documentation
Azure-native documentation for deploying, operating, and extending Simple Chat with the same polished visual language as the latest-release experience.
Simple Chat gives teams an Azure-native way to deploy, ground, govern, and extend AI experiences without stitching together a separate chat app, search layer, and admin plane.
Four pages that cover the full path
Use these entry points when you want to get from deployment decisions to daily usage without hunting through the entire docs tree.
Getting Started
Pick the right deployment path, line up prerequisites, and follow the repo's recommended order of operations.
Features
See the core workspace experience, optional feature packs, platform services, and supported file types in one place.
FAQ
Jump straight to the issues teams hit most often around networking, auth, uploads, search, and model configuration.
Latest Release Highlights
Review the newest user-facing work with curated summaries, screenshots, and links into the deeper feature documentation.
One application, multiple working modes
Simple Chat is opinionated about the hard parts: identity, grounding, document processing, and admin controls are already wired together.
Context-aware AI conversations
Use Azure OpenAI with hybrid retrieval over personal, group, and public workspace content so responses stay tied to your own data.
Document pipelines that stay searchable
Ingest PDFs, Office files, images, audio, and video through Azure AI services, then retrieve them with citations and optional metadata enrichment.
Controls for enterprise rollouts
Layer on Entra ID roles, content safety, feedback review, conversation archiving, and operational logging without rebuilding the app.
What sits behind the experience
The platform runs on Azure App Service and composes search, storage, document processing, and conversation state into a single application surface.
Platform at a glance
Core application state lives in Azure Cosmos DB, document retrieval runs through Azure AI Search, ingestion is handled by Azure AI Document Intelligence and related media services, and authentication uses Entra ID. That combination makes it practical to run Simple Chat as a governed internal tool instead of a demo-only sample.
Working in the repo
The docs, app, and deployers are all maintained together, so the contributor guide is the fastest way to align with the expected workflow.
Want to make changes?
Use the Contributing guide for the fork-based workflow, target branch expectations, and local development references before you start editing code or docs.