azure-memory-state

Select Azure-native storage backends for durable agent memory management.

Updated May 24, 2026
One-click install
npx skills add https://github.com/FVossebeld/agent-skills-for-context-engineering --skill azure-memory-state
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-memory-state
Source: https://github.com/FVossebeld/agent-skills-for-context-engineering/tree/main/azure/skills/azure-memory-state
Command: npx skills add https://github.com/FVossebeld/agent-skills-for-context-engineering --skill azure-memory-state

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides the design and implementation of Microsoft-native agent memory and state management, enabling durable storage and organized retrieval across prompts, tool outputs, and session lifecycles.

Core Features & Use Cases

  • Choose and configure Azure-native memory stores (Cosmos DB, Blob/ADLS, Redis) to meet latency, scoping, and audit requirements.
  • Model working memory, session state, episodic history, and semantic memory with clear boundaries and access controls.
  • Support append-only logs and audit trails for governance and traceability.
  • Partition memory by tenant, user, and context to prevent cross-user leakage and ensure compliance.
  • Provide guidelines for memory clean-up, privacy, and lifecycle management.

Quick Start

Configure an Azure-native memory plan by selecting Cosmos DB for session state, Blob Storage for scratchpads, and Redis for fast caching, then define memory types and retention rules for your agent.

Frequently Asked Questions about azure-memory-state

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage durable agent memory and state across Azure services?

Partition agent memory by tenant, user, and context to prevent cross-user leakage. Apply access controls and configure append-only logs to ensure governance, compliance, and traceability across your Azure storage backends.

What's the best way to choose between Cosmos DB, Blob Storage, and Redis for agent state?

Model semantic memory and episodic history with clear boundaries using Azure-native stores. Define memory clean-up, privacy rules, and lifecycle management to maintain organized retrieval and governance across session lifecycles.

How do I partition agent memory by tenant and user in Azure to ensure compliance?

Model semantic memory and episodic history with clear boundaries using Azure-native stores. Define memory clean-up, privacy rules, and lifecycle management to maintain organized retrieval and governance across session lifecycles.

Does Azure Blob Storage and ADLS support append-only audit logs for agent history?

Configure retention policies and memory clean-up rules within Blob Storage to manage lifecycle and privacy. This approach ensures durable storage while maintaining organized retrieval of agent scratchpads and audit logs.

When should I use Redis versus Cosmos DB for working memory in AI agents?

Apply retention policies and lifecycle management to both Redis and Cosmos DB stores to ensure memory clean-up and privacy. This distinction helps model clear boundaries for agent state and semantic memory retrieval.

How do I configure memory retention policies and clean-up for Azure agent state?

Partition memory by tenant, user, and context when applying retention rules to satisfy governance and compliance requirements. This approach guarantees that append-only logs and audit trails remain traceable across session lifecycles.