GIABO is a 27-specialist swarm that administers the project office inside Microsoft 365. It reads the record, talks to the team, follows up with care, and stops for a person whenever a locked plan is at stake.
Not a chatbot with a longer prompt. A Digital PMO employee: specialists for schedule, blockers, risk, and change control, working as one office across Copilot and Teams.
Stand the office up from the Azure Marketplace. Point it at a SharePoint site. Talk to it in Microsoft 365 Copilot or Microsoft Teams the way you would brief a coordinator. GIABO routes the request, writes the fact to the project record, and asks the Project Manager before any locked baseline moves. It does not replace the PM. It will not approve its own change.
The work the office does every day, without a daily blast or a silent rewrite.
New documents and meeting notes in the linked library are brought into the project record automatically. Content is addressed by SHA-256 so the same file is an update, not a second copy — a sovereign audit hash for every ingested artefact.
Log hours, raise a blocker, flag a risk, or request a plan change in ordinary language. The conversation guide hands each message to one specialist. A proposed change pauses as an approval card for the Project Manager.
Follow-ups are scored by critical path, risk, and deadline — not a morning mail merge. If someone was contacted in the last 24 hours, GIABO stays quiet. Fatigue protection holds even on a critical-path slip.
SharePoint intake and deterministic office records are keyed with SHA-256. Re-running a sweep does not invent a second artefact. The audit trail stays addressable, idempotent, and yours.
PRINCE2, PMP, and Agile intelligence in one office — each specialist stays in its lane.
Stage tolerances are classified, not bargained. A real breach raises an exception hold until a person acknowledges it or escalates to the board. In-tolerance risk is logged, not dramatised.
Hours and percent complete stay on the schedule specialist. Critical-path integrity is recorded, not rewritten into a new end date. Moving a locked baseline is change control — never a progress note.
Impediments and cross-team waits go to a servant-leader facilitator. You get a blocker and a next step. Progress percent is not silently rewritten, and the locked plan is not slipped to “clear the board.”
Provision from the Azure Marketplace. Work in Microsoft 365 Copilot — set up a project, request a governance brief, check plan usage — or chat in Microsoft Teams. There is no separate admin console to learn. The Agent Handbook below is the product manual.