What the creator can design
Bring the first task you want users to complete in a new or existing application. AI Agent Creator helps define that journey and its architecture. It may recommend a platform agent, custom application, explicit workflow, or a model call with a defined task.
The plugin designs the solution but does not implement or certify it. These examples are not customer results or deployment templates.
Application families
The products shown are examples. Discovery must verify product fit, connections, availability, and release status.
Knowledge assistants
Help users find permitted information and cite its source. Define source ownership, permissions, freshness, and what happens when evidence conflicts or is missing. A fixed lookup may not need an agent loop.
Agents that use business tools
Investigate a task and prepare or perform approved operations. Define read-only access, approval boundaries, authorization, and retry behavior that prevents duplicate business actions.
Document and media processing
Turn incoming material into structured results. Define the output schema, review threshold, correction path, and downstream handoff. This may be a fixed pipeline with no conversational interface.
Voice and audiovisual experiences
Use speech or audiovisual presentation when the task requires it. Define interruptions, corrections, exit paths, privacy, and accessibility. An avatar or generated video alone does not require an agent.
Background workflows
Respond to events or process jobs without a chat interface. Define who owns job state, how work resumes, which branches stay fixed, and when investigation stops.
Coordinated specialist agents
Split responsibilities only when one agent cannot meet the requirement reliably. Define handoffs, access boundaries, shared state, conflict handling, and failure behavior. Coordination adds overhead. Microsoft's orchestration guidance recommends the lowest complexity that meets the requirement.
Capabilities you can combine
Families can overlap. Add persistent memory, multiple agents, or personalization only when the journey needs them. Define ownership, permissions, provenance, expiry, and deletion.
Choose an architecture during discovery
You do not need to choose a platform before discovery. Bring the outcome and existing constraints. The creator compares existing capabilities with custom execution against the first journey's requirements. Microsoft's technology planning guidance starts by checking whether a ready-to-use solution meets the need.
Choose the user channel separately from the runtime. Keep knowledge access and permission to perform actions distinct. The architecture review must verify product fit and proposed connections, and name owners for unresolved checks.
Describe your first journey
Tell the creator who will use the application and what their first task is:
/ai-agent-creator Design a maintenance assistant for property managers. Help them investigate
resident requests and prepare a work order for approval. Reuse our existing
identity and service system. Compare an agent with a simpler workflow before
recommending the architecture.
Set up your application workspace, then bring your own idea. If you are extending a system, prepare its context.
Review and approve the architecture package before starting a separate implementation session. Architecture approval does not authorize implementation or deployment.
