Community Champion

Posted on by

DO NOT PRESS

Sometimes innovation isn’t about solving problems.
Sometimes it’s about proving that you can build something… even when you absolutely shouldn’t.

For the Community Champion challenge, I built a Canvas App with a single button:

After you click the button DO NOT PRESS, the system saves a line into a SharePoint list:

It has no business value, no purpose, and is wildly overengineered.
Naturally, it triggers multiple cloud services.

The Concept

The app presents the user with one very clear instruction: do not press the button.

If the user ignores this warning, the system reacts dramatically by:

  1. Logging the incident in SharePoint
  2. Triggering a Power Automate flow that triggers when a new item is created or modified.
  3. Starting an Azure Automation Runbook that give an output like this:
    DO NOT PRESS was pressed by at 1/23/2026 2:31:53 PM. The time is 14:32:41
  4. Sending a judgmental email to the person who pushed the button saying:
    “Why would you do that?”

Nothing is prevented. Nothing is fixed.
Everything is logged.

Architecture Overview

Canvas App
→ Power Automate (Instant Flow)
→ SharePoint List
→ Azure Automation Runbook
→ Email Notification

This design intentionally uses far more components than necessary to accomplish absolutely nothing.

Canvas App

The Canvas App contains:

  • One screen
  • One large, highly visible button
  • Text: DO NOT PRESS

Button behavior

When pressed, the button:

  • Window saying I TOLD YOU NOT TO PUSH THE BUTTON
  • Created an item in SharePoint list
  • Calls a Power Automate Cloud flow
  • Passes the current user and timestamp
  • Displays a notification confirming poor decision-making

There is no confirmation dialog.
There is no undo.

SharePoint List – Logging the Incident

A SharePoint list is used to permanently record the mistake.

List name: DoNotPressthebutton

Columns:

  • Title – “They pressed the button at date and hour”

This ensures full auditability of an action that should never have happened.

Power Automate

The Power Automate flow is triggered directly from the SharePoint.

Flow steps:

  1. Create SharePoint item
    Logs the button press immediately.
  2. Start Azure Automation Runbook
    Passes user and timestamp as parameters.
  3. Send Email (Outlook)
    Sends a message with the subject: Why would you do that?

The email confirms:

  • Who pressed the button
  • When it happened
  • That the action has been recorded for no reason whatsoever

Azure Automation Runbook

The Azure Runbook exists solely to prove that this button press was serious enough to involve Azure.

The runbook:

  • Receives parameters from Power Automate
  • Writes a log entry such as: “DO NOT PRESS was pressed by at 1/23/2026 2:31:53 PM. The time is 14:32:41”

No resources are modified.
No remediation is performed.
The runbook completes successfully, as disappointed as possible.

Email Notification

An email is sent after the flow runs:

Subject: Why would you do that?
Body:

  • Confirms the button was pressed
  • Names the user
  • Reassures everyone that this has been logged

This email exists purely to shame the action.

Why This Exists

  • It solves no business problem
  • It introduces unnecessary complexity
  • It is intentionally overengineered
  • It is fully documented

This solution demonstrates:

  • Canvas Apps
  • Power Automate
  • SharePoint integration
  • Azure Automation
  • End-to-end orchestration

All in service of a button that should not be pressed.