Counts as reported in the Daily Task Digest of Sunday, 6 September 2026 (11 open: 5 high, 4 medium, 2 low; "No tasks are currently blocked pending input from others"). The digest of Friday, 4 September 2026 reported 9 open items, so scope grew by 2 over the weekend.
Vendor evaluation is complete and a recommendation is on the table: Zava Trading scored 8/10 (€14,500 one-time + €7,150/month, 99.9% standard SLA), ahead of Contoso Supplies Ltd at 7/10 and Fabrikam Manufacturing at 6/10. The brief itself is marked "Complete", but compliance is only Partial — the RFP is compliant while the SOW template is still missing, and no EcoVadis or CreditSafe ratings were found for the vendors.
Source: Executive_Procurement_Brief_ERP_Integration_2026 (sections 2–5); supporting set — ERP Cloud Implementation - Main RFP, ERP Cloud Implementation - Statement of Work, ERP Cloud Implementation - Q&A, RFP-2026-001_response3_CloudFirst-ERP.
A status update on the S2P agent has been outstanding since Adil Eli asked "What is the status of S2P agent?" on 22 April 2026 and is still logged as awaiting reply. Jira governance tickets ZAG-1 through ZAG-5 are assigned to Corey Gray, with ZAG-5 ("Draft compliance criteria for agent behavior") reported overdue, and ZAG-6 ("Set Up Agent Registration & Verification") is still unassigned in the ZAVA AI Governance space.
Sources: Daily Task Digest, 6 September 2026 (items 5 and 7); Jira weekly update emails of 26 August and 2 September 2026; governance artefacts — GovernedAI Governance Framework for S2P Agent, AI_Governance_Policy_Book.
Two Copilot data connectors are broken and unremediated: ServiceNowTickets2607141032 (flagged 21 August 2026, carried as a compliance risk) and Jira2606051042 (flagged 12 August 2026, carried as a data-integrity risk). On the automation side, the "Cowork Plan Approval" flow has failed repeatedly and one flow — "When agent is added or updated" — was disabled by the platform after consistent failures.
Sources: Daily Task Digest, 4 September 2026 (items 3, 4, 7); emails "Your Copilot connection ServiceNowTickets2607141032 needs immediate attention", "Alert! We've disabled one of your flows", "1 of your flow(s) have failed".
The Planner task "Communication Error Communication" in the plan "Absolute Technology R400 Infrastructure" was due 18 August 2026 and was reported 7 days late as of 25 August 2026. The digest still lists its current status as unverified. The team's General channel holds no posted discussion — only the system message from when the team was created on 23 February 2026 — so there is no conversational status to draw on.
Sources: email "You have late tasks" (25 August 2026); Daily Task Digest, 6 September 2026 (verification section); Teams — Absolute Technology R400 Infrastructure > General.
The FCS Application Upgrade team exists (created 23 February 2026, four members) but its General channel contains no posted messages, and no email, chat or document in the searched sources reports status, owners or milestones for it. Nothing here is a judgement on the workstream — it is an evidence gap.
Source: Teams — FCS Application Upgrade > General (system event only).
The deployment platform is documented — a Power Platform environment with Dataverse, a System Administrator role, and a Teams CoE structure — and the AI Agent Central v3 release is live with an employee AI Hub and Microsoft Agent 365 integration. The five readiness pillars (Business & AI Strategy, Technology & Data, Organizational Readiness, Security & Governance) exist as templates, which suggests assessment work is drafted rather than closed out.
Sources: AI Agent Central - Deployment Guide; index (AI Agent Central v3 release page); Pillar1–Pillar5 readiness templates; The Agent Readiness Framework - Pillars & Practices.
| Risk | Workstream | Owner | Severity | Evidence & mitigation |
|---|---|---|---|---|
| ServiceNow connector failure — compliance exposure | Integration health | Corey Gray | High | Flagged 21 Aug 2026 and still open: "Please review the connection status in the Microsoft 365 Admin Portal." Mitigation: repair ServiceNowTickets2607141032 via M365 Admin Portal → Microsoft Search → Connectors. |
| Jira connector failure — stale governance data | Integration health | Corey Gray | High | Flagged 12 Aug 2026: "Resolve this issue to ensure your data stays up to date." Mitigation: re-authorise Jira2606051042 (authentication/permissions review). |
| ERP procurement cannot close — SOW template missing | ERP | Corey Gray + Executive Sponsor | Medium | Compliance score recorded as Partial: "RFP compliant, SOW pending". Mitigation: upload the SOW template against the Pierre Fabre contract templates before contract generation. |
| No current EcoVadis / CreditSafe ratings for shortlisted vendors | ERP | Procurement Team | Medium | Section 1 of the brief records that no ratings were found and a compliance update is required. Also note Zava Trading's "regulatory coverage not fully described" risk entry. Mitigation: obtain ratings before award. |
| S2P agent status unanswered since April | S2P / governance | Corey Gray | High | Request from Adil Eli dated 22 Apr 2026 still logged as awaiting reply on 6 Sep 2026 — a stakeholder-confidence risk. Mitigation: issue a status note covering progress, blockers and next milestones. |
| ZAG-5 compliance criteria overdue; ZAG-6 unassigned | AI governance | Corey Gray | Medium | "ZAG-5: Draft compliance criteria for agent behavior" reported overdue; ZAG-6 "Set Up Agent Registration & Verification" shown as unassigned work. Mitigation: prioritise ZAG-5, assign ZAG-6. |
| Automation instability — approval flow disabled | Integration health | Corey Gray | Medium | "It's been failing every time we try to run it so we turned it off" (flow "When agent is added or updated"); the Cowork Plan Approval flow also reported failures. Mitigation: review failure logs and re-enable. |
| Agent workloads on a retired API surface | AI platform | Not identified | Medium | Azure OpenAI Assistants APIs required transition to Microsoft Foundry Agent Service by 26 Aug 2026; that date has passed. Mitigation: confirm no remaining dependency, migrate to Foundry Agent Service or the Responses API. |
| No reportable status for FCS Application Upgrade | FCS | Unassigned | Watch | No messages, mail or documents found for this workstream. Mitigation: nominate a reporting owner and establish a written status cadence. |
Microsoft's guidance is that applications relying on the Assistants API had to be migrated before 26 August 2026, after which it is no longer available; the supported replacements are the Microsoft Foundry Agent Service and the OpenAI Responses API. Foundry Agent Service (classic) carries its own, later retirement date. Programme relevance: directly affects any S2P or AI Agent Central workload built on the older surface.
Microsoft Learn Q&A — Assistants API retirement · Microsoft Learn Q&A — Foundry Agent Service (classic) timeline
Atlassian is expanding usage-based pricing across more cloud products, with actual usage of AI capabilities, automation and Bitbucket features priced from 3 December 2026; the vendor frames it as added visibility and control over spend. Programme relevance: the ZAG governance backlog runs in Jira, so automation and AI usage in that workflow becomes a budget line.
Atlassian company news · Praecipio analysis · Demicon analysis
At Knowledge 2026 ServiceNow announced Action Fabric, opening the ServiceNow AI Platform and its system of action to any AI agent regardless of where it was built, alongside AI Control Tower and related governance capability. Programme relevance: shapes how the ServiceNow connector and future agent integrations should be architected once remediated.
SAP's 2026 technology roadmap signals an accelerated shift to cloud, with product releases organised into phases across the year; SAP publishes release timing through Road Map Explorer and the S/4HANA Cloud Public Edition release pages. Programme relevance: the ERP procurement draws historical data from ARIBA/SAP, so SAP release phasing is a scheduling input for the integration workstream.
SAP Road Map Explorer · SAP S/4HANA Cloud Public Edition product releases
A Databricks account was activated for this tenant on 3 September 2026. It is not yet referenced in any programme status, plan or risk item. Programme relevance: a new data platform dependency that should be brought into scope and governance explicitly rather than adopted informally.
Source: email "Welcome to Databricks" (3 September 2026) — internal signal, no external corroboration sought.