Agent 365 CLI

Agent 365 CLI is a cross-platform command-line tool for deploying and managing Agent 365 applications on Azure.

You don't need to install the CLI manually. The AI-guided setup checks for the CLI, installs or updates it automatically, and runs all required commands on your behalf. This page is a reference for developers who need to install or use the CLI directly - for example, when building CI/CD automation, troubleshooting a specific step, or working without an AI coding agent.

Note

The complete developer workflow - including AI-guided setup, role guidance, and post-deployment steps - is in Get started with Agent 365 development. This page is the CLI reference: installation, update, uninstall, available commands, and troubleshooting.

Prerequisites

The CLI requires .NET 8.0 or later. For all other prerequisites - Azure subscription, required Entra roles, and custom client app registration - see AI-guided setup.

Install the Agent 365 CLI

Use the following steps to install the Agent 365 CLI globally on your operating system.

Prerequisites

You must have .NET installed. (.NET 8.0 is recommended.)

Use dotnet tool install

Install the Agent 365 CLI by using the following command:

dotnet tool install --global Microsoft.Agents.A365.DevTools.Cli

For the latest instructions and available versions, visit the official NuGet page: Microsoft.Agents.A365.DevTools.Cli on NuGet.org

Verify installation

After installing the Agent 365 CLI, verify that it's properly installed by running the --help command:

a365 -h

This command displays the help information and confirms the CLI is ready to use.

Update

Update Agent 365 CLI by using the dotnet tool update command:

dotnet tool update --global Microsoft.Agents.A365.DevTools.Cli

Note

To update Agent 365 CLI, you need an internet connection to access the latest NuGet package: Microsoft.Agents.A365.DevTools.Cli.

Uninstall

Uninstall Agent 365 CLI by using the dotnet tool uninstall command:

dotnet tool uninstall --global Microsoft.Agents.A365.DevTools.Cli

File locations

The default location for a tool's executable file depends on the operating system:

OS Path
Linux/macOS $HOME/.dotnet/tools
Windows %USERPROFILE%\.dotnet\tools

The SDK adds this location to your path when you first run it. So you can invoke global tools from any directory without specifying the tool location.

Tool access is user-specific, not machine global. A global tool is only available to the user that installs the tool.

Available commands

For the complete list of available commands, use the --help command or see Agent 365 CLI Reference.

Tip

You don't need to run CLI commands manually. The AI-guided setup automates the full workflow - CLI installation, configuration, blueprint setup, deployment, and publishing - using an AI coding agent. Use the CLI reference here if you're building CI/CD automation, troubleshooting a specific step, or working without an AI coding agent.

For complete instructions on how to set up an Agent 365 agent by using the CLI, see Get started with Agent 365 development.

Troubleshooting

This section provides information about how to troubleshoot errors with Agent 365 CLI.

Tip

Agent 365 Troubleshooting Guide contains high-level troubleshooting recommendations, best practices, and links to troubleshooting content for each part of the Agent 365 development lifecycle.

CLI-specific issues covered in this section:

Agent doesn't appear in Teams

Create agent instances troubleshooting: Agent doesn't appear in Teams

Can't create agent instance in Teams

Create agent instances troubleshooting: Can't create agent instance in Teams