Writing / Governance & operations
Agents get their own accounts, the EU’s first AI Act standard, a tax e-notice deadline
Issue three: agent accounts in Copilot Studio, the first harmonised standard under the EU AI Act, Türkiye’s new e-notification rules, UiPath audit-log and model changes, Maestro and a Gartner signal.
This week is about accounts and records. Microsoft is giving agents their own Microsoft 365 accounts, UiPath stopped logging prompts and responses by default in new AI policies, and Türkiye’s Revenue Administration rewrote the password and event-log rules for tax e-notifications. Brussels, meanwhile, delivered the first concrete compliance tool for high-risk AI.
Copilot Studio: agent accounts, business process memory and triggers
Microsoft has started rolling out three Copilot Studio capabilities through its Frontier programme. With agent accounts, an agent works under its own credentials and scoped permissions instead of borrowing a user’s or maker’s identity; people can call it in Teams and Outlook and @mention it in Word, Excel and PowerPoint comments. Business process memory carries preferences and process context into the next cycle; makers switch it on, and users can view and delete what was saved. Triggers start an agent’s cycle from an external signal such as an e-mail, or on a set cadence, without a prompt. Admins can scope access and manage the agent’s lifecycle in the Power Platform admin center. Further access policies, cost management and lifecycle controls are planned “in the coming months”. The post gives no general-availability date, licensing or price.
Why it matters. The robot-account question RPA teams have argued about for years has moved inside the office suite. An agent with its own identity is the right call for the audit trail, because it separates what the agent did from what a person did. My reading: an agent with a mailbox and a Teams presence sits squarely within the KVKK principle decision from last issue, and memory brings its own questions about retention and privacy notices. I wouldn’t multiply these accounts in production before the cost and lifecycle controls land. For a pilot, start simple: one owner, one purpose and a list of the channels each account may read.
The first harmonised standard under the EU AI Act: EN 18286
Commission Implementing Decision (EU) 2026/2274 published the reference of EN 18286:2026, a quality management system standard for AI drafted by CEN and CENELEC, in the Official Journal. According to the Commission, providers of high-risk AI systems that apply it get a presumption of conformity with the Article 17 quality management requirements it covers. The standard is built around the AI system’s lifecycle rather than the organisation, and is designed to sit on top of ISO/IEC 42001, ISO 9001 or sector systems. Organisations without 42001 can use it to extend an existing QMS or build a new one. The Commission says more harmonised standards will follow.
Why it matters. Until now, high-risk obligations came with legal text and draft guidance, but no concrete answer to an auditor’s “measured against what?”. EN 18286 is the first one. If your company sells AI-enabled products or services into Europe, bring the quality team that runs your ISO 9001 or 27001 into the conversation now. One caveat: this covers Article 17 only. Whether your system is high-risk in the first place is a separate question, and it comes first.
Türkiye’s Communiqué 596: a 30 November e-notification deadline, and a rule on sharing passwords
Tax Procedure Law General Communiqué No. 596 resets the procedures for electronic tax notifications under Article 107/A, as amended by Law No. 7587, and repeals Communiqué No. 456. Corporate taxpayers, individuals taxed on actual business, agricultural or professional income, and general and limited partnerships must join the system. Those not yet enrolled have until the end of the month after publication, which is 30 November 2026; new taxpayers must join within 15 days of starting business. A notice counts as served at the end of the fifth day after it reaches the system, and event logs are time-stamped and kept for thirty years. Recipients must protect their user code and password, not share them with third parties and not let others use them. Anyone enrolled before 1 July 2026 carries on with existing credentials.
Why it matters. A robot that checks the e-notification inbox every morning and routes notices to the right team is one of the most common finance automations in Türkiye. The five-day rule is a reminder that a day of robot downtime is a day off a legal deadline, so monitoring and alerting here are not optional. The more delicate point is the password: write down which identity the robot uses to log in to the Digital Tax Office, and under whose authority. Ask your financial advisor and legal team how the no-sharing rule applies to robot accounts; this isn’t legal advice. And if a group company still isn’t enrolled, the last day is 30 November.
UiPath: AI audit logging default changes, Claude Sonnet 4 removed
Since 16 October, new AI Trust Layer policies no longer save prompt inputs and model outputs in audit logs by default; until saving is enabled, those fields show as “Blocked by Policy”. Existing policies keep their setting. On 13 October, following its retirement on Amazon Bedrock, Claude Sonnet 4 was removed from the UiPath platform; UiPath-managed models moved to Claude Sonnet 4.6 automatically. Bring-your-own (BYO) configurations still pointing at Sonnet 4 become invalid and fall back to UiPath-managed models unless updated. Model Hub now shows the status of BYO configurations. Separately, Relay can now carry Snowflake and SQL Server connections from on-premises networks, with Relay client 26.4.4 or later.
Why it matters. Not logging content by default is sensible for data protection, but if you ever need to investigate an agent’s bad decision, the prompt and the response may simply not be there. I think this should be a policy decision, not a default: which processes keep content logs, for how long, and who can read them. The Sonnet 4 note is the quieter risk. Where you brought your own model, an agent may have fallen back to a different one without anyone noticing, which is both a quality and a data-residency question. Check the BYO status in Model Hub this week.
Maestro: Flow leaves preview, and a coding agent can now build a BPMN process
The 13 October notes unify the canvas names as Maestro BPMN, Maestro Case and Maestro Flow, and Maestro Flow is no longer labelled as preview. In Maestro Case, stages that can end a case get a badge, failed or terminated stages no longer show as in progress, a new API endpoint lists the ad-hoc tasks available on a case, and role definitions are validated. In Flow, your own guardrail configuration now appears by name with its provider. A preview from 7 October lets a coding agent such as Claude Code, Codex, GitHub Copilot, Cursor or Jules build a Maestro BPMN process from a process description, a process map, a PDD or a BPMN model. The agent proposes a plan for approval, then builds, debugs and deploys.
Why it matters. Handing part of the PDD-to-process path to a coding agent is tempting, but the output can’t be better than the PDD. A weak PDD now turns into a wrong process faster. I’d treat the agent’s plan like a design review and record the approval. Flow leaving preview makes a production decision easier; still check the support and release terms in your own contract.
Gartner: over $3.5 trillion of AI infrastructure spending could face impairment by 2030
According to the title of Gartner’s 14 October release, more than $3.5 trillion of AI infrastructure spending could be exposed to impairment by the end of 2030. Gartner’s page blocks automated access, so this item rests on the title alone; other figures visible in search snippets couldn’t be read on the primary page, so I’ve left them out.
Why it matters. It reads like a warning to infrastructure investors, but enterprise buyers are exposed too. If model and GPU providers consolidate, the company or the price behind a multi-year AI contract can change. My rule: an architecture that keeps the model swappable (an abstraction layer, your own evaluation set) and a contract with an exit clause. This week’s Sonnet 4 note is a small example of how quietly a model can change underneath you.
Next week I’ll be watching whether Microsoft publishes licensing and cost controls for agent accounts, and which harmonised standards line up behind EN 18286.
Sources
- Delegate shared business processes to agents that are more persistent and proactive with Microsoft Copilot Studio
Microsoft Copilot Blog, October 15, 2026 · Accessed October 19, 2026 - First harmonised standard supporting the AI Act published in the Official Journal
European Commission, Shaping Europe's digital future, October 19, 2026 · Accessed October 19, 2026 - Harmonised standards: Artificial intelligence (AI)
European Commission, Internal Market, Industry, Entrepreneurship and SMEs, October 14, 2026 · Accessed October 19, 2026 - Tax Procedure Law General Communiqué No. 596 (Vergi Usul Kanunu Genel Tebliği, Sıra No: 596)
Official Gazette of Türkiye, Ministry of Treasury and Finance (Revenue Administration), October 11, 2026 · Accessed October 19, 2026 - Automation Cloud release notes — October 2026
UiPath Documentation, October 16, 2026 · Accessed October 19, 2026 - Maestro release notes — October 2026
UiPath Documentation, October 13, 2026 · Accessed October 19, 2026 - Gartner Says Over $3.5 Trillion of AI Infrastructure Spending Could Be Exposed to Impairment by the End of 2030
Gartner, October 14, 2026 · Accessed October 19, 2026
This radar is compiled by an AI-assisted research pipeline in which every item links to its primary source. The commentary is mine. If you spot a mistake, write to me and I will fix it.