October 16 edition.
I started these weekly recaps to make it easier to keep up. I need the consolidation as much as anyone reading it. This week, the draft needed another pass as Friday’s updates arrived.
Microsoft’s October 15 announcements changed the lead: Copilot Studio agents are getting their own accounts, shared business-process memory and triggers. Legal skills are moving into Word and Cowork. GitHub has two new security capabilities, and Power Platform makers have connector changes to check.
The question running through it all: what happens when the demo becomes something a team depends on? Identity, memory, review and cost all become part of the build.
This week in 60 seconds
- Agent accounts are rolling out through Frontier. Copilot Studio agents can have their own Microsoft 365 presence. Their shared memory needs particular care, even in one-to-one chats.
- Legal skills have a GA announcement and a phased rollout. More than 20 skills span Word and Cowork. The old Legal Agent is retiring, without a specified shutdown date.
- You can build apps in Copilot Studio. They run on the same Microsoft Copilot Managed Runtime as apps built in Cowork. App Builder and Vibe retire November 30.
- SharePoint is compiling team knowledge. Its Frontier preview builds linked Markdown; Cowork and custom Studio-agent integrations remain upcoming.
- GitHub adds AI security work. AI Scan examines pull requests; Agentic Autofix tackles eligible existing alerts. They have different inputs and limits.
- Maintenance matters. Review Azure DevOps authentication, Word download URLs and November 16 GitHub model retirements. HydraFusion Max, Argon and Maia round out the week.
1. Copilot Studio agents get accounts, memory and triggers
Microsoft’s October 15 announcement brings agent accounts, business-process memory and triggers to agents using the GitHub Copilot harness. An agent can have its own Microsoft 365 identity and mailbox, with supported Teams, email and Office-comment interactions. This is a Frontier rollout, with an early-release environment, administrator setup and licensing prerequisites. Microsoft announcement.
The memory detail deserves more attention than the mailbox. Agent-account memory is shared across users, including one-to-one conversations. Microsoft says summaries of contributed files or chats can appear in responses to people who cannot access those originals. There is no shared-memory opt-out in this preview. That is specific to agent accounts; the older general memory feature describes separate memories for individual users. Agent-account documentation · General memory documentation.
Triggers can start work from events or schedules, but the tools and instructions still determine what the agent does. Publishing and activation are required, and usage is metered. The account preview supports generating documents; targeted editing and coauthoring of existing documents are not supported. Trigger documentation.
There is setup behind the identity. Makers need Microsoft 365 E5 plus Agent 365, or E7; each agent needs an available Microsoft 365 Frontier for AI Teammates license. Administrators must activate the template and enable agent accounts. Usage charges are separate. Check those prerequisites before promising a team a working pilot. Account prerequisites.
For a focused pilot, use a small shared process, synthetic information and two users. Have one person contribute context, then ask the other to query it. Inspect what the agent remembers, which identity its tools use and what the trigger actually starts.
2. Build apps in Copilot Studio on the same runtime as Cowork
You can now build apps directly in Copilot Studio. Describe what you need, refine the generated app in an interactive preview, then publish and share it. The authoring experience brings the conversation, app preview, code, data and connections together. Apps overview.
Apps built in Copilot Studio and Copilot Cowork run on the same Microsoft Copilot Managed Runtime. Microsoft hosts the apps, with Entra authentication, tenant governance and a shared administrator inventory. That gives makers different places to build while keeping the resulting apps on a common platform. Managed Runtime overview.
Microsoft announced Apps in Copilot Studio in its October 7 update. It remains in public preview, with a gradual rollout; Microsoft says the preview is not intended for production use. October 7 update.
Vibe.PowerApps is on the way out. And yes, I still think “vibe” is a funny word to put beside critical business apps.
Microsoft’s October 12 notice says the App Builder agent and vibe.powerapps.com retire on November 30, 2026. New creation ends in mid-October, when migration tooling is also expected. Apps that are not successfully migrated become inaccessible through those retired experiences. Public copy of Microsoft’s retirement notice.
Find the owner of each affected app and verify the migrated result. Starting migration is only one step.
3. Check the credits before the first build
A question came up in my recent Apps discussion: can this use credits from the rest of the tenant? The precise answer is unallocated tenant credits. Eligible Copilot Studio environments without an allocation configuration default to drawing from that prepaid pool. That does not mean capacity already reserved for another environment. Microsoft’s capacity documentation.
Apps reuse an existing personal developer environment or create one through routing when needed. Each app does not automatically create another environment. Managed Runtime FAQ.
Building, testing and evaluating can consume credits before publication. To contain prepaid consumption, allocate an amount and disable tenant-pool draw where appropriate. Check linked pay-as-you-go billing, which can still fund activity. App runtime has separate per-user controls in the Microsoft 365 admin center. Cost controls · App billing.
4. Skills move across Chat, Cowork and legal work
Microsoft’s October 9 notice brings skill creation, editing, uploading and sharing to Copilot Chat. Rollout begins in October and is expected to finish by mid-November; Information Barriers tenants have a November rollout with additional sharing restrictions. Chat-created skills can work in Cowork. Cowork-created skills reach Chat only when shared. Public copy of MC1493223.
October 15 added a concrete industry example: more than 20 legal skills across Word and Cowork. Word supports document review and tracked edits; Cowork supports broader work across agreements and files. Partner legal plugins are beginning to roll out. Defined-term navigation is a future preview. Microsoft legal announcement.
The GA announcement does not mean every tenant has it immediately. MC1509799 gives a mid-October to mid-December rollout. It also says the standalone Legal Agent is retiring and existing users will lose access, but provides no shutdown date. December’s rollout target is not a retirement deadline. Public copy of MC1509799.
For eligible commercial Copilot subscribers, Word desktop’s legal plugin defaults on. Cowork users add Legal for Cowork through Customize. The two have separate administrator controls. Contract review currently uses a playbook; generated analysis and redlines still need professional review. Setup and supported workflows · Administrator controls.
The central Tools registry covers plugins, skills, MCP servers and connectors. Reusable work needs an owner, access decisions and a way to check its output. Microsoft’s Tools registry documentation.
Start with one recurring deliverable and test the skill against a second case. For a legal pilot, compare playbook coverage, citations and reviewer corrections.
The useful question is whether the skill captures how the team actually works: which evidence it needs, which rules it applies and what happens when information is missing. A reusable instruction can repeat a weak process just as efficiently as a good one.
5. GitHub adds security detection and remediation
Two October 15 GA launches cover different jobs. AI Scan examines pull-request changes beyond CodeQL’s current language coverage, including PHP, Bash and Terraform. Its findings are advisory and cannot block merges; fork and Dependabot pull requests are excluded. AI Scan announcement.
Agentic Autofix investigates existing code-scanning alerts, changes code, attempts CodeQL validation and opens a draft pull request. It can group up to 25 default-branch alerts. Alerts found only on a pull request or another branch cannot be assigned. These launches do not establish one automatic detection-to-fix pipeline. Agentic Autofix announcement.
Eligibility and administrator settings apply. Both consume Code Security AI Credits; Agentic Autofix also uses Actions minutes. Preview organizations must enable Agentic Autofix again. Its validation has limits, including custom queries and third-party alerts. Access requirements · Validation limits.
For AI Scan, public repositories are eligible; private and internal organization repositories need Code Security or Advanced Security. An individual Copilot license is not required. That still leaves the credit budget and someone responsible for reviewing the findings. AI Scan eligibility.
The test I care about: does the proposed fix address the vulnerability while preserving the application’s behavior? Count false positives, review effort and cost as well as cleared alerts.
6. More model choice, and more reasons to rerun evaluations
HydraFusion Max
GitHub’s October 14 update expands HydraFusion and introduces Max. Its pool includes Claude Opus 5.5, GPT-6 Astra, GPT-6.1 Sol and GPT-6 Luna, with orchestration choosing models and workflows. Both remain in research preview across VS Code, the Copilot app and CLI, subject to eligibility and policies. GitHub’s announcement.
Each model pass contributes to billing at that model’s standard rate; the Auto-selection discount does not apply. Discarding a draft also does not automatically undo its file edits. Compare a strong single model, HydraFusion and Max on the same task, including the total cost and review effort. HydraFusion documentation.
Foundry and Argon
Microsoft’s October 14 gpt-chat-latest update adds GPT-6-level intelligence, GenUI and progressive interleaved responses to existing Foundry deployments without redeployment. The model remains preview. Record the version and test date when evaluating an endpoint whose behavior can change. Foundry announcement · Model documentation.
Gemini 4 Argon’s October 13 release broadens September’s restricted access: developers and enterprises through the API, Ultra subscribers in Antigravity, and Pro or Ultra in the Gemini app and AI Mode. GitHub announced gradual availability for Pro+, Max, Business and Enterprise; ordinary Pro is not listed. Original announcement · Broader release · GitHub release note.
7. Maia 300 is next year’s infrastructure story
Microsoft announced Maia 300 on October 12, with production deployments planned for 2027. Maia 200 is already serving Microsoft workloads. Keep those generations separate when discussing what powers a Copilot session today. Microsoft announcement.
Microsoft reports up to seven times Maia 200’s rack-scale token throughput in a full 96-accelerator configuration. That figure describes Microsoft’s full rack-scale system comparison. Long-running agent work needs capacity; this announcement does not establish a new Copilot price. Architecture deep dive.
8. Work IQ brings business data and team knowledge into Copilot
Work IQ is getting more useful context from two directions: business applications and team knowledge. Business Applications in Work IQ lets people ask Microsoft 365 Copilot questions grounded in Dynamics 365 and Power Apps data. The feature is in preview.
Think questions about sales opportunities, active cases or other information already held in a business application. Setup includes availability for the intended users and Work IQ settings for the environment. Microsoft documents different defaults for production environments and sandboxes. Work IQ quickstart · Default settings.
Separately, SharePoint’s October 14 announcement, updated October 15, introduces team knowledge bases in Frontier public preview. Teams contribute content; Work IQ compiles it into interlinked Markdown. Current access requires usage-based billing. Cowork tools and custom Copilot Studio-agent integration are upcoming; Autopilot has its own rollout. SharePoint announcement.
Microsoft distinguishes asking about knowledge-base pages from maintaining them: questions require Microsoft 365 Copilot but do not consume Copilot Credits; creation and maintenance do. SharePoint permissions govern access. Knowledge-base usage and permissions.
The useful shift is bringing application data and documented team knowledge closer to the conversation where work happens. Keep source references, corrections and exceptions visible as that knowledge evolves.
9. Two connector checks for Power Platform makers
Azure DevOps: MC1508508 targets connections created before September 1, 2024. Removal of their legacy authentication has begun and finishes by November 30. That is a completion date, not a guaranteed grace period. Create a replacement, complete consent, repoint dependencies and test before removing the unused connection. Public copy of the October 15 notice · Connector documentation.
Word Online (Business): MC1508992 was published October 15 but specifies October 14 as the change date. It flags use of CreateWordFileWithContent URLs for unauthenticated downloads. Use authenticated file-content retrieval or appropriate sharing links. The standard Populate Word Template action returns binary content; do not assume every Word flow breaks. Public notice copy · Word connector reference.
The notice expects no breaking changes for GetSchema, GetFile or ConvertFile/GetFilePDF. Start with integrations passing a returned URL to an unauthenticated caller, then verify the final document handoff.
These notices are reasons to inspect the actual dependencies and delivery steps. They are not evidence that a particular customer system has failed.
10. Model deadlines, meeting memory and two quick updates
GitHub Copilot, November 16: Claude Opus 4.8, Opus 5 and GPT-5.6 Terra retire across Copilot experiences. Suggested replacements are Opus 5.5, or GPT-6.1 Sol/GPT-6 Luna for Terra. Individual GitHub Copilot subscribers on annual plans retain Opus 4.8. Check organization policies and saved selections. October 15 notice.
Codex, October 14: GPT-5.5 retired for ChatGPT sign-in. The API and API-key-authenticated Codex sessions are unaffected. This is separate from GitHub’s model lifecycle. OpenAI model documentation.
Teams meeting memory: When released, Facilitator will use it first; Copilot support is planned later. The notice’s rollout dates concern admin controls, with generation roughly four weeks afterward. Deleting the transcript does not automatically delete the meeting memory. Its default expiration is five years; Purview retention can override that expiration. Updated notice · Retention documentation.
GitHub in Teams and Slack: October 15 adds investigation and PR tracking across repositories in one conversation. The integrations remain public preview for paid Copilot plans, with connection, sandbox and permission requirements. Announcement · Teams requirements.
ChatGPT Voice: October 15 release notes announce GPT-Live-1.1 and GPT-Live-1.1 Quip, with more natural accents and additional voice options. Availability varies by account and region. OpenAI release notes.
Where teams can put this to work
There are practical starting points here: build an internal app in Studio or Cowork, capture a recurring deliverable as a skill, or give a shared business process an agent with its own account. Choose a clear owner, a defined task and an output the team can review.
For teams acting this week, I’d begin with the maintenance: find affected apps and connections, assign owners and check the billing settings. Then pick one new capability with a result you can verify. That gives the next experiment a useful business purpose.
Missed the previous edition? Read last week’s recap on named Copilot models, GPT-6.1 and Advanced Reasoning.
Leave a Reply