Microsoft Teams
Airgate posts to Microsoft Teams through Teams Workflows (Power Automate) flows that start with the trigger When a Teams webhook request is received. Airgate never needs Microsoft Graph permissions for Teams: you own the flow, and Airgate only calls its HTTP POST URL.
| Use | What happens | Set up |
|---|---|---|
| Guest sponsor delivery | A visitor registers on a self-registration portal and picks the employee they are visiting. Airgate sends the visitor’s Wi-Fi password to that employee as an Adaptive Card in a Teams chat; the employee hands it over. | Sponsor approval in Microsoft Teams |
| Event notifications | A webhook posts selected Airgate events (for example auth.reject or system.alert) to a flow, which can post them to a channel. |
Webhooks and HTTP actions |
| Messages from policy | The Microsoft Teams message preset of a context action posts a message when a policy rule runs it. | Webhooks and HTTP actions |
Sponsor delivery in short
Section titled “Sponsor delivery in short”- In Teams, open Workflows › New flow › Create from blank. Trigger When a Teams webhook request is received, Who can trigger the flow Anyone.
- Action Post card in a chat or channel: Post as
Flow bot, Post inChat with Flow bot, RecipienttriggerBody()?['sponsor_email'], Adaptive CardtriggerBody()?['attachments'][0]['content']. - Save and copy the trigger’s HTTP POST URL.
- In Airgate, Guests › Guest accounts › Defaults › Microsoft Teams: turn on Teams delivery enabled, paste the Workflow URL, Save, and Send test to your own address.
- On the portal, Receipts › Sponsors (Microsoft Teams): turn sponsors on and list each host’s name and Teams sign-in address.
The request body is a Teams message with the Adaptive Card plus plain fields
(sponsor_email, sponsor_name, guest_name, guest_email,
guest_phone, guest_company, username, password, valid_until,
portal) that a custom flow can use.
Before you begin
Section titled “Before you begin”- A Microsoft 365 user who can create flows in Teams Workflows or Power Automate, in the same tenant as the sponsors.
- An Airgate administrator with
guest:write(sponsor delivery) oradmin:write(webhooks, HTTP actions).
Verify
Section titled “Verify”Guests › Guest accounts › Delivery log shows each sponsor card with
channel Teams and status sent or failed; the flow’s run history in
Power Automate shows the matching runs.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause | Fix |
|---|---|---|
Teams workflow answered 401 / 403 |
The trigger does not allow anonymous callers, or the URL was cut. | Set Who can trigger the flow to Anyone; copy the full URL. |
Teams workflow answered 404 |
The flow or trigger was deleted. | Save the current HTTP POST URL in Airgate. |
Status sent but no card |
The flow could not post to the recipient. | Check the flow’s run history and the sponsor’s address. |
Related
Section titled “Related”© 2026 Airowire Networks Pvt. Ltd. Airgate is a product of Airowire.Product · Release notes · Security