Polier
DEEN

Sign-up not open yet

DEEN

Sign-up not open yet

Planned · Microsoft Teams

Approvals and notices where your team talks

Planned: Polier sends approval cards and notices to Microsoft Teams. Everything runs through Azure DevOps first – comments, pull request threads, status and "/approve" –, Teams comes as another channel.

Sign-up not open yet

Comes last, after the core product

Channels

Polier (AI agent)

The plan for work item #4799 is ready for approval (risk tier 2: authentication).

Approve the plan?

only valid for plan version 2 and exactly this state

ApproveReject

Mara K.

Looks right. I approve.

Polier (AI agent)

Approval recorded. I am starting on the code; the draft PR follows after build, tests and review.

Polier (AI agent)

The pipeline for pull request !812 is green and the reviewer status is "passed". The pull request is waiting for your review.

Jan P.

Thanks, I will take a look.

Polier (AI agent)

The monthly budget reached 75 %. At 100 % nothing new starts.

Polier (AI agent)

One task is parked because of a rate limit and continues later at the same place.

Illustration with sample data, not the result of a real run. This interface is a draft and not built yet.

Decisions are made in Teams, context gets lost in threads. Approvals and questions from Polier are meant to arrive where your team talks anyway – and stay bound to the rules in Azure DevOps.

From ballmüller solutions

In development, not available yet

Planned

What is planned for Teams

A bot of its own per instance, no shared bot for all customers.

Planned, not built yet.

Approval

Approval cards

Plan approvals and action approvals as a card in Teams. One click answers the waiting request.

  • bound to the plan's hash and version
  • only configured approvers count
  • every approval is in the audit

Notices

Notices as needed

The events Polier already knows as notifications today are meant to arrive in Teams as well.

  • plan ready, question, approval needed
  • budget levels, parked or failed run
  • pull request ready, kill switch

Instance

One bot per customer

As a bot of its own per instance, built with the Microsoft 365 Agents SDK. No shared bot for all customers.

  • approved in Teams by your admin
  • rights as in Azure DevOps
  • rolled out with the instance

Already in development

First: Azure DevOps

These routes are intended in the flow and built, but not yet tried against a real organization.

In development, so far tested against test doubles.

  • Plan and status as a comment

    The plan is a comment on the work item; every comment carries the line "Polier (AI agent), on behalf of …".

  • Questions in the work item

    A question is a comment with a mention; your answer lets the waiting run continue.

  • Findings in the pull request

    The reviewer writes threads and sets the status on the pull request. "@polier" in a comment starts a new review.

  • "/approve" on the work item

    Plan approval by comment only counts from configured people, only for exactly this plan and not from a comment edited afterwards.