Agent 365 CLI config command reference

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.

Manage Agent 365 CLI configuration. Provides options to manage Agent 365 CLI configuration settings. You can initialize new configurations interactively or display current configuration settings.

Minimum role required: None (local configuration)

Syntax

a365 config [command] [options]

Options

Option	Description
-?, -h, --help	Show help and usage information

config init

Interactively configure Agent 365 CLI or import from a file.

a365 config init [options]

Use this command to set up your Agent 365 CLI configuration through an interactive process or by importing settings from an existing configuration file.

init options

Option	Description
-c, --configfile <configfile>	Path to an existing config file to import
-g, --global	Create config in global directory (AppData) instead of current directory
-?, -h, --help	Show help and usage information

Remarks

The config init command launches an interactive wizard that minimizes manual input:

• Azure CLI integration: Automatically detects your subscription, tenant, resource groups, app service plans, and regions.
• Smart defaults: Generates resource names from your agent name and a timestamp (for example, myagent-webapp-11140916). You can customize these names before saving.
• Platform detection: Detects your project type (.NET, Node.js, Python) from the deployment project path and warns if no supported type is found.
• Client app validation: Validates your client app ID against your Entra tenant, checking that required permissions are configured and admin consent is granted. You have up to three attempts before the wizard exits.

Custom blueprint permissions (optional): The wizard includes an optional step to configure permissions for additional external resources, such as Teams presence or OneDrive files. Most agents don't require this. You can also configure permissions after initial setup using a365 config permissions.

Updating existing configuration: Re-running a365 config init loads your current a365.config.json as defaults. Press Enter at each prompt to keep the current value, or type a new value to update it.

config display

Show current Agent 365 CLI configuration.

a365 config display [options]

This command displays the current configuration settings for the Agent 365 CLI, so you can review your current setup.

display options

Option	Description
-g, --generated	Display generated configuration (a365.generated.config.json)
-a, --all	Display both static and generated configuration
-?, -h, --help	Show help and usage information

Configuration file structure

The CLI uses a JSON configuration file (a365.config.json) with the following key properties:

{
  "$schema": "./a365.config.schema.json",
  "tenantId": "your-tenant-id",
  "subscriptionId": "your-subscription-id",
  "resourceGroup": "rg-Agent 365-example",
  "location": "westus",
  "appServicePlanName": "asp-Agent 365-example",
  "appServicePlanSku": "B1",
  "webAppName": "webapp-Agent 365-example",
  "agentBlueprintDisplayName": "My Agent 365 Blueprint",
  "agentIdentityDisplayName": "My Agent 365 Agent",
  "agentUserPrincipalName": "agent@contoso.onmicrosoft.com",
  "agentUserDisplayName": "My Agent 365 User",
  "managerEmail": "manager@contoso.onmicrosoft.com",
  "agentUserUsageLocation": "US",
  "agentIdentityScopes": [
    "User.Read",
    "Mail.Send",
    "Calendars.ReadWrite",
    "Files.ReadWrite"
  ],
  "agentApplicationScopes": [
    "Mail.ReadWrite",
    "Chat.ReadWrite",
    "Sites.Read.All"
  ],
  "deploymentProjectPath": ".",
  "deploymentProjectFile": "YourProject.csproj",
  "botName": "my-Agent 365-bot",
  "botDescription": "My AI-powered agent for Microsoft 365 tasks"
}