Teams and Google Chat notifications

AEVU can post short alerts to a Microsoft Teams channel or a Google Chat space when something needs attention.

Who does this: a workspace member with the integration.manage permission (Owner and Admin by default). Members with integration.view can see the screen but not change it. The organisation must allow Teams channel notifications and/or Google Chat notifications (Organization → Integrations), and your plan must include channel notifications (Team and above). The platform operator must also offer the capability: Teams and Google Chat notifications are not on by default (Platform:AvailableCapabilities).

What a message contains

Deliberately little: the event name, the workspace name, and a secure link into AEVU. No project name or code, no risk text, no money, no people, no AI content. The link goes through normal sign-in and access checks and carries no token.

Event you can choose	Sent when
Stage gate waiting for approval	A project's gate is sent to the PMO for a decision
Critical risk alert	A risk alert rule raises a Critical alert
Change request waiting for approval	A change request reaches an approval step
Import finished	A spreadsheet import finishes adding rows

Create a Teams Workflow webhook

Teams needs a Workflows (Power Automate) address. The old Office 365 connector addresses (*.webhook.office.com) are retired and AEVU refuses them on purpose.

1. In Teams, open the channel, choose More options (...) → Workflows.
2. Pick the template whose trigger is When a Teams webhook request is received (it posts the request to a channel). Template names vary by Teams version.
3. Name the flow, confirm the team and channel, and create it.
4. Copy the webhook URL it shows.
5. Add a co-owner to the flow. The flow stops when its owner leaves the organisation.

Accepted Teams addresses are on *.logic.azure.com (path /workflows/…) or *.environment.api.powerplatform.com (path …/workflows/…), https, port 443.

Create a Google Chat webhook

1. Open the Chat space, choose the space name → Apps & integrations → Webhooks (or Manage webhooks).
2. Add a webhook, name it (for example AEVU), and save.
3. Copy the URL.

Accepted Chat addresses look like https://chat.googleapis.com/v1/spaces/<space>/messages?key=…&token=….

The URL is a credential

Anyone with the address can post to the channel. AEVU encrypts it, never shows it again (only the host and last four characters), never logs it and never puts it in the audit log. Treat it like a password.

Set it up in AEVU

1. Open Settings → Channel notifications.
2. Under Channels choose Add a channel.
3. Choose Where it posts (Teams or Google Chat; an unavailable provider is greyed out with the reason), give it a name such as PMO approvals, and paste the webhook URL.
4. Choose Add channel. AEVU checks the address twice: the shape, and that the host resolves only to public addresses.
5. On the channel row choose Send test message. When it is delivered the row shows Test delivered. Check it arrived in the channel.
6. Under Rules choose New rule: give it a name, choose the Send when event(s), choose Projects (all, or Chosen projects), choose the Channel, and choose Save as draft.
7. A new rule is saved off (the On column). You can switch it on only once the channel has a delivered test.

You can have up to 20 channels per workspace. The Deliveries button on a channel row shows each message: Waiting to send, Sending, Delivered, Failed or Not sent.

Changing or removing

• Change a channel's name or replace its webhook; a new address clears the last test and any broken state, so test again.
• Remove deletes the channel and its rules, and works even if the provider is switched off.

How delivery behaves

• Messages are queued and sent by a background worker; they survive a restart.
• Delivery is at least once, so a rare duplicate is possible and the history flags it.
• Temporary failures are retried with growing delays (up to 6 attempts), then marked Failed.
• A 404 or 410 from the provider marks the channel Broken and stops messages until you save a new webhook.
• Redirects are never followed.

Common problems

Problem	Fix
"That address can't be used"	Use a Workflows URL (Teams) or a chat.googleapis.com webhook, https only
Provider greyed out	The platform, plan, organisation or workspace has it off; the text says which
Rule cannot be switched on	Send a test message first (notification.testRequired)
Broken channel	The webhook was deleted or the flow's owner left; create a new webhook and replace the address
21st channel refused	Limit of 20 (notification.channelLimit)

Not yet proven live

Real posts to Teams and Google Chat have not been exercised against production destinations. Send a test message and confirm it arrives before relying on rules.