<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Change Management on Thinx-Tank</title><link>https://blog.thinxai.net/tags/change-management/</link><description>Recent content in Change Management on Thinx-Tank</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 19 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.thinxai.net/tags/change-management/index.xml" rel="self" type="application/rss+xml"/><item><title>The Agent You Approved Is Not the Agent Running</title><link>https://blog.thinxai.net/posts/the-agent-you-approved-is-not-the-agent-running/</link><pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/the-agent-you-approved-is-not-the-agent-running/</guid><description>&lt;p&gt;On October 15, Microsoft announced a set of Copilot Studio features in its &lt;a href="https://www.microsoft.com/en-us/copilot/blog/copilot-studio/delegate-shared-business-processes-to-agents-that-are-more-persistent-and-proactive-with-microsoft-copilot-studio/"&gt;Microsoft Copilot Blog post on persistent, proactive agents&lt;/a&gt;: agent accounts with their own credentials, business process memory, and triggers that start an agent on an external signal or a set cadence, no prompt required. The features are rolling out through the Frontier program.&lt;/p&gt;&#10;&lt;p&gt;Read the memory description closely. Business process memory lets an agent carry forward preferences and process context into each new cycle, and Microsoft puts it plainly: any idiosyncrasy of the business process that one person raises to the agent becomes a shared resource for everyone else. One person&amp;rsquo;s aside, offered in one conversation, becomes operating context for the whole team in the next cycle.&lt;/p&gt;</description></item></channel></rss>