Poznámka
Na prístup k tejto stránke sa vyžaduje oprávnenie. Môžete sa skúsiť prihlásiť alebo zmeniť adresáre.
Na prístup k tejto stránke sa vyžaduje oprávnenie. Môžete skúsiť zmeniť adresáre.
Agent 365 CLI
Important
You need to be part of the Frontier preview program to get early access to Microsoft Agent 365. Frontier connects you directly with Microsoft’s latest AI innovations. Frontier previews are subject to the existing preview terms of your customer agreements. As these features are still in development, their availability and capabilities may change over time.
Deploy Agent 365 application binaries to the configured Azure App Service and update Agent 365 Tool permissions The deploy command provides options to create Agent 365 deployments. Use this command to deploy application binaries to your Azure infrastructure and grant Agent 365 Tools permissions.
Minimum role required: Azure Contributor + Global Administrator
For information about using this command, see Deploy agent to Azure.
Syntax
a365 deploy [command] [options]
Options
| Option | Description |
|---|---|
-c, --config <config> |
Path to the configuration file (default: a365.config.json) |
-v, --verbose |
Enable verbose logging |
--dry-run |
Show what would be done without executing |
--inspect |
Pause before deployment to inspect publish folder and ZIP contents |
--restart |
Skip build and start from compressing existing publish folder (for quick iteration after manual changes) |
-?, -h, --help |
Show help and usage information |
Remarks
Running a365 deploy without a subcommand runs a two-phase deployment:
- Phase 1 — Application binaries: Builds and deploys your application to Azure App Service.
- Phase 2 — MCP permissions: Reads required scopes from
toolingManifest.jsonand updates the agent blueprint with the necessary permissions.
Both phases run even with --dry-run. The dry-run output is divided into two labeled sections so you can review what each phase would do.
Preflight checks
Before deploying, the CLI validates:
- Azure authentication and subscription: Your Azure CLI session and subscription must be valid. If not, deployment stops with an error. Fix with
az login --tenant <TENANT_ID>andaz account set --subscription <SUBSCRIPTION_ID>. - Azure App Service existence: The target web app must exist before deployment proceeds. If the app isn't found, run
a365 setupor correctwebAppNameandresourceGroupina365.config.json.
Configuration
The CLI reads from two configuration files:
a365.config.json— your project configuration (user-maintained).a365.generated.config.json— dynamic state generated by setup commands.
MCP tool scopes are read from toolingManifest.json in your deployment project directory.
The CLI also stores a global copy of configuration and state at:
- Windows:
%LocalAppData%\Microsoft.Agents.A365.DevTools.Cli - Linux/macOS:
~/.config/a365
Flag behavior
--restart: Skips the build step and starts directly from compressing the existing publish/ folder. If publish/ doesn't exist, the deploy fails. Run a full deploy (without --restart) first to produce the publish/ folder.
--inspect: Pauses before the upload step so you can inspect the publish/ folder and the generated ZIP file. Available for the app phase only.
--dry-run: Prints everything that would happen without making any changes. When running a365 deploy (two-phase), the output is divided into:
- Part 1 — Deploy application binaries
- Part 2 — Deploy/update Agent 365 Tool permissions
deploy app
Deploys your agent code to the Azure Web App created during setup.
a365 deploy app [options]
Deploy Microsoft Agent 365 application binaries to the configured Azure App Service. This command deploys application binaries to your configured Azure app service in Azure.
app options
| Option | Description |
|---|---|
-c, --config <config> |
Path to the configuration file (default: a365.config.json) |
-v, --verbose |
Enable verbose logging |
--dry-run |
Show what would be done without executing |
--inspect |
Pause before deployment to inspect publish folder and ZIP contents |
--restart |
Skip build and start from compressing existing publish folder (for quick iteration after manual changes) |
-?, -h, --help |
Show help and usage information |
deploy mcp
Updates MCP server permissions on your agent blueprint.
a365 deploy mcp [options]
mcp options
| Option | Description |
|---|---|
-c, --config <config> |
Configuration file path (default: a365.config.json) |
-v, --verbose |
Enable verbose logging |
--dry-run |
Show what would be done without executing |
-?, -h, --help |
Show help and usage information |
Usage notes
Update MCP servers scopes and permissions on existing agent blueprint. This command adds permissions for Agent 365 Tools to the agent blueprint.
If you add or modify MCP servers in your agent code, use this command to update the permissions on your agent blueprint.
This command:
- Reads your MCP server configuration from your code.
- Updates the agent blueprint with the required permissions.
- Grants necessary API permissions for the MCP servers.
The permission update applies in the following order:
- OAuth2 permission grant (blueprint service principal → MCP platform)
- Inheritable permissions (agent blueprint → MCP resource)
- Admin consent (agent identity → MCP platform)
When to use deploy mcp:
- After adding new MCP servers to your agent.
- After changing MCP server configurations.
- When MCP tools aren't accessible to your agent.
You don't need to run deploy mcp:
- On initial deployment. This is handled automatically during setup.
- When only changing agent logic without MCP changes.
- After routine code updates that don't affect tooling.
Note
a365 deploy mcp only updates permissions - it doesn't deploy your code. Run a365 deploy app first if you have code changes.
Troubleshooting
Use the following sections to resolve potential problems with the deploy command.
- Not logged into Azure or wrong subscription
- Web App not found
- Permissions update fails
--restartfails
Not logged into Azure or wrong subscription
Run az login --tenant <TENANT_ID> and az account set --subscription <SUBSCRIPTION_ID>.
Web App not found
Ensure a365 setup has been run, or verify that webAppName and resourceGroup are correct in a365.config.json.
Permissions update fails
- Confirm
AgentBlueprintId,AgenticAppId, and environment are set ina365.config.json. - Ensure your account has rights to manage service principals and grants.
- Verify that
toolingManifest.jsonexists in your deployment project directory and contains valid scopes.
--restart fails
Run a full deploy without --restart to produce the publish/ folder, then use --restart for subsequent iterations.
Logs
CLI log files are stored at:
- Windows:
%LocalAppData%\Microsoft.Agents.A365.DevTools.Cli\logs\ - Linux/macOS:
~/.config/a365/logs/
To view the last 80 lines of the latest deploy log file, use Get-Content on Windows or tail on Linux/macOS:
# Windows
Get-Content $env:LOCALAPPDATA\Microsoft.Agents.A365.DevTools.Cli\logs\a365.deploy.log -Tail 80
# Linux/macOS
tail -80 ~/.config/a365/logs/a365.deploy.log
For runtime application logs, use Log Stream in the Azure portal for stdout/stderr from your App Service.