Your security team stores petabytes of telemetry and logs for compliance in Azure Blob Storage. Searching for that data means copying it somewhere else first, adding egress costs, latency, and compliance risk. That changes now.
Cribl Lake bring your own storage (BYOS) for Microsoft Azure is now available. Connect your existing Azure storage accounts directly to Cribl Lake, create datasets, route data from Cribl Stream, and instantly search data in place with Cribl Search, all without moving, duplicating, or rehydrating a single byte.
The result is a fully integrated, search-in-place experience that gives your organization more control over where data lives, how it’s secured, and how it’s managed.
Bring your own storage to Cribl Lake
Cribl Lake BYOS for Azure offers the flexibility to store telemetry in your Blob Storage while preserving the simple workflows and operational experience you expect from Cribl Lake.
That means you can:
Keep telemetry in your own Azure tenant - data never leaves your environment
Search data directly where it lives - Cribl Search queries your Blob Storage via federated engine with zero egress fees
Apply retention and governance policies through Cribl Lake - no separate Azure lifecycle policy management
Deploy across regions and environments with multiple storage locations mapped to different teams, compliance boundaries, or use cases
Reduce unnecessary data movement and associated costs that come with it
Rather than being forced to choose between control and usability, Cribl Lake BYOS delivers both.
Search data in place — no movement required
The biggest challenge with traditional data lake architectures is the operational overhead of moving or duplicating data before it can be analyzed. With BYOS, Cribl Search queries data directly in your Blob Storage Account through a federated search engine. No rehydration pipelines, no extra copies, no separate storage silos.
You can instantly investigate telemetry stored in Azure while continuing to use familiar Cribl workflows for dataset management and discovery.
For Azure-first organizations, that means faster investigations, fewer operational bottlenecks, and a simpler path to adopting a scalable lake architecture.
Built for enterprise control and governance
Many organizations have strict requirements around data locality, encryption, access controls, and retention. Cribl Lake BYOS was designed with those realities in mind:
Entra ID authentication - Authenticate with service principals. No static keys or long-lived SAS tokens required. Cribl never stores your Azure credentials.
Customer-managed encryption - Encrypt your data by default with Azure server-side keys or use the Azure Key Vault integration to manage your own keys.
Retention policies - Apply and manage retention through Cribl Lake
Role-based access controls - Leverage Cribl’s easy-to-use role-based access controls alongside Azure-native access controls
Data residency - Data stays entirely within your Azure environment and tenant
This approach gives security and platform teams stronger control over how telemetry is stored and protected while still enabling fast access for operational and investigative workflows.
Flexible architecture for modern telemetry environments
Telemetry environments are rarely centralized or static. Teams often need to support multiple business units, regions, compliance boundaries, or storage tiers.
BYOS supports this flexibility by allowing organizations to:
Multiple storage locations - Connect storage accounts across regions and environments
Dataset storage by use case - Route security data to one location, observability to another
Cost control - Store data into different storage classes to control costs for compliance retention
ARM template deployment - One-click infrastructure setup with Cribl-generated ARM templates for your Azure environment
Consistency across clouds - Already using BYOS on AWS? The Azure experience works the same way.
Whether organizations are centralizing security and IT telemetry, managing observability pipelines, or scaling long-term retention strategies, BYOS adapts to existing Azure investments and operating models.
Faster time to value
BYOS for Azure is designed to get you operational in minutes, not weeks. Guided workflows help you:
Connect Azure storage accounts with a Cribl-generated ARM template
Validate permissions and configuration during setup. Errors surface immediately, not after data starts flowing
Configure secure Entra ID access without manual credential management
Start creating searchable datasets in minutes
The onboarding experience is designed to reduce friction so you can focus on using your data rather than troubleshooting infrastructure.
See Cribl Docs for step-by-step instructions on setting up BYOS.
Available now
Cribl Lake BYOS for Azure is now available to Enterprise customers at 0.02 credits/GB – a fraction of what you'd spend on egress, rehydration pipelines, or duplicating data into another cloud. For more pricing details, see Cribl’s pricing page.
Keep your telemetry in Azure and get the full value of Cribl Lake. Enjoy you-controlled storage, Azure-aligned security and retention, and searchable data through Cribl Search, all with a fast and guided setup experience.
