This insight was synthesized by AI from public community discussions. We do not display original user posts or comments verbatim—all content has been rewritten and aggregated. Verify before acting on it.
Custom Terraform Provider for Azure AD Table Storage Auth
A community/enterprise Terraform provider that cleanly separates Azure Storage Table entity management from ACL operations, enabling full Azure AD authentication while gracefully handling the ACL limitation. Targets DevOps teams who must disable shared key auth for security compliance but are blocked by the official provider's limitations.
Why this matters
You manage Azure infrastructure with Terraform and your security team has mandated elimination of shared key authentication from all storage accounts. For Blob and Queue storage, the official AzureRM provider already supports Azure AD authentication. But Storage Tables are stuck — the provider's table resource tries to read ACLs even when you haven't configured them, and those ACL operations don't support AAD. You're caught between compliance requirements and tooling limitations. Some team members suggest splitting ACL management into a separate resource, but the migration paths between auth modes have unvalidated edge cases. You end up maintaining manual scripts alongside Terraform just for table operations, creating drift and audit gaps.
- · Built for DevOps and platform engineering teams at Azure-using organizations who are mandated by security policies to eliminate shared key authentication from storage accounts and use Terraform for infrastructure management.
- · Most likely monetization: Open-source core with paid enterprise tier (support, SLA, additional policy modules).
The Pain · Narrative
You manage Azure infrastructure with Terraform and your security team has mandated elimination of shared key authentication from all storage accounts. For Blob and Queue storage, the official AzureRM provider already supports Azure AD authentication. But Storage Tables are stuck — the provider's table resource tries to read ACLs even when you haven't configured them, and those ACL operations don't support AAD. You're caught between compliance requirements and tooling limitations. Some team members suggest splitting ACL management into a separate resource, but the migration paths between auth modes have unvalidated edge cases. You end up maintaining manual scripts alongside Terraform just for table operations, creating drift and audit gaps.
Score Breakdown
Market Signal
Go-to-Market
Senior DevOps engineers and platform team leads at mid-to-large enterprises using Azure Table Storage with active security compliance mandates (SOC2, CIS, or internal policies) requiring keyless authentication
~5,000-10,000 active teams globally who use both Azure Table Storage and Terraform with security compliance requirements
GitHub open-source release with targeted outreach to Azure/Terraform community channels and DevOps security newsletters
$99/month per organization for enterprise tier (support, migration tooling, policy modules)
500 GitHub stars and 20 enterprise tier signups within 60 days of launch
MVP Scope · 1–2 weeks
- Research Azure Table Storage REST API AAD auth capabilities and ACL operation limitations across API versions
- Design provider architecture with separate resources for table entities (AAD) and table ACLs (key fallback)
- Set up Go development environment with Terraform Plugin SDK and Azure SDK for Go
- Build minimal provider with a single resource for table entities using AAD authentication
- Write acceptance tests validating table entity CRUD operations with AAD auth
- Implement table ACL resource with shared key fallback and clear documentation of the auth split
- Add migration validation logic that checks current auth mode and ACL state before allowing transitions
- Build import capability for existing AzureRM table resources to reduce switching friction
- Create documentation site explaining the auth architecture and migration paths
- Publish alpha release to Terraform Registry and announce in Azure/Terraform communities
Differentiation
Why This Might Fail
Self-rebuttal — the most important trust signal
- 1HashiCorp is actively working on this exact feature (PRs referenced in the discussion) and could ship official support within months, eliminating the need for a custom provider
- 2The addressable market is extremely narrow — only teams using Azure Table Storage (not Cosmos DB Table API), with Terraform, and with active keyless auth mandates may number in the low thousands
- 3Open-source Terraform providers have weak monetization paths; users expect community providers to be free, making it hard to convert to paying enterprise customers
Evidence Summary
How AI synthesized this insight — no verbatim quotes
Approximately 8 commenters in this discussion express frustration with the lack of Azure AD authentication support for Storage Tables in the Terraform AzureRM provider. The core blocker is that ACL operations for tables don't support AAD, and the provider architecture requires reading ACLs regardless of configuration. Multiple users highlight that the primary motivation is disabling shared key auth for security compliance. One commenter proposes splitting ACLs into a dedicated resource, and another discusses the complexity of migration paths between auth modes. The discussion reveals both a clear technical gap and active community engagement, though no explicit willingness to pay signals.
Action Plan
Validate this opportunity before writing code
Recommended Next Step
Validate
Promising signals, but needs confirmation. Create a landing page, collect email sign-ups, then decide.
Landing Page Copy Kit
Ready-to-paste copy based on real Reddit community language — no editing required
Headline
Custom Terraform Provider for Azure AD Table Storage Auth
Sub-headline
A community/enterprise Terraform provider that cleanly separates Azure Storage Table entity management from ACL operations, enabling full Azure AD authentication while gracefully handling the ACL limitation. Targets DevOps teams who must disable shared key auth for security compliance but are blocked by the official provider's limitations.
Who It's For
For DevOps and platform engineering teams at Azure-using organizations who are mandated by security policies to eliminate shared key authentication from storage accounts and use Terraform for infrastructure management
Feature List
✓ Terraform provider with separate resources for table entities (AAD auth) and table ACLs (shared key fallback) ✓ Automatic detection and graceful handling of auth mode transitions ✓ Policy validation that warns when shared key auth remains enabled for ACL operations ✓ Migration assistant that validates ACL state safety before auth mode switches ✓ Compatibility layer with existing AzureRM provider table resources for easy adoption
Where to Validate
Share your landing page in r/GitHub · hashicorp/terraform-provider-azurerm — that's exactly where these pain points were discovered.
Sign up to unlock full deep analysis
GTM, MVP scope, why-it-might-fail, ActionPlan Copy Kit. Free signup grants 10 detail views/month.
Other opportunities in the same theme
Auto-clustered by AI from related discussions