29 October 2026 · PKI & AI briefing
Application certificate trust and the machinery around AI agents are today’s focus. Solace has published additional product fixes, while Microsoft has introduced a managed agent runtime in Foundry. Both developments leave operators with concrete work: identify the component that needs updating, and establish which permissions and recovery behavior an application actually has.
PKI: Solace reports more application trust-store fixes
Solace’s advisory, updated on 28 October, says its Broker and Appliance Terraform Providers v1.4.0 and Nisshi v0.8.1 were released that day to address the certificate-trust issue described there. It also lists Agent Mesh v2.455.0 as available. Its Broker MCP update remains a target for 29 October, rather than a confirmed release. The advisory’s overall status remains active with product updates pending. Read Solace’s product advisory and version-specific status.
Practical reading: Treat this as a component inventory problem. Record the product, installed version, deployment location and supported update path. An agent deployment may include a broker, client libraries, a desktop application and infrastructure tooling; do not infer that updating one of them updates the others. Match each installed component to its vendor notice. Keep normal TLS certificate verification enabled, and validate required outbound connections after a supported update. A release date in an advisory does not establish that your own deployment has received the fix.
AI: Microsoft brings its Copilot harness to Foundry
Microsoft’s 28 October announcement describes a shared Copilot harness: the execution layer that coordinates a model’s context, tools and actions. Microsoft says it runs the agent loop and sandbox, while developers supply instructions, tools and model choice. This is a change in how an application can be assembled, not a new model announcement. Read Microsoft’s platform announcement.
The accompanying Foundry post identifies the harness release as public preview. It describes reusable skills, connected tools with configured authentication and approvals, and bounded delegation to subagents. It also says harness-runtime charges begin on 1 December 2026; model inference, separately billed tools and connected services can still incur charges before then. A preview of the runtime is not a free end-to-end workload. Read the Foundry release and billing scope.
Limits worth checking: Microsoft’s setup documentation requires a new prompt agent for the initial preview; switching an existing agent’s harness is not supported. It also distinguishes the creator’s permissions from the agent identity’s permissions. The managed sandbox is not a durable output store, so important outputs need durable storage. Read the harness setup and identity requirements.
Recovery still needs application-level design
The same Foundry release post announces general availability of long-running hosted-agent resilience this week. At this source check, the linked Learn reference still carries a preview label and an August update date. Treat the announcement and the reference’s status label separately, and confirm support for the exact API path before a production rollout.
The technical reference explains that recovery can re-enter a handler from its beginning; it does not restore the application’s in-memory state. Application code must preserve meaningful progress and prevent duplicate external effects. For example, in a hypothetical ticket-creation workflow, a restart should check a stable operation identifier before creating a second ticket. Reconnecting to an output stream is not proof that every business action completed exactly once.
What to check next
- Certificate operators: reconcile installed components against confirmed fixes, keeping planned releases marked as pending.
- Agent developers: review tool permissions and approval points, then test interruption and restart behavior with non-sensitive test data.
- Deployment owners: verify release status, regional availability and billing scope before enabling a new service.
Source check: 29 October 2026, 07:30 UTC. This is the briefing date, not the date of every underlying event. Solace’s page labels its update “28 October, 2:30 PM EST”; no exact UTC conversion is assumed. Microsoft’s announcements are dated 28 October. Documentation is used for implementation context, not presented as newly published news. This briefing reports vendor statements and offers editorial guidance; it does not claim independent product testing or measured performance.