Microsoft.Agents.A365.DevTools.Cli
1.1.193
Prefix Reserved
dotnet tool install --global Microsoft.Agents.A365.DevTools.Cli --version 1.1.193
dotnet new tool-manifest
dotnet tool install --local Microsoft.Agents.A365.DevTools.Cli --version 1.1.193
#tool dotnet:?package=Microsoft.Agents.A365.DevTools.Cli&version=1.1.193
nuke :add-package Microsoft.Agents.A365.DevTools.Cli --version 1.1.193
CLI tool for Microsoft Agents 365 development
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
This package has no dependencies.
| Version | Downloads | Last Updated |
|---|---|---|
| 1.1.193 | 50 | 6/1/2026 |
| 1.1.188 | 222 | 5/27/2026 |
| 1.1.184 | 458 | 5/19/2026 |
| 1.1.181 | 307 | 5/15/2026 |
| 1.1.178 | 293 | 5/11/2026 |
| 1.1.176 | 218 | 5/8/2026 |
| 1.1.174 | 210 | 5/6/2026 |
| 1.1.171 | 260 | 5/1/2026 |
| 1.1.165-preview | 153 | 4/30/2026 |
| 1.1.163-preview | 142 | 4/29/2026 |
| 1.1.161-preview | 140 | 4/28/2026 |
| 1.1.154-preview | 191 | 4/23/2026 |
| 1.1.145-preview | 211 | 4/20/2026 |
| 1.1.139-preview | 247 | 4/14/2026 |
| 1.1.132-preview | 282 | 4/8/2026 |
| 1.1.124-preview | 293 | 3/31/2026 |
| 1.1.117-preview | 212 | 3/25/2026 |
| 1.1.115-preview | 372 | 3/12/2026 |
| 1.1.109-preview | 287 | 3/6/2026 |
| 1.1.104-preview | 185 | 3/3/2026 |
Added
- --skip-sp-provisioning option on setup all — skips the interactive in-line provisioning of missing resource service principals (issue #429). Default: setup prompts per-resource and runs az ad sp create --id <appId> using the operator's az login. With this flag, missing SPs are excluded from the consent URL and listed in the Action Required block with the az command and a per-SP consent URL. Implicitly enabled when stdin is redirected (CI / pipe scenarios).
- Action Required block in the setup all summary now lists missing service principals — each entry shows the resource, pending scopes, the az ad sp create command, and the per-SP consent URL needed to complete provisioning.
Fixed
- setup all now exits silently on Ctrl+C instead of printing ERROR: Setup failed: A task was canceled. followed by a misleading partial summary.
- setup all --m365 no longer fails with AADSTS650053 because the Messaging Bot scope was hard-coded to scopes the resource SP does not publish (issue #429).
- setup all no longer fails with AADSTS650053 for any drift between requested scopes and what a resource SP actually publishes (issue #429). Unpublished scopes are filtered out before building the consent URL; per-resource warnings surface what was dropped.
- setup all no longer fails with AADSTS650052 ("organization lacks a service principal for ...") when a resource SP is missing in the tenant (issue #429). Setup now prompts per-resource and provisions the SP via az ad sp create. Declined / failed paths are surfaced in the Action Required block.
- setup all no longer fails with AADSTS650053 or AADSTS500011 for V2 MCP per-server audiences (issue #429). Scopes now route to the correct per-audience resource instead of collapsing onto the WorkIQ Tools URI.
Changed
- setup all and setup permissions now issue the S2S app role assignment and delegated AllPrincipals OAuth2 consent via az rest against the operator's existing az login session, replacing the previous Connect-MgGraph PowerShell fallback (issue #429). pwsh and the Microsoft.Graph PowerShell modules are no longer required for this path. The per-prompt [y/N] confirmation is unchanged.
- setup all: fallback consent prompt now explains the ambiguity (declined vs error) and offers to grant the permissions programmatically via az login; per-audience permission lists and consent URLs show per-server MCP names (e.g. mcp_MailTools) instead of a generic Agent 365 Tools for every audience.