Skip to content

feat(copilot): add AskT49 Microsoft 365 integration - #504

Merged
dodeja merged 4 commits into
mainfrom
alexgarcia/dev-14359-microsoft-365-copilot-agent-store-list-terminal49
Nov 9, 2026
Merged

dodeja merged 4 commits into
mainfrom
alexgarcia/dev-14359-microsoft-365-copilot-agent-store-list-terminal49

Conversation

@alosec

@alosec alosec commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

Adds AskT49 as a Microsoft 365 Copilot declarative agent under integrations/microsoft-365-copilot. Microsoft hosts the agent and calls the existing Terminal49 MCP server through user OAuth; tool definitions come from runtime discovery.

This directory owns only the Microsoft distribution package: three manifests, instructions, two icons, environment templates, and provisioning configuration. The MCP server and gateway remain the source of truth for tools and authentication. Microsoft's pinned Agents Toolkit packages and validates the app. No new service, npm workspace, dependencies, lockfile, vendored schemas, or custom build pipeline.

Validation: npm run agent-verify passes all seven steps under Node 24.22.1. Toolkit packaging and all seven provisioning steps pass from this directory, including Microsoft package validation. ZIP contents verified as exactly three resolved manifests and two icons. The existing installation identity was preserved locally. Previous live Copilot testing verified OAuth and dynamic tool discovery with a successful read-only carrier lookup; app display name is AskT49.

Both OAuth registration and update use AnyTenant, allowing customers in other Microsoft organizations to connect their own Terminal49 accounts. PKCE, user consent, and server-side account authorization remain required. Existing app and OAuth registration identities are preserved.

The live OAuth configuration was updated for cross-tenant access. All seven toolkit provisioning steps and all 59 Microsoft package checks passed. Partner Center accepted package v1.0.4 into a draft offer; it has not yet been submitted for certification.

Remaining release QA: fresh-user cross-tenant sign-in, container/fleet workflows, account isolation, reconnect, and declined write confirmation. Reviewer access and listing screenshots are still being prepared.

Refs DEV-14359.


Run Proof
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.

RetriggerView in GreptileConfidence Score: 5/5

The PR appears safe to merge within its stated development scope.

Summary

Adds AskT49 as a Microsoft 365 Copilot agent backed by the existing hosted MCP server.

  • Microsoft 365 Copilot can reach Terminal49 shipment tools through AskT49.
  • AskT49 is guided to ground shipment answers and confirm consequential changes.

No actionable issues were found.

Acknowledged scope: alosec explicitly defers public store submission and fresh-user, fleet, account-isolation, reconnect, and declined-write release checks. Development OAuth remains restricted to the home tenant.

Diagram

sequenceDiagram
    participant U as User
    participant C as Microsoft 365 Copilot
    participant W as Terminal49 OAuth
    participant M as Hosted MCP server
    participant A as Terminal49 API
    U->>C: Open AskT49
    C->>W: Sign in through registered OAuth client
    W-->>C: User access token
    C->>M: Discover tools with user token
    M-->>C: Available tools
    U->>C: Ask about shipments
    C->>M: Call selected tool
    M->>A: Request data with resolved user access
    A-->>M: Result
    M-->>C: Tool result
    C-->>U: Answer
Loading

Reviews (1) · Last reviewed commit: "docs(copilot): document provisioning and..." · Reviewed by Greptile

@vercel

vercel Bot commented Nov 5, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
api Ready Ready Preview Nov 5, 2026 7:55pm UTC

Request Review

@linear-code

linear-code Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

DEV-14359

@github-actions github-actions Bot added the risk-shadow:high Shadow-only risk signal: high label Nov 5, 2026
@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Shadow risk calibration

Signal Result Authority
Path classifier risk:medium Deterministic advisory policy
heuristic fallback risk-shadow:high Shadow only

Calibration result: disagreement (medium vs high).

Shadow risk never blocks or enables merge. Keep it in observation mode until roughly 50 pull requests have human-reviewed labels, then calibrate before considering any policy use.

@github-actions github-actions Bot added risk:unknown Advisory evidence unavailable or changed; no merge permission risk:medium Advisory path risk; current-head human review needed and removed risk:unknown Advisory evidence unavailable or changed; no merge permission labels Nov 5, 2026
@alosec
alosec marked this pull request as ready for review November 5, 2026 00:54
greptile-apps[bot]
greptile-apps Bot previously approved these changes Nov 5, 2026
@greptile-apps
greptile-apps Bot dismissed their stale review November 5, 2026 19:54

Dismissed because a newer commit was pushed; Greptile will re-review the current head.

@github-actions github-actions Bot added risk:unknown Advisory evidence unavailable or changed; no merge permission and removed risk:medium Advisory path risk; current-head human review needed labels Nov 5, 2026
@github-actions github-actions Bot added risk:medium Advisory path risk; current-head human review needed risk:unknown Advisory evidence unavailable or changed; no merge permission and removed risk:unknown Advisory evidence unavailable or changed; no merge permission risk:medium Advisory path risk; current-head human review needed labels Nov 5, 2026
@dodeja
dodeja merged commit 3f9bd6a into main Nov 9, 2026
28 checks passed
@dodeja
dodeja deleted the alexgarcia/dev-14359-microsoft-365-copilot-agent-store-list-terminal49 branch November 9, 2026 00:30

This branch was successfully deployed

1 active deployment
Preview — c0c7b920 Deployed Nov 5, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk:medium Advisory path risk; current-head human review needed risk-shadow:high Shadow-only risk signal: high

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants